Kindle 4 NT (4.1.0 fw) Hacking help

[mog]

Thank you guys for all your help. I can now put custom screensavers on my kindle ( creation of a "screensaver" folder ).

geekmaster: "(...)lot less willing to defend amazon after all the hostile updates that break custom apps in 5.1.0 and 4.1.0 firmware."

..have anyone found a way to run Developer application ( kindlet ) on my Kindle NT 4.1.0fw?

[geekmaster]

Originally Posted by mog

Thank you guys for all your help. I can now put custom screensavers on my kindle ( creation of a "screensaver" folder ).

..have anyone found a way to run Developer application ( kindlet ) on my Kindle NT 4.1.0fw?

There are reports that the jailbreak works on 4.1.0, which then allows kindlets. There are some kindlets (hopefully more get indexed later) in the Master Index sticky, kindlet category. Some kindlets should work on any kindle model, and some may depend on features specific to certain kindle models. If you have not installed the jailbreak, check out the K4 hacking wiki (linked into the K4 category of the master index).

[mog]

"Ixtab" Simple JailBreak Method(Alternate way of gaining Root Access)

Download http://dl.dropbox.com/u/16679763/kin...lbreak-1.0.zip
Unzip
Copy RUNME.sh and data.tar.gz to your Kindle
Reboot from settings menu (Settings, then press the "options" button again)
Don't be alarmed if all your books aren't there! In 5 seconds for me they refreshed back.

i have fallowed the lxtab jailbreak ( until now, everything ok ) and now, what is the next step i need to do, to make my kindle open Kindlets ?


PS: do i need to follow "Enable ssh access through wifi" or "Internet Access for Kindle4NT via a Windows XP computer" ?

[poomex]

Originally Posted by Gondolkodo

You just have to SSH into the kindle (e.g. with the USBnet-methode) and then create a RUNME.sh in the /mnt/us with the following content:

mntroot rw
if [ ! -f /var/local/adunits.bkp ]; then
	mv /var/local/adunits /var/local/adunits.bkp
	touch /var/local/adunits
fi
mntroot ro

Save, exit and make the following:

chmod +x /mnt/us/RUNME.sh; mntroot rw

Make a backup about the mntus.params file with this:

cp /var/local/system/mntus.params /var/local/system/mntus.params.BKP

Extend the original mntus.params with the followings:

if [ -e /mnt/us/RUNME.sh ]; then
	sh /mnt/us/RUNME.sh
fi

If you would like to see a log then change the "sh /mnt/us/RUNME.sh" with "sh /mnt/us/RUNME.sh > /mnt/us/RUNME.log"

If you are ready, just create and link the screensaver folder, just like before:

mkdir /mnt/us/screensaver
mount /dev/mmcblk0p1 /mnt/base-mmc
mv /mnt/base-mmc/opt/amazon/screen_saver/600x800 /mnt/base-mmc/opt/amazon/screen_saver/600x800.bkp
ln -sfn /mnt/us/screensaver /mnt/base-mmc/opt/amazon/screen_saver/600x800
exit

As far as I know this is the only black/hackway and there's no "block the ads" and "put screensavers" hack.
I tried it on my own K4 NT SO, works.

From what I have tried to remove the ads it looks like it's enough to do:

	
mv /var/local/adunits /var/local/adunits.bkp
touch /var/local/adunits

You don't need to create the script.

[knc1]

Originally Posted by poomex

From what I have tried to remove the ads it looks like it's enough to do:

    
mv /var/local/adunits /var/local/adunits.bkp
touch /var/local/adunits

You don't need to create the script.

Just don't forget to revert that change before trying to do the next firmware update that Amazon pushes to you.

[nikiiiva]

Hi,
how do you revert change before applying next firmware, and does it have to be done even if I do only factory restore without update? Is that necessary for Gondolkodo's instructions also?

Thanks

[knc1]

Originally Posted by nikiiiva

Hi,
how do you revert change before applying next firmware, and does it have to be done even if I do only factory restore without update? Is that necessary for Gondolkodo's instructions also?

Thanks

The steps shown do:

• Renames a directory ('mv' move to another name)
• Creates a file by the same, original directory name

To revert those changes do:

• Remove (rm) the file that was created
• Rename the directory to its original name with ('mv' from the backup name)

If you let Amazon push you an "automatic" update (v4.1.1?) then it may: install, fail with an error code, or brick the machine.
Can't say which, that update hasn't been shipped yet.

If instead you get the next update (v4.1.whatever) from the Amazon support site, then you have a chance to be sure the original directory and files are back to "factory state" before you install the manually downloaded file.

[nikiiiva]

So if I understood correctly, I will have to manually change all files to their original state before I do either factory restore to the same firmware or update to the new one when it comes? Also I do not understand what "automatic" update means? I downloaded firmware from amazon and copied it to my device when I updated.

Thanks

[geekmaster]

Originally Posted by nikiiiva

So if I understood correctly, I will have to manually change all files to their original state before I do either factory restore to the same firmware or update to the new one when it comes? Also I do not understand what "automatic" update means? I downloaded firmware from amazon and copied it to my device when I updated.

Thanks

Modern kindles frequently brick themselves WITHOUT any hacks. Hacks just hasten the process.

[knc1]

Originally Posted by nikiiiva

So if I understood correctly, I will have to manually change all files to their original state before I do either factory restore to the same firmware or update to the new one when it comes? Also I do not understand what "automatic" update means? I downloaded firmware from amazon and copied it to my device when I updated.

Thanks

No.
That is not a general requirement, I was specific in my earlier post.

The "factory restore" does not do what it sounds like outside of the en_LAB126 dialect.

Automatic means the updates which Amazon will download onto your machine while it is connected to Wifi. The machine will then automatically install that update in the process of going to sleep the next time.

What you did is what I meant by a "manual update" - you where in charge of what and when.

[nikiiiva]

Ok. Now I understand. Thanks. Is there any way to disable OTA update?

[knc1]

Originally Posted by nikiiiva

Ok. Now I understand. Thanks. Is there any way to disable OTA update?

Several.
I can not recall if they are indexed.

If you find them (the threads and/or wiki pages) include them in a post as links and I will be sure they get put into the index.

[nikiiiva]

Originally Posted by knc1

Several.
I can not recall if they are indexed.

If you find them (the threads and/or wiki pages) include them in a post as links and I will be sure they get put into the index.

Found them. Here there are, https://www.mobileread.com/forums/sho...d.php?t=169150. There are several methods but no one confirmed that they work on K4 NT. When I try, I will report back there.

[Ot70]

Originally Posted by Gondolkodo

You just have to SSH into the kindle (e.g. with the USBnet-methode) and then create a RUNME.sh in the /mnt/us with the following content:

mntroot rw
if [ ! -f /var/local/adunits.bkp ]; then
	mv /var/local/adunits /var/local/adunits.bkp
	touch /var/local/adunits
fi
mntroot ro

Save, exit and make the following:

chmod +x /mnt/us/RUNME.sh; mntroot rw

Make a backup about the mntus.params file with this:

cp /var/local/system/mntus.params /var/local/system/mntus.params.BKP

Extend the original mntus.params with the followings:

if [ -e /mnt/us/RUNME.sh ]; then
	sh /mnt/us/RUNME.sh
fi

If you would like to see a log then change the "sh /mnt/us/RUNME.sh" with "sh /mnt/us/RUNME.sh > /mnt/us/RUNME.log"

If you are ready, just create and link the screensaver folder, just like before:

mkdir /mnt/us/screensaver
mount /dev/mmcblk0p1 /mnt/base-mmc
mv /mnt/base-mmc/opt/amazon/screen_saver/600x800 /mnt/base-mmc/opt/amazon/screen_saver/600x800.bkp
ln -sfn /mnt/us/screensaver /mnt/base-mmc/opt/amazon/screen_saver/600x800
exit

As far as I know this is the only black/hackway and there's no "block the ads" and "put screensavers" hack.
I tried it on my own K4 NT SO, works.

Thank you so much man, you gave me a knowledge!!!

[jack_slapped]

Originally Posted by poomex

From what I have tried to remove the ads it looks like it's enough to do:

	
mv /var/local/adunits /var/local/adunits.bkp
touch /var/local/adunits

You don't need to create the script.

I know this is kind of an old thread, but I was wondering if anyone could help me out with removing the ads off of my kindle 4 NT. I tried using these lines of code and got access denied. The username I used was "framework" password "mario". As none of the root usernames would work for me.

I wanted to try this method, but I wasn't exactly sure how to do it. So I decided against it. If anyone could shed some light on how to remove ads on the 4.1.0 firmware I would be very grateful. All the information on the wiki seems to be outdated.

mntroot rw
if [ ! -f /var/local/adunits.bkp ]; then
	mv /var/local/adunits /var/local/adunits.bkp
	touch /var/local/adunits
fi
mntroot ro

Save, exit and make the following:

chmod +x /mnt/us/RUNME.sh; mntroot rw
Make a backup about the mntus.params file with this:

cp /var/local/system/mntus.params /var/local/system/mntus.params.BKP

Extend the original mntus.params with the followings:

if [ -e /mnt/us/RUNME.sh ]; then
	sh /mnt/us/RUNME.sh
fi

If you would like to see a log then change the "sh /mnt/us/RUNME.sh" with "sh /mnt/us/RUNME.sh > /mnt/us/RUNME.log"

If you are ready, just create and link the screensaver folder, just like before:

mkdir /mnt/us/screensaver
mount /dev/mmcblk0p1 /mnt/base-mmc
mv /mnt/base-mmc/opt/amazon/screen_saver/600x800 /mnt/base-mmc/opt/amazon/screen_saver/600x800.bkp
ln -sfn /mnt/us/screensaver /mnt/base-mmc/opt/amazon/screen_saver/600x800
exit