04-13-2012, 03:43 PM | #46 | |
Connoisseur
Posts: 59
Karma: 57554
Join Date: Jan 2012
Location: Romania
Device: Kindle Touch
|
Quote:
All you need to do is create the diagnostic_logs on the root of your Kindle partition and create an empty device_info.xml in it. You should end with the following structure: K:\diagnostic_logs\device_info.xml (assuming K:\ is your Kindle) |
|
04-13-2012, 03:54 PM | #47 | |
Zealot
Posts: 100
Karma: 6058
Join Date: Aug 2009
Device: Kindle Paperwhite, Kindle Touch as backup
|
Quote:
|
|
04-13-2012, 04:06 PM | #48 | |
Connoisseur
Posts: 59
Karma: 57554
Join Date: Jan 2012
Location: Romania
Device: Kindle Touch
|
Quote:
And you must create it on the root of the kindle, not in any folder. Last edited by wolftail; 04-13-2012 at 04:08 PM. |
|
04-13-2012, 04:07 PM | #49 |
Zealot
Posts: 100
Karma: 6058
Join Date: Aug 2009
Device: Kindle Paperwhite, Kindle Touch as backup
|
|
04-13-2012, 04:10 PM | #50 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
|
|
04-13-2012, 04:12 PM | #51 |
Connoisseur
Posts: 59
Karma: 57554
Join Date: Jan 2012
Location: Romania
Device: Kindle Touch
|
|
04-13-2012, 04:13 PM | #52 |
Zealot
Posts: 100
Karma: 6058
Join Date: Aug 2009
Device: Kindle Paperwhite, Kindle Touch as backup
|
OK. I did that. Blank text file, no extension, in the root. The device_info.xml in the diagnostic_logs folder ... restart. No dice.
|
04-13-2012, 04:17 PM | #53 | |
(offline)
Posts: 2,907
Karma: 6736094
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
Following this, I have updated the wiki as well (tried to restructure things so they don't get out of hand), and it seems like we ran into an (edit) conflict. Could you please check the latest version, just to make sure it's ok? |
|
04-13-2012, 04:18 PM | #54 | |
Connoisseur
Posts: 59
Karma: 57554
Join Date: Jan 2012
Location: Romania
Device: Kindle Touch
|
Quote:
I'm pretty sure that when I started writing, your message wasn't posted yet but I was going through diagnostics to test everything while writing so I ended up posting it after you. |
|
04-13-2012, 04:19 PM | #55 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
For those who did not understand the purpose of the two linux commands I posted, they go in the RUNME.sh file, or better yet, the payload dropped by data.tar.gz. They do nothing unless the folder or file are missing, in which case they are created. All automatic, with no manual steps or worry by the end user. The USER does not need extra steps. Those are part of the payload...
Here they are again: mkdir -p /mnt/us/diagnostic_logs touch /mnt/us/diagnostic_logs/device_info.xml More details here: https://www.mobileread.com/forums/sho....php?p=2041719 Last edited by geekmaster; 04-13-2012 at 04:23 PM. |
04-13-2012, 04:33 PM | #56 |
Connoisseur
Posts: 59
Karma: 57554
Join Date: Jan 2012
Location: Romania
Device: Kindle Touch
|
Looks perfect to me. I only made minor edits to make things clearer but your version is actually a lot easier to understand and follow.
|
04-13-2012, 05:31 PM | #57 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Why aren't those linux commands in the jailbreak installer or payload?
|
04-13-2012, 06:05 PM | #58 |
Connoisseur
Posts: 59
Karma: 57554
Join Date: Jan 2012
Location: Romania
Device: Kindle Touch
|
No one updated the payload yet because it was easier to add one extra step in the instructions. Adding the device_info.xml creation in the payload should make things a bit easier for everyone.
|
04-14-2012, 12:18 AM | #59 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
The Universal Jailbreak needs another step:
After the "You are Jailbroken" file appeared, my "Update Your Kindle" menu option was still grayed out after I copied an update install package to my touch (fw 5.0.4). I needed another restart not listed in the jailbreak instructions before the "Update Your Kindle" menu option worked. So, I suggest adding another restart AFTER the "You are Jailbroken" file is installed. This should help avoid some confusion... EDIT: This universal jailbreak is nice. It has a lot more restarts and other steps than using my simple one-step "secret" jailbreak, but we are saving that for when we need it, and as long as this "more complicated" method is well-documented and people follow the instructions, it will do the job just fine. Also, after I installed the new diags partition that comes on new kindles, I am happy to say that the universal jailbreak recommended in this thread works fine on it too (except for the extra restart needed before any packages can be installed). Last edited by geekmaster; 04-14-2012 at 01:16 AM. |
04-14-2012, 02:48 AM | #60 |
Junior Member
Posts: 8
Karma: 10
Join Date: Mar 2012
Device: KT
|
5.1, jailbreak and no ads
Hello, I tried diag method yesterday and found a solution too. It is enough to go to Device Settings in diagnostics and mandatory file is created . But I have another problem. After factory reset I lost disabled ads, but cannot find a solution to disable them again. Old method used data.tar.gz method and JB_RUNME.sh. Do I need use data.tar.gz and RUNME.sh + booting into diagnostics partition to remove ads again?
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kindle Touch 5.0 Jailbreak | yifanlu | Kindle Developer's Corner | 246 | 01-03-2013 04:57 PM |
Kindle Touch Jailbreak Support Team | geekmaster | Kindle Developer's Corner | 39 | 01-14-2012 05:26 AM |
iPod Why jailbreak an iPod touch | Donnageddon | Apple Devices | 3 | 03-27-2011 01:55 PM |