Now when I try to update I get the U006 error, I have tried putting a data.tar.gz and _RUNME file into my Kindle directory and restarting etc. but get no screensaver folder created and still receive an error when updating.

Is there anyway to undo what I have done without having backups or can I restore my Kindle to how it was originally?

If you updated to FW 4.1.0, you'll have to follow the directions in the wiki to jailbreak your device via diags, enable usbnet, then you'll have to restore your screensavers over SSH. (Hopefully the stuff you followed made you do a backup somewhere...).

(FW 4.1.0 broke the data.tar.gz stuff on *main*)

If the failing update you're speaking of *is* the 4.1.0 official update, then, yep, what knc1 said, complain to the right people . (You don't necessarily need to do a full downgrade, just to restore the default screensavers).

Next time, try to understand the implications of stuff you're blindly following . [Yes, I'm a bit tired of the whole screensavers mess on the K4, it's not like there wasn't any update/idiot-proof code out there when the K4 was released...]

Now when I try to update I get the U006 error, I have tried putting a data.tar.gz and _RUNME file into my Kindle directory and restarting etc. but get no screensaver folder created and still receive an error when updating.

Is there anyway to undo what I have done without having backups or can I restore my Kindle to how it was originally?

I am using the Kindle 4 non touch version.
Thanks,
~arkarain

Isn't this a question for the author of that video?
I.E: Your in the wrong place.

I HAVE contacted the author of the video, but have no reply as of yet, I posted on here because I may get a faster solution this way and it stands to reason that the author isn't the only one who knows a solution to this.

If you updated to FW 4.1.0, you'll have to follow the directions in the wiki to jailbreak your device via diags, enable usbnet, then you'll have to restore your screensavers over SSH. (Hopefully the stuff you followed made you do a backup somewhere...).

(FW 4.1.0 broke the data.tar.gz stuff on *main*)

If the failing update you're speaking of *is* the 4.1.0 official update, then, yep, what knc1 said, complain to the right people . (You don't necessarily need to do a full downgrade, just to restore the default screensavers).

Next time, try to understand the implications of stuff you're blindly following . [Yes, I'm a bit tired of the whole screensavers mess on the K4, it's not like there wasn't any update/idiot-proof code out there when the K4 was released...]

Thanks for the help but the problem is that I'm not able to update to firmware 4.1.0, I actually want to remove my screensavers

@arkarain: Then see my first paragraph, it also applies on FW 4.0.x. Either restore default screensavers over SSH, or adapt the runme script from the K4 #I_can't_update_to_4.1.0 wiki page to the stuff you did. (That implies you have a backup of the default screensavers somewhere, or extract them from the forensic K4 images).

Or, join the 'hitting a nail with Mjolnir' fellowship, and follow the debricking stuff to downgrade to 4.0.x.

@arkarain: Then see my first paragraph, it also applies on FW 4.0.x. Either restore default screensavers over SSH, or adapt the runme script from the K4 #I_can't_update_to_4.1.0 wiki page to the stuff you did. (That implies you have a backup of the default screensavers somewhere, or extract them from the forensic K4 images).

Or, join the 'hitting a nail with Mjolnir' fellowship, and follow the debricking stuff to downgrade to 4.0.x.

Thanks for the clarification, I'm a bit of a noob to this kind of stuff and probably shouldn't have used such a complex method in the first place like you said. I'll try the methods you suggested if I can work out how to do them :P

README:
The video references /mnt/us/screensavers in the "DIAGS" file system - which may be an error unless the "DIAGS" mode has mmcblk0p4 mounted at the same point that the "MAIN" mode has it mounted.
(mmcblk0p4 is the device that holds the FAT-32 file system that the user sees as the "USB storage" over the cable when in normal operation.)
PS: It is not a "propriatary USB cable".

You can check if the above is so by entering the command:
mount
without any arguments and read if/where /dev/mmcblk0p4 is mounted (and if it is mounted read/write).

README:
The video references /mnt/us/screensavers in the "DIAGS" file system - which may be an error unless the "DIAGS" mode has mmcblk0p4 mounted at the same point that the "MAIN" mode has it mounted.
(mmcblk0p4 is the device that holds the FAT-32 file system that the user sees as the "USB storage" over the cable when in normal operation.)
PS: It is not a "propriatary USB cable".

You can check if the above is so by entering the command:
mount
without any arguments and read if/where /dev/mmcblk0p4 is mounted (and if it is mounted read/write).

Thanks a lot! Only got a chance to try this just now and it worked brilliantly first time, only note I have to someone else who needs to try this is that the root password mario may have changed so you should use this link http://members.ping.de/~sven/kindle.html
and look under the 4.0.1 part.

Thanks a lot for the help I would not have been able to figure that out on my own and I doubt the Youtube user would either

Thanks a lot! Only got a chance to try this just now and it worked brilliantly first time, only note I have to someone else who needs to try this is that the root password mario may have changed so you should use this link http://members.ping.de/~sven/kindle.html
and look under the 4.0.1 part.

Thanks a lot for the help I would not have been able to figure that out on my own and I doubt the Youtube user would either

Post it the comments section of that youtube thing if you wish.
(You might want to edit out my non-technical comments)
Plus your own additions above.

I HAVE contacted the author of the video, but have no reply as of yet, I posted on here because I may get a faster solution this way and it stands to reason that the author isn't the only one who knows a solution to this.

There are many pages of comments on that video page, many complaining about problems. Too bad he does not care enough to respond (unless he does not understand how it worked but just blindly followed instructions he found here)...

It would be nice if people who make videos give a little credit to those who CREATED the information he is using in his video.
Also, on the K3 with diags SSH installed at the factory, the entry barrier was MUCH TOO LOW for noob "developers", and there are a LOT of poorly tested (even dangerous) hacks created by those who may not have tested them adequately (especially making them "future proof" to not damage kindles with firmware updates).

At least with the hacks that need a jailbreak (update*.bin files), the author of the hack needs to learn enough to package and sign his hack for each kindle version, which implies that he knows enough to test it properly.

BEWARE the source of your hacks, and check what problems others have had with it (especially firmware version incompatibilities), before just blindly following instructions.

ALSO, it is a good idea to treat these instructions as a GUIDE. When following a cooking recipe, you need to know enough about cooking to NOT set your hair or clothing on fire, and kindle HACKING requires a similar skill set.

There are many pages of comments on that video page, many complaining about problems. Too bad he does not care enough to respond (unless he does not understand how it worked but just blindly followed instructions he found here)...

It would be nice if people who make videos give a little credit to those who CREATED the information he is using in his video.

Credit where credit is due is always nice.
And in this case, perhaps that author's readers would have known where to find the answer to the problem the author had created.

arkarain updated the comments section of that video, so that may lessen one source of these "E006 Help Me" posts.

I left the anger in my post on purpose, unprofessional as it was, because I decided that it didn't hurt readers to know that having to fix someone else's plagiarized hack pisses a person off.

Credit where credit is due is always nice.
And in this case, perhaps that author's readers would have known where to find the answer to the problem the author had created.

arkarain updated the comments section of that video, so that may lessen one source of these "E006 Help Me" posts.

I left the anger in my post on purpose, unprofessional as it was, because I decided that it didn't hurt readers to know that having to fix someone else's plagiarized hack pisses a person off.

Like the Russian website that even copied my personal screenshots from the Select Boot thread (and my custom u-boot images and profiles)? At least he relented (a little) and provided a link-back later, but no mention of "geekmaster" (or other devs here, or even MobileRead) anywhere on his web page.