Hi everyone! Playbook Doubt! Can someone help?

[quackquack147]

Hi there,
I am planning to port other OS like Debian obviously to playbook and android for android lovers. i am sick and tired of their OS.
TI OMAP3/4/5 got 2 stage booting. First stage only inits the cpu and then chain loads into second stage bootloader.
here in playbook both the stages are encrypted and or signed, i am not sure which one is true of they both are true or they are both lies.
Now i am stuck with this question. what can the cfp do?
lets say i want to upload my first stage bootloader using it. and it does well and i go to next stage. 1 st stage loader is called x-loader or MLO and the second stage is called u-boot.
reading the howto i understood i can load the first stage loader and also second stage boot loader.
now my question is what if the loader which i compiled from source and also loaded DOESN'T WORK and i need to debrick the process. can the cfp then load the factory default loader and restore the device?
and then i can debug and finally put the first stage loader which chain loads to second stage loader?
i am almost done with everything compiling source and et al. i need to know this first because if i fail to do so then the next thing is uart usb debug. if i fail with that too then i need to jtag the device.
so can some understanding fellow here help me with this doubt?
can the cfp debrick a device whose bootloader i have nuked? first stage loader. since first stage loader is extremely important w/o it second stage loader wont get triggered.
please try to reply quick as my work is stuck because i dont have the answer to this question.
and can someone also explain how to go about doing it if the first stage loader is screwed up and its unable to go to next stage then how do i debrick it?
thanks in advance to anyone/everyone who helps me with this issue.
thanks
-paul