[Kindle Fire HDX 7" & 8.9" General] meteorrock:
Singing for your freedom || wildcatter and logcatter

Ok then, we got to get up a port up on this device for testing. He is looking in. (<fattire> is). Its a go for a proceed. Help each other and its done. :)

____________________

Riddle code and hints:

♪ Looking for keys.....................* bash: syntax error near unexpected token `||' *................recompiling signature code...................side project to proceed for the team here...................Looking for *universe mode*...............closing pipes.............Improving code............stack overflow.com..................GNU for freedom.... ♪

Netbeans misspelled. Recompiling for a go ahead..................replace p with funny tongue stick out, it is an error.............work at it team. It will compile. Do Not forget the ::; one is missing when you pull out funny face. Its by the push::pull...............ok then. Debug the code. See why you put code into a box on XDA? Use this method here ~

~ ~

~. Ok team. ~Enough hints for today. I will check back in, in a few days. Listen to Miley Cyrus * Adore you* for today. BTW the ~ is your home now in bash. :wink:

________________________________

UPDATE: THEY have a bounty set up for the first person to want to crack that bootloader here. Here is the link for that. Ok guys, you are good to go. Good luck. Make sure to read the instructions. Have faith and freedom, you will make it happen. I am there looking. http://xdaforums.com/showthread.php?p=51351456

Ok guys , this is getting to be a tutorial, but here is the link for that uboot image. It is up on the github. You will need to recompile that image and look for bugs. You see those red highlighted lines in there? Take those lines out. Every folder in there needs to be scrubbed for an unbroken bootloader. It was up for 2 whole years and you guys did not know. But I will help you along for some good money. Every last one. Dig down into the source code inside those files. Do NOT mess with the driver folder until later. Start up at the top file, mod it, then recompile and see if it boots up. And work your way down if it does NOT. You might have to modify the makefile some.That is how it is done. BTW <.mk> is your makefiles. < .c > is your C language. Its tedious, but who knows? It has to compile without errors, everyone. If you get an error, redo. ~ ~Ok Larry. Make it yours. I will be back in 3 days. https://github.com/KFire-Android/kf_u-boot

_____________________

Ok, I do NOT penalize others for their lack of speed. One week. It will take time and determination. Now you know. Its the hard way, but a good way to learn. :) <Leaplinlar>, I am going to make you or someone rich. I already have money. Make sure to use apt-get for your tools. Well, you know. :) Dont forget that "common* folder. ADB up, if that device supports it. Your good. ```````````Ok we are set. Ok larry. We got boot? Recompile..............yep. Sneek peek and look. Ok enginner. see ya in a few days.

Ok, he has boot.............recompile........... you got an opps? Ok then. There you go. Work that debugger tool..............Keep working that debugger tool. You will get it..Anyway you work together. You can rip that bootcoder in no time. Yeah, its 2 am here. You got files? I got ya back in the dropbox. There ya go. You got to clean it up <leaplinlar>. See ya. Claim bounty. Make sure that code is proper. See Ya. Nice working with ya. See what teamwork up in IRC will get everyone? :) Luv ya all.

BTW check here. He has his uboot.bin image. You will need to debug and clean it up. http://stackoverflow.com/questions/18856801/what-is-difference-between-u-boot-bin-and-uimage-bin

___________________

Ok team. Start looking over the header files next. That is the next step. Ok then. < .h> files. Nice. :) Its crude, but its up. Do not let them persade you from your dreams. Click. bye bye IRC. That is how you do it. ..........For awhile. Use *whois*, it will bring up your IP addy. Use a mask. All they do it talk. Now you know. No more hints. Do not let them drag you down. Use a different call name. Yep. It was me. :kiss: Now you will have to clean up that code for a LONG time. Just like at nook color.

Ok guys, it was not a troll. Here <leaplinlar> I am not that cruel or mean. Check this link. http://superuser.com/questions/528816/how-to-hide-public-ip-adress-on-irc-channel

You have to STOP thinking children (was I a kid today?) can NOT code. Its your next step up here. Ok then. Check your dropbox and look at it. Get coding. I am still your queen. Peaches.

______________________

Ok guys. I am flying blind. Take that reworked code and rewrap it up into a uboot.bin. I am using this anology as striking crude oil. You will have to refine the code here on out. You got source code. That red highlighting on the github is thier onboard diff tool. You remember those? You dont need a frontend debugger tool. Use gdb for a final conclusion. Use the terminal to guide you. Some of you might feel more comforable with a userface like Kdevelop. I do not use one. Here is one more link to help get you started. I reworked the whole mainline kernel code on the nook color once, it only took me 120 hours from start to finish. Along with the user face. So you will need determination and time here. Do that on the linux side for further use. See the software stack on android(operating system) on wikipedia? Use that diagram and look it over for abit. Check over this link in the meantime for a wrap up. http://www.wiki.xilinx.com/Build+Uboot

Here is another link here to do it in the terminal. Follow the other links in there to get help.http://stlinux.com/u-boot/introduction

Those RSA keys will be stored on your RAM memory for retrival on bootup. Lets look for a workaround on that in the next few days.

Ok guys, Those keys might be generated on the amazon server side. Lets look up Nmap for a workaround on that.

It leaked out. Do not update that amazon kindle fire until further notice. There it goes. They are changing something. Use strace command. Ok then. Ok I almost have it. They got a leak up in the call stack. See if you can probe up in there. There in. Try to pull those keys out of the server. Yep. They got em. Ok I am out for awhile. Opps. Went black hat on ya.

_________________

Ok guys. Before we continute. UPDATE those headers in linux. We got security updates for you to proceed. Check over your iptables and see if they are up to snuff. Also check over your network in virtualization. Use a bridged network IP addy. (DHCP) instead of NAT. If you do not have linux in virtualization, stop now or you will get caught. Check over bridged network and mask your ip addys in that Vmware. Look over the options. Were going in. You see, the admins always take the easy and lazy way out. So you will have to fight to find those keys up in that callstack. If you do not understand these questions, its ok. Copy and paste buzz words. Look over all of that information to get up to speed online today. You will have to filter through that callstack up in there on that server. Look online on updating IP tables. Ok, <Phoenix>. She is up in the protocol stack. Shhhhhh. Don't get caught. :) Regenerate that mac address every 15 minutes up in there. Check advanced options on network adapter.

sudo apt-get update && sudo apt-get upgrade

sudo apt-get install nmap