Register Guidelines E-Books Today's Posts Search

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

Notices

Reply
 
Thread Tools Search this Thread
Old 05-20-2018, 07:01 PM   #76
kapaggar
Member
kapaggar began at the beginning.
 
kapaggar's Avatar
 
Posts: 19
Karma: 10
Join Date: May 2018
Device: KT3
Talking Yes I really mean adb shell access

Quote:
Originally Posted by knc1 View Post
What do you mean: "an adb shell" on a KT3?
A KT3 runs Amazon/Linux, not Google/Linux (a.k.a: Android).
Wait .. you mean people dont use it ?? It was the first thing I did in diags mode since I cant make rescue pack n CRP work on KT3.

Quote:
What do you mean: "dd rootfs and main kernel" ?
I.E: To the kindle storage or From the kindle storage?
to be exact , I read this thread and was confident that with some modifications this can work on KT3


Quote:
If "to" - What are you trying to accomplish?
Yes this was my aim for the weekend. have taken backups of mmcblk0p1,2,3 of update 5.9.5.1 just in case.

>> There must be a lot to the story which you are not mentioning here.

By mistake the 5.9.5.1 got installed and I want to get back to 5.8.11 .. Since I didnt find any thread for KT3 that did this, I was thinking of making a thread to ask about how to use that adb shell for writing main rootfs and kernel from extracted 5.8.11 update.bin
kapaggar is offline   Reply With Quote
Old 05-20-2018, 07:38 PM   #77
kapaggar
Member
kapaggar began at the beginning.
 
kapaggar's Avatar
 
Posts: 19
Karma: 10
Join Date: May 2018
Device: KT3
Talking verified again

So after reading your comment, I tried again enabling adb in diags and yes I wasnt dreaming..

Attached are snaps i took while in diags mode.. 1st one is choosing usb in adb mode.


see if the device is recognised in adb

Code:
$ adb devices -l
List of devices attached
P0011807638506JH       device usb:336592896X product:zeux_fox model:fox device:fox

$ adb version
Android Debug Bridge version 1.0.39
Revision 3db08f2c6889-android
Installed as /usr/local/bin/adb
After that just launch adb shell to get in kindle
Code:
$ adb shell

/dev # cat /proc/version 
Linux version 3.10.53-lab126 (jenkins-official@sjc10-jbuild07) (collect2: error: ld returned 1 exit status) #1 PREEMPT Fri Jul 22 00:45:40 PDT 2016

/dev # uname -a
Linux kindle 3.10.53-lab126 #1 PREEMPT Fri Jul 22 00:45:40 PDT 2016 armv7l GNU/Linux


/dev # ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

/dev # df -kh
Filesystem                Size      Used Available Use% Mounted on
/dev/root                62.2M     33.8M     25.3M  57% /
tmpfs                   249.9M      4.0K    249.9M   0% /dev
tmpfs                   249.9M         0    249.9M   0% /dev/shm
/dev/mmcblk0p3           62.0M     17.2M     41.5M  29% /var/local
/dev/loop/0               3.0G      1.3G      1.7G  43% /mnt/base-us
fsp                       3.0G      1.3G      1.7G  43% /mnt/us
/dev/loop/1               3.7M    384.0K      3.3M  10% /mnt/wfm
Attached Thumbnails
Click image for larger version

Name:	IMG-20180521_2.jpg
Views:	332
Size:	77.3 KB
ID:	164058   Click image for larger version

Name:	IMG-20180521.jpg
Views:	302
Size:	64.8 KB
ID:	164059  
kapaggar is offline   Reply With Quote
Old 05-20-2018, 08:38 PM   #78
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
First six of device serial number and "Diags" system version please (the content of prettyversion.txt will do just fine, or whatever similar is available - that is: the firmware version not the kernel version).

I posted other questions for you, which you have not answered.
You just got carried away with your answer to one of those questions.

Last edited by knc1; 05-20-2018 at 08:40 PM.
knc1 is offline   Reply With Quote
Old 05-21-2018, 05:40 AM   #79
kapaggar
Member
kapaggar began at the beginning.
 
kapaggar's Avatar
 
Posts: 19
Karma: 10
Join Date: May 2018
Device: KT3
Thumbs up My apologies if I didnt anwer all your questions.

Quote:
First six of device serial number and "Diags" system version please (the content of prettyversion.txt will do just fine, or whatever similar is available - that is: the firmware version not the kernel version).
Serial and Main OS version
Code:
# cut -c1-6 /proc/usid
G000K9

# cat /etc/prettyversion.txt
Kindle 5.9.5.1 (~~otaVersion~~)
Diags version
Code:
/dev # cat /etc/prettyversion.txt 
Kindle 5.8.0 078 Non-OB (~~otaVersion~~)
Quote:
I posted other questions for you, which you have not answered.
You just got carried away with your answer to one of those questions.
Oh no! I thought i answered all your questions...may be you missed that previous reply. see postcount 76 and 77

Just to make things more clear ...
I bought this kindle 5-6 months ago and was content with the stock os untill I had difficulty reading hindi pdf.
so 3-4 days back I decided to read about jailbreak and thanks to your wonderful forum and wiki.
i was able to do it without issues.

- I installed KOreader which gave reflow texts possible on hindi pdf without giving low resolution bitmaps.

- Also got some cool personal screensavers ( I havent read enough threads on this site but there are some great gems in these posts )

now after playing a lot with all these things i wanted to downgrade my 5.9.5.1 to 5.8.10 or 5.8.11 just with JB , usbnet and customSS mods.

That is long and short of me browsing mobileread.com

- I also tried to find things for KT3 here , but there is no such prefix
- I managed to make RP work on KT3 just now (after facing same errors in https://www.mobileread.com/forums/sh...=195670&page=7 )

after seeing run.ff fail in
sed: /mnt/mmc/opt/factory/system_diags: No such file or directory
above i just touched the file , as this wasnt there in diags partition of KT3
Code:
[root@kindle us]# touch /mnt/mmc/opt/factory/system_diags
[root@kindle us]# umount /mnt/mmc
Here is the installation log of mrpi

Spoiler:
Code:
**** **** **** ****

[2018-05-21 @ 14:04:19 +0530] :: [MRPI r14394] - Beginning the processing of package 'Update_rp_20131220.N_install.bin' (rp 20131220.N I) . . .

--
Running 'run.ffs' for 'rp 20131220.N I' (Update_rp_20131220.N_install.bin) @ Mon, 21 May 2018 14:04:19 +0530

eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
eips: pixel_in_range> (608, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (624, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (640, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (656, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (672, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (688, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (704, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (720, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (736, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (752, 288) pixel not in range (0..600, 0..800)
eips: pixel_in_range> (768, 288) pixel not in range (0..600, 0..800)
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0
update_to_display: update_mode=PARTIAL, wave_mode=257 inverted=0

Success! :)
kapaggar is offline   Reply With Quote
Old 05-21-2018, 08:44 AM   #80
ammadeusy
Member
ammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blueammadeusy can differentiate black from dark navy blue
 
Posts: 10
Karma: 13116
Join Date: Aug 2014
Device: pw4/pw5
Thumbs up

Quote:
Originally Posted by coplate View Post
Hello all.

I am looking for a test subject.

If you have updated your kindle, and re-isntalled KUAL Booklet, but you are just getting a blank screen, I would like you to try this and report back
Hello @coplate, I have a pw3 5.9.5.1 (G090G1) recently updated that I did not even noticed it happened. kual was not running, then it was not showing the Kual book in my list and the installation was not working because I was putting the .bin files at the root instead of the /mrpackages folder.

1-I did install your Update_jailbreak_hotfix_1.14_5.8.10_install.bin that did not seem to do a change (maybe because of the mistake with the /mrpackages?)
2-then I did your instructions with the jar and RUNME.sh files. nothing changed.
3-then I did put two things at the mrpi folder to have kual back:
Update_dummy_0.0.N.bin
Update_KUALBooklet_v2.7_install.bin

4-reapplied your jar and RUNME.sh files, which broke the KUAL.
5-reinstall KUALBooklet (step 3), but the books are not opening from the file explorer.
6-full reinstall of Koreader, everything in order.

with that, kual/koreader is back working normally, but with a short blank screen before the full start. is this blank screen you are meaning?

thanks!

Last edited by ammadeusy; 05-21-2018 at 11:18 AM.
ammadeusy is offline   Reply With Quote
Old 05-21-2018, 10:23 AM   #81
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@kapaggar: Huh. Guess they sprung a new diags rootfs/menu on us. (And that it supports adb is new, hence @knc1's surprise, we're used to USBNet & dropbear ).

For the record, you don't have any issues exiting from diags and restarting into the main system?
And is there actually a menu mentioning USBNet and/or SSH?

Once you've made proper dumps of all this, I'd sure be glad to take a look at it... .

Last edited by NiLuJe; 05-21-2018 at 10:26 AM.
NiLuJe is offline   Reply With Quote
Old 05-21-2018, 10:57 AM   #82
kapaggar
Member
kapaggar began at the beginning.
 
kapaggar's Avatar
 
Posts: 19
Karma: 10
Join Date: May 2018
Device: KT3
Thumbs up Thanks NiLuJe

Quote:
Originally Posted by NiLuJe View Post
@kapaggar: Huh. Guess they sprung a new diags rootfs/menu on us. (And that it supports adb is new, hence @knc1's surprise, we're used to USBNet & dropbear ).
I hope you are doing great in life..

I am only a week old in kindle areana.. only reading with android KOReader till now. so thanks for having patience with me. I have linux exposure but heard lab126 two days ago and how things are structured in kindle world. Going through upstart scripts rn.

but
Code:
/dev # cat /etc/prettyversion.txt 
Kindle 5.8.0 078 Non-OB (~~otaVersion~~)

# modinfo g_android
filename:       /lib/modules/3.10.53-lab126/kernel/drivers/usb/gadget/g_android.ko
version:        1.0
license:        GPL
description:    Android Composite USB Driver
author:         Mike Lockwood
alias:          fs-functionfs
srcversion:     15D9B2BC43668E716D2824A
depends:        libcomposite
intree:         Y
vermagic:       3.10.53-lab126 preempt mod_unload ARMv7 p2v8 
parm:           qmult:queue length multiplier at high/super speed (uint)
parm:           dev_addr:Device Ethernet Address (charp)
parm:           host_addr:Host Ethernet Address (charp)
means its from the update_KT3_5.8.0_initial mentioned in the wiki https://wiki.mobileread.com/wiki/5_x_Jailbreak ??

Good for KT3 owners that they dont have to struggle to make usbnet work in diags as adb shell workds ootb .. When I installed RP and made /ENABLE_DIAGS in usbms i got diags after reboot..
which enables adbd by default

my /etc/upstart/diags has
Code:
CONFIG_USB_MODE=/opt/factory/rit/usb_mass_enable 
init_adb_or_usb_mass_storage()
{
  if [ -f $CONFIG_USB_MODE ]; then
     echo "Config mass stoarge"
     modprobe g_mass_storage file=/dev/mmcblk0p4 removable=1
     rm -fR $CONFIG_USB_MODE
  else
     echo "Config USB adb mode"
     /usr/bin/config_adbd.sh    
  fi
}
For the record, you don't have any issues exiting from diags and restarting into the main system?
No.. just idme -d --bootmode main in adb shell and restart
And is there actually a menu mentioning USBNet and/or SSH?
No, under USB mode there are 3 options.
1. adb
2. mass storage ( havnt tried this )
3. USB_DOWNLOAD ( opens usbms and if update file stored in its root processes it after i unmounts usbms .... i tried this to downgrade from 5.9.5 to 5.8.10 but update error 15 came)

Once you've made proper dumps of all this, I'd sure be glad to take a look at it...
What are dumps in kindle dev parlance ? partition dd dumps ? targz of some dir ?
kapaggar is offline   Reply With Quote
Old 05-21-2018, 12:55 PM   #83
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
The versioning of diags rootfs/kernels has always been pretty peculiar (and, by definition, harder to study, because we've never seen a diags update in the wild, nor have we ever heard of someone capturing one OTA, so we're left with what we've seen ourselves on a handful of devices) so I wouldn't obsess too much about it .

Good to know about your experience, though, it indeed makes a good part of the RP unnecessary on those devices .

EDIT: I don't recall the initrd's updater's error code OTOH for a downgrade ('attack', as the constant was lovingly labeled), but that's probably it.

And, yeah, I meant dd partition dumps/images .
NiLuJe is offline   Reply With Quote
Old 05-21-2018, 03:20 PM   #84
kapaggar
Member
kapaggar began at the beginning.
 
kapaggar's Avatar
 
Posts: 19
Karma: 10
Join Date: May 2018
Device: KT3
Talking Taking dump now

Quote:
Originally Posted by NiLuJe View Post

EDIT: I don't recall the initrd's updater's error code OTOH for a downgrade ('attack', as the constant was lovingly labeled), but that's probably it.

And, yeah, I meant dd partition dumps/images .

Are below commands fine ? i will run these in diag if you give a green flag.
any precaution to take before taking these dumps and putting on google Drive ?
Code:
# dd if=/dev/mmcblk0boot0 |gzip > /mnt/us/images/mmcblk0boot0.gz
# dd if=/dev/mmcblk0boot1 |gzip > /mnt/us/images/mmcblk0boot1.gz

# dd if=/dev/mmcblk0p1 |gzip > /mnt/us/images/mmcblk0p1.gz
# dd if=/dev/mmcblk0p2 |gzip > /mnt/us/images/mmcblk0p2.gz
# dd if=/dev/mmcblk0p3 |gzip > /mnt/us/images/mmcblk0p3.gz
kapaggar is offline   Reply With Quote
Old 05-21-2018, 08:22 PM   #85
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
IIRC, ideally, dump main from diags and diags from main (to make sure the source partition is unmounted when dumping).

c.f., this trusty old wiki page for examples.

In terms of sensitive data, the rootfs partition themselves should be safe enough, IIRC, only varlocal & the userstore can potentially contain user/device secrets.
NiLuJe is offline   Reply With Quote
Old 05-21-2018, 10:54 PM   #86
coplate
Guru
coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.
 
Posts: 645
Karma: 1888888
Join Date: Jun 2009
Device: prs-505, Kindle Keyboard 3g, PW3
Quote:
Originally Posted by kapaggar View Post
I hope you are doing great in life..

I am only a week old in kindle areana.. only reading with android KOReader till now. so thanks for having patience with me. I have linux exposure but heard lab126 two days ago and how things are structured in kindle world. Going through upstart scripts rn.

but
Code:
/dev # cat /etc/prettyversion.txt 
Kindle 5.8.0 078 Non-OB (~~otaVersion~~)

# modinfo g_android
filename:       /lib/modules/3.10.53-lab126/kernel/drivers/usb/gadget/g_android.ko
version:        1.0
license:        GPL
description:    Android Composite USB Driver
author:         Mike Lockwood
alias:          fs-functionfs
srcversion:     15D9B2BC43668E716D2824A
depends:        libcomposite
intree:         Y
vermagic:       3.10.53-lab126 preempt mod_unload ARMv7 p2v8 
parm:           qmult:queue length multiplier at high/super speed (uint)
parm:           dev_addr:Device Ethernet Address (charp)
parm:           host_addr:Host Ethernet Address (charp)
means its from the update_KT3_5.8.0_initial mentioned in the wiki https://wiki.mobileread.com/wiki/5_x_Jailbreak ??

Good for KT3 owners that they dont have to struggle to make usbnet work in diags as adb shell workds ootb .. When I installed RP and made /ENABLE_DIAGS in usbms i got diags after reboot..
which enables adbd by default

my /etc/upstart/diags has
Code:
CONFIG_USB_MODE=/opt/factory/rit/usb_mass_enable 
init_adb_or_usb_mass_storage()
{
  if [ -f $CONFIG_USB_MODE ]; then
     echo "Config mass stoarge"
     modprobe g_mass_storage file=/dev/mmcblk0p4 removable=1
     rm -fR $CONFIG_USB_MODE
  else
     echo "Config USB adb mode"
     /usr/bin/config_adbd.sh    
  fi
}
For the record, you don't have any issues exiting from diags and restarting into the main system?
No.. just idme -d --bootmode main in adb shell and restart
And is there actually a menu mentioning USBNet and/or SSH?
No, under USB mode there are 3 options.
1. adb
2. mass storage ( havnt tried this )
3. USB_DOWNLOAD ( opens usbms and if update file stored in its root processes it after i unmounts usbms .... i tried this to downgrade from 5.9.5 to 5.8.10 but update error 15 came)

Once you've made proper dumps of all this, I'd sure be glad to take a look at it...
What are dumps in kindle dev parlance ? partition dd dumps ? targz of some dir ?



thanks for posting all of this:

I can confirm that that driver is in the "kindle8" source code, but is not available in the "paperwhite7" source code, which makes me sad.

Do you do anything special to boot into diags to get to that ADB option, are you using the shell script in rescue pack, or using the serial port?

Thanks for any more information you can give!



Edit:





So I downloaded several software packages:, and only one of them has this file:
/lib/modules/3.10.53-lab126/kernel/drivers/usb/gadget/g_android.ko



oasis9 - update_kindle_all_new_oasis_5.9.5.2.bin - NO

oasis8 - update_kindle_oasis_5.9.5.1.bin - NO

kindle8 - update_kindle_8th_5.9.5.1.bin - YES

paperwhite7 - update_kindle_all_new_paperwhite_5.9.5.1.bin - NO

voyage7 - update_kindle_voyage_5.9.5.1.bin - NO

kindle7 - update_kindle_5.9.5.1.bin - NO

Last edited by coplate; 05-21-2018 at 11:21 PM.
coplate is offline   Reply With Quote
Old 05-22-2018, 03:01 AM   #87
kapaggar
Member
kapaggar began at the beginning.
 
kapaggar's Avatar
 
Posts: 19
Karma: 10
Join Date: May 2018
Device: KT3
Quote:
Originally Posted by coplate View Post
thanks for posting all of this:
I can confirm that that driver is in the "kindle8" source code, but is not available in the "paperwhite7" source code, which makes me sad.
Do you do anything special to boot into diags to get to that ADB option, are you using the shell script in rescue pack, or using the serial port?
Thanks for any more information you can give!
You are welcome.
Its new kindle so i havnt tried prying covers open. but I can get a cheap one if things go ugly .. as now these are being sold refurbished by amazon.in https://www.amazon.in/dp/B073SGQK7L

here is my kindles history, as i remember it.
> Bought it 4-6 months ago. not used much.
> OTA happened got 5.8.10
> factory reset
> downgraded to 5.8.0 for JB
> did JB, installed KUAL and MrPi friends . wifi on for usbnet.
> at some point here OTA 5.9.5.1 crept into device.. not cool.
> installed RP ( failed first attempt) and then got into diag via "idme -d --bootmode diags"

so now my diags partition is not pristine as it contains usbnet ssh dropbear etc
It s only now i found that I can make /ENABLE_DIAGS in main and reboot to get in diags mode.

I can try uninstalling RP but there is no update*uninstall.bin for that. I hope i answered some of your questions, please tell me what more info , cmd output for main / diags you need.. I am uploading partitions too if anyone want that.


Quote:
Originally Posted by NiLuJe View Post
IIRC, ideally, dump main from diags and diags from main (to make sure the source partition is unmounted when dumping).

c.f., this trusty old wiki page for examples.

In terms of sensitive data, the rootfs partition themselves should be safe enough, IIRC, only varlocal & the userstore can potentially contain user/device secrets.
many many thanks NiLuJe, I did exactly as you told me.. dumped mmcblk0p2 from main mode and mmcblk0p1,mmcblk0boot0,mmcblk0boot1 from diags mode.

Here is the upload dir for the below commands. KindleUploads


Code:
# dd if=/dev/mmcblk0boot0 |gzip > /mnt/us/images/mmcblk0boot0.gz
# dd if=/dev/mmcblk0boot1 |gzip > /mnt/us/images/mmcblk0boot1.gz
# dd if=/dev/mmcblk0p1 |gzip > /mnt/us/images/mmcblk0p1.gz
# dd if=/dev/mmcblk0p2 |gzip > /mnt/us/images/mmcblk0p2.gz
kapaggar is offline   Reply With Quote
Old 05-22-2018, 08:06 AM   #88
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@coplate: Interesting that it's in the KT3 and not the Oasis 2, given the release chronology... .

@kapaggar: Got it, thanks .
NiLuJe is offline   Reply With Quote
Old 05-22-2018, 01:45 PM   #89
coplate
Guru
coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.coplate ought to be getting tired of karma fortunes by now.
 
Posts: 645
Karma: 1888888
Join Date: Jun 2009
Device: prs-505, Kindle Keyboard 3g, PW3
Quote:
Originally Posted by NiLuJe View Post
@coplate: Interesting that it's in the KT3 and not the Oasis 2, given the release chronology... .

@kapaggar: Got it, thanks .

I have the suspicion, that it is becasue of this:

This link to the Kindle 'X' / 'Migu' on amazon.cn
http://www.chinadaily.com.cn/busines...t_29913054.htm

This is the software download link:
https://www.amazon.cn/gp/help/custom...deId=202167860

It runs Android OS.

Images of that device from China show it looks nearly identical to the kindle basic 8th gen, and some sites of dubios quality report that it does in fact use the same hardware. I have not verified by trying to buy one :-)

I would suppose that there is some correlation between that, and why the this model has different behaviour.

Last edited by coplate; 05-22-2018 at 01:47 PM.
coplate is offline   Reply With Quote
Old 05-22-2018, 02:12 PM   #90
kapaggar
Member
kapaggar began at the beginning.
 
kapaggar's Avatar
 
Posts: 19
Karma: 10
Join Date: May 2018
Device: KT3
Quote:
Originally Posted by coplate View Post
I have the suspicion, that it is becasue of this:

This link to the Kindle 'X' / 'Migu' on amazon.cn
http://www.chinadaily.com.cn/busines...t_29913054.htm

This is the software download link:
https://www.amazon.cn/gp/help/custom...deId=202167860

It runs Android OS.

Images of that device from China show it looks nearly identical to the kindle basic 8th gen, and some sites of dubios quality report that it does in fact use the same hardware. I have not verified by trying to buy one :-)

I would suppose that there is some correlation between that, and why the this model has different behaviour.

I tried to check like adb if fastboot also works like android on KT3 .. Bricked

From main bootmode I launched idme -d --bootmode fastboot

Click image for larger version

Name:	idme.jpg
Views:	255
Size:	91.0 KB
ID:	164077
and now its stuck in some strange mode..

not getting detected as USB / fastboot / adb in mac or windows10

Time to make a saperate thread asking for help and all things that come with it..

Last edited by issybird; 05-22-2018 at 02:15 PM. Reason: Replaced oversized image with thumbnail.
kapaggar is offline   Reply With Quote
Reply


Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
[KUAL]Kindle reflective screen loader icantbebothered Kindle Developer's Corner 26 10-27-2013 09:08 AM
Kindle 4 NT - Updated Screen-saver code, updated hack bmsleight Amazon Kindle 2 10-07-2012 03:57 PM
Is the software updated needed? JVM Kobo Reader 1 03-31-2011 09:26 AM


All times are GMT -4. The time now is 07:34 AM.


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