The only thing that I know now is what I’m able to see at this moment: Color orange white of the Boot loop, Fast boot picture and Fast boot command answers, comunication OK.
I can reach Fast boot with a self build factory cable. (Shows red "Fast boot"letters on top of the display, green light blinking, red off, no loop)
(For communication with the KF2-7 after Fastboot I have change over to a normal USB cable in respect that my homebrew factory isn’t so nice)
Fast boot gives normal answers, reacts normal and show answers like that:
C:\KF7>fastboot -i 0x1949 getvar product
finished. total time: 0.000s
C:\KF7>fastboot -i 0x1949 devices
From that point I guess that I’m dealing with a simple 2nd gen KF7 (Without HD) , easy to brick while making jokes with a wrong Boot image from KF7 1st Gen - for example.. . Right? Right?
Then I just tried:
fastboot -i 0x1949 erase cache
OKAY [ 71.337s]
finished. total time: 71.337s
fastboot -i 0x1949 erase userdata
finished. total time: 184.179s
Instruction worked but it changed anything, boot loop continues. I guess now as a nobo and limited Know How that may be the system is damaged and had to be re-flashed. (Also don’t have the right system .img or original backup .img’s from the device) I don’t want to use first aid flash fast boot or recovery at this moment. It’s because I have no info what was the original state of that KF2-7. I don’t want to brick it so close from a working device with innecessary actions, trial and error, flashing wrong files a.s.o. Now it doesn’t show so bad to recover the device without any brick.
What’s your indication for the next step regarding this specific situation?