I'm on a rooted Nexus 7 2013 wifi only with twrp recovery installed. I'm currently running stock android 4.3 and wish to update to 4.4.2. I had originally held off updating but now want to do so. Here's what happened.
1. I first went to Settings /about phone /System update and tried to update. That failed repeatedly even though I have unmodified stock rom. (now even download fails though earlier it has downloaded successfully and the file is somewhere on the tablet).
2. So I next went to
http://forum.xda-developers.com/showthread.php?t=2380113
And downloaded the ota update zip file (JSS15R to kot49h). Then went to my Twrp 2.6.3.0 recovery screen and tried flashing the zip file from there. It failed. I didn't wipe anything first because I didn't want to lose my data.
So I'm stuck. Can I update without losing my data?
Thanks
Jeff
are you using supersu 1.69 or older for root?
if yes you must disable ota survival in supersu settings and re-root after update.
and normaly you can ota update without wipe your data, but i dont want to assure that.
dusu84 said:
are you using supersu 1.69 or older for root?
if yes you must disable ota survival in supersu settings and re-root after update.
and normaly you can ota update without wipe your data, but i dont want to assure that.
Click to expand...
Click to collapse
Thanks for offering to help.
I'm running supersu 1.91. I went into its settings and found it had "survival mode" selected, so I unselected it. Then booted into twrp screen and tried to flash the downloaded ota zip file again. No luck. Here's the fail screen image.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Apparently some twrp versions have trouble flashing. I would like to update twrp but don't know how. No update button and can't find anything on the twrp website about updating.
because of the unexpected content in app_process... have you maybe running xposed framework?
then flash xposed_disabler zip first.
dusu84 said:
because of the unexpected content in app_process... have you maybe running xposed framework?
then flash xposed_disabler zip first.
Click to expand...
Click to collapse
Aha! You're a genius! I think we're getting somewhere now. Yes, I have Xposed, GravityBox, and XPrivacy installed and running.
Should I uninstall them?
Where do I find xposed_disabler zip?
I'll start searching for xposed_disabler but would appreciate any pointers.
Also, this may have nothing to do with this, but when I searched for key loggers I got this message (I ignored} :
you should see the xposed disabler recovery zip in your recovery on sdcard. this zip should be copied to your sd card when you install xposed framework. when the zip isnt there you can also download this in the original xposed thread. (im not allowed to share links because im new at xda).
because the message by search for key loggers... i dont know. sorry.
Anderson2 said:
And downloaded the ota update zip file (JSS15R to kot49h). Then went to my Twrp 2.6.3.0 recovery screen and tried flashing the zip file from there. It failed. I didn't wipe anything first because I didn't want to lose my data.
So I'm stuck. Can I update without losing my data?
Thanks
Jeff
Click to expand...
Click to collapse
Jeff, your best bet really is to just flash back to stock, then just flash recovery and root in one step using the Nexus 7 Toolbox. This whole process will take you about 15 minutes and you will have a solid foundation.
The first reaction of many people to a suggestion like that is "what about my data?" My answer is to think carefully about what data would actually be affected by wiping your device. If you have things set up normally on Android there is very little that won't be put back on your device after going through the initial setup again. All your apps will reinstall from Google Play, contacts and email will sync, settings will sync... Even your WiFi settings. Wallpapers will sync, and pictures and videos will sync if you have one or more of the various accounts set up that do that. The only things missing will be things that you downloaded from the web and any sideloaded apps. That probably isn't more than a handful of apps and/or PDF documents... And only if they are stored on internal memory vs. Virtual SD card. If you have any stragglers, you can use Titanium Backup for ROOT, but I don't even find that necessary.
Just make sure you have your Google account sync set to on, and whatever other apps you use sync for like SkyDrive, DropBox, and any other things that get their names from two capitalized words mashed together.
Mike
Sent from my Nexus 7 using Tapatalk
Ah, but I am one of those who avoid syncing and trusting Google with my data.
Anderson2 said:
Where do I find xposed_disabler zip?
Click to expand...
Click to collapse
hey, have you find the xposed disabler recovery zip and whether have you flashed it?
is the ota update now working?
greets
EDIT: the xposed disabler recovery zip must be directly on your sd card... not in a specifically folder.
dusu84 said:
hey, have you find the xposed disabler recovery zip and whether have you flashed it?
is the ota update now working?
greets
EDIT: the xposed disabler recovery zip must be directly on your sd card... not in a specifically folder.
Click to expand...
Click to collapse
Not, I didn't find the xposed disabler recovery zip. At least not from a site I can trust. I searched my Nexus 7 contents and didn't find a xposed disabler recovery zip.
What I did do was uninstall Xposed, rebooted, and now Settings /about phone /system update did download the 4.4.2 system update - but didn't keep the file (at least not in the cache folder) because "verification failed". So I'm back where I was.
I also have Avast Mobile Security installed and it has a stealth anti-theft component that protects itself from tampering. I wonder if it might be blocking things. I might temporarily uninstall Avast to see.
One more thought: the Nexus 7 apparently has a way of booting into "safe mode". I don't know how to get into it, but perhaps the Android update might succeed when in safe mode.
This is really a pain! I can't believe I'm the only one facing this problem.
Anderson2 said:
Not, I didn't find the xposed disabler recovery zip. At least not from a site I can trust. I searched my Nexus 7 contents and didn't find a xposed disabler recovery zip.
What I did do was uninstall Xposed, rebooted, and now Settings /about phone /system update did download the 4.4.2 system update - but didn't keep the file (at least not in the cache folder) because "verification failed". So I'm back where I was.
I also have Avast Mobile Security installed and it has a stealth anti-theft component that protects itself from tampering. I wonder if it might be blocking things. I might temporarily uninstall Avast to see.
One more thought: the Nexus 7 apparently has a way of booting into "safe mode". I don't know how to get into it, but perhaps the Android update might succeed when in safe mode.
This is really a pain! I can't believe I'm the only one facing this problem.
Click to expand...
Click to collapse
ok strange...
btw. what the xposed disabler recovery zip does is copying /system/bin/app_process.orig back to /system/bin/app_process ... and in system/bin/app_process you have the unexpected contents according to your image what you have posted.
the xposed disabler recovery zip can you download from here: http://forum.xda-developers.com/attachment.php?attachmentid=2314045&d=1381353218
but the problem with the app_process should done with uninstall xposed i think. after you uninstalled xposed, have you try to flash the ota zip again?
you come into safe mode by holding "shut down" after you press on/off button.
dusu84 said:
ok strange...
btw. what the xposed disabler recovery zip does is copying /system/bin/app_process.orig back to /system/bin/app_process ... and in system/bin/app_process you have the unexpected contents according to your image what you have posted.
the xposed disabler recovery zip can you download from here: http://forum.xda-developers.com/attachment.php?attachmentid=2314045&d=1381353218
but the problem with the app_process should done with uninstall xposed i think. after you uninstalled xposed, have you try to flash the ota zip again?
you come into safe mode by holding "shut down" after you press on/off button.
Click to expand...
Click to collapse
Thanks for hanging with me.
It gets stranger still. Safe mode method doesn't work for me. When the power off popup comes on, if I short press or long press, it doesn't bring up the safe mode option.
I uninstalled Xposed and rebooted. Then I went back to my Twrp recovery screen and tried to reflash the ota zip again. It failed again but with an interesting error message about debuggerd contents.
And in case I'm missing something here is my tablet information.
Anderson2 said:
Thanks for hanging with me.
It gets stranger still. Safe mode method doesn't work for me. When the power off popup comes on, if I short press or long press, it doesn't bring up the safe mode option.
I uninstalled Xposed and rebooted. Then I went back to my Twrp recovery screen and tried to reflash the ota zip again. It failed again but with an interesting error message about debuggerd contents.
Click to expand...
Click to collapse
im sure we will make it
i hope this can solved the debuggerd problem: http://forum.xda-developers.com/attachment.php?attachmentid=2307599&d=1381111112
download it and flash it with twrp. perhaps a reeboot into recovery. then try to flash the ota update zip again.
dusu84 said:
im sure we will make it
i hope this can solved the debuggerd problem: http://forum.xda-developers.com/attachment.php?attachmentid=2307599&d=1381111112
download it and flash it with twrp. perhaps a reeboot into recovery. then try to flash the ota update zip again.
Click to expand...
Click to collapse
Here's what I did that finally worked. (sort of cheated)
1. Made a nandroid backup of the current state.
2. I had previously restored to an earlier nandroid and then tried to update again various ways. No success.
3. Finally, I restored a nandroid I made when I first rooted right after I bought the tablet. From this state the tablet updated itself automatically to 4.4.2!
My next task is to check my data to see if it went back to that early days. If so, maybe I can restore just data from the recent nandroid. Otherwise, I'll just work around it.
So far data and apps appear OK. How lucky can I be? Shows the advantage of making an early nandroid when tablet is still new.
(big sigh of relief)
Anderson2 said:
Here's what I did that finally worked. (sort of cheated)
1. Made a nandroid backup of the current state.
2. I had previously restored to an earlier nandroid and then tried to update again various ways. No success.
3. Finally, I restored a nandroid I made when I first rooted right after I bought the tablet. From this state the tablet updated itself automatically to 4.4.2!
My next task is to check my data to see if it went back to that early days. If so, maybe I can restore just data from the recent nandroid. Otherwise, I'll just work around it.
Click to expand...
Click to collapse
Anderson2 said:
So far data and apps appear OK. How lucky can I be? Shows the advantage of making an early nandroid when tablet is still new.
(big sigh of relief)
Click to expand...
Click to collapse
perfect its solved :good:
still have a nice day with your kitkat nexus!
Thank you.
One problem remains. I tried to do a new nandroid and discovered that when I went to the recovery screen instead of twrp, all it showed was open Android with red exclamation and something about "no command".
I think it deleted my Twrp, (or my Twrp was not compatible with kitkat). I don't recall how to reinstate twrp. Will try to find out. Rom Toolbox tells me there is no available recovery for my device, which must be wrong.
EDIT reinstalled twrp using goo manager. So I'm good!
I didn't read through this whole thread so excuse my response if you already found your answer.. I think if you have twrp flashed then the ota is going to fail every time. Reflash the stock recovery and run the ota update.
Sent from my Nexus 7 using Tapatalk
If I were in your shoes, I would just flash the factory KitKat ROM. You can download it here: https://developers.google.com/android/nexus/images
If you edit flash-all.bat (windows) or flash-all.sh (Linux) you can flash it without wiping your data. I would not bother though, I would let it while my data and restore it through synching or through Titanium Backup
Sent from my Nexus 7 using XDA Premium HD app
Related
Can someone please help me? I'm worried my phone may be really screwed up.
I recently rooted my phone using the instructions from this forum and everything went great. I had no problems for a couple days.
Then I installed Titanium Backup and backed up all my apps.
Then I deleted some apps, like Allshare, Dropbox and other bloatware. I still had no problems.
Then I saw that an OTA update was available. I read somewhere that the update can cause problems if stock apps are removed, so I went into Titanium Backup to restore the apps I had deleted. This is where things started to go wrong. When I tried to restore apps, Titanium Backup was hanging and I had to restart the phone. After Dropbox wouldn't restore, I restarted the phone and I'm stuck in a reboot cycle. The phone restarts, I see the usual boot up screens, I see my lock screen, there's a circled i with a cross through it in the notification bar and I can't unlock the phone. How can I get access to my phone back? I'm really upset that this has happened. I thought I was being very careful and this is exactly the kind of thing I was trying to prevent from happening.
Please help.
BraveRobot said:
Can someone please help me? I'm worried my phone may be really screwed up.
I recently rooted my phone using the instructions from this forum and everything went great. I had no problems for a couple days.
Then I installed Titanium Backup and backed up all my apps.
Then I deleted some apps, like Allshare, Dropbox and other bloatware. I still had no problems.
Then I saw that an OTA update was available. I read somewhere that the update can cause problems if stock apps are removed, so I went into Titanium Backup to restore the apps I had deleted. This is where things started to go wrong. When I tried to restore apps, Titanium Backup was hanging and I had to restart the phone. After Dropbox wouldn't restore, I restarted the phone and I'm stuck in a reboot cycle. The phone restarts, I see the usual boot up screens, I see my lock screen, there's a circled i with a cross through it in the notification bar and I can't unlock the phone. How can I get access to my phone back? I'm really upset that this has happened. I thought I was being very careful and this is exactly the kind of thing I was trying to prevent from happening.
Please help.
Click to expand...
Click to collapse
Be Brave, little Robot.
From what you've described, you're not out of luck here. I seriously doubt you've hard-bricked your phone. In order for me to help you, I need you to verify the following:
You can get into your Recovery (either CWM or TWRP).
You can get into download mode.
If these two are true, you're in luck. Below, I've copied a post I made yesterday helping someone else through a similar situation. Some things may be a bit different, but for the most part, it'll help you through you stuff.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Ok, now that we've identified what's wrong with your phone, we can now help solve it!
Solution/Fixes
Are you able to get into a custom Recovery? If not, you need to use Odin and follow The Rooting Guide to get back to a custom recovery (I recommend TWRP, but CWM is just as good).
Next, you want to download a Rom and put it on your device. I'd recommend (just for now), to get Freeza's stock TW Rom.
Now, before you try to flash this Rom, you'll have to wipe. In order to get rid of the FCs, you'll have to at least wipe System. I'd recommend a full wipe of your Internal SD Card (after backing up anything you want to save), but it's not technically necessary. Afterwards, you can wipe data and cache/dalvik cache.
Then you can flash your Rom. It seems like you know how to do this, but in case you don't, I have previously posted directions over here.
Hope this helps!
Click to expand...
Click to collapse
Be Brave, little Robot.
Click to expand...
Click to collapse
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
BraveRobot said:
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
Click to expand...
Click to collapse
I've always given my instructions in TWRP, but the options/settings should be very similar in CWM. In the quoted post below, there are instructions on how to flash a new Rom.
For your situation, I'd recommend wiping system in step 4 below:
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
I'm going home from work for the night. I'll try to keep up with the thread, but if you have any questions, look over at this thread, I think Miguelcoo1 asked just about every question that can be asked, haha (he's a good guy, I'm just giving him a hard time).
In CWM recovery it says wipe data/factory reset. Is that what I want?
BraveRobot said:
In CWM recovery it says wipe data/factory reset. Is that what I want?
Click to expand...
Click to collapse
Is there an advanced option? Factory rest only wipes Data and Cache, if I recall correctly.
Here are my options:
- reboot system now
- install zip from sdcard
- wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
In advanced, here are my options:
- reboot recovery
- wipe dalvik cache
- wipe battery stats
- report error
- key test
- show log
- fix permissions
- go back
By the way, I have to wait 5 minutes between posts because my account is new. (How do I get rid of that?)
BraveRobot said:
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
Click to expand...
Click to collapse
Here's the guide for CWM
Ok, it sounds like you're on an old version of cwm. In my Sig, click on flashable and you can flash the newest version of cwm. Then you should have the option to wipe system.
Sent from my SPH-L710 using xda app-developers app
topherk said:
Ok, it sounds like you're on an old version of cwm. In my Sig, click on flashable and you can flash the newest version of cwm. Then you should have the option to wipe system.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Alright. I don't mean to sound ungrateful, but this is all very new to me. How do I flash the new CWM onto my phone?
g_money said:
Here's the guide for CWM
Click to expand...
Click to collapse
Oh! from g_money's guide, under "Mounts and Storage" there should be an option to wipe system. Now be aware, wiping system is wiping your Rom, so you won't be able to boot your phone back up to anything besides recovery and download modes (which is no different than you can do right now anyways).
topherk said:
Oh! from g_money's guide, under "Mounts and Storage" there should be an option to wipe system. Now be aware, wiping system is wiping your Rom, so you won't be able to boot your phone back up to anything besides recovery and download modes (which is no different than you can do right now anyways).
Click to expand...
Click to collapse
I am so freaking lost.
What is the end-game here? Am I trying to wipe system and then reflash a new rom? And if so, where does that rom come from? Am I basically starting over like in the root guide using Odin?
BraveRobot said:
I am so freaking lost.
What is the end-game here? Am I trying to wipe system and then reflash a new rom? And if so, where does that rom come from? Am I basically starting over like in the root guide using Odin?
Click to expand...
Click to collapse
If you go into recovery/backup and restore/restore, do you have any backups listed?
g_money said:
If you go into recovery/backup and restore/restore, do you have any backups listed?
Click to expand...
Click to collapse
It says "No files found."
So I guess I didn't back anything up?
Could someone clue me into what I'm trying to do?
Am I trying to flash a new rom or do I need to do something else?
Sorry for being a noob. I'm trying to learn about this stuff, but it's a little difficult. I really appreciate you guys helping me.
BraveRobot said:
Could someone clue me into what I'm trying to do?
Am I trying to flash a new rom or do I need to do something else?
Sorry for being a noob. I'm trying to learn about this stuff, but it's a little difficult. I really appreciate you guys helping me.
Click to expand...
Click to collapse
Yes the instructions topherk gave you where to wipe and flash freezas stock rom. He gave you the links. Make sure you have the rom on your sd card ready to flash.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Ok, that worked. Thanks guys! Everything seems to be back working again.
Does anyone have any idea went wrong with my Titanium Backup? It's kind of useless if it's going to crash my phone when I use it for the main thing it was designed for.
Edit: Actually, I may try to return my phone to stock. Can anyone recommend a guide to un-doing root access and putting everything back completely stock? I think that's probably better for someone with my level of knowledge.
No I think your ok. At some point you restored one bad data or something. The only thing you should ever restore are apps you downloaded from the play store. Never restore any system apps. And samsung apps (bloat) you don't want to delete you just want to freeze.
Transmitted with a portable device using Xparent Blue Tapatalk 2
BraveRobot said:
Ok, that worked. Thanks guys! Everything seems to be back working again.
Click to expand...
Click to collapse
Good to hear
BraveRobot said:
Does anyone have any idea went wrong with my Titanium Backup? It's kind of useless if it's going to crash my phone when I use it for the main thing it was designed for.
Click to expand...
Click to collapse
Reread topherk's previous posts. It's a great guide for understanding Titanium. And Titanium is an awesome program.
BraveRobot said:
Edit: Actually, I may try to return my phone to stock. Can anyone recommend a guide to un-doing root access and putting everything back completely stock? I think that's probably better for someone with my level of knowledge.
Click to expand...
Click to collapse
LOL. I hear ya. But if your phone's working, it's all good right? QBking77 has a video on unrooting here. After what you've been through, you may want to stick around and learn even more?
g_money said:
Good to hear
Reread topherk's previous posts. It's a great guide for understanding Titanium. And Titanium is an awesome program.
LOL. I hear ya. But if your phone's working, it's all good right? QBking77 has a video on unrooting here. After what you've been through, you may want to stick around and learn even more?
Click to expand...
Click to collapse
Yeah, I guess I'll keep it rooted, but I'm going to give things a few days rest after that scare. I need my phone! Maybe I'll come back and mess with it more later.
Short version: Flashed superuser.zip and lost root access but the phone appears to be ok. How can I get it back
Received my S3 from a Sprint MVNO already rooted w/:
L710 VPUND8 + PhilZ Touch 6, CWM Base version v6.0.4.5, "d2spr"
But with no Superuser App installed, from what I read, I thought I needed one to act as a gatekeeper.
Read the Google play descriptions for Superuser-ClockworkMod and SuperSU-Chainfire, both seem to warn about installing new/or upgrading over a pre/existing One. I tried both they seem to install but give the 'Update SU Binaries" warning. At that point I canceled an uninstalled.
Looked on my phone and saw a empty ClockworkMod file. Went back installed Superuser and followed the instructions to updated SU binaries eg., flash from recovery superuser.zip, rebooted checked for root and it was gone. And what I did, could not be undone (no uninstall, not by
factory reset, although Noid might have been helpful?) Clearly I did know what I was doing, looking back I have some idea, but my eagerness
got the best of my prudence. While clearly I do not deserve Root (or should of had it with only 2 months of Android experience) but I miss it
already. Is there any way I as a noob can restore it, but this time with a Super User App (uninstallable) for peace of mind?
I think I can "now" outline "most" of my mistakes along the way if that is helpful, but I assume you already know.
****SOLUTION***** provided by "bilgerryan" Boot into Phliz recovery select re-root system. . .reboot. . .done, got root!
If I use these instructions to re-root: (honai-android.blogspot.com/2014/05/how-to-root-galaxy-s3-sprint-sph-l710)
Will I still have:
1. The Stock Sprint KitKat?
2. The same Recovery - PhilZ?
3. All my Providers custom Apps?
4. All my downloaded Apps/Data?
5. My activation with my Provider?
Will it fix:
1. My SuperUser/SU Binaries issue?
What if anything will change? (SuperSU vs SuperUser)
What do you think my success rate is?
when you tried to update the binary how did you try to install it with the "normal" or "CWM/TWRP" one in the SuperSU app?
6th_Hokage said:
when you tried to update the binary how did you try to install it with the "normal" or "CWM/TWRP" one in the SuperSU app?
Click to expand...
Click to collapse
I did not try to update the SU binaries in the SuperSU app only in the Superuser app and when I lost root I thought I should stop and do more research. Not sure what you mean by "normal" this being my first time.
noknot said:
I did not try to update the SU binaries in the SuperSU app only in the Superuser app and when I lost root I thought I should stop and do more research. Not sure what you mean by "normal" this being my first time.
Click to expand...
Click to collapse
"Normal" Is the choice most of use it won't auto boot you into the recovery and if your using Philz Touch recovery it has a rooting option in the Philz settings section
6th_Hokage said:
"Normal" Is the choice most of use it won't auto boot you into the recovery and if your using Philz Touch recovery it has a rooting option in the Philz settings section
Click to expand...
Click to collapse
Thanks good to know, I did not look at the menu options in SuperSU before I canceled and uninstalled. Can I now installed SuperSU app via Google play, even with Superuser being (a system app?) uninstallable?
noknot said:
Thanks good to know, I did not look at the menu options in SuperSU before I canceled and uninstalled. Can I now installed SuperSU app via Google play, even with Superuser being (a system app?) uninstallable?
Click to expand...
Click to collapse
well yes you can but you would have to use Root Browser to delete Superuser app then install SuperSU by chainfire
Didn't need to remove my crapped out version of supersu (though ymmv) and couldn't Uninstall it.
Flashed this version thru philz:
SuperSU (zip)
http://download.chainfire.eu/396/SuperSU/
Was then able to update supersu binaries through the playstore...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
6th_Hokage said:
well yes you can but you would have to use Root Browser to delete Superuser app then install SuperSU by chainfire
Click to expand...
Click to collapse
Does that mean I would need to re-root first? Do you have any easier (more noob fool proof) suggestions?
Thanks
g_money said:
Didn't need to remove my crapped out version of supersu (though ymmv) and couldn't Uninstall it.
Flashed this version thru philz:
SuperSU (zip)
http://download.chainfire.eu/396/SuperSU/
Was then able to update supersu binaries through the playstore...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Is your superSU now with your downloaded (and uninstallable) apps or still uninstallable?
noknot said:
Is your superSU now with your downloaded (and uninstallable) apps or still uninstallable?
Click to expand...
Click to collapse
Most flashable zip apps become uninstallable but you can disable them through app manager settings....I thought you still had root sorry for the non-noob fix....and if you just download a root app from the play store you can still uninstall it
noknot said:
Is your superSU now with your downloaded (and uninstallable) apps or still uninstallable?
Click to expand...
Click to collapse
Once I installed the correct file and updated my binaries supersu became "uninstallable"
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
Once I installed the correct file and updated my binaries supersu became "uninstallable"
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Sorry I read my question and it was not at all intelligible, what I was trying to ask you was:
1. Is your supersu app now just like any market app and have an option to uninstall?
And
2. Before your final flash was it a "system app" with only the option to turn off not uninstall and not with your other downloaded apps?
trying to find out if the re-flash removed the first one or just wrote over it.
6th_Hokage said:
Most flashable zip apps become uninstallable but you can disable them through app manager settings....I thought you still had root sorry for the non-noob fix....and if you just download a root app from the play store you can still uninstall it
Click to expand...
Click to collapse
At the time I did not know I was flashing the app (I had already installed it from G play) I thought I was following the instructions to up date the out of date binaries.
Is the reason the factory reset did not return my phone "back to the way I got from the provider" is this flash permanently modified the ROM?
Had I make a Nandroid backup before I flashed would I have been able to restore back to the "way I got from the provider?"
If I am able to get a Nandroid from the provider could I also restore it?
Sorry for all the questions, 6th_Hokage. . . . .anybody?
noknot said:
At the time I did not know I was flashing the app (I had already installed it from G play) I thought I was following the instructions to up date the out of date binaries.
Is the reason the factory reset did not return my phone "back to the way I got from the provider" is this flash permanently modified the ROM?
Had I make a Nandroid backup before I flashed would I have been able to restore back to the "way I got from the provider?"
If I am able to get a Nandroid from the provider could I also restore it?
Sorry for all the questions, 6th_Hokage. . . . .anybody?
Click to expand...
Click to collapse
if you Odin back to stock you won't have root or the apps you added...and yes; before you do something major to the rom make a backup. In Philz recovery there are 2 factory wipe features 1. to just remove the user data [Google accounts, contacts, games and other play store apps (except for ones you made into system apps those will stay)] then there's 2. "full wipe new rom" (this one removes everything except for the recovery, bootloader and modem; you will just have to flash a new rom in the recovery before you reboot)
6th_Hokage said:
if you Odin back to stock you won't have root or the apps you added...and yes; before you do something major to the rom make a backup. In Philz recovery there are 2 factory wipe features 1. to just remove the user data [Google accounts, contacts, games and other play store apps (except for ones you made into system apps those will stay)] then there's 2. "full wipe new rom" (this one removes everything except for the recovery, bootloader and modem; you will just have to flash a new rom in the recovery before you reboot)
Click to expand...
Click to collapse
I saw you mention this in another thread:
"Philz has the option to root the phone in Philz settings tho.......so one doesn't need SuperSU zip just the recovery and to download SuperSU and BusyBox from the play store "
I have PhilZ Touch 6, CWM Base version v6.0.4.5, "d2spr" and don't see that option. Do I need to update to philz_touch_6.48.4-d2lte to see that option?
noknot said:
I saw you mention this in another thread:
"Philz has the option to root the phone in Philz settings tho.......so one doesn't need SuperSU zip just the recovery and to download SuperSU and BusyBox from the play store "
I have PhilZ Touch 6, CWM Base version v6.0.4.5, "d2spr" and don't see that option. Do I need to update to philz_touch_6.48.4-d2lte to see that option?
Click to expand...
Click to collapse
Yes.
Recovery FLASHABLE version now posted near the bottom of the first post of the 3Minit Battery Mod for Conquest-Singularity and both Stock ND8 and NDC with 1000+ animated battery icons..
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v7.0, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
6th_Hokage said:
if you Odin back to stock you won't have root or the apps you added...and yes; before you do something major to the rom make a backup. In Philz recovery there are 2 factory wipe features 1. to just remove the user data [Google accounts, contacts, games and other play store apps (except for ones you made into system apps those will stay)] then there's 2. "full wipe new rom" (this one removes everything except for the recovery, bootloader and modem; you will just have to flash a new rom in the recovery before you reboot)
Click to expand...
Click to collapse
So by flashing the superuser.zip from Philz recovery I changed the ROM? So I no longer have L710 VPUND8 ?
x2
noknot said:
xx
Click to expand...
Click to collapse
roirraW "edor" ehT said:
Yes.
Recovery FLASHABLE version now posted near the bottom of the first post of the 3Minit Battery Mod for Conquest-Singularity and both Stock ND8 and NDC with 1000+ animated battery icons..
[BATTERY] Plasma Battery! ??? & wickeddecimalbarwide_colors
Charging still shot
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Conquest: Singularity v7.0, Ktoonsez' latest kernel and the latest Philz Touch Recovery.
Click to expand...
Click to collapse
Should I update Philz 1st, before I try to restore stock L710 VPUND8?
I was running rooted stock version of kit kat. Yesterday afternoon I had Google Music running while doing housework when suddenly the music stopped. I checked the phone and the screen was black and would not turn on. Pulled the battery and then it stuck at the AT&T logo for 30+ minutes. I booted into CWM to perform a factory reset and potentially reinstall the ROM from the external sd card. The factory reset produced the following error.
Code:
--Wiping Data ...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
Fiddled around more with CWM to reset and try to fix. Now, upon reboot, it hands at the Samsung Galaxy Note II screen.
Any help on fixing this so it can at least limp along until my Nexus 6 gets here would be greatly appreciated.
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
ShrekOpher said:
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
You can check here
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my SHIELD Tablet using XDA Free mobile app
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
John.T.Erskine said:
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
Click to expand...
Click to collapse
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Tried that and received the same error as the OP. Can not mount SD card.
ShrekOpher said:
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Same issue
I'm having the same issue as OP. The phone won't get back to recovery. Won't even go into download mode.......Please help!
Edit: I was so used to working on my wife's phone (Note 1) that I was using the wrong button combination for download mode. I still can't get back to recovery, but I'll be ok once I get home.
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
absinthesummer said:
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
Click to expand...
Click to collapse
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
ProjektTHOR said:
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
Click to expand...
Click to collapse
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Flash that, re-root, flash new recovery (note: use a newer recovery, cwm sometimes has issues with our device, but twrp has been updated to work with 4.3+ same with philz, if you prefer that UI. Once 4.4.4 comes out, it doesn't play well with cwm, philz, OR older versions of twrp- I had a fight with a note 3 and recoveries yesterday, finally got it going with the latest twrp).
Boot up the device, flash/update your supersu. If you want to install a different rom now, go ahead. Once you have a new recovery installed, format (manually) /system /data /internal storage /cache /dalvik. The internal storage is important b/c it's usually what causes the /data corruption. Always wipe internal storage when switching between roms (or even between an update, I do). I don't usually wipe everything 3 times like some people do, but it is important to wipe the essentials. In twrp, internal storage is an option when wiping. In cwm & philz, you have to go under mounts & storage & it's second up from the bottom (format /data including /data/media> sdcard). Then back out to the main recovery menu and flash your rom, if you have any issues reboot recovery (not system) and re-flash it.
One more thing, make sure you have enough system storage for the gapps. I've run into issues where the rom flashed fine but gapps was too big for the system and didn't flash correctly. Try a slim gapps
Hope this helps, if you have any other questions I'm happy to try to help. We'll get it fixed for ya
Not able to flash other ROMS besides Stock now.......
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
dirtyalphaman said:
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
Click to expand...
Click to collapse
Ok so you've got the ne5 bootloader, so any time you flash stock you'll have to flash that version or above. Stock rom works, but custom ones don't, correct?
What's weird is that the latest dn3 is a modified stock rom so that shouldn't be an issue.
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
---------- Post added at 12:32 PM ---------- Previous post was at 12:21 PM ----------
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
Also, cwm is pretty old and prone to bugs on our devices. However philz is based on cwm and very similar in terms of user interface. It's not as different as twrp is. It has the same style and setup just a few additional tools that cwm doesn't have. It's also more compatible with our devices. If I had to choose one I wouldn't choose cwm, I'd go with philz or twrp for the sake of compatibility.
Thanks. I'll try this when I get home. Yea, once I flashed stock I kept getting Security Notices. I saw this was due to Knox and disabled it but that was a few flash attempts ago. I will follow you steps and let you know how it goes. Once again, thanks.
absinthesummer said:
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Click to expand...
Click to collapse
You are a saint. I'm not sure why I was struggling to find stock 4.4-series firmwares that could be flashed. I was so focused on getting them from sammobile or samware-firmware that I didn't even think to look here. I am going to try this process today and let you know if it works out!
absinthesummer said:
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
Click to expand...
Click to collapse
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
dirtyalphaman said:
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
Click to expand...
Click to collapse
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
absinthesummer said:
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
dirtyalphaman said:
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
Click to expand...
Click to collapse
Awesome! Good luck (and I think we're all flash-aholics)
Thank you for all of your help!!! Flashed the latest DN5 rom and it's working great. I found an issue that might have been preventing me from flashing earlier besides the botched root. My external sd card is having a few issues. A week or so ago it changed to read only and wouldn't let me move any files to or from it. Tonight it wouldn't let me flash the rom, but it worked when moved the rom to the internal storage. So I'm good to go! Can't thank you enough!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}
Root with NRT (Video by Rootjunky)
More videos here: http://www.wugfresh.com/videos/
Ah,.. So nice to see this. Thank you!
Sent from my Nexus 9 using XDA Free mobile app
Cool
btw twrp is out.
tyvar1 said:
Cool
btw twrp is out.
Click to expand...
Click to collapse
Yes, it will auto update on first run and it will know twrp is out. Full root support. And everything.
Sent from my Nexus 5 using Tapatalk
WugFresh said:
Yes, it will auto update on first run and it will know twrp is out. Full root support. And everything.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I usually flash my recovery the old fashioned way lvia fastboot like I did yesterday with the first version of TWRP but I decided to flash the newer version of TRWP with the Tooolkit. I was unencrypted prior to using the Toolkit and when it did the modified boot.img my device rebooted and encrypted itself. I assume I can just restore my backup from yesterday to go back to unencrypted.
nrage23 said:
I usually flash my recovery the old fashioned way lvia fastboot like I did yesterday with the first version of TWRP but I decided to flash the newer version of TRWP with the Tooolkit. I was unencrypted prior to using the Toolkit and when it did the modified boot.img my device rebooted and encrypted itself. I assume I can just restore my backup from yesterday to go back to unencrypted.
Click to expand...
Click to collapse
This makes no sense. Yes to your question. But how did you come to that conclusion? Can you add me on Google hangouts chat.
Sent from my Nexus 5 using Tapatalk
WugFresh said:
This makes no sense. Yes to your question. But how did you come to that conclusion? Can you add me on Google hangouts chat.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Started a hangouts chat
Tnx for this tool.
I did something wrong(fix permission) in twrp and i got boot-looped.
then i thought it would be smart o delete everything on the device...(not my brightest moment)
used the tool to flash stock + unroot.
Worked fine but:
When finishing it couldn't connect to the network when it was setting up.
I resolved this by rebooting.
Then when i put my backup back from Google play the navigation bar was missing and the notification tray was missing too.
I resolved that by doing a factory reset.
tnx again.
berendspruijt said:
Tnx for this tool.
I did something wrong(fix permission) in twrp and i got boot-looped.
then i thought it would be smart o delete everything on the device...(not my brightest moment)
used the tool to flash stock + unroot.
Worked fine but:
When finishing it couldn't connect to the network when it was setting up.
I resolved this by rebooting.
Then when i put my backup back from Google play the navigation bar was missing and the notification tray was missing too.
I resolved that by doing a factory reset.
tnx again.
Click to expand...
Click to collapse
Thats a lot of rando weirdness, you may want to flash stock again. Glad to hear its helped you.
{{ WugFresh }}
nrage23 said:
Started a hangouts chat
Click to expand...
Click to collapse
Determined to be kernel related. I am looking into whats involved with unencrypted N9 devices now though, and will see what I find out.
{{ WugFresh }}
Added the new LRX21R to the kit, just hit update and you will see it in the pull down list.
{{ WugFresh }}
berendspruijt said:
Tnx for this tool.
I did something wrong(fix permission) in twrp and i got boot-looped.
then i thought it would be smart o delete everything on the device...(not my brightest moment)
used the tool to flash stock + unroot.
Worked fine but:
When finishing it couldn't connect to the network when it was setting up.
I resolved this by rebooting.
Then when i put my backup back from Google play the navigation bar was missing and the notification tray was missing too.
I resolved that by doing a factory reset.
tnx again.
Click to expand...
Click to collapse
Should never need to fix permissions. If needs permissions fixed it means have bad deved rom or dirty flashed over different rom base. This breaks the uids and is just a bad way to fix things. Will bite you again sooner or later.
prdog1 said:
Should never need to fix permissions. If needs permissions fixed it means have bad deved rom or dirty flashed over different rom base. This breaks the uids and is just a bad way to fix things. Will bite you again sooner or later.
Click to expand...
Click to collapse
jep i was being stupid...
I wanted to flash the new update LRX21R manually.
so i got a zip file from the ota thread.
tried to flash it in twrp
but it failed.
so i tried fixing permissions.
why i chose that option i dont know.
i should have read up on that function before using it.
Tested the tool today to Flash 5.0 (LRX21R).
The flash stock(with option not to wipe enabled) command failed to update my Nexus 9! Problem more likely with the factory image.
Had to manually flash each image and there was no option for vendor image in the advance tools.
Successfully Flashed TWRP, but root didn't work as this method doesn't install SU binaries.
Had to use chainfire's root method instead.
The toolkit hadn't been updated to Include LRX21R when I was using it.
berendspruijt said:
jep i was being stupid...
I wanted to flash the new update LRX21R manually.
so i got a zip file from the ota thread.
tried to flash it in twrp
but it failed.
so i tried fixing permissions.
why i chose that option i dont know.
i should have read up on that function before using it.
Click to expand...
Click to collapse
It's a fix for a bad rom flash with apps that FC. It just a work around, flash is still bad. I used it in testing years ago just to see what broke. Should never be used. I have flashed tens of thousands of times and have never needed. Update won't flash if you are rooted or have anymodded files. It is only for pure stock. Have to flash back to stock unrooted to flash it. Might as well just flash the new full image.
corkiejp said:
Tested the tool today to Flash 5.0 (LRX21R).
The flash stock(with option not to wipe enabled) command failed to update my Nexus 9! Problem more likely with the factory image.
Had to manually flash each image and there was no option for vendor image in the advance tools.
Successfully Flashed TWRP, but root didn't work as this method doesn't install SU binaries.
Had to use chainfire's root method instead.
The toolkit hadn't been updated to Include LRX21R when I was using it.
Click to expand...
Click to collapse
Just an FYI for future use, the option "Force Flash Mode" does just that. It extracts the package further and flashes the images individually.
And yes, google seemed to mess these packs up a bit where that is necessary.
Root will work now on that build now that its listed. And when Chainfire releases the kernel autopatcher zip, Any Build mode will work on Lollipop, so you won't have to wait on me adding builds - although I am pretty quick!
{{ WugFresh }}
Sent from my Nexus 5 using Tapatalk
WugFresh said:
Just an FYI for future use, the option "Force Flash Mode" does just that. It extracts the package further and flashes the images individually.
{{ WugFresh }}
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the Tip on using "Force Flash Mode" from the settings.
What about vendor.img, still not available in the advance mode.
corkiejp said:
Thanks for the Tip on using "Force Flash Mode" from the settings.
What about vendor.img, still not available in the advance mode.
Click to expand...
Click to collapse
oh snap. I forgot to add that. It takes care of it in the flashstock.bat and force flash, but it deff needs a button in adv utils. Will add in v1.9.9 which may be ready later tonight, or tmrw the latest.
sad face for having to rearrange buttons now! Lol.
{{ WugFresh }}
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU!
You are the MAN! I was having a helluva time rooting my N9 until this beauty came along. Even an idiot like me can root with this great tool. Thanks again!
With that in mind, I have a couple of questions...
1. I did not flash a custom recovery when I rooted. Can I still get OTA updates?
2. Can I flash TWRP at a later date using the tool?
Once again, mucho thanks.
I unfortunately can not provide some sort of logs but I can tell some sort of history.
So I have some rom that I installed ages ago I believe the zipfile says note4our.
Anyways I dropped my phone a couple weeks ago and noticed that my phone was slowly acting up, as in random reboots, and sometimes it would restart into download mode. Sometimes it would just hang at the very first screen that says kernel in the top left. Luckily I was able to go into recovery and clearing caches seemed to sort me out temporarily. Last night the phone randomly rebooted and has not been able to boot up at all. Just constant bzz bzz reboot lol. I am still able to go to recovery mode, however when I plug it into my computer it seems that I can't get any files on or off via a drag and drop, and I also can't use windows to move files between an sdcard mounted in the phone to the internal storage either. Which is weird since it windows can list all of my files but it can't open it either. I do not have read-only checked. When I try to move files windows says something about the device having stopped hence I can't move.
So I'm guessing there's no way for me to recover my files later? Or will my twrp backup of the just the data portion suffice? Any other things I should try before I go full nuclear and do a complete wipe and try a fresh? Normally I would use this situation to update as well but I figured I would do that after my reflash since I'm sure I would need to update my bootloader or something and I'm still trying to potentially salvage my files if I still can.
So yeah it's been over a year or so, and I need my hand held at this point. Please and thank you and I'll do my best to provide anymore information after work tonight.
That locked USB is av ***** ain't it. I've been getting that for the last couple of updates to. It wont stay locked. It just needs enough time to make sure the build stays the same. Pull the battery put put it back in and wait a few minutes. It still unlock again.
Sent from my SM-N910P using Tapatalk
@bryyando
A possible scenario may have been your SuperSU updated to systemless root in Google Play and later you factory reset? That would cause you lose root and fail to boot with existing custom kernel.
If that happened, you could flash the SuperSU zip and it should boot again. Here's an updated version of the original system based SuperSU that the ROM had:
http://forum.xda-developers.com/attachment.php?attachmentid=3969639&d=1481813000
If that doesn't work, you could try to flash the ROM without wiping data. Or you could backup data partition but I think you need to include more than one partition to make it valid (but that may only pertain to titanium backup; I'm not sure). Since recovery is working, you could include that partition.
If it comes to trying to the nuclear option, I'd recommend flashing the linked SuperSU after restoring TWRP backup of data.
Maybe one of those options works but I suspect your issue is loss of root. It's a must have with custom kernel. Otherwise, no boot.
If you do boot and recover without losing data, make a backup. Valuable time saver to have a current backup.
Sent from my SM-N910P using Tapatalk
@samep
So I totally remembered about dirty flashing while at work and proceeded to do that when I got home, before I read this thread. The phone appears to marginally do better as it is rebooting after it at least optimizes some apps... Also I for reference my ROM version is 1.1 and twrp is 2.8.7.0 lol
And just my luck my spare note 2 seems to have an emmc failure...
@samep
Managed to do a twrp backup of my data partition. Oddly enough my phone rebooted the first time, but made it the second time. For the hell of it I cleared just the caches and then did a bootup. Each time it had less apps to optimize and eventually I made it past the lockscreen, my phone alerted me to my missed messages and then would do a bootloop again. I did notice that the screen had weird pink lines on the bottom right before it vibrated and restarted. Still can't save files onto computer while connected in recovery mode. I luckily found an sdcard that should have enough memory for me to move my pictures and notes that I'm trying to save. Then I'll do an advanced wipe this time. Flash my 1.1 rom, then the supersu you provided and see if it works. If that doesn't then I'll odin up to PE1? Or whatever the new roms need and see if my phone crashes still while on stock and then go from there. Did I miss anything?
bryyando said:
@samep
Managed to do a twrp backup of my data partition. Oddly enough my phone rebooted the first time, but made it the second time. For the hell of it I cleared just the caches and then did a bootup. Each time it had less apps to optimize and eventually I made it past the lockscreen, my phone alerted me to my missed messages and then would do a bootloop again. I did notice that the screen had weird pink lines on the bottom right before it vibrated and restarted. Still can't save files onto computer while connected in recovery mode. I luckily found an sdcard that should have enough memory for me to move my pictures and notes that I'm trying to save. Then I'll do an advanced wipe this time. Flash my 1.1 rom, then the supersu you provided and see if it works. If that doesn't then I'll odin up to PE1? Or whatever the new roms need and see if my phone crashes still while on stock and then go from there. Did I miss anything?
Click to expand...
Click to collapse
Since you mentioned a ROM with Xposed framework, I hadn't considered that Xposed framework may have gotten corrupted causing the reboots. You're on an old ROM. I'd update and not worry with it.
I'd recommend backing up your data that you'd like to keep, wiping internal memory, format data and factory reset, Odin PE2 and clean install freeza's Note 4our beta 3. Kernel and ROM are based on PE2.
The ROM is here but this link points to a known issue you'll need to fix Xposed installer to update or install Xposed modules.
http://forum.xda-developers.com/showthread.php?p=67383249
But if you're not interested in Xposed at all, you may consider another ROM. I'd recommend being on the right update as you're trying to do already. You may not have noticed freeza updated to PE2 if that was your goal.
If you prefer Xposed framework and custom modules, freeza offers a quick and custom way to get there with minimum flashing.
Sent from my SM-N910P using Tapatalk
@samep
I think we might be on the right track with a potentially corrupted xposed. I did notice that some of modules would stop working sometimes. Also what may be potentially interesting is that my phone does reboot when I am in recovery mode. Although xposed probably wouldn't cause that? I do think my phone is more stable in recovery mode as it seems is running for longer periods while I'm in there vs trying to boot up in which I barely make it past the samsung boot animation. I am slowly moving folders over so I have both a twrp data backup as well as the original files, it is just taking a long time as I am not normally at home to do this. On top of that ODIN flash, I noticed that twrp has been updated to 3.0.2.0 I'm guessing I should update that as well. I adb load the img file correct? The tar is just compressed for easier download?
bryyando said:
@samep
I think we might be on the right track with a potentially corrupted xposed. I did notice that some of modules would stop working sometimes. Also what may be potentially interesting is that my phone does reboot when I am in recovery mode. Although xposed probably wouldn't cause that? I do think my phone is more stable in recovery mode as it seems is running for longer periods while I'm in there vs trying to boot up in which I barely make it past the samsung boot animation. I am slowly moving folders over so I have both a twrp data backup as well as the original files, it is just taking a long time as I am not normally at home to do this. On top of that ODIN flash, I noticed that twrp has been updated to 3.0.2.0 I'm guessing I should update that as well. I adb load the img file correct? The tar is just compressed for easier download?
Click to expand...
Click to collapse
The .img version of TWRP is for updating within TWRP or Flashify. You'd need the .img.tar version for Odin. Flash in Odin after flash of stock tar with Odin defaults. Use AP mode for both flashes in separate Odin sessions, closing Odin when done with each flash.
For TWRP flash, uncheck only the auto reboot option in Odin, once flash is started, wait until you see success, 0 failed and then pull USB cable and battery. Wait at least 1 minute and reinstall battery. You must boot directly into recovery on initial boot after TWRP flash or you lose it to stock recovery; it can restore itself if you fail to do it right.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Did you mean your phone runs longer in safe mode rather than recovery? If safe mode isn't stable, then yes, it's time to take advantage of the update. I think you're doing the right thing.
Sent from my SM-N910P using Tapatalk
I have not tried or was aware of safe mode. I meant that the phone would sometimes reboot while in recovery mode as well.
samep said:
The .img version of TWRP is for updating within TWRP or Flashify. You'd need the .img.tar version for Odin. Flash in Odin after flash of stock tar with Odin defaults. Use AP mode for both flashes in separate Odin sessions, closing Odin when done with each flash.
For TWRP flash, uncheck only the auto reboot option in Odin, once flash is started, wait until you see success, 0 failed and then pull USB cable and battery. Wait at least 1 minute and reinstall battery. You must boot directly into recovery on initial boot after TWRP flash or you lose it to stock recovery; it can restore itself if you fail to do it right.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Did you mean your phone runs longer in safe mode rather than recovery? If safe mode isn't stable, then yes, it's time to take advantage of the update. I think you're doing the right thing.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
samep said:
The .img version of TWRP is for updating within TWRP or Flashify. You'd need the .img.tar version for Odin. Flash in Odin after flash of stock tar with Odin defaults. Use AP mode for both flashes in separate Odin sessions, closing Odin when done with each flash.
For TWRP flash, uncheck only the auto reboot option in Odin, once flash is started, wait until you see success, 0 failed and then pull USB cable and battery. Wait at least 1 minute and reinstall battery. You must boot directly into recovery on initial boot after TWRP flash or you lose it to stock recovery; it can restore itself if you fail to do it right.
https://dl.twrp.me/trltespr/twrp-3.0.2-0-trltespr.img.tar
Did you mean your phone runs longer in safe mode rather than recovery? If safe mode isn't stable, then yes, it's time to take advantage of the update. I think you're doing the right thing.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
I won't say that's terminal. There's been two occasions that I had to flash TWRP again because it was buggy but the phone was otherwise fine after that.
It's possible you have more than one partition corrupted. I wouldn't worry unless you have trouble flashing with Odin.
Hopefully once you're done with Odin and flash the new ROM, you're back to normal.
Sent from my SM-N910P using Tapatalk
Seem to be having problems with ODIN, hangs when I load up the tar for a bit and then when I hit run it says 0 succeed 0 fail. Are there separate drivers I need as well?
bryyando said:
Seem to be having problems with ODIN, hangs when I load up the tar for a bit and then when I hit run it says 0 succeed 0 fail. Are there separate drivers I need as well?
Click to expand...
Click to collapse
You need the Samsung driver. Google Samsung SM-N910P support and you should find it. Like this:
http://www.samsung.com/us/support/owners/product/galaxy-note-4-sprint (scroll down to driver and agree to terms to download)
On your tar, verify the md5 against the zip. If good, extract the tar.md5 from it. When you load that into Odin AP slot, expect about minute delay to verify it. I usually wait before plugging my USB in to download for that reason. You shouldn't try to start the download before it's ready.
When you plug-in in download mode, also verify your phone is added (highlights when added) in the COMM window.
Sent from my SM-N910P using Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/a/d1EyB
This is what I got, and same thing. Doesn't really get past the powered by android screen. Maybe sometimes it shows the sprint logo. Guess my phone is dead?
@samep
There was this too.
bryyando said:
@samep
There was this too.
Click to expand...
Click to collapse
So it flashed and booted?
I didn't see the whole Odin log to verify your phone was added as COM. You should see a progress bar lb the phone screen and some warning like writing; do not disconnect.
Sent from my SM-N910P using Tapatalk
Here's what it said about my twrp install, except it never boots up...
Yeah the rom tried to boot but then it would just get into a bootloop again.
bryyando said:
Yeah the rom tried to boot but then it would just get into a bootloop again.
Click to expand...
Click to collapse
Did you factory reset? If not, try that in stock recovery now and reboot.
Sent from my SM-N910P using Tapatalk
Tried it again,
Did a factory reset but still bootloop. Was able to get into recovery mode tho
samep said:
Did you factory reset? If not, try that in stock recovery now and reboot.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
bryyando said:
Tried it again,
Did a factory reset but still bootloop. Was able to get into recovery mode tho
Click to expand...
Click to collapse
You did the wipes I suggested in post #6? I've seen that happen when internal memory isn't wiped for users with CM coming to back to stock. I've seen it happen with nand erase all for some users but you didn't do that, did you?
When that happens for those doing just the nand erase all without tar and PIT with repartition, the Odin flash doesn't take right. Just boot stock recovery, factory reset and wipe cache partitions and power down , pull battery for at least 1 minute and reinstall, boot to download mode and flash stock tar with Odin defaults. Let it auto boot.
Even if you didn't have CM, I'd consider that before proceeding. I'd even flash TWRP and wipe internal memory if that was skipped as a prep in the previous stock tar flash. I'm not sure if stock recovery factory reset is any different than TWRP but it seems to have made a difference for some users that had flash issues with Odin in the past so consider that before wiping with TWRP.
Try stock tar prep and install without PIT or repartition or nand erase all (Odin defaults only). Hopefully that helps to boot. I'd need to know if you already wiped internal memory before suggesting the PIT. There is s thread with links already posted but it's less of a last ditch effort fix but rather more of a diagnosis for hardware failure. Small chance it works so most likely a bad flash or corruption only fix. Most of these failures seem to indicate hardware failure, IMO. Dropping it hard enough could possibly damage hardware or corrupt. I don't know as fact but I'd think either is possible. Best wishes for resolution.
Sent from my SM-N910P using Tapatalk