yashsingh1/xdaforums huggingface dataset:
[Kindle Fire General] Lunarino:
VERY Excited about "Project OtterX: New Direction"

Wowie - 31 pages. It's been fascinating to read about how this NEW DIRECTION has been progressing.

Now I REALLY-REALLY-REALLY wanna make it work on my KF 1st Generation device using my Win7 pc.

I've been trying to follow along with Tom Toates/sd_shadow's intriguing YouTube video guide 'OtterX ROM/TWRP/Bootloader [2014-05-08]'

https://www.youtube.com/watch?v=8_poieP0ruI&feature=youtu.be

in order to attempt my first custom rom install.

While referring to the following:

TWRP for OtterX -

http://xdaforums.com/showpost.php?p=50852364&postcount=3&nocache=1&z=8346177081111819

OtterX ROM/TWRP/Bootloader [TWRP 2.7.1 2014-06-08] -

http://xdaforums.com/showthread.php?t=2671619

OtterX Project: Bootloader v2.05 -

http://xdaforums.com/showpost.php?p=50852363&nocache=1&z=5815035090781748

I have done all of the necessary downloads and placed the files in a file folder on C:/, mimicking the file structure shown in the video.

At first I was getting a different prompt after entering the command "adb shell" than the one shown.

It was suggested that I try to enter the command "adb devices" - it returned the following:

List of devices attached

1A12000600000001 recovery

It was also recommended I try to push a file like a text file from the same folder as adb

So I tried "adb push test.txt /sdcard" - it did not return any response but when I checked the directory I was happy to see that the file was indeed copied over.

I am somewhat embarrassed to say that it turns out I was not booted into recovery mode. Hence the "dollar sign" prompt ($) Ughhh

So now after entering the command "adb shell" I got the "~ # ←[6n prompt"

Then back to

INSTALLATION:

1. [OPTIONAL-RECOMMENDED] Make sure to backup your vital partitions via from recovery via adb like so:

Code: Select Code

adb shell "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin" - it returned the following:

dd: can't open '/dev/block/mmcblk0boot0': No such file or directory

Now I wonder what important detail I may have failed to consider that is causing this error.

I've searched that string in the forums and got 15 results - none within this thread - they do not seem to apply to my situation as far as I can tell.

Thanks in advance for your kind consideration.
[Kindle Fire General] lovejoy777:
you open a shell

$adb shell

then you dd

# dd if bla bla bla

---------- Post added at 06:47 PM ---------- Previous post was at 06:46 PM ----------

so you dd from within the shell not from your normal "$" prompt
[Kindle Fire General] Lunarino:
Thanks for the response :)

You are correct. I tried to make that clear, sorry.

C:\ADB\Otter\OtterX ROM TWRP Bootloader [2014-05-08]>[B]adb shell[/B]
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # ←[6n[B]dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin[/B]
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
dd: can't open '/dev/block/mmcblk0boot0': No such file or directory
~ # ←[6n

I do notice that your examples are different than mine.

$adb shell... / >adb shell... (Dollar sign)

# dd if... / ~ # ←[6ndd if... (Pound and space)

(I should mention that, despite my best efforts, I have been guilty of making the DUMBEST mistakes during this adventure. So that is my suspicion again here) What is the simple detail that I am not catching?
[Kindle Fire General] lovejoy777:
sorry. i think hash shows it as one command.

just copy and past whats in his instructions (post2)

---------- Post added at 11:13 PM ---------- Previous post was at 11:12 PM ----------

one line at a time
[Kindle Fire General] Lunarino:
... just copy and paste what's in the instructions ...

Thanks once again for your time :)

The code box above, would you say that's exactly what I did on line 4?
[Kindle Fire General] lovejoy777:
ok try doing

$adb shell (enter)

#dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin (enter)

sorry if you already tried that. its just hard to know whats happening your end.
[Kindle Fire General] Lunarino:
try doing

Thank you for your patience. I am concerned that I have been unable to proceed without getting the same prompts to show up on my screen as the ones you show above. I'm guessing that may be important. You can see the prompts that I am working with here below, copied and pasted directly from my command prompt window. The entries typed by me are all in BOLD:

Using Windows 7, TWRP v2.2.2.1 and Bootloader version is 1.4a on a Kindle Fire 1st Generation Reader

I start out by clicking on Start/All Programs/Accessories/Command Prompt

(I've also tried right click "Run as administrator" - No difference)

Here are the results I get:

1-While the KF is connected and in the TWRP v2.2.2.1 home screen

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Troubleshooter>[B]cd\[/B]

C:\>[B]cd adb[/B]

C:\ADB>[B]adb devices[/B]
List of devices attached
1A12000600000001 recovery

C:\ADB>[B]adb shell[/B]
~ # ←[6n[B]dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin[/B]
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
dd: can't open '/dev/block/mmcblk0boot0': No such file or directory
~ # ←[6n

2-While the KF is connected and in the "You can now transfer files from your computer to Kindle" screen

(same results before or after pressing on "Disconnect)

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>[B]cd\[/B]

C:\>[B]cd adb[/B]

C:\ADB>[B]adb devices[/B]
List of devices attached
1A12000600000001 device

C:\ADB>[B]adb shell[/B]
# [B]dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin[/B]
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
/dev/block/mmcblk0boot0: cannot open for read: No such file or directory
#

I seem to recall that the first time I tried this 2 days ago I did see a dollar sign prompt ($) instead of (~ # ←[6n)

Perhaps it should be noted that I am also unable to "push test.txt /sdcard" now (I did succeed 2 days ago)

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Troubleshooter>[B]cd\[/B]

C:\>[B]cd adb[/B]

C:\ADB>[B]dir *.txt[/B]
Volume in drive C is Cyrinx
Volume Serial Number is 2F33-8133

Directory of C:\ADB
07/30/2014 05:10 AM 630 OtterX ROM TWRP Bootloader [TWRP 2.7.1 2014-06-08].txt
07/31/2014 10:41 PM 27 test.txt
2 File(s) 657 bytes
0 Dir(s) 70,125,686,784 bytes free

C:\ADB>adb devices
List of devices attached
1A12000600000001 recovery

C:\ADB>[B]adb shell[/B]
~ # ←[6n[B]push test.txt /sdcard[/B]
push test.txt /sdcard
/sbin/sh: push: not found
~ # ←[6nexit
exit

Hopefully this can help to clarify what is happening on this end so that someone knowledgeable like yourself can figure out where I may be going wrong.

:highfive:Cheers to you!
[Kindle Fire General] dokie80:
Dunno if this matter, but try to run command prompt as administrator? U can right click the command prompt app, and choose run as administrator.

I vaguely remember that I need to do that for some step related to KF.
[Kindle Fire General] lovejoy777:
open a new terminal with kindle pluged in and twrp booted and type.

adb devices

you should get a string of numbers (your kindle id).
[Kindle Fire General] Lunarino:
run as administrator

Thanks for the input :) I did mention in my post that it makes no difference however.

---------- Post added at 03:30 PM ---------- Previous post was at 03:24 PM ----------

adb devices

Thanks again for your help :) I did show in my post that I always do so.

It will either say "recovery" or "device" depending in the Kindle boot mode.

[EDIT]

It will either say "recovery" or "device" depending on the current Kindle boot mode.
[Kindle Fire General] Astrobrewer:
push is an adb command line parameter, not an android shell command. Android os doesn't have a push command, hence the message saying "push: not found." Try "adb push test.txt /sdcard/" at the windows command prompt. I've made this same mistake myself. It's very tempting to use adb shell and execute android commands interactively, and it's easy to get mixed up between actual android commands (like dd) and adb command line parameters (like push and pull).
[Kindle Fire General] Hashcode:
It seems like you may have something connected incorrectly or even be connected to another device. The serial # for your device shown by "adb devices" looks very odd for a Kindle.

Typical responses for TWRP 2.2.x would be "0000000000000000" or perhaps start with "D0" something.

adb shell "cat /proc/cmdline" if you can.
[Kindle Fire General] Lunarino:
"adb push test.txt /sdcard/"

Thanks so much for the post. I'll give "adb push test.txt /sdcard/" a try at the windows

C:\ADB>

prompt
[Kindle Fire General] sd_shadow:
Pushing the test file, is just a test to see if adb can connect, same with adb devices command

.

What was the stock rom version, you started with?

Does twrp mount sd card option still work?
[Kindle Fire General] Lunarino:
serial # shown by "adb devices" looks very odd

Many thanks to you for the reply.

Hmmm, I've made sure that my DroidX phone was never connected to my pc while attaching the KF for this project. I wonder what else it could be?

I've tried connecting with all of my 6 or 7 different USB cables (short and long) to various ports of my pc and laptop (front, sides and back) the results have all been the same.

Looking at my actual serial number from within "Settings/More/Device/Serial Number/) does indeed look quite different. GOOD:cool:EYE! [D01E XXXX XXXX XXXX] - curious

Perhaps if I try my first ever factory reset I'll start getting some more standard behavior/results?

---------- Post added at 05:45 PM ---------- Previous post was at 05:41 PM ----------

But first I'll attempt "adb shell "cat /proc/cmdline" and see what I get. Thanks again!
[Kindle Fire General] sd_shadow:
serial number in stock rom's settings>more.device serial number

will not be the same as the one in recovery

if in stock rom, and you try adb devices what do you get?

stock rom is still system version 6.3.3_user_4112920?

you can try a factory reset but i don't think that will help
[Kindle Fire General] Lunarino:
stock rom & twrp mount

Hi again :) It's really great to get your responses.

Acknowledged

I believe the answer is 6.3.3

From the home screen on v2.2.2.1, I select

Mount/Mount USB Storage

"USB Storage Mounted - - Be sure to safely..."

Windows lets me see the contents then "Unmount" to end

---------- Post added at 07:11 PM ---------- Previous post was at 06:52 PM ----------

Howdy :cowboy:

As far as serial number? curiouser & curiouser

Yes, System Version - Current Version: is indeed "6.3.3_user_4112920", as you say

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>[B]cd\[/B]

C:\>[B]cd adb[/B]

C:\ADB>[B]adb devices[/B]
List of devices attached
1A12000600000001 recovery

C:\ADB>[B]adb shell[/B]
~ # ←[6n[B]adb devices[/B]
adb devices
/sbin/sh: adb: not found
~ # ←[6n

I am kinda reluctant to do a reset because I'll surely lose the ability to see some flash content that one of your previous operations allowed me to get past. But if there's nothing else to try then, of course, I shall.
[Kindle Fire General] sd_shadow:
Depends on method of factory reset.

if you select factory reset in TWRP, user data is only thing lost, TWRP and FFF bootloader will remain.

Should be the same if selected in stock rom's settings
[Kindle Fire General] Lunarino:
Try "adb push test.txt /sdcard/"

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009
Microsoft Corporation. All rights reserved.

C:\Windows\system32>[B]cd\[/B]

C:\>[B]cd adb[/B]

C:\ADB>[B]adb push test.txt /sdcard/[/B]
[I]13 KB/s (27 bytes in 0.002s)[/I]

C:\ADB>

Hey, it looks like it works again, thanks.

But there's something strange.

The 1st time it was suggested to me to try that command I saw no confirmation. But within windows, drive letter G:\, it was transferred, visible and readable.

This time, there was a confirmation (13 KB/s (27 bytes in 0.002s) but in G:\ the file was not there at all.

So, within TWRP, I used the file manager and navigated over to /sdcard. It contains that single file only (test.txt)

I've been under the impression that the 2 directories were one and the same.

Now it appears to me that they are totally separate!

---------- Post added at 07:42 PM ---------- Previous post was at 07:34 PM ----------

Hi again :) Looks like I was able to try the command you recommended successfully. I hope it helps.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>[B]cd\[/B]

C:\>[B]cd adb[/B]

C:\ADB>[B]adb shell[/B]
~ # ←[6n[B]cat /proc/cmdline[/B]
cat /proc/cmdline
console=ttyO2,115200n8 mem=463M@0x80000000 init=/init vram=5M omapfb.vram=0:5M
~ # ←[6n

---------- Post added at 07:47 PM ---------- Previous post was at 07:42 PM ----------

Now THAT is REALLY encouraging!
[Kindle Fire General] sd_shadow:
that appears to be the correct response for a Kindle Fire 1

Maybe, but nothing in the data partition should affect what you are doing.

---------- Post added at 09:14 PM ---------- Previous post was at 09:05 PM ----------

did you start on TWRP 2.2.2.1 or did I suggest downgrading because you were having trouble?

did you change the bootloader too?
[Kindle Fire General] Lunarino:
did you start on TWRP 2.2.2.1

Hiyah :)

I have ever only used TWRP 2.2.2.1 so far.

I believe it was a necessary step in order to follow along with Downgrade stock 6.3.3 to rootable 6.3.2

The same goes for bootloader 1.4a

I'd be happy to try and learn how to apply different versions of these if you believe it may help me to successfully get OtterX going on this thing.

Thanks again for giving this some of your valuable time!
[Kindle Fire General] sd_shadow:
It's possible that TWRP and/or FFF bootloader did not install correctly.

Should be easy to fix.

download zip-otter-twrp-2.6.3.0-selinux-recovery.zip

place it on sd card and install it in twrp with install option, then reboot, select boot recovery, see if TWRP changed to 2.6.3.0

then post results here
[Kindle Fire General] Lunarino:
download recovery/flash-zip/zip-otter-twrp-2.

Okay :) Recovery now shows me a new TWRP of v2.6.3.0 (that was super fast & easy)
[Kindle Fire General] sd_shadow:
"adb devices" serial number may have changed

try the " backup your vital partitions via from recovery via adb" step again

if that does not work

download fff-u-boot_v1.4a.zip

place on sd card, install in TWRP, reboot, should not see any change

try the " backup your vital partitions via from recovery via adb" step again
[Kindle Fire General] Lunarino:
It looks like the newer TWRP is making a difference.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>[B]cd\[/B]

C:\>[B]cd adb
[/B]
C:\ADB>[B]adb devices[/B]
List of devices attached
0123456789ABCDEF recovery

C:\ADB>

I'd like to go back to the youtube tutorial OtterX ROM/TWRP/Bootloader [2014-05-08] and see if I can successfully enter that command, "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin" & see what happens

---------- Post added at 01:01 AM ---------- Previous post was at 12:24 AM ----------

I no longer get the error "dd: can't open '/dev/block/mmcblk0boot0': No such file or directory" YAY

However, the feedback I do get appears to be slightly different than what's shown on your command prompt screen.

Should I interpret that as having not worked?

If so, I've downloaded

fff-u-boot_v1.4a.zip

and am poised to abort and then apply it before trying again.

Your 256+0 records shows up as 1024+0 on mine

Yours 131072 bytes - Mine 524288

Yours (128.0KB) - Mine (512.0KB)

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>[B]cd\[/B]

C:\>[B]cd adb[/B]

C:\ADB>[B]adb devices[/B]
[I]List of devices attached
0123456789ABCDEF recovery[/I]

C:\ADB>[B]adb shell[/B]
~ # ←[6n[B]dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin[/B]
dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0.bin
[I]1024+0 records in
1024+0 records out
524288 bytes (512.0KB) copied, [U]0.104126[/U] seconds, [U]4.8MB[/U]/s[/I]
~ # ←[6n

Thanks again for your help!!!
[Kindle Fire General] sd_shadow:
I think it worked, they should be different, but don't think anyone else has posted their results, so not really sure.

---------- Post added at 12:11 AM ---------- Previous post was at 12:07 AM ----------

You could copy files to different folder, try again and compare md5 check sums of 1st try to 2nd try, if they match they should be good.
[Kindle Fire General] Lunarino:
I am extremely impressed! It took less than 20 minutes to breathe new life into this device. My compliments to all involved.
[Kindle Fire General] Vlasp:
is there a way to add mic capabilities like you guys did in jellybean? thanks!
[Kindle Fire General] Lunarino:
Need guidance please - Otterx broken

So, the device performed fantastically. Until someone tried some kind of built in upgrade feature within CM while it was away away for the weekend.

There was a serious error message given about "must be factory reset". That was attempted and failed.

They then panicked and came over here to read up and retry the steps I had successfully taken in order get it all back. I think they only made matters worse.

I tried to start over from the beginning but am lost (unfortunately I cannot get accurate information on what exactly they already tried)

It looks as if things may still be recoverable but since my skills are severely limited I am reluctant to proceed blindly.

Here's what I do know:

When the KF 1st Gen. tablet is switched on we see the new larger white "Kindle Fire" logo with "[ Press power to open boot menu ]" on bottom.

Then it goes to the Yellow "fastboot mode" with a blue downward pointing arrow in front with "FASTBOOT MODE ENTERED" on the bottom left.

V2.05 allows me to select "RECOVERY BOOT" and I still have TWRP 2.7.0.0 accessible, thank goodness.

I can also still select "ADVANCED--->" They tried setting the partition mode to Amazon but I put it back on "OtterX"

While connected to the pc nothing happens any longer.

Using file manager it looks like the /sdcard directory is now empty.

I still have backups of xloader.bin, bootloader.bin, boot1.bin and boot0.bin on my pc C:\ADB folder

Does this give anyone with familiarity any clues as to the current condition of the device?

Do you think any steps may be taken in order to either fix the wonderful Otterx again or even bring it back to the previous state before I did the partitions backups?

Thanks in advance for your kind consideration!
[Kindle Fire General] sd_shadow:
changing partition mode will format(wipe) the rom and sd card

Don't need the backups

redo the wipes, STEP 4: WIPE PARTITIONS IN RECOVERY and then STEP 5: DOWNLOAD / PUSH CM11 ROM and GAPPS TO SDCARD VIA ADB
[Kindle Fire General] DroidLover93:
Question?

Is there any possibility of being able to transfer files via computer to my device? for example, I would like to be able to take pictures from my computer and put them in my device storage.. I just tried to do it and I see "amazon Otter X" in my portable devices are but when I clicked on it there was nothing in it. :\

---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------

Sorry for waisting your time. My sister just figured out my problem.
[Kindle Fire General] Lunarino:
redo the wipes, STEP 4

I was successful using

OtterX ROM/TWRP/Bootloader [2014-05-08] https://www.youtube.com/watch?v=8_poieP0ruI

to guide me last time.

But it looks like you are directing me to

OtterX ROM/TWRP/Bootloader [TWRP 2.7.1 2014-06-08] http://xdaforums.com/showthread.php?t=2671619

instead

...

STEP 4: WIPE PARTITIONS IN RECOVERY

[Main Menu] Wipe -> Advanced -> check "Cache" and Swipe

[Main Menu] Reboot -> Recovery (wait for it to come back into TWRP)

[Main Menu] Wipe -> "Format Data", type "yes" and hit enter

[Main Menu] Wipe -> Advanced -> check "System" and Swipe

STEP 5: DOWNLOAD / PUSH CM11 ROM and GAPPS TO SDCARD VIA ADB

...

adb push cm-11-20140508-UNOFFICIAL-otterx.zip /sdcard/

adb push gapps-kk-20140606-signed.zip /sdcard/gapps-kk-20140606-signed.zip

STEP 6: FLASH AND REBOOT

File manager tells me that I was able to successfully push both to the sdcard

I seem to be stuck on "updating partition details..." It's been running for 20 minutes now.

I think I may be using the wrong TWRP version - v2.7.0.0. Shouldn't it say "OtterX 2.7.1" somewhere?
[Kindle Fire General] sd_shadow:
TWRP has been updated since I make the video, guess I should make a note to use newer files when available.

neither 2.7.0.0 nor 2.7.1.0 Otter X Twrp say otter X, but 2.7.1.0 is the prefered TWRP. Original TWRP file names do say Otter, Blaze, or OtterX

just install zip-otterx-twrp-2.7.1.0-recovery.zip in TWRP
[Kindle Fire General] Lunarino:
just install zip-otterx-twrp-2.7.1.0-recovery.zip

Thanks so much!

Everything went smoothly. At least I can now see the animated blue CM screen again.

Now here's the same error screen they got after attempting to update/upgrade CM from within settings:

[COLOR="RoyalBlue"]Encryption unsuccessful[/COLOR]
---------------------------------------------------------
Encryption was interrupted and can't complete. As a
result, the data on your tablet is no longer accessible.

To resume using your tablet, you need to perform a
factory reset. When you set up your tablet after the
reset, you'll have an opportunity to restore any data that
was backed up to your Google account.
----------------------------------------------------------
(Button "Reset tablet")

I'll not try the button as she tells me it did not work for her on Saturday.

Is there any hope for me to fix things at this point?
[Kindle Fire General] sd_shadow:
one of the partitions did not get set right

I would fix partitions in TWRP

Wipe>advanced> select a partition (cache, system, data...) fix partition (or repair)

select one, select fix, then go back and repeat till you have repaired all

should have to re-push rom and gapps, and re-install
[Kindle Fire General] dinagoshen:
Hi, CM already showed me twice that there are newer versions that could be installed, M8 and M9.

Can/should I proceed with the upgrade ? how exactly ?

Thanks
[Kindle Fire General] Lunarino:
one of the partitions did not get set right

Thank you for the suggestions.

I've attempted the above at least a dozen times unfortunately with no success.

Again, I do sincerely appreciate the time and effort offered to myself and others!

---------- Post added at 11:42 AM ---------- Previous post was at 11:39 AM ----------

I was just informed that the options you mentioned there are what caused my current problems. She says that she selected "8".

I would advise EXTREME caution before proceeding.
[Kindle Fire General] sd_shadow:
the older TWRP could have caused the new rom to fail

---------- Post added at 11:38 AM ---------- Previous post was at 11:15 AM ----------

@Lunarino next I would revert to amazon partitions in bootloader, then in twrp rewipe everything, and reformat, then back in bootloader choose otter partitions again

In TWRP rewipe eveything
[Kindle Fire General] Lunarino:
the older TWRP

Reading back, I do now realize that I have used TWRP 2.2.1 and 2.6.3.0.

2.7.0.0 was used to initially install OtterX successfully.

2.7.1.0 has been somewhat helpful in order to at least see the CM11 content again.

I am such a BIG fan of your excellent YouTube instructional tutorials that I wonder if I should try

[How-To] Revert from OtterX Project to Stock Kindle Fire Rom - https://www.youtube.com/watch?v=wL9DRLZCXAg

---------- Post added at 12:45 PM ---------- Previous post was at 12:42 PM ----------

Sounds good. Can do.
[Kindle Fire General] sd_shadow:
Yes, only to backup partitions

not for installing or using OtterX CM11

You should not have any cm11 content if you are wiping partitions

Can If you want, but I recommend using my pre-rooted 6.3.3.zip rather than the full stock update.zip, less of a chance of problems like bad bootloader.

Still need to go through all the same steps to change partitions, wipe, change twrp...