Wow, I see. I did not know it was that big of a deal for people to use it. I will hold off on just trying it for the fun of it. Personally, I am the type of Linux guy who does dd everything and restores fresh as it is far easier than all of the uninstalling and then reinstalling. But from what you are telling me, it sounds like it may not be a good idea to use it.
On another note, I thought about also trying the following, something I think I figured out four years ago when I got mine. (Note, I did do a back up back then.) I know this isn't directly related to the browser not working but it might hopefully make it all back to factory default again. I just was not 100% it is the correct method as I asked others but never got a response.
Code:
Backup:
dd if=/dev/mmcblk0p1 of=/mnt/us/mmcblk0p1.bin bs=1024
Restore:
sudo su # Become root, so you don’t need to sudo everything
fdisk -l # Look for your Kindle’s identifier, something like /dev/sdc, a 2GB drive with 4 partitions. using /dev/sdX here to represent drive
mkfs.ext3 /dev/sdX2 # Make a ext3 partition for /var/local
dd if=/mnt/us/mmcblk0p1.bin of=/dev/sdX1 bs=1MiB # This will take a long time to finish
UPDATE:
I solved it. After removing all of my hacks, one by one, I factory resetted, and the browser works. Then, I elected to not install two of them, Doukan and Kite, since I never used them. Sure enough, the browser still works.
So it probably was Doukan. The reason I thought the browser worked with Doukan installed was what worked was Doukan's browser, not Kindle's webkit one.
Anyway, Idk why it did not work with Doukan installed, but it is not that important to me why.
Thank you for trying to help. Again, it looks like it probably was Doukan, as you stated.
I would still be curious if my restore method is correct, though, since one never knows in the future. Thanks again.