11-08-2012, 06:35 PM | #16 |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Perhaps our failsafe should have iptables adjusted to allow SSH over wifi, in case USB networking is not working, like we did for the K4.
|
11-08-2012, 06:35 PM | #17 | |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
|
|
11-08-2012, 06:45 PM | #18 |
BLAM!
Posts: 13,477
Karma: 26012492
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
To expand a bit on the issue:
* USBNet relies on volumd to toggle between USBMS/USBNET. * volumd uses modprobe to remove & load the usb gadgets. * On remove, modprobe will try to unload the parent modules of the removed module if they're unused. * As a consequence, depending on the device, if the device is plugged in, modprobe will fail either on remove or load with a 'Device or resource busy' error. (Which, AFAICT, is completely true & valid). Now, USBNet does a bunch of safety checks (namely, waiting for usb0 to come up before calling ifconfig to set a custom IP). Simple_usbnet just called volumd (through lipc), and let the system handle it. Apparently, if you leave it alone long enough, it *does* end up coming up properly (on volumd's terms), so that was mostly transparent on simple_usbnet (although, you'd have to actually unplug the device too to make the switch effective). USBNet, ont the other hand, *needs* stuff to look okay *during* the lifetime of its helper script, so it'll wait for 15s for usb0 to come up, and throw that error and give up after that. After that, it's basically undefined behaviour. usb0 might come up properly (on volumd's terms), or not . I didn't use simple_usbnet much, and I'm used to this limitation from the K2/3, so I never looked too deeply into it at the time, because I was avoiding it, but if someone can confirm that simple_usbnet handled toggling while plugged in slightly better, I can add a setting that bypasses those checks (and duplicate simple_usbnet's behavior). That means losing the custom IP (if the setting is enabled), but since we default to the same settings as volumd, that's not terribly annoying... Last edited by NiLuJe; 11-08-2012 at 07:04 PM. |
11-08-2012, 06:59 PM | #19 |
BLAM!
Posts: 13,477
Karma: 26012492
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
To get back to Beekr25's message:
I didn't check the files, but given the first post and your answers a few messages later, I'm guessing you didn't put USBNet in the image, ixtab? So, err, why the hell is Beekr25 seeing an eips print from USBnet? ^^ @Beekr25: So, yeah, more details ;D. Did you happen to have USBNet installed before doing this? (Because if you did, and you're seeing it after a full flash, something obviously went wrong during the flash). You mentioned it appeared 'over the advert', so was that *after* the boot process (ie. on the Home page)? Or did you just reinstall it after the 5.3 flash? Last edited by NiLuJe; 11-08-2012 at 07:04 PM. |
11-08-2012, 07:25 PM | #20 | |
(offline)
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
|
Quote:
Nothing more, no other changes. Last edited by ixtab; 11-08-2012 at 08:38 PM. |
|
11-08-2012, 07:40 PM | #21 | |
Junior Member
Posts: 2
Karma: 5792
Join Date: Nov 2012
Device: Kindle Paper White
|
Quote:
Yes I had USBNet Installed. The message appeared sometime between step 7-9 but I didn't notice it until I realized the screen was unresponsive. A further update I have since powered off the unit and now it's stuck on the Kindle screen with a boy reading a book. Ive tried a 30 second hold and a 3 minute hold of the power button but it won't move past the reading boy screen. I currently have the unit plugged in to fully charge it to see if that makes a difference. As I just bought the unit I may have to try my luck with a return if there is no fix. Ben |
|
11-08-2012, 07:47 PM | #22 |
Junior Member
Posts: 9
Karma: 5792
Join Date: Oct 2012
Device: Kindle Paperwhite
|
BE NOTICE that, it may require you to set up the RNDIS driver again when you're in DIAG mode (in case you set up before, you need to do it again for the DIAG mode, including set the IP address)
Code:
################################################# # N O T I C E * N O T I C E * N O T I C E # ################################################# Rootfs is mounted read-only. Invoke mntroot rw to switch back to a writable rootfs. ################################################# [root@[192_168_15_244] root]# ls /mnt/us -l -rwxr-xr-x 1 root root 162 Nov 8 17:35 USBnet.xml drwxr-xr-x 2 root root 8192 Nov 8 17:32 diagnostic_logs drwxr-xr-x 9 root root 8192 Oct 26 12:31 documents drwxr-xr-x 10 root root 8192 Nov 8 17:31 linkss -rwxr-xr-x 1 root root 169891140 Nov 8 03:39 rootfs.img.gz drwxr-xr-x 9 root root 8192 Nov 8 17:22 system -rwxr-xr-x 1 root root 4718592 Nov 8 04:16 uImage drwxr-xr-x 6 root root 8192 Nov 1 06:06 usbnet [root@[192_168_15_244] root]# dd if=/mnt/us/uImage of=/dev/mmcblk0 bs=4096 seek=65 1152+0 records in 1152+0 records out 4718592 bytes (4.5MB) copied, 0.546835 seconds, 8.2MB/s [root@[192_168_15_244] root]# zcat /mnt/us/rootfs.img.gz | dd of=/dev/mmcblk0p1 bs=4096 87500+0 records in 87500+0 records out 358400000 bytes (341.8MB) copied, 103.336101 seconds, 3.3MB/s [root@[192_168_15_244] root]# idme -d --bootmode main; reboot Devmode enabled Reading vars from temp storage... ...None found, Copying vars from /proc Setting bootmode to main Writing new vars to temp area You must reboot before new values will take effect Seems it's all set. Thanks for so many works on it. Last edited by msg7086; 11-08-2012 at 07:51 PM. |
11-08-2012, 07:53 PM | #23 |
Going Viral
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
|
@ixtab: I suggest that you add the following message to the top post:
Fully recharge the battery before you begin this process! Perhaps a new step order of: 0 - Place device in airplane mode 1 - Fully recharge the battery 2 - Ensure that you are running version 5.2.0 of the Amazon software 2.5 - Only when the battery is fully charged, proceed with: Steps 3 ... last as now posted. |
11-08-2012, 08:26 PM | #24 |
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
Posts: 6,586
Karma: 6299991
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
|
^ seconded. This one could be painful.
|
11-08-2012, 08:54 PM | #25 |
BLAM!
Posts: 13,477
Karma: 26012492
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
|
@Beekr25: Yeah, that does sound like a bad flash, there shouldn't have been any trace of USBNet left. Which might explain why it appears to be borked ;/.
EDIT: You mentioned that USBNet still comes up. If you had it in auto mode, try doing a hard-reboot with the Kindle unplugged, and then only plug it & try to get in via SSH a bit after the spinner appears (if it gets there), that's when USBNet is triggered. If you can get in, you might want to throw a stop framework or stop lab126_gui fast to avoid the halt on failure, and give you time to look at the system. (Or a touch /mnt/us/ENABLE_DIAGS, since you had ixtab's rescue pack, too). (Or assume only the rescue pack is still working, boot while plugged in, and see if it comes up in USBMS long enough for you to drop an ENABLE_DIAGS). Last edited by NiLuJe; 11-08-2012 at 09:06 PM. |
11-09-2012, 05:27 AM | #26 |
abibliophobic
Posts: 220
Karma: 219708
Join Date: Aug 2012
Device: KV jailbroken
|
I'm stuck in diags mode Can't enable USB networking I get to the press x for enable USBnet and the only x I can click is exit at the very bottom, but that does nothing.
I can't use the DisableDiags option from the menu as that chucks up an error that the file is missing. Please help. I've followed everything, step by step. Last edited by Akirainblack; 11-09-2012 at 05:33 AM. |
11-09-2012, 05:33 AM | #27 | |
Carpe diem, c'est la vie.
Posts: 6,433
Karma: 10773668
Join Date: Nov 2011
Location: Multiverse 6627A
Device: K1 to PW3
|
Quote:
I just upgraded to the "safe" 5.3.0, and it worked fine for me. Then I installed the usb network hack for the main partition. The "exit diags" menu also works for booting back to main. It will reset the idme bootmode var for you. If it complains about a missing xml file, just select the first diag on the main diag menu (Device Settings) to create that file. Then go disable diags again... |
|
11-09-2012, 05:37 AM | #28 |
abibliophobic
Posts: 220
Karma: 219708
Join Date: Aug 2012
Device: KV jailbroken
|
I installed the "rescue pack" which says it includes the USBnet.
I also did wait after clicking that X but nothing changed on the laptop it was plugged into. Sorry got overly worried, I'd bricked my Paperwhite. Thanks geekmaster, back to normal now. <Phew> |
11-09-2012, 05:50 AM | #29 |
Pest
Posts: 204
Karma: 239254
Join Date: Jan 2012
Location: Italy
Device: KT, PW3
|
I guess that PW will be shipped in Europe with 5.3 firmware... That's bad.
|
11-09-2012, 07:40 AM | #30 |
Old Kaz
Posts: 202
Karma: 1064151
Join Date: May 2010
Device: PocketBook Era
|
ixtab
Updating 5.20>5.30 from this thread successfully. Thanks!!! Collections Manager not work - stands on the screen www.ixtab.tk... (Kindlet JailBreak - 20121029). |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Kindle Paperwhite Update Version 5.3.0 | JoHunt | Amazon Kindle | 115 | 11-30-2012 03:32 PM |
5.3 Update for Paperwhite -- will it interfere with the jailbreak? | sparrowlight | Kindle Developer's Corner | 159 | 11-19-2012 08:11 AM |
Paperwhite Update Coming One of These Days? | copyrite | Amazon Kindle | 13 | 11-05-2012 01:56 PM |
Paperwhite Shipping Update? | nobylspoon | Amazon Kindle | 454 | 10-26-2012 09:56 AM |