Open War for Open Android: Antitrust for Cyanogen?

Android and openness is something we talk about all the time, but the recent … more

What Do You Do with All of Your Old Photos?

Smartphone cameras have advanced so tremendously over the past few years that they have … more

Diving into the April 2015 Material Design Update

Before the release of Android 5.0 Lollipop, the Holo Design guidelines served as the … more

New Cyanogen Partnerships Bring Privacy Concerns

New Privacy concerns have emerged regarding Cyanogen’s latest announcements, … more
Post Reply Subscribe to Thread Email Thread

[How To] Fix Otter X Install Errors, Partition sizes, Unable to Mount System...

15th December 2014, 04:07 PM |#1  
sd_shadow's Avatar
XDA: ASSIST
OP Recognized Contributor
Flag South Dakota
Thanks Meter: 2,574
 
6,533 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Several people have had trouble Installing Cm12 and Slimpop Otter X Roms.
Seems to be a variety of reasons for this.

-
For those having trouble with MTP on TWRP versions 2.8.X.X and Window 7
try Updating Windows Media Player
Quote:
Originally Posted by wicpp

I am having Windows XP SP3 and I was experiencing the same USB MTP installation failure, I updated my Windows Media Player and it fixed the problem. The option in Windows Media Player Help->Check for updates was not working, so I downloaded Media Player from Microsoft webiste and installed it and after that driver is now working fine.

  • Problem: Installed OtterX Bootloader, and now can't access bootmenu options with Power button, and just bootloops.
    Solution 1: Try Disconnect from PC, Power off (Hold Power button for 10-20 secs), connect to wall charger
    Solution 2 : Reflash TWRP
    Solution 3 : Reflash 2.05 bootloader
  • Problem: Twrp Cannot connect to PC. Device not found. In the device manager, Amazon OtterX is listed, but has an exclamation next it.
    Solution:
    If drivers were working before, try selecting drivers for device.
    Fixing OtterX Drivers: I posted screenshots of how Kindle should look like in Device manager, once converted to OtterX in post #9 here
    In Device manager>select unknown device or device with a yellow triangle or ! >Update driver software>
    browse my computer for driver software>Let me pick from a list of Device Drivers on my computer>
    show all(uncheck show only compatible)>look for ADB interface or android phone
    select yes to Ignore warning
    may need to reboot both.
  • Problem: Twrp is recognized by PC, but neither MPT mount, nor ADB push works. May get an unauthorized device error/warning
    Problem: Installed TWRP 2.8..X.X now whenever i try to get into recovery it goes to teamwin logo and goes back to the kindle fire screen
    Solution:
    If you are using Twrp 2.8.XX, use a Linux or Mac machine, or downgrade to 2.7.1.0 Twrp:
    Downgrade 2.8.X.X Twrp to 2.7.1.0 TWRP see Flashing TWRP in OtterX bootloader
  • Problem: When Installing Lollypop you get an :updater binary error"
    Solution:
    If you are still using bootloader 2.04, upgrade to 2.05:
    If you still can push files to Twrp, try pushing 2.05.zip, install, reboot, wipe cache, reboot, format data, wipe everything in wipe>advanced...

Partition Sizes and File System
It seems that if you use TWRP 2.8.XX when switching from Amazon to OtterX partitions, sometimes things are getting fouled up, could be that this was an issue before, but has been more noticeable with lollipop.
Partitions sizes for OtterX partitions with 2.05 bootloader should be ...
all should say Present: Yes
system: Current file System: Ext4 - Size: 751MB (768MB)
Cache: _Current File System: Ext4 - Size: 503MB (512MB)
Data:__Current File System: _ f2fs - Size: 5820MB (5880mb)
see post #2 for screenshots
  • If you have Twrp 2.7.1.0 and bootloader 2.05, and have wiped cache, rebooted, Fomated Data, wiped partitions in wipe>advanced and still have issues:
    Solution:
    Reboot to bootloader, select Amazon partitions, select recovery, wipe cache, reboot to bootloader select OtterX partitions, select recovery, wipe cache, reboot, format data, wipe all partitions.
  • Verify Partition sizes match post #2

Of course, all this assumes that drivers are installed correctly on you PC, none of the above will work if drivers are not correct.
If adb commands were working correctly before, and/or fastboot commands are still working, likely drivers are correct.

Please reply if this Guide helped
Please include: What errors you were having, and steps you took to fix.

I made Some videos that cover most of the steps
Flashing TWRP in OtterX bootloader
[How-To] Revert from OtterX Project to Stock Kindle Fire Partitions/Rom

Don't use the EMMC corruption fix
Quote:
Originally Posted by Hashcode

Why did you try EMMC corruption fix? That wipes out every partition on the device and attempts to restore the barebones xloader, bootloader

You'll need to flash a recovery.img via fastboot to get back up and running.

Last edited by sd_shadow; 22nd March 2015 at 06:20 PM.
The Following 12 Users Say Thank You to sd_shadow For This Useful Post: [ View ]
 
 
15th December 2014, 04:15 PM |#2  
sd_shadow's Avatar
XDA: ASSIST
OP Recognized Contributor
Flag South Dakota
Thanks Meter: 2,574
 
6,533 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Partition Screnshots
Select Wipe
Select Advanced
Check a Partition

Data Partition:
Data partition
Cache Partition
Cache Partition
System Partition
System Partition


Quote:
Originally Posted by Hashcode

...And all of the other partitions will be ext4, only userdata will be formatted f2fs.

Attached Thumbnails
Click image for larger version

Name:	IMG_20141215_112950_191.jpg
Views:	290
Size:	225.1 KB
ID:	3065567   Click image for larger version

Name:	IMG_20141215_113002_786.jpg
Views:	288
Size:	224.1 KB
ID:	3065568   Click image for larger version

Name:	IMG_20141215_113015_413.jpg
Views:	280
Size:	242.3 KB
ID:	3065569  
Last edited by sd_shadow; 6th March 2015 at 12:38 AM.
The Following 6 Users Say Thank You to sd_shadow For This Useful Post: [ View ]
15th December 2014, 04:16 PM |#3  
sd_shadow's Avatar
XDA: ASSIST
OP Recognized Contributor
Flag South Dakota
Thanks Meter: 2,574
 
6,533 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Flashing TWRP in OtterX bootloader
see [Video] Flashing TWRP in OtterX bootloader

Download
adb-fastboot.zip,
and an OtterX TWRP .IMG file like otterx-twrp-2.7.1.0-recovery.img
Size: 7528448 bytes MD5: ec8e8a67492d5fd06494f854bb59b2ae
for flashing OtterX Bootloader use otterx-u-boot_v2.05.bin
Size: 238720 bytes MD5: 241a3fd1edad0a0d95886ddeb4693e1c
Step 1:
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, and otterx-twrp-2.7.1.0-recovery.img to adb folder.
Step 2
connect Kindle Fire to pc, via usb, power off Kindle
Step 3
Open a Command Prompt (start>all programs>accessories>Command prompt)
change directory to adb with
Code:
cd\adb
fastboot devices
Power on Kindle
should get a return code back something like
Code:
123456789abcde  kindle
if so enter
Code:
fastboot flash recovery otterx-twrp-2.7.1.0-recovery.img
Code:
fastboot reboot
after reboot you should be able to enter recovery by pressing power button once and selecting recovery

if you don't get a reply with fastboot devices, and you have checked drivers and it is listed as android phone>adb interface
flashing may still work
Code:
fastboot flash recovery otterx-twrp-2.7.1.0-recovery.img
Code:
fastboot reboot
-

if still unable to enter recovery, may need to reflash bootloader
same steps
Code:
fastboot flash bootloader otterx-u-boot_v2.05.bin
Code:
fastboot reboot
if unable to get partitions correct, or adb was working but now does not, could be that something wrong with the bootloader, flashing
otterx-u-boot_v2.04.bin may fix
download otterx-u-boot_v2.04.bin
verify md5: 30569AE834BAFD70D6E7EFB90338F4CB
Code:
flashboot flash bootloader otterx-u-boot_v2.04.bin
Code:
fastboot reboot
In Bootloader, select Amazon partitions
select recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
select reboot system (don't worry about system not rooted warning, or no rom installed, just select an option)
In bootloader>select OtterX partitions
reboot recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
reflash 2.05 bootloader
Code:
fastboot flash bootloader otterx-u-boot_v2.05.bin
Code:
fastboot reboot
In Bootloader, select Amazon partitions
select recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
In bootloader>select OtterX partitions
reboot recovery
in TWRP>Wipe>Advanced Wipe>check Cache>swipe to wipe
reboot recovery
Wipe>format data
Wipe>Advanced Wipe>check all>swipe to wipe
reboot recovery
if using 2.7.10 try adb push
if using 2.8.X.X try MTP
Last edited by sd_shadow; 1st March 2015 at 05:45 AM.
The Following 7 Users Say Thank You to sd_shadow For This Useful Post: [ View ]
15th December 2014, 04:44 PM |#4  
lovejoy777's Avatar
Recognized Developer
Flag Nottingham
Thanks Meter: 3,968
 
3,464 posts
Join Date:Joined: Dec 2011
Donate to Me
More
you have single handed saved so many kindles. thanks for your continued support. cheers steve. long live otterx

Sent from my Nexus 5 using Tapatalk
The Following 4 Users Say Thank You to lovejoy777 For This Useful Post: [ View ]
16th December 2014, 03:50 AM |#5  
Junior Member
Thanks Meter: 1
 
3 posts
Join Date:Joined: Dec 2014
More
Thumbs up Thanks
Thanks so much @sd_shadow, your instructions saved my Kindle Fire. I flashed twrp v2.7.1.0 from v2.8.1.0 and it worked properly.
The Following User Says Thank You to bow_one For This Useful Post: [ View ]
16th December 2014, 08:04 AM |#6  
Junior Member
Thanks Meter: 1
 
9 posts
Join Date:Joined: Mar 2011
Smile Still using TWRP 2.8.x.x
I have idea for using TWRP 2.8.x.x without error when flash new ROM
The steps to perform this is:
Step 1: Wipe Factory Reset
Step 2: Intall Slim-otterx-5.0.1.alpha.0.7-v0.3.zip
Step 3: Intall newest version: Slim-otterx-5.0.1.alpha.0.9-V0.8.zip
Step 4: Install Gapps and Restart

It is successful with me. You can try it and give me comment if you can't.
17th December 2014, 04:29 PM |#7  
Junior Member
Flag Oldsmar, Florida
Thanks Meter: 3
 
26 posts
Join Date:Joined: Jun 2011
More
Partition info in TWRP 2.7.1.0 ?
Great stuff @sd_shadow, keep up the good work. Where in twrp are you seeing the screens in post #2?
Thanks,
The Don
17th December 2014, 04:47 PM |#8  
sd_shadow's Avatar
XDA: ASSIST
OP Recognized Contributor
Flag South Dakota
Thanks Meter: 2,574
 
6,533 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Quote:
Originally Posted by DonDeLome

Great stuff @sd_shadow, keep up the good work. Where in twrp are you seeing the screens in post #2?
Thanks,
The Don

Good question,
Wipe> Advanced> check a partition (Cache, System, or Data) then select Repair or Change File System

Sent from my XT907 using Tapatalk
Last edited by sd_shadow; 17th December 2014 at 04:59 PM.
The Following 3 Users Say Thank You to sd_shadow For This Useful Post: [ View ]
17th December 2014, 05:16 PM |#9  
sd_shadow's Avatar
XDA: ASSIST
OP Recognized Contributor
Flag South Dakota
Thanks Meter: 2,574
 
6,533 posts
Join Date:Joined: Sep 2011
Donate to Me
More
Screenshot of Device Manager and OtterX Drivers
If you have not used the install.drivers.bat from Kindle Fire Utility, download, unzip, run install.drivers.bat.
KFU mirrors: AFH - Mega

Steps 1-3
Step 4

show all(uncheck show only compatible)>look for ADB interface or android phone

Step 5
Step 6
Step 7

If that worked Kindle should now look like this


Correct Drivers
Last edited by sd_shadow; 25th February 2015 at 04:04 PM.
The Following 2 Users Say Thank You to sd_shadow For This Useful Post: [ View ]
18th December 2014, 04:29 PM |#10  
Junior Member
Thanks Meter: 0
 
12 posts
Join Date:Joined: May 2011
Hi,

i have a problem.... every step works fine until adb push after step 3.

when i try to push the zip files to my device i only get "error: device unauthorized. Please check the confirmation dialog on your device"

But after step 3 there is no OS anymore to boot in an confirm.

How to solve the problem?
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes