Develop Bugs

SOLVED! [Q] HELP! User data keeps disappearing after reboot!

"I don't know what specific directory or partition is messed up but every single time my phone reboot I think I lose my user data or something. All of my apps force close and the tutorial about how to use my phone keyboard starts as if I just flashed a new Rom. This keeps happening no matter which Rom I use. I don't know why this is happening. I've tried 2 different SD cards and it still happens. Please Help!"
I didn't exactly figure out what was wrong but I found a solution. There was something wrong with my cache partitions.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/

aznbatman said:
I don't know what specific directory or partition is messed up but every single time my phone reboot I think I lose my user data or something. All of my apps force close and the tutorial about how to use my phone keyboard starts as if I just flashed a new Rom. This keeps happening no matter which Rom I use. I don't know why this is happening. I've tried 2 different SD cards and it still happens. Please Help!
Click to expand...
Click to collapse
What ROM(s) are you using? From the Terminal Emulator, have you tried running fix_permissions? I run Redemption, and when I install a new version of it that's the first thing I do, then reboot.

RMarkwald said:
What ROM(s) are you using? From the Terminal Emulator, have you tried running fix_permissions? I run Redemption, and when I install a new version of it that's the first thing I do, then reboot.
Click to expand...
Click to collapse
I'm running redemptive 1.9 and I've tried multiple other roms and still have the same problem. Fix permissions didn't work either. I get an error with the packages.XML file. This problem happens no matter what rom I try.

Hey guys. I had the same $#it happen to me last week! I was sitting on the couch and cleaning my rooted Droid with stock Rom... and when I held the power button to shutdown phone I got a long vibrate instead of the usual short one! This got my attention, and sure enough, when I finally took out the battery and reported, I got the UIDs are inconsistent.... error along with the I'm feeling lucky button. Force Closes, galore! I fixed it by doing a hard reset and basically returning my phone to factory setting. Still rooted, but lost all my contacts,favorites, texts, apps... basically everything that wasn't on the SD card...:-/ still trying to restore all my settings... it was perfectly set to how I wanted it.
Sent from my ADR6300 using XDA App

Stuck in a bootloop!

I plugged my phone into my computer to charge it earlier today, and after a delay of a few minutes, it rebooted into a bootloop. I've been on CM7 nightly 107 for a few weeks now without any issues and having rebooted several times, so I'm not sure what the catalyst could've been. It was at ~30% remaining battery life before it rebooted, so it didn't power down out of necessity.

probably gonna have to wipe and start over.. just hold down the volume down button and power button at the same time.. wipe all then reflash the rom..

I've tried wiping cache and dalvik, but I really don't want to lose my installed apps and settings. Is there any other option, or am I stuck with a factory reset and reflash?

Install Titanium Backup and backup your apps then reboot your phone into recovery. In recovery, wipe user data and reboot. After you go through the inital setup try to duplicate the problem. If it doesn't happen then restore your apps one at a time and try to duplicate the issue after each app restore. If after restoring an app, you are able to duplicate the issue then uninstall the app and see if that fixes it.
If it does happen again prior to restoring apps you need to reflash the ROM. If after reflashing your ROM you have the same issue try a different computer. If it happens on one computer and not the other then the computer is suspect. If it happens on both then the phone is suspect.

I can't get into Android, so I can't back up my apps. Will reflashing CM n107 (or a later CM release) have a chance of fixing it?

Reflashing may work, give it a shot but if that doesn't work then do a full wipe and flash.

Alright. Not what I was hoping for but it's definitely a helpful answer. Is there some procedure for marking this thread solved, or should I just let it sit?

Flashing the rom again alone may fix your problem true.. But if this doesn't then wiping is your only option.. Just let this be a learning experience. Probably every one here has gone through this before once or twice and learned from it. Get an app like titanium backup like mentioned and backup your apps so you don't have to reinstall from scratch. It's such a time saver. Then you can learn how to backup other things like email settings and messages. I recommend sms backup for your messages if you like to keep those.. And in Titanium backup look for the one called Email Settings and you can usually back that up and save your email accounts and all emails. Good luck!

Aeltar said:
Alright. Not what I was hoping for but it's definitely a helpful answer. Is there some procedure for marking this thread solved, or should I just let it sit?
Click to expand...
Click to collapse
No prob. I don't like it when I have to do it either. You don't have enough posts to retitle the thread so don't worry about it.

Rooted, Flashed Evo Classic, Loved it... now it keeps rebooting!

I rooted my Evo for the first time today using the Revolutionary method. Everything went smoothly following the instructions. I downloaded and flashed the latest Evo Classic ROM and I was loving it. It seems to be an awesome ROM. I have 200 MB free space instead of 46MB with all of my apps installed. Everything was great until I went to go to bed. I put the phone on the stock HTC charger and climbed in bed. Less than a minute later it rebooted. The phone has always done that at random times so I didn't think anything of it. Shortly after it booted it rebooted again. It just keeps rebooting over and over as long as it's on the charger! Now it even reboots when it's not charging but the interval is as long as 10 minutes instead of 1.
Has anyone else had this issue? I spent HOURS getting everything just right and customizing settings after flashing this ROM and I really don't want to have to do it all over again. I followed the instructions for flashing the ROM. I cleared the cache and wiped all data. I backed up my apps with Titanium Backup and restored a select number of them. My phone is my alarm clock. Now I can't trust it to wake me up in the morning to go to work!
EDIT: I just restored from my stock NAND backup and it is working fine for tonight. I'm guessing I need to just start from scratch and reflash Evo Classic? I can't seem to find anyone else that had this problem so I assume it was something with my flash or an app I had installed?

I flashed a fresh Evo Classic ROM and started over. Everything was great. I got it all setup and restore my apps. No rebooting problems. Put it on the charger. Worked fine. As a troubleshooting step I opened Sleep, my alarm clock app, and within 30 seconds it rebooted. Obviously something with that app triggered it. I uninstalled it. About a minute later it started a reboot loop in one minute intervals.
Apparently no one has any ideas or I am invisible. I can't post in the Evo Classic thread because I don't have enough posts to earn me the privilege.

Did you wipe dalvik? And what recovery are you using?

I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions.
I only see two options:
Wipe Data/Factory Reset
Clear Cache Partition
I have done both of these each time I flashed. I just flashed again and installed only the Sleep As An Droid app fresh from the market. I opened it and within one minute it rebooted. Obviously this app doesn't agree with this ROM or something isn't going right during the wipe and/or flash.
Any other suggestions for a stable ROM that has the new Sense notification bar with quick settings?
EDIT: I found the Dalvik Cache wipe option under advanced. Doing it now and will reflash and try again.
EDIT 2: Well that failed. I wiped data, cache partition, and dalvik and flashed the ROM. I logged into my Google account, downloaded the app from the market, put the phone on the charger, opened the app, and it rebooted.

Is it rebooting if you don't use that particular app at all?

Evo450 said:
I am using Revolutionary recovery (I think?). It is the one that was installed when I rooted following the directions..
Click to expand...
Click to collapse
That recovery is called clockwork. You might think about changing your recovery to amon ra since some people have issues with clockwork because it doesn't properly wipe cache and dalvik

Hey there! Sorry about your issues. I don't always check the q&a, so you are usually better off posting on my thread or pm. I just happened to peep on here today
First. Use this. It's the second step on my instructions to flash Classic. Not necessary, but recommended. http://forum.xda-developers.com/showthread.php?t=705026
Second, don't use titanium backup. Instead, use mybackup root (free in market and included with my Rom). Not to bash tb, but mybackuproot has never given me issues while I've heard stories about tb.
Third, once you get amon ra installed, boot into recovery and wipe everything but your sdcard.
Fourth, download a fresh copy of classic from a reliable network, like home computer. Downloading from a phone is bad news (just a tip since you're newly rooted )
Fifth, flash and enjoy!
Please let me know how it goes for you.
Truly,
Tommy
tapatalk signature here. lovely.

Thank you very much for the reply! I will try your suggestions some time this weekend. I need my phone to work 100% as I am traveling so maybe Sunday I will try again.

I followed all of your suggestions and redownloaded the ROM, installed RA Recovery, cleared all data, cache, and dalvik several times, and reflashed the ROM.
I restored my apps and data using MyBackup Root and it took over 2 hours! I opened my alarm app and... reboot. Back to the same old reboot over and over.
I think I'll just go back to the stock ROM and remove the bloatware and call it good.

Theirs one obvious thing nobody mentioned. Google how to check a md5 sum do that with every rom you download and if it does not say its right don't flash, redownload and check again. Also restore as little as possible through mybackup and if you are restoring things like your alarms or any system settings don't.
As for good roms with quick settings like r2r going green lightning fast, or unleashed r6.
Ps I would suggest useing r2r superwipe before whatever you may flash n wipe both caches a few times first it might help
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Also id recommend copying all contents of SD card to computer and wipe SD card then reload everything back onto SD card. I know sometimes the SD card can become corrupt and cause bootloops and random reboots

I checked the Md5 sums of everything I downloaded. I only restored my apps, text messages, and Bluetooth pairings. I even ended up buying a new, larger SD card yesterday and I formated and used it when I flashed.
This afternoon I flashed my latest backup of my stock ROM and used Titanium Backup to removed all of the Sprint bloatware. My phone is running very fast now with over 110 MB of internal memory available so I can't complain.
Maybe next weekend I will try another ROM but for now I need me phone to be working since I do not have a land line and I rely on my phone for work.

You said this happened before you ever rooted? Maybe its a factory defect if u got a.warrenty I would suggest unrooting and sending to them.
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.

Its not normal they keep giveing you defects... I have never heard of.this problem anyway... I would take it bac
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
My girlfriend had the same issue with her second evo. She had the Black Evo at first than a friend of hers swapped her to the white Evo. She had the issue only on the white evo. She ended up having to replace the phone with another one. That one did the same thing for awhile so we thought it was an issue with an app she was running. I have the black evo and made a exact copy of her phone. I never once had the issue.
Sprint ended up replacing it agian with a line that something was different in the white Evo from the black one that was causing the issue. Ever since that day she hasn't had a problem with her phone. I just rooted and did her rom last night.
My question would be does the phone get hot? Or feel hot? The reason I ask is that the phones processor may restart the phone (in effort to cool it down) randomly. That is something to consider.

Glad I got the black
sent from a silky smooth evo useing tapatalk
did I help? hit that lil thanks button then

Evo450 said:
I got my original Evo on launch day and it had the random reboot problem from the first month. It was very infrequent at first but after a few months it got worse and worse. Finally, one day it started rebooting in a loop while I was at work. I took it directly to a Sprint store where they ordered me a replacement. The replacement has been great. It reboots on it's own once in a great while (maybe once every two months).
This seems to be very common. The reboots I got when I flashed the Evo Classic ROM were as bad as my original phone was just before it got replaced. The difference is that is definitely software based because flashing the stock ROM fixes it. The reboots I had on my original phone happened when the phone heated up randomly and were not fixed by a factory reset.
Click to expand...
Click to collapse
I kept getting the same thing when i flashed classic. I went back to shooter port which runs butter smooth and is fantastic looking with sense 3.0.
DO THIS TO TRY TO GET EVERYTHING WORKING (no more soft reboot)
-connect your sd card to your computer
-copy contents to your computer for a backup
-copy PC36IMG.zip to your sd card make sure it is on root of sd card(attached to message)
-disconnect usb cable then pull battery
-enter bootloader (vol down + power)
-when it asks if you want to install the new update select yes
-after thats done pull the battery again
-enter bootloader then select recovery ( you should now have amonRa 2.3 )
-flash zip from sd card (vrsuperwipe.zip *thanks to virus*)
-go back and go into wipe menu, wipe dalvik-cache, wipe sdext, battery stats, and rotate settings.
-go to partition sd card and partition for a gingersense rom if you have not done so already. (0 swap, 1024 or 2048 ext2, remaining FAT)
ABOVE PROCESS COULD TAKE SOME TIME, MAKE SURE YOUR SD CARD IS MOSTLY EMPTY BEFORE YOU DO THIS (ONLY HAVE PC36IMG.ZIP ON IT)
-select usb mass toggle and connect to computer
-copy over your choice of rom, i suggest the shooter e3d port by team nocturnal.
-flash rom
-go to flash zip from sd card again this time select TeamNocturnal folder and pick a kernel to flash (try all of them if you would like, some phones run better with different kernels. mine runs well with HDMwIn kernel.
-wipe dalvik-cache one more time and you are ready to reboot with no more random restarts hopefully.
good luck - and please hit the thanks button if any of this works for you

Nandroid complications?

For the record, running amon ra 3.0.7...(I forget exact version, it's blue and uses capacitive back button) and I wiped everything 3 times before flashing the following ROMs.
Ok so the other night I went ahead and tried Deck's ICS ROM alpha 5. For the most part, a very beautiful port and can't wait till it stabilizes a little more. I can tell It's going to be a beast. But prior to flashing, I did a full nandroid like I always do, and TB backup. Flashed said ROM, tried to restore apps, few complications; couldn't restore games, certain apps such as zedge, or maps. Had to install from market because it would hang, but still restored data upon install. Figured this was due to the ROM having bugs....
Albeit beautiful, couldn't live without calendar, and certain apps wouldn't work. So I restored my decks 1.3d nandroid and instantly got hit with problems. Half my apps showed as properly installed, half of those actually worked without FC'ing. Downloaded maps cuz again couldn't restore, and instantly FC. So I reboot, and get constant FC's from random apps. So I wipe again, this time everything beside sd 4 times, still same problems. So since I wasn't on wifi to pull the ROM I uploaded to Dropbox, I simply did factory reset. TB now restored fine besides games which still puzzles me, but maps went fine.
I've had similar problems with Nandroid in the past. The only use I seem to get is just maintaining the ROM, everything else is fubar.
What is causing this? Is there a fix? Is it simply a pebkac? (Problem Exists Between Keyboard And Chair)
Sent from my OG Evo 4G via XDA app. Did I mention from inside my pocket?

I use that version and flash a lot. I've never had anything like that happen. Are you wiping everything except bat stats and SD? Did you try and fix permisissions? Do u run an ext3 or ext4 partition? Could there possibly be a problem with your SD card. Perhaps back everything on it up reformat and partition and restore your stuff to it. Maybe you could run a disk diagnosis program on your computer to see if there are physical errors?
Just a few suggestions

fitz420 said:
I use that version and flash a lot. I've never had anything like that happen. Are you wiping everything except bat stats and SD? Did you try and fix permisissions? Do u run an ext3 or ext4 partition? Could there possibly be a problem with your SD card. Perhaps back everything on it up reformat and partition and restore your stuff to it. Maybe you could run a disk diagnosis program on your computer to see if there are physical errors?
Just a few suggestions
Click to expand...
Click to collapse
Haven't tried fixed permissions as I just factory reset from in the ROM itself and restored apps as if a fresh ROM, but I will next time issue arises. I have no partition, but have considered doing so but keep putting it off. Been wanting to format my card and one by one out things back on it, but yeah, I wipe everything but bat, unless full, and sd. But I have noticed this issue usually only arises when I have already done a full wipe of everything and try to flash back. If I were to just flash over my current ROM, then restore back, everything works fine....kinda confused...
Sent from my OG Evo 4G via XDA app. Did I mention from inside my pocket?

Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.

This is a very sad story about my NoteII going bad.
I would describe myself as computer savvy and moderately experienced with Android. I equipped half of the family with various ROM-customized Android phones and am an enthusiastic Note user since it came out in 2011. Until now, I never had to ask a question in the forum.
Let me start in December 2012 when my NoteII arrived. I updated it, then came cwm and the monxdified ROM. For about a month I was a very, very pleased NoteII user.
Then, one day in Mid-January, I installed an app called "(root) Uninstaller pro", which began to auto-backup up all my apps to internal SD in a background process while I didnt notice. I only realized something had gone wrong when apps began to FC because no space was left on sdcard0. I removed the app and all the backups.
From the day after that , Play Store began to "randomly" refuse to update or install apps, because of "Not enough storage space available‎". Which was bull****. I literally had Gigabytes of free space on internal and external storage. For example, Play Store would refuse to update my tiny TB Pro key apk for "Not enough space" reasons but then happily install Asphalt7 and update Titanium Backup and Dolphin for me. Moreover, every affected app also does not install "manually" from apk. When removed, it can not be reinstalled, except via update.zip from the recovery.
Of course, I googled the error. I found no root cause explanation, just a bunch of hints. I deleted all app data from play store and various store-related apps. I deleted and re-setup my Play Store account. The usual suspects, cache and dalvik, got their wipe. Nothing helped. I downloaded the latest monx ROM and updated it from TWRP. Problem still there. Then my job required my full attention so I left the thing running with only partial updates for several weeks. After all, it still worked petty well.
Then, lately, I decided to tackle the issue again. I went to Settings and did a full factory reset WITH internal SD reformat. In TWRP, I did another factory reset and full wipe, then I flashed the latest (DMB2) monx ROM and restored from my TB backup.... "Not enough storage space available‎".
A friend suggested I should try "Fix permissions". Boy, what a bad Idea. From that moment, LBE Security guard caused a Hot Reboot every time I tried to use Active Protection. Many resets and wipes later, it still does today. I can only install it via update.zip, though, not properly reinstall it: "Not enough storage space available‎".
But all this still is only the beginning. I decided it was time to clean up the mess and factory resetted again (no SD wipe this time, after all it didnt help last time), took good old ODIN and completely reflashed with Stock XXDMB2. Result: Boot Loop. TWRP told me "cannout mount /data" and claimed internal and external SD to be empty (which was not the case). So I reverted to cwm6 and did a fullwipe/reset. Only after that, the newly flashed Stock DMB2 suddenly booted. I went on and reinstalled monxdified DMB2 (the very same zip that had worked before!). But regardless of what I tried, all I got was another boot loop.
Back to Odin, Stock again. This time (and every time after) it booted right away without needing help from cwm, BUT on the very first GUI ("choose country") it told me that UIDs were wrong and suggested to reformat /data. Wait, wasnt that what Odin just did? Instantly after this error, com.google.gapps did an FC. CWM to the rescue. This time, "fix permissions" seemed to actually fix them.
To make this long story a bit shorter, I reiterated though quite a number of futile attempts to install a booting custom ROM until 2am, and failed. Now I am on Stock DMB2 with a non-working LBE and only a handful of the most important apps restored. The "Not enough storage space available‎" problem is still here.
I wonder how the "Not enough storage" problem was able to survive so many flashes and resets. I am utterly helpless about how a Stock ROM, flashed from Odin can expose UID problems and FCs on first boot. Could this be a sign of a malfunction on the internal flash storage? If so, how would I be able to find out? Or could it be that this "uninstaller" did something nasty to the secure storage system of JB (which I dont have any idea of how it works and what it needs at all), at a point that all my wipes and flashes did not actually reach?
What else could I do to really, really reset every possible bit on this otherwise wonderful piece of hardware and possibly get rid of all those pesky problems (and back into a Custom ROM)?
Please help me to make this baby shine again!

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Ive read your story and i feel really bad for you. Good luck m8, if I had some knowledge id help you for sure but im new to android ) goodluck! Dont give up x
Sent from my GT-N7100 using xda premium

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Sent from my GT-N7100

Re: MegaWipe
UtkarshGupta said:
Do a mega wipe with recovery. Then install stock rom and nothing else. Don't restore stuff. Instead download them from play store.
Click to expand...
Click to collapse
Ok. So I found MegaWipe and put it on my SD-Card. I started it and the aroma Installer presented to me the Mega Wipe Option which I chose. A text screen appeared which said, that several partitions had been wiped but it happened in less than a second which I foudn to be suspicious. Then, when tapping "Next" again in the MegaWipe Aroma Tool, I found out Aroma was frozen and the recovery system did not react to any key press or tap anymore. I had to press the Power button for a while to get back into recovery where I flashed a ROM, then rebooted.
Guess what: all my apps were still present, the SMS history and Launcher fully intact. Dalvik had been wiped apparently (all apps re-optimized), though, and my Wifi AP settings were gone. Of course, the "not enough memory" problem is still here, too!
It appears like whatever problem I have, it also prevents me from using MegaWipe properly. Any more ideas?

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Try again.
Sent from my GT-N7100

Re: MegaWipe
UtkarshGupta said:
Try again.
Click to expand...
Click to collapse
Tried again. Twice. Internal SD contents were gone. Froze again after "Installation complete". Maybe that "Mega Wipe" took two seconds instead of one this time. The second time I tried flashing Omega after the wipe just for the kicks and that (full wipe Option in Aroma) apparently took my user data away, finally.
To my not-so-big surprise it greeted me with "Inconsistend System UIDs" right after startup, completely with the gapps FC I had already seen with stock so many times, now. This does not feel like real progress.
I have read around a bit. Maybe I should try to flash a multipart ROM in Odin with repartition? Appears to be pretty dangerous, though, and I dont know where to find one that matches my "DBT" CSC properly...

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
Flash latest stock rom for your country.
Sent from my GT-N7100

Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.

Re: Help! "wrong UIDs" right after flashing Stock!? and lots of other Problems.
u use CWM? i had a problem with cwm if i use aroma it always freeze use a other recovery and do the megawipes?? iam not very good at this but i wish you all the luck ..
Sent from my GT-N7100 using xda app-developers app

Re: MegaWipe
UtkarshGupta said:
Flash latest stock rom for your country.
Click to expand...
Click to collapse
XXDMB2 *is* the latest Stock ROM for my country. In my first post I described how I flashed it and it did not work out very well.
nameejokerx said:
Flashing stock that wipe ur internal and format sdcard.
Some stock rom dont wipe fully internal thus issue still exist even u flashing stock rom.
Click to expand...
Click to collapse
Yes, and which one would be such a ROM? I was not very adventurous with ROMS until now and did never flash multipart ROMs. I am afraid bad things could happen if I flash something with wrong CSC. Where exactly should I look for such a ROM and what do I have to take care of? Of course HOWTO pointers are welcome, too.
Sorry if this sounds too clueless but I really dont want to make things even worse.

Maybe SDS
Hi all,
after some more wiping and flashing, fiddling and tiddling and basically reinstalling everything from scratch, mostly without help from Titanium, I got my NoteII back to work. I only restored my most important app data, all apks reloaded from play store instead from backup, made several backups with twrp during this process. Two times, the "no space" problem came back and both times I basically reverted back to the last working backup from twrp. This way, I managed to turn it back into a usable system.
Not for long though, because two hours ago, in the midde of buying an ebook in kindle, my NoteII screen went black and now the whole thing is completely dead. I took out the battery for 10 minutes, but it won't come back on again; not even a download screen or battery loading animation.
So my problems might just have been the harbingers of its future death. I just read that "SDS" also affects some Note2 models and it has something to do with the internal storage which would be sort of a match for the symptoms I experienced. Looks like I'll have to send it in. Because of all the flashing and restoring I had not yet encrypted my internal storage and will have to change all passwords. Duh
I really should have stayed with my trusty old Note1 which never failed on me...