[XDA Assist] alwright1980:
I recently posted the following in the respective threads in order to elicit help. I got a couple of responses that were encouraging but nothing definitive, and definition may not be possible but i am gun shy right now and need input. I really just have a couple of qiestions. I need them answered to be as sure as I can that i can proceed with using original development without worrying too much of the risk.

It needs very much to be understood that I in no way at all think that using the programs and software or their developers are responsible for the consequences of my actions.

Please answer if you think you can help.

I recently hard bricked my device. A note 5 n920t that previously had run great on the stock oi6 rom with the arter97 kernel, stockymod and system less root. I was having a problem viewing anything streaming but Comercials within hulu and anything at all on netflix. I had spoken with tmobile techs and had been told I needed to take the cokc update to fix this. I tried but was unsuccessful in doing so, presumably because of the software alterations. So I updated via odin with a sammobile sourced .tar. i then tried to reinstate my software changes after performing my nand, using Philz touch cwm. After installing the ketnel however I did not allow the device to reboot, but rather proceeded with the stockymod. Then in rebooting I ran into permanent midnight. Black screen with no response from device at all.

What i need to know is, is it pretty safe bet that this lack of allowing to kenel to teboot and "take" the reason that i had device failure? Or is there another reason that i am missing?

. I didn't think it would cause any errors to flash two zips in a row. In fact almost all advanced recoveries have an "install multiple zips" option. I just had to figure that running the kernel script then the stockymod script might have been fine if that were all it were, but the diverse scripting involved in the aroma installer when debloating is where I figure the error occured. There is no caution against doing this. I thought that I had not followed directions, but arter97s install instructions as you probably know are quite simple and direct. And for that matter so is darkmans stockymod debloat method. One person said I may have just removed too much stuff and that that was a known problem with debloater scripts and to use ccleaner ro manually remove or disable. That is fine by me. I want to hold on to this unit, and I think I would have to go through insurance to get replacement this timeL. I didn't think it would cause any errors either. In fact almost all advanced recoveries have an "install multiple zips" option. I just had to figure that running the kernel script them the stockymod script might have been fine but the diverse scripting involved in the aroma installer when debloating is where I figure the error occured. There is no caution against doing this. I thought that I had not followed directions, but arter97s install instructions as you probably know are quite simple and direct. And for that matter so is darkmans stockymod debloat method. One person said I may have just removed too much stuff and that that was a known problem with debloater scripts and to use ccleaner ro manually remove or disable. That is fine by me. I want to hold on to this unit, and I think I would have to go through insurance to get replacement this time

Lastly what potential errors would I face in restoring data partition to a new rom from an old rom of a different sort either if between ones that are both tw based or not like stock==> almost stock or stock==>cm remix or cm13 and in reverse.