I browsed through the general q&a and i am not finding exactly what i am looking for, so please hold the yelling if i missed it. but i am not against being told where to go....
background info....I purchased a DNA off of EBay and i turned it on, and got it going. The SW version is current, stock rooted and the phone is S-Off. The phone still had some of the guys pictures on it, so i jumped in to recovery (CWM touch recovery) and wiped the phone, cache, and restarted. When i did the phone hung, and never booted, so i held the power button down, it then rebooted, checked the apps and all was good. his pics are still on the phone.....going through the phone and wiping (backup and reset) and it's the same thing....
So my question is, what can i do to get the phone back to square one, fully clean but still keep the root and s-off? the reason i am asking is when i wiped it wouldnt boot properly. should i reflash a stock rooted rom? whats the best way to wipe the internal memory? i have rooted and rom'd going back to the original droid, but the HTC's always intimidate me. So please any suggestions they would be welcome. I want to get it stock, then make a perfect good backup, then start trying some roms.....
Thanks in advance!
So I read up a little more, and decided that the best thing to do was Format the SD card. After i did that, i wiped everything again and after it boots, it still just hangs. Then i hold power down and it restarts and i get the "android is upgrading screen" then i am fine. So i am still concerned that it never boots properly. So my question still stands..... should i download another stock rom, or is there something else i should do?
mooseknuckles said:
So I read up a little more, and decided that the best thing to do was Format the SD card. After i did that, i wiped everything again and after it boots, it still just hangs. Then i hold power down and it restarts and i get the "android is upgrading screen" then i am fine. So i am still concerned that it never boots properly. So my question still stands..... should i download another stock rom, or is there something else i should do?
Click to expand...
Click to collapse
if you wipe the phone in recovery ( im assuming /data, /cache, /dalvik, and/or /system) you would have to flash a new ROM on top of that, because you are wiping the entire thing. i dont think you can do a regular wipe in CWM and expect it to boot after that. but, yes, for what you want, formatting /sdcard would probably suffice.
[indiferenc] said:
if you wipe the phone in recovery ( im assuming /data, /cache, /dalvik, and/or /system) you would have to flash a new ROM on top of that, because you are wiping the entire thing. i dont think you can do a regular wipe in CWM and expect it to boot after that. but, yes, for what you want, formatting /sdcard would probably suffice.
Click to expand...
Click to collapse
I don't think cwm wipes the rom by selecting factory reset in it.
Sent from my HTC6435LVW using xda premium
It doesn't, and if he had wiped system it never ever ever would have booted even after resetting it 9001 times.
Wiping data, factory reset, same thing different terms for different versions of recoveries, technically wiping data would delete sdcard with /data/media but usually doesn't. Format SD and a factory reset/data wipe would be what he's looking for, but it not booting afterwards is an issue pointing to something else.
I'd suggest looking at your current ROM version then getting a rooted version and flashing it then seeing if it persists. Any ROM will do, really, I just said that way if you want to stay on that version of sense.
Tapatalked from my HTC DNA - ReVolt
Related
(I searched before asking)
So I'm flashing my buddy's Metro Ascend. I got it rooted. Flashed CWM Recovery 2.x.x.x. (The common one, .5.1.8, I think). It hangs if I try to format the cache, period. Hangs during factory reset, wipe cache and format cache. I stupidly flashed anyway and it seemed to work, but after a reboot, the entire system seems broken. Force closes left and right and the Launcher doesn't load. It still received incoming calls at first, but now it doesn't even do that. I'm not too familiar with troubleshooting this particular phone and my friend really needs it fixed. So please, someone help me? (No lectures or flaming please, just advice. I'm not looking for motherly scolding about my irresponsibility )
Sent from parts unknown.
Probably need to wipe the phone clean and flash rom again. If cwm is not working good try Amon Ra.
There's also a system format file floating around that you can flash in recovery to wipe your system clean.
Thanks. Never heard of Amon Ra but I'll look it up. The inability to finish the wipe data/factory reset kills me. I know my way around a Captivate with my eyes closed, but this is all goofy to me.
Still open to suggestions if anyone else has something to add. Easy way back to stock? Suggestions for a good rom/mod to flash? (Currently attempting Icarus 1.0)
Sent from parts unknown.
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
did you not wipe system and data? I am not super skilled, but maybe it tried to stick the entire ROM into the left over space of the last ROM that is still on there?
It won't boot to recovery? It should boot to recovery
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
Click to expand...
Click to collapse
The error message you received is going to be the key to understanding the issue that occured. When it says unmounted, it is referring to a specific partition, either /data or /system most likely.
For starters, when it hangs on the htc white screen, this is usually either a kernel or ramdisk issue. If the kernel is known to be good, then it is probably a ramdisk issue. most ramdisk issues relate to a mismatch/incompatibility between the loaded kernel and the ROM.
First suggestion would be to reflash the ROM, clearing /cache and /data.
Second suggestion would be to restore a backup. This will confirm there is nothing wrong with your device hardware wise and you'll know it is a specific issue with the ROM you wanted to load.
Third suggestion, find the exact error, word for word, which occured in recovery and post up in the ROM thread asking if other users of that ROM also encountered, how they handled. Also feel free to post back up here.
When writing the programming behind a custom recovery, the error messages are added in there to help allow users and developers better knowledge of the exact issue so they can work to resolve them. Without the exact error message, it is similar to going to a car shop and saying, some light came on my dash, but I don't know what it was and now the car doesn't work. Fix it? Another words, it is very vague.
Hope the suggestions and tips help! Good luck!
my first instinct was to reflash the backup or new rom again but it wont boot to any rom, recovery or bootloader. it just hangs on the htc white screen
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
weezymagic said:
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
Click to expand...
Click to collapse
are you on twrp 1.0.x ? There is s charging issue where it won't restart right because it thinks It's already in recovery
sent from my EVO 3D via XDA app
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
Click to expand...
Click to collapse
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Twolazyg said:
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Click to expand...
Click to collapse
Agreed^^^^^
I have a locked Moto Photon 4g, rooted. And decided to play with other ROMs to see if I could improve battery life, maybe reduce lag a little. I chose Rocko 3.0 (I know it's not supported) because it's one of two options I could find that would work with a locked device, therefore allowing me to retain 4g (I need it in my area. 3g is a dog here but 4g works well).
I used System Recovery to install it, and it seemed to go smoothly. The only things that don't seem to have gone as planned are:
1) I did NOT wipe the data or the cache's, when flashing, as I anticipated the flash process would do this. It didn't, and everything stayed intact and seems to be working fine.
2) As indicated in the video by QBKING77, there are some cosmetic differences between Rocko ROM and the stock ROM. But, missing seems to be the built in numbered percentage for the battery monitor, and the different boot options.
3) When booting re-booting, MOST of the time, i get the message "the process com.android.phone has ended unexpectedly. Please try again". I hit the "force close" button, and it occasionally comes up again a few minutes later, but then stops. It doesn't seem to do any harm, so I am inclined to leave it unless someone has a simple answer for fixing it. I have already cleared the cache and Dalvik cache, and this did not help. I would prefer NOT to wipe the device and start over just for an annoying thing I have to click past one or two times.
Any thoughts? Can anyone give me some more insight into the benefits of Rocko 3.0 (again, I know, unsupported. But, some of us want to keep 4g AND ROM).
Thanks!
I have noticed that if you do not clear everything your supposed to before installing a Rom it only causes problems. its like the previous rom and one your installing form a hybrid. I would suggest clearing data, system, cache, dalvik cache and reinstalling.
Sent from my MB855 using xda app-developers app
Go here and download the one that says FULL WIPE. Flash this in your recovery, wipe dalvik cache under Advanced, then install your rom again and report back with the results.
As far as battery, make sure that you calibrate after flashing. This means, charge your phone fully, reboot to recovery, go under Advanced again and wipe battery stats. Run your battery down till phone shuts off, plug it in while holding the power button (this will bypass charge mode, booting straight to android), charge to full battery again. Your good to go.
Acvice said:
Go here and download the one that says FULL WIPE. Flash this in your recovery, wipe dalvik cache under Advanced, then install your rom again and report back with the results.
As far as battery, make sure that you calibrate after flashing. This means, charge your phone fully, reboot to recovery, go under Advanced again and wipe battery stats. Run your battery down till phone shuts off, plug it in while holding the power button (this will bypass charge mode, booting straight to android), charge to full battery again. Your good to go.
Click to expand...
Click to collapse
Thanks. So, I downloaded Full Wipe, dropped on my SD, installed it through cwm recovery (again, I'm running a stock device), and now, my phone will only boot to the Motorola Dual Core splash screen and sits indefinitely. I went into Android Recovery and tried to reinstall Full Wipe, and it said "e: signature verification failed, installation aborted". I did a fill wipe from Android Recovery and then told it to re-install the Rocko ROM and it said the same thing, "e: signature verification failed, installation aborted". I understand this is because I am on a stock device and need to do all my installs through cwm recovery, but I can't get to it. So, what do I do now?
So, now, unless I am booting into Android Recovery, I can't boot past the Motorola Splash screen. Kinda bricked for the moment.
Any insight would be appreciated.
pelikan3 said:
Thanks. So, I downloaded Full Wipe, dropped on my SD, installed it through recovery, and now, my phone will only boot to the Motorola Dual Core splash screen and sits indefinitely. Any insight?
Click to expand...
Click to collapse
Sounds like you need to SBF back to stock. Be sure not to accept the OTA update that will probably come once back on stock.
I would suggest giving MOF Rom a try. It is supported.
pelikan3 said:
Thanks. So, I downloaded Full Wipe, dropped on my SD, installed it through cwm recovery (again, I'm running a stock device), and now, my phone will only boot to the Motorola Dual Core splash screen and sits indefinitely. I went into Android Recovery and tried to reinstall Full Wipe, and it said "e: signature verification failed, installation aborted". I did a fill wipe from Android Recovery and then told it to re-install the Rocko ROM and it said the same thing, "e: signature verification failed, installation aborted". I understand this is because I am on a stock device and need to do all my installs through cwm recovery, but I can't get to it. So, what do I do now?
So, now, unless I am booting into Android Recovery, I can't boot past the Motorola Splash screen. Kinda bricked for the moment.
Any insight would be appreciated.
Click to expand...
Click to collapse
What i sent you was just a flashable zip that tells recovery to wipe cache, system, and data. Same thing as doing it manually. When you flashing it the first time, did you immediately flash rocko rom afterwards? Thats what i was trying to get you to do, it should have booted up in Rocko afterwards.
But being stock means that bootstrap is the only recovery you can use. Its a workaround based off of CWM. You can't actually get CWM on your phone without being unlocked.
Boot into android recovery (Bootstrap), wipe system, wipe data, wipe cache, wipe dalvik, then try to install Rocko. Tell me if that works. If not, youll just need to SBF back to stock and install boostrap recovery again.
I did SBF back to stock. That was a VERY long process, but it turned out well.
For the moment, I'm going to sit, as-is, stock and unrooted, until I get a better idea of what the benefits are of the MOF ROM over stock.
Thanks!
pelikan3 said:
I did SBF back to stock. That was a VERY long process, but it turned out well.
For the moment, I'm going to sit, as-is, stock and unrooted, until I get a better idea of what the benefits are of the MOF ROM over stock.
Thanks!
Click to expand...
Click to collapse
Glad its working for ya. Make sure not to take the system update if you ever plan on unlocking or running a custom from as you won't ever be able to. But the benefits of mof is generally 1080p recording over 720, some bug fixes and bloat removal, toggles, and generally just a bit speedier and lag free. 1080p and the bug fixes can be had by taking that update. But again, you won't be able to get rid of it if you do it so make sure you're cool with that.
Sent from my MB855 using xda app-developers app
Acvice said:
Glad its working for ya. Make sure not to take the system update if you ever plan on unlocking or running a custom from as you won't ever be able to. But the benefits of mof is generally 1080p recording over 720, some bug fixes and bloat removal, toggles, and generally just a bit speedier and lag free. 1080p and the bug fixes can be had by taking that update. But again, you won't be able to get rid of it if you do it so make sure you're cool with that.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'm not really certain theirs much benefit to 1080p, because I'm not going to be hooking my Photon to a larger screen, where I understand the true benefit lies. I wouldn't mind a little less lag, though, it's not critical. The biggest thing for me is some kind of built in battery and wireless management that dramatically improves battery life.
But, I don't plan on going with an unlocked solution unless they find a way to preserve 4g on an unlocked device.
pelikan3 said:
Thanks, I'm not really certain theirs much benefit to 1080p, because I'm not going to be hooking my Photon to a larger screen, where I understand the true benefit lies. I wouldn't mind a little less lag, though, it's not critical. The biggest thing for me is some kind of built in battery and wireless management that dramatically improves battery life.
But, I don't plan on going with an unlocked solution unless they find a way to preserve 4g on an unlocked device.
Click to expand...
Click to collapse
Bummer, cause the real battery improvement comes with using custom kernels and getting rid of all those perpetually syncing items (motoblur).
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
I've looked all over for answers on this. I hope I didn't miss something, but here is my issue:
After being fed up with Touchwiz, I tried flashing AOSP ROMs instead. Ever since then, every AOSP ROM I flash will freeze during boot (usually it freezes after 15-20 seconds), I'll see a glitched image for 10 seconds, and then reboot. This bootloop has happened with AICP, Resurrection Remix, and a few others. I'm about to try CyanogenMod, but I assume that will fail as well since the others were mostly based off CM. I always wipe data, cache, and dalvik before flashing (sometimes system too, and now internal storage to try to fix this issue).
Can anyone figure this out?
I have very limited access to a PC and my Mac refuses to recognize this phone in download mode, so Odin isn't readily available and Heimdall has been no good so far.
G900TUVS1FOL1
EDIT: Apparently EVERYTHING is bootlooping this phone. I flashed other Touchwiz-based ROM's and those aren't working. Finally I returned to stock firmware using Kies, and I'm STILL stuck in an endless loop.
I NEED HELP. SERIOUSLY.
This is probably a bad idea, but I'm headed to T-Mobile to try and get help. I can't afford to wait.
t3st4m3nt said:
This is probably a bad idea, but I'm headed to T-Mobile to try and get help. I can't afford to wait.
Click to expand...
Click to collapse
in twrp you need to format data partion and wipe internal storage cache,data, and davilk cache
then use kies for emergency restore
malbert16442 said:
in twrp you need to format data partion and wipe internal storage cache,data, and davilk cache
then use kies for emergency restore
Click to expand...
Click to collapse
Honestly, I feel like I should've just stuck with your ROMs
I've done all of the above, and I do so every time I flash a ROM. I tried re-flashing after wiping system, no good. And the restore from Kies failed to fix the issue.
Kies removed twrp, so I was able to take it to a Samsung Center at Best Buy without the device drawing suspicion of having been rooted (they ignore Knox at this one), and they failed to solve the issue with a home reset. Right now they have no idea what is happening, and neither do I.