Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Readers > Amazon Kindle > Kindle Developer's Corner

Notices

Reply
 
Thread Tools Search this Thread
Old 01-31-2012, 03:59 PM   #1
mad77
Junior Member
mad77 began at the beginning.
 
mad77's Avatar
 
Posts: 3
Karma: 10
Join Date: Jan 2012
Device: Kindle Touch
Question Kindle Touch (with jb) fails to upgrade to 5.0.3

My Kindle Touch (with jailbreak and ssh) can't be updated from 5.0.0 to 5.0.3: the screen goes black and nothing happens, until I reset it (and it's still at 5.0.0).

My changes (the Kindle was bought without ads):
- jailbreak (yifanlu's mp3)
- ssh
- a small (reverted) change to /etc/sysconfig/iptables to accept ICMPs.
- a small (not reverted) change to /etc/upstart/sshd.conf to have my own authorized_keys copied from /usr/local/etc/dropbear/ to /var/tmp/root/.ssh/

I can't find anything meaningful in the logs, and I've also tried to copy /etc/shadow- to /etc/shadow (just in case, since I noticed it was modified...)

Any idea about how can I debug this situation?

Many thanks!
mad77 is offline   Reply With Quote
Old 02-02-2012, 12:59 PM   #2
ixtab
(offline)
ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.
 
ixtab's Avatar
 
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Just an idea.

This worked for me even on a rather heavily modded 5.0.1, which I actually didn't expect to update without problems:
  1. put the 5.0.3 update .bin on the device via USB
  2. eject USB
  3. enable usbnetwork and log in via SSH.
  4. run showlog -f
  5. On the device, choose Menu > Settings, Menu > Update your Kindle.

This allowed me to follow the update progress both on the Kindle itself, as well as the messages it left in the logs.

No guarantees, but as said it worked for me, so you may want to give it a shot.
ixtab is offline   Reply With Quote
Advert
Old 02-02-2012, 01:24 PM   #3
mad77
Junior Member
mad77 began at the beginning.
 
mad77's Avatar
 
Posts: 3
Karma: 10
Join Date: Jan 2012
Device: Kindle Touch
Quote:
Originally Posted by ixtab View Post
Just an idea.

This worked for me even on a rather heavily modded 5.0.1, which I actually didn't expect to update without problems:
  1. put the 5.0.3 update .bin on the device via USB
  2. eject USB
  3. enable usbnetwork and log in via SSH.
  4. run showlog -f
  5. On the device, choose Menu > Settings, Menu > Update your Kindle.

This allowed me to follow the update progress both on the Kindle itself, as well as the messages it left in the logs.

No guarantees, but as said it worked for me, so you may want to give it a shot.

Nice and useful idea, but no luck.

Once I hit the "Continue" button, I just get its press in the logs and then the screen goes black and the ssh down:
Code:
[!]120202:191722 root: CVM received X11 ButtonPress button=1 time=1328206642.792564
[!]120202:191722 root: CVM received X11 ButtonRelease button=1 time=1328206642.794974
   120202:191722 Xorg: W GestureEngine:Touch::Sending button : 1 down
   120202:191722 Xorg: W GestureEngine:Touch::Sending button : 1 up
   120202:191722 cvm[1237]: I def:print::CVM POINTER_CLICKED-gen btn=1  -> radius=0.0
   120202:191722 cvm[1237]: I def:print::
   120202:191722 cvm[1237]: I KDialog:DismissingDialog:frameid=-858340634:
   120202:191722 powerd[875]: I lipc:evts:name=t1TimerReset, origin=com.lab126.powerd:Event sent
   120202:191722 ota[879]: I lipc:evts:name=readyToUpdate, origin=com.lab126.ota:Event sent
   120202:191723 winmgr[1135]: W ligl:fbioctl::Waiting for marker
mad77 is offline   Reply With Quote
Old 02-02-2012, 01:30 PM   #4
ixtab
(offline)
ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.ixtab ought to be getting tired of karma fortunes by now.
 
ixtab's Avatar
 
Posts: 2,907
Karma: 6736092
Join Date: Dec 2011
Device: K3, K4, K5, KPW, KPW2
Weird. You may want to turn on debugging (From memory, it should be "debugOn.sh" on the device, but double-check this), then trying again.

Other than that, I'm clueless

I was about to suggest you update to 5.0.1 first, but there doesn't seem to be any such update package...
ixtab is offline   Reply With Quote
Old 02-02-2012, 01:57 PM   #5
mad77
Junior Member
mad77 began at the beginning.
 
mad77's Avatar
 
Posts: 3
Karma: 10
Join Date: Jan 2012
Device: Kindle Touch
Thumbs up [SOLVED] Kindle Touch (with jb) fails to upgrade to 5.0.3

Quote:
Originally Posted by ixtab View Post
Weird. You may want to turn on debugging (From memory, it should be "debugOn.sh" on the device, but double-check this), then trying again.

Other than that, I'm clueless

I was about to suggest you update to 5.0.1 first, but there doesn't seem to be any such update package...
To add weirdness to weirdness... it just worked!

Thank you very much: I just executed debugOn.sh and tried again, and the upgrade proceeded successfully. Unbelievable.

I leave here the logs; maybe they can be useful to someone else to understand what goes on. Thanks again!
Code:
   120202:194321 cvm[1243]: D HeapMonitor:DebugInfo::HeapMonitor: percentFree=57
   120202:194321 Xorg: W GestureEngine:Touch::Sending button : 1 down
   120202:194321 Xorg: W GestureEngine:Touch::Sending button : 1 up
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::dispatchEvent
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::non-text component, enabled:false
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::dispatchEvent
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::non-text component, enabled:false
   120202:194321 winmgr[1139]: D lua:dbg::+++++event_handle_button 1, 0, 4, 353:174 264859 1127
   120202:194321 winmgr[1139]: D lua:dbg::nofocus 0
   120202:194321 winmgr[1139]: D lua:dbg::client button 1 pressL:D_N:dialog_ID:com.lab126.booklet.settings_M:true_FH:F_RC:true
   120202:194321 winmgr[1139]: D lua:dbg::nofocus false
   120202:194321 winmgr[1139]: D lua:dbg::tap 1 while modal dialog has focus
   120202:194321 winmgr[1139]: D lua:dbg::+++++setControlClient 
   120202:194321 winmgr[1139]: D lua:dbg::client button 0 press
   120202:194321 winmgr[1139]: D lua:dbg::c->signalHandled = 0 
   120202:194321 winmgr[1139]: D lua:dbg::resending non handled event to 0x100001d
   120202:194321 powerd[881]: I lipc:evts:name=t1TimerReset, origin=com.lab126.powerd:Event sent
[!]120202:194321 root: CVM received X11 ButtonPress button=1 time=1328208201.191953
[!]120202:194321 root: CVM received X11 ButtonRelease button=1 time=1328208201.193117
   120202:194321 cvm[1243]: I def:print::CVM POINTER_CLICKED-gen btn=1  -> radius=0.0
   120202:194321 cvm[1243]: I def:print::
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::dispatchEvent
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::non-text component, enabled:false
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::dispatchEvent
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::non-text component, enabled:false
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::dispatchEvent
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::non-text component, enabled:false
   120202:194321 cvm[1243]: D KindleButtonListener:mousePressed:btn=1,event time=1328208201192,current time=1328208201204:
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::dispatchEvent
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::non-text component, enabled:false
   120202:194321 cvm[1243]: D KindleButtonListener:mouseReleased:btn=1,event time=1328208201195,current time=1328208201210:
   120202:194321 cvm[1243]: I KDialog:DismissingDialog:frameid=-1666228042:
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::deactivate:temp:false
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::setAWTFocussedComponent
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::setAWTFocussedComponent
   120202:194321 cvm[1243]: D KindleInputMethod:DebugInfo::removeNotify
   120202:194321 winmgr[1139]: D lua:dbg::=====focus lost from L:D_N:dialog_ID:com.lab126.booklet.settings_M:true_FH:F_RC:true
   120202:194321 winmgr[1139]: D lua:dbg::looking for screenSaver in SS
   120202:194321 winmgr[1139]: D lua:dbg::vis changed L:D_N:dialog_ID:com.lab126.booklet.settings_M:true_FH:F_RC:true vis =false
   120202:194321 winmgr[1139]: D lua:dbg::liglFlash Root 48 341 504x214
   120202:194321 winmgr[1139]: D lua:dbg::Reverting draw mode to N from N
   120202:194321 winmgr[1139]: D lua:dbg::=====PAUSED
   120202:194321 winmgr[1139]: D lua:dbg::*****unmanage signal fired
   120202:194321 winmgr[1139]: D lua:dbg::name : L:D_N:dialog_ID:com.lab126.booklet.settings_M:true_FH:F_RC:true
   120202:194321 winmgr[1139]: D lua:dbg::type : normal
   120202:194321 winmgr[1139]: D lua:dbg::class: 
   120202:194321 winmgr[1139]: D lua:table::+++printing table : params
   120202:194321 winmgr[1139]: D lua:table::  FH F
   120202:194321 winmgr[1139]: D lua:table::  RC true
   120202:194321 winmgr[1139]: D lua:table::  M true
   120202:194321 winmgr[1139]: D lua:table::  L D
   120202:194321 winmgr[1139]: D lua:table::  ID com.lab126.booklet.settings
   120202:194321 winmgr[1139]: D lua:table::  N dialog
   120202:194321 winmgr[1139]: D lua:table::---printing table : params
   120202:194321 winmgr[1139]: D lua:dbg::calling relayout func, clientName = dialog
   120202:194321 winmgr[1139]: D lua:dbg::dialogLayer_layout action: removed
   120202:194321 winmgr[1139]: D lua:dbg::no dialog layout needs on remove
   120202:194321 winmgr[1139]: D lua:dbg::looking for pillowAlert in D
   120202:194321 winmgr[1139]: D lua:dbg::=====focus set to : L:C_N:searchBar_ID:system
   120202:194321 winmgr[1139]: D lua:dbg::focus changed to L:C_N:searchBar_ID:system
   120202:194321 winmgr[1139]: D lua:dbg::+++++setControlClient 
   120202:194321 winmgr[1139]: D lua:dbg::control window changing from L:D_N:dialog_ID:com.lab126.booklet.settings_M:true_FH:F_RC:true
   120202:194321 winmgr[1139]: D lua:dbg::control window changing to L:C_N:searchBar_ID:system
   120202:194321 winmgr[1139]: D lua:dbg::+++++setDrawModeAndSensitivity
   120202:194321 winmgr[1139]: D lua:dbg::+++++draw mode call N
   120202:194321 winmgr[1139]: D lua:dbg::setting draw mode rect 0, 30 :: 600, 70 -- N
   120202:194321 winmgr[1139]: D lua:dbg::=====DRAW MODE PENDING
   120202:194321 winmgr[1139]: D lua:dbg::draw mode not changing
   120202:194321 winmgr[1139]: D lua:dbg::no sensitivity value, send -1
   120202:194321 winmgr[1139]: D lua:dbg::+++++liglSetSensitive nil, -1
   120202:194321 winmgr[1139]: D lua:dbg::Supported app orientations changed: U
   120202:194321 winmgr[1139]: D lua:dbg::*****unmanage finished
   120202:194321 cvm[1243]: D ButtonActionDialog:DebugInfo::Clicked button -- OK
   120202:194321 ota[887]: I lipc:evts:name=readyToUpdate, origin=com.lab126.ota:Event sent
   120202:194321 winmgr[1139]: D lua:dbg::No damage for Root 48 341 504x214
   120202:194321 winmgr[1139]: D lua:dbg::flashing rect = 0,0 600x800 mode = 1
   120202:194322 winmgr[1139]: W ligl:fbioctl::Waiting for marker
   120202:194322 winmgr[1139]: D lua:dbg::looking for screenSaver in SS
   120202:194322 winmgr[1139]: D lua:dbg::=====UNPAUSE
   120202:194322 winmgr[1139]: D lua:dbg::pending draw mode being sent now
   120202:194322 winmgr[1139]: D lua:dbg::+++++draw mode call N
   120202:194322 winmgr[1139]: D lua:dbg::setting draw mode rect 0, 30 :: 600, 70 -- N
   120202:194322 winmgr[1139]: D lua:dbg::=====sending draw mode to ligl
   120202:194322 winmgr[1139]: D lua:dbg::draw mode not changing
   120202:194322 winmgr[1139]: D lua:dbg::+++++liglSetSensitive nil, -1
   120202:194322 winmgr[1139]: D lua:dbg::sensitivity not changing
   120202:194322 winmgr[1139]: D lua:dbg::liglUnpausedRectResolve
   120202:194322 winmgr[1139]: D lua:dbg::looking for screenSaver in SS
mad77 is offline   Reply With Quote
Advert
Old 02-09-2012, 02:46 AM   #6
svw0506
Junior Member
svw0506 began at the beginning.
 
Posts: 2
Karma: 10
Join Date: Feb 2012
Device: kindle touch
1、connect usb
2、ssh use usbnet
3、put bin to /mnt/us/
4、execute /usr/sbin/otaup /mnt/us/Update_kindle_5.0.3.bin
then you will see log,next is whole log:
http://pastie.org/pastes/3225026
svw0506 is offline   Reply With Quote
Reply

Tags
5.0.3, jailbreak, kindle touch, update, upgrade

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
upgrade fails on initial setup mvox Kobo Tablets 11 11-15-2011 10:09 AM
Touch Rooting Touch fails? jerrry94087 Barnes & Noble NOOK 4 08-26-2011 01:43 AM
Calibre fails with proxy after upgrade John H Devices 3 08-09-2011 09:47 AM
calibre 0.6.17 fails to upgrade booksonthemove Calibre 11 10-19-2009 05:14 PM
Calibre fails to start after upgrade njw7 Calibre 0 12-18-2008 05:41 AM


All times are GMT -4. The time now is 10:35 AM.


MobileRead.com is a privately owned, operated and funded community.