Beforehand: Sorry for asking. I was sure this wasn't duplicate.
I have made myself a soft brick. The story: used kingoroot or something similar, then was too much in a rush hitting the "yes, please, ruin my rooted device via a firmware update!" button.
Now I made it to this exact situation:
- I can reach recovery mode
- I get the right answer when testing for root in recmode
- I think I got the right rom file but it wont install correctly neither from adb sideload nor via applying it from external sdcard
My guessed salvation: updating the bootloader because I think this gives me the problems with sideloading. I'm here to ask if this is correct and if so how one does so.
Apparently I made some mistakes. The rom archive lists some roms that are neither tagged by OTA nor by a build number (I think I have to choose one of those because None of the ones that have a build number have the one I need). I need build number B116 because it says so an the recovery screen. I choose this one because I am a native german speaker. Is this the correct file?
I unpacked the file and found a file named update.zip containig something that looked like a system. I tried to sideload it and I tried to apply it from sdcard both didn't work.
Whenever I try to sideload the rom sideload gets stuck at 52%. Trying to install it via sdcard results in abort.
The most successful way seems to be installing from sdcard which I reread how to do here. I forgot to put the package into a directory called dload. When doing this installation does not abort in a split second but rather a few seconds later saying can't install this package (2016 02 27 17:38:09 CST over newer build (Thu May 4 14:58:09 CST 2017) shame is, that the newest non-OTA builds are all older than the given date.