In a desperate attempt to remove "Kindle Feedback" from Home screen after KindleBreak, a user from 4PDA got boot loop on their Kindle Oasis 3.
The user did "chmod /var/local/ 255" from SSH over WinSCP to attempt to block write permission. The result is that Kindle in now in boot loop.
- Kindle Oasis 3
- FW 5.12.4, JB by KindleBreak
- No Rescure pack or Coward's Rescue Pack
- Storage is accessible during boot loop
- Kindle had Wi-Fi turned on before that
Tried the following, to no avail:
1) put update_.bin - Kindle says "Repair needed"
2) ENABLE_DIAGS doesn't work (no Rescue pack)
3) Changing usbnet's config to use Wi-Fi only and adding "auto" file to /usbnet/ didn't help - Kindle is not accessible with WinSCP
4) Kubrick didn't help, Kindle has only one partition /dev/sde (or /dev/sdd sometimes) instead of "mmcblkpN..." parts. Kubrick GUI cannot detect Kindle.
5) JB Hotfix throws error 004, most probably because it cannot write to /var/local/mkk/ . I tired to extract it with kindletool, add "chmod 755 /var/local/" in the install-dispatch.sh right before " HACKNAME="jb_dispatch" ", then create ota2 package for oasis3 as update.bin, but it didn't work - the same error 004.
6) In the dispatch file of the JB Hotfix I found references that it tries to run /mnt/us/RUNME.sh if it is present. So simple .sh file just to change the permissions didn't work neither. The file was placed there and JB Hotfix ran again (attempted):
7) The only thing to try is to DO_FACTORY_RESET , but I am not sure this will fix the permissions.
Any suggestions/comments are very much appreciated! :)
Maybe I did something wrong with Hotfix patch.
Or is there anything we didn't try?
The user did "chmod /var/local/ 255" from SSH over WinSCP to attempt to block write permission. The result is that Kindle in now in boot loop.
- Kindle Oasis 3
- FW 5.12.4, JB by KindleBreak
- No Rescure pack or Coward's Rescue Pack
- Storage is accessible during boot loop
- Kindle had Wi-Fi turned on before that
Tried the following, to no avail:
1) put update_.bin - Kindle says "Repair needed"
2) ENABLE_DIAGS doesn't work (no Rescue pack)
3) Changing usbnet's config to use Wi-Fi only and adding "auto" file to /usbnet/ didn't help - Kindle is not accessible with WinSCP
4) Kubrick didn't help, Kindle has only one partition /dev/sde (or /dev/sdd sometimes) instead of "mmcblkpN..." parts. Kubrick GUI cannot detect Kindle.
5) JB Hotfix throws error 004, most probably because it cannot write to /var/local/mkk/ . I tired to extract it with kindletool, add "chmod 755 /var/local/" in the install-dispatch.sh right before " HACKNAME="jb_dispatch" ", then create ota2 package for oasis3 as update.bin, but it didn't work - the same error 004.
6) In the dispatch file of the JB Hotfix I found references that it tries to run /mnt/us/RUNME.sh if it is present. So simple .sh file just to change the permissions didn't work neither. The file was placed there and JB Hotfix ran again (attempted):
Code:
#!/bin/sh
#
chmod 755 /var/local/Any suggestions/comments are very much appreciated! :)
Maybe I did something wrong with Hotfix patch.
Or is there anything we didn't try?