Develop Bugs

[Q] Kindle Fire HD 8.9" un-unbrickably bricked?

Hello everyone,
So I got bored of my Kindle Fire HD 8.9" 's limitations and decided to root it and install a second bootloader. The rooting went along just fine (used bin4ry's method). Even as I tried installing a second bootloader, everything seemed to go normally.
I used @Hashcode 's method from this thread: http://forum.xda-developers.com/showthread.php?t=2128175
However, after Step 5 (when I should have got a blue Kindle Fire logo), the device got bricked. No screen, no nothing. I can't even hard reset (tried holding power done for 20 seconds, 30 seconds, 300 seconds) or get it to connect to my computer to fastboot / adb / anything.
The worst part is that I cannot even use a factory cable now, because the 8.9" doesn't support it for resetting. The device was almost fully charged to begin with and I recharged it once more overnight just to be sure.
Did I do anything wrong? Any ideas?
Here's what happened:
Code:
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb pull /sdcard/boot0block.i
mg
4740 KB/s (2097152 bytes in 0.432s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb pull /sdcard/stock-boot.img
4077 KB/s (8388608 bytes in 2.009s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb pull /sdcard/stock-recovery.img
4415 KB/s (8388608 bytes in 1.855s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb pull /sdcard/stock-system.img
4078 KB/s (929038336 bytes in 222.434s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb push stack /data/local/tmp/
190 KB/s (4096 bytes in 0.021s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb shell su -c "dd if=/data/
local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=65194
88 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb shell su -c "mount -o rem
ount,rw ext4 /system"
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb shell su -c "mv /system/e
tc/install-recovery.sh /system/etc/install-recovery.sh.bak"
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb shell su -c "mount -o rem
ount,ro ext4 /system"
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb devices
List of devices attached
B0CB06033056015K device
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>fastboot -i 0x1949 flash boot
loader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (6 KB)...
OKAY [ 0.011s]
writing 'bootloader'...
OKAY [ 0.030s]
finished. total time: 0.048s
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>fastboot -i 0x1949 flash boot
kfhd8-freedom-boot-8.3.0.img
target reported max download size of 1006632960 bytes
sending 'boot' (6 KB)...
OKAY [ 0.010s]
writing 'boot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>fastboot -i 0x1949 flash reco
very kfhd8-twrp-2.4.4.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (6 KB)...
OKAY [ 0.008s]
writing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.041s
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb devices
List of devices attached

What system version? Make sure the device is off truly then try to get it into fastboot again. at that point you could flash stock system, boot and recovery. The only thing you cannot restore would be the boot product bin as you can see that wasn`t part of the backup procedure. Your right the factory cable will do nothing. Did you perform md5 check on all the files you used?

Device truly off?
Thepooch said:
What system version? Make sure the device is off truly then try to get it into fastboot again. at that point you could flash stock system, boot and recovery. The only thing you cannot restore would be the boot product bin as you can see that wasn`t part of the backup procedure. Your right the factory cable will do nothing. Did you perform md5 check on all the files you used?
Click to expand...
Click to collapse
Thanks for your response!
I think I had 8.4.3 (is that right?). I did follow instructions to flash the 8.1.something file before, if that's what you're asking. How do I make sure that the device is truly off? It looks off pretty much all the time.
I just called up Amazon and they said they'd send me a free replacement, but I went ahead and told them I rooted it. Didn't want them to pay for my sins.

blopido said:
Thanks for your response!
I think I had 8.4.3 (is that right?). I did follow instructions to flash the 8.1.something file before, if that's what you're asking. How do I make sure that the device is truly off? It looks off pretty much all the time.
I just called up Amazon and they said they'd send me a free replacement, but I went ahead and told them I rooted it. Didn't want them to pay for my sins.
Click to expand...
Click to collapse
long press the power button for 30 seconds then
Code:
fastboot -i 0x1949 getvar product
in terminal and when it says waiting for device plug in your kindle. If after multiple attempts it will no go into fastboot I can only assume that for some reason it is permanently bricked, at this point you should post in bootloader install thread in development the result so no one else makes this same mistake and Hashcode can look into what is broken for 8.4.3. Amazon may have finally patched up the 2nd bootloader install method for 8.4.3 resulting in a permanent brick. Thanks Amazon nice work!!

Thepooch said:
long press the power button for 30 seconds then
Code:
fastboot -i 0x1949 getvar product
in terminal and when it says waiting for device plug in your kindle. If after multiple attempts it will no go into fastboot I can only assume that for some reason it is permanently bricked, at this point you should post in bootloader install thread in development the result so no one else makes this same mistake and Hashcode can look into what is broken for 8.4.3. Amazon may have finally patched up the 2nd bootloader install method for 8.4.3 resulting in a permanent brick. Thanks Amazon nice work!!
Click to expand...
Click to collapse
Thanks @Thepooch. I tried the fastboot option multiple times but to no avail. I think it is well and truly bricked. Also, I can't post to the dev forums, so I've sent a PM to Hashcode.
Thanks again for your help. Do you think opening up the device might help? Reset the battery or something? Or can I get any value for this device?

Thepooch said:
long press the power button for 30 seconds then
Code:
fastboot -i 0x1949 getvar product
in terminal and when it says waiting for device plug in your kindle. If after multiple attempts it will no go into fastboot I can only assume that for some reason it is permanently bricked, at this point you should post in bootloader install thread in development the result so no one else makes this same mistake and Hashcode can look into what is broken for 8.4.3. Amazon may have finally patched up the 2nd bootloader install method for 8.4.3 resulting in a permanent brick. Thanks Amazon nice work!!
Click to expand...
Click to collapse
Can someone confirm that you can use older version to flash over newer (i.e. 8.1 files on a device on 8.4.3) w/o problem ??
Have a 8.4.3 devce in fastboot where I need to put stock images on which I don't have for 8.4.3. ...
Could this, in your case, have caused 2nd bootloader intallation/brick issues?

Toobii said:
Can someone confirm that you can use older version to flash over newer (i.e. 8.1 files on a device on 8.4.3) w/o problem ??
Have a 8.4.3 devce in fastboot where I need to put stock images on which I don't have for 8.4.3. ...
Could this, in your case, have caused 2nd bootloader intallation/brick issues?
Click to expand...
Click to collapse
Not sure, Toobii. Will wait for @Hashcode to react. He probably has the best idea.

I managed to go back to 8.3.1 from 8.4.3 after getting a Red Screen from fastboot, then let the Kindle update itself back to 8.4.3 before rooting and installing a 2nd bootloader again (using KFF). Just be careful to follow Hashcode's procedure and you should be good to go.

GenghisKhan67 said:
I managed to go back to 8.3.1 from 8.4.3 after getting a Red Screen from fastboot. Just be careful to follow Hashcode's procedure and you should be good to go.
Click to expand...
Click to collapse
I did it as well, as the log says. It's completely bricked, no red screen etc.

GenghisKhan67 said:
I managed to go back to 8.3.1 from 8.4.3 after getting a Red Screen from fastboot, then let the Kindle update itself back to 8.4.3 before rooting and installing a 2nd bootloader again (using KFF). Just be careful to follow Hashcode's procedure and you should be good to go.
Click to expand...
Click to collapse
How exactly did you go back from 8.43 to 8.31?

blopido said:
I did it as well, as the log says. It's completely bricked, no red screen etc.
Click to expand...
Click to collapse
I still wonder did you perform an md5 check on your files? I myself was able to roll back from 8.4.1 all the way to 8.1.4 but the method was special developed by soupmagnet just for me. it replaced boot, bootloader, recovery and system all in one swoop then I flashed Hashcodes 8.4.1 which is where I am presently. None of this has been tested with 8.4.3 nor am I willing to even go there. Amazon whipped out that 8.4.3 very soon after they had pulled 8.4.1 for some reason . Seems devious if you ask me why would the do this unless it was to patch some final hole. Since you can purchase a new motherboard on the net for around 200$ it places a value on your screen, digitizer, case and battery at about 100$ sad but true.

Thepooch said:
I still wonder did you perform an md5 check on your files?
Click to expand...
Click to collapse
TBH, no I didn't.
Thanks for the estimate, will see where I can sell it.

blopido said:
TBH, no I didn't.
Thanks for the estimate, will see where I can sell it.
Click to expand...
Click to collapse
Question: Can someone with Jtag or something similar help reflash the ROM?

badbutz said:
How exactly did you go back from 8.43 to 8.31?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=42538836&postcount=8

Kindle Fire HD 8.9" un-unbrickably bricked
blopido said:
Hello everyone,
So I got bored of my Kindle Fire HD 8.9" 's limitations and decided to root it and install a second bootloader. The rooting went along just fine (used bin4ry's method). Even as I tried installing a second bootloader, everything seemed to go normally.
I used @Hashcode 's method from this thread: http://forum.xda-developers.com/showthread.php?t=2128175
However, after Step 5 (when I should have got a blue Kindle Fire logo), the device got bricked. No screen, no nothing. I can't even hard reset (tried holding power done for 20 seconds, 30 seconds, 300 seconds) or get it to connect to my computer to fastboot / adb / anything.
The worst part is that I cannot even use a factory cable now, because the 8.9" doesn't support it for resetting. The device was almost fully charged to begin with and I recharged it once more overnight just to be sure.
Did I do anything wrong? Any ideas?
Click to expand...
Click to collapse
blopido,
You did everything perfectly. This is the risk we take when deploying the second bootloader with TWRP Recovery.
First, let me apologize for the delay, I have been out. I just responded to your message but the core is:
We will attempt recovery, if the recovery fails we will facilitate contacting Amazon on your behalf and ask for a replacement. We do advise Amazon that the device was Rooted and during a software install the device was damaged. This can be a hit and miss but they usually replace the device for free. I do have to warn you, your account will be flagged and they will be less forgiving a second time, just a heads up.
Send the Kindle to:
Xerocomm, Inc.
RMA # (Send email for number)
1684 Northstar Drive
Petaluma, CA 94954
(707) 774-5923
Please do not send the device without a Return Authorization ([email protected]) otherwise the box will be refused.
I responded to your email, I will be looking for your response.

prokennexusa said:
blopido,
You did everything perfectly. This is the risk we take when deploying the second bootloader with TWRP Recovery.
First, let me apologize for the delay, I have been out. I just responded to your message but the core is:
We will attempt recovery, if the recovery fails we will facilitate contacting Amazon on your behalf and ask for a replacement. We do advise Amazon that the device was Rooted and during a software install the device was damaged. This can be a hit and miss but they usually replace the device for free. I do have to warn you, your account will be flagged and they will be less forgiving a second time, just a heads up.
Send the Kindle to:
Xerocomm, Inc.
RMA # (Send email for number)
1684 Northstar Drive
Petaluma, CA 94954
(707) 774-5923
Please do not send the device without a Return Authorization ([email protected]) otherwise the box will be refused.
I responded to your email, I will be looking for your response.
Click to expand...
Click to collapse
Thanks. Taking this conversation to email.

JTAG
blopido said:
Question: Can someone with Jtag or something similar help reflash the ROM?
Click to expand...
Click to collapse
blopido,
So far that is used on the Sony XBOX 360 and alike there is nothing similar available for the Kindle, yet....
UrJTAG

blopido said:
Hello everyone,
So I got bored of my Kindle Fire HD 8.9" 's limitations and decided to root it and install a second bootloader. The rooting went along just fine (used bin4ry's method). Even as I tried installing a second bootloader, everything seemed to go normally.
I used @Hashcode 's method from this thread: http://forum.xda-developers.com/showthread.php?t=2128175
However, after Step 5 (when I should have got a blue Kindle Fire logo), the device got bricked. No screen, no nothing. I can't even hard reset (tried holding power done for 20 seconds, 30 seconds, 300 seconds) or get it to connect to my computer to fastboot / adb / anything.
The worst part is that I cannot even use a factory cable now, because the 8.9" doesn't support it for resetting. The device was almost fully charged to begin with and I recharged it once more overnight just to be sure.
Did I do anything wrong? Any ideas?
Here's what happened:
Code:
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb pull /sdcard/boot0block.i
mg
4740 KB/s (2097152 bytes in 0.432s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb pull /sdcard/stock-boot.img
4077 KB/s (8388608 bytes in 2.009s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb pull /sdcard/stock-recovery.img
4415 KB/s (8388608 bytes in 1.855s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb pull /sdcard/stock-system.img
4078 KB/s (929038336 bytes in 222.434s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb push stack /data/local/tmp/
190 KB/s (4096 bytes in 0.021s)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb shell su -c "dd if=/data/
local/tmp/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=65194
88 seek=1"
0+1 records in
0+1 records out
4096 bytes transferred in 0.001 secs (4096000 bytes/sec)
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb shell su -c "mount -o rem
ount,rw ext4 /system"
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb shell su -c "mv /system/e
tc/install-recovery.sh /system/etc/install-recovery.sh.bak"
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb shell su -c "mount -o rem
ount,ro ext4 /system"
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb devices
List of devices attached
B0CB06033056015K device
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>fastboot -i 0x1949 flash boot
loader kfhd8-u-boot-prod-8.1.4.bin
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'bootloader' (6 KB)...
OKAY [ 0.011s]
writing 'bootloader'...
OKAY [ 0.030s]
finished. total time: 0.048s
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>fastboot -i 0x1949 flash boot
kfhd8-freedom-boot-8.3.0.img
target reported max download size of 1006632960 bytes
sending 'boot' (6 KB)...
OKAY [ 0.010s]
writing 'boot'...
OKAY [ 0.031s]
finished. total time: 0.047s
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>fastboot -i 0x1949 flash reco
very kfhd8-twrp-2.4.4.0-recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (6 KB)...
OKAY [ 0.008s]
writing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.041s
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>adb devices
List of devices attached
Click to expand...
Click to collapse
Every fastboot command returns "sending xxx (6KB)" thats definitely sth wrong.
Looks like you didn't put the proper file on the directory and you continued without noticing that.
Here is the correct response(taken from another xda thread, its for KFHD7 but you get the idea)
C:\>fastboot -i 0x1949 flash boot kfhd7-freedom-boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8145 KB)...
OKAY [ 2.794s]
writing 'boot'...
OKAY [ 0.681s]
finished. total time: 3.475s
My suggestion: Play dumb and send it back to Amazon for warranty replacement.

arda99 said:
Every fastboot command returns "sending xxx (6KB)" thats definitely sth wrong.
Looks like you didn't put the proper file on the directory and you continued without noticing that.
Here is the correct response(taken from another xda thread, its for KFHD7 but you get the idea)
C:\>fastboot -i 0x1949 flash boot kfhd7-freedom-boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8145 KB)...
OKAY [ 2.794s]
writing 'boot'...
OKAY [ 0.681s]
finished. total time: 3.475s
Click to expand...
Click to collapse
I got that too.
C:\Users\WindowsUserName\Desktop\For Kindle Fire\adt-bundle-windows-x86-20130514\
adt-bundle-windows-x86-20130514\sdk\platform-tools>fastboot -i 0x1949 flash boot
kfhd8-freedom-boot-8.3.0.img
target reported max download size of 1006632960 bytes
sending 'boot' (6 KB)...
OKAY [ 0.010s]
writing 'boot'...
OKAY [ 0.031s]
finished. total time: 0.047s
Click to expand...
Click to collapse
My suggestion: Play dumb and send it back to Amazon for warranty replacement.
Click to expand...
Click to collapse
As I said, I don't want to. Don't think it's right. Have sent it to @prokennexusa. Let's see how it goes.

blopido said:
I got that too.
As I said, I don't want to. Don't think it's right. Have sent it to @prokennexusa. Let's see how it goes.
Click to expand...
Click to collapse
You got "sending 6KB" as I said that's wrong. Its not the "everything is OK but sh*t just happens" story. You did it completely wrong and bricked the device, hopefully you could be aware of the issue and get things right on the replacement.

[Q] Can't get fastboot even with cable.

Windows 7, completely fresh installation, plug powered down kindle fire in with fastboot cable and just boots regularly. I cannot figure this out at all! Please help.

Update
Okay, so I was able to switch back to an ubuntu system and here is what I have:
I can enter fastboot mode and perform operations. Following the twrp - second bootloader guide results in a boot loops and I am unable to get past the orange kindle fire logo, it doesn't do anything at all.
Under linux does anyone know what I need to do to get this thing working again!? I have never had so many problems with a device! Ahhh, wish I hadn't tried to add wallpapers.
The issues started when I tried to push framework.odex and services.odex and it didn't go.

Solved
Okay, for anyone running Ubuntu like I was and stuck in a boot loop here's what I did:
Download stock recovery.img and boot.img.
Download KFHD_SRT V ??? tool or any other stock system.img.
Flash the three files using fastboot, then reboot will give you all stock restore.
sudo fastboot -i 0x1949 flash system system2.img
target reported max download size of 1006632960 bytes
sending 'system' (907264 KB)...
OKAY [ 66.375s]
writing 'system'...
OKAY [ 62.345s]
finished. total time: 128.720s
sudo fastboot -i 0x1949 flash recovery recovery.img
< waiting for device >
target reported max download size of 1006632960 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.610s]
writing 'recovery'...
OKAY [ 1.488s]
finished. total time: 2.098s
sudo fastboot -i 0x1949 flash boot boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.628s]
writing 'boot'...
OKAY [ 1.046s]
finished. total time: 1.674s
sudo fastboot -i 0x1949 reboot
rebooting...

[Q] Kindle Fire 2 won't boot or charge

Earlier this week my daughter handed me her Kindle Fire saying it was hanging on boot and did not seem to be charging.
Background
Originally purchased as a Kindle Fire I replaced the motherboard when the USB socket broke away and it could not be soldered back (pad was missing). I purchase and fitted a replacement motherboard from the US and on arrival it turned out to be a Kindle Fire 2 motherboard.
The only differences apart from the faster processor and more RAM was that the socket for the ambient light sensor was missing. Anyhow I fitted the board and all has been fine for a year.
Symptoms
When switched on it displayed the battery symbol displayed so it was plugged into a 1Amp charger and left overnight. The next morning it was displaying the standard orange Kindle Fire boot logo no animation.
I disconnected from the power supply and did the 20 second power button reset. When it was powered back on each time the orange Kindle Fire logo was displayed with no animation and there it would stop. Disconnected from the power it would stay in the state for over an hour making me think that the battery had a reasonable charge although the charging light never actually went green. Eventually it would go back to the critical battery state as seen initially.
I have repeated the overnight charge process and reset several times with the same results. Whilst plugged in the amber charge light was displayed but never went green.
At this point I decided that it must be because it was not getting past the bootloader and as a result it was not reaching the proper state to be able to charge properly. So I thought it might be a problem with the software and decided to re-flash everything (maybe the battery had died during OTA update I thought) and I purchased a factory/fastboot cable.
I used the tools and images in the KFFirstAide several times using the 10.2.1 and 10.2.3 images (example shown below). But each time the results where the same after a reset the device would either go straight to the static orange Kindle Fire logo or show the battery symbol apparently charge a little at some point boot to the orange Kindle Fire logo.
At this point I am thinking it is a problem with the battery but before I go and spend £30 on a device where I have already replaced the motherboard for $50 and I want to be sure there are no other options, the current used price on ebay seems to be around £50-70 for a similar device.
My daughter is happy to give up on it but my curiosity is piqued and I want to know what is actually wrong and are there any more diagnostics.
I am unix fluent (software developer for 28 years, my first linux distro (slackware was on 40 x 3.5Mb disks!) so if necessary I could switch to using linux tools if that helps.
Is it worth checking the battery with a multi meter?
Code:
C:\Kindle Fire Restore\10.2.3>fastboot -i 0x1949 getvar product
product: Otter2-Prod-04
finished. total time: 0.004s
C:\Kindle Fire Restore>fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
target reported max download size of 486539264 bytes
sending 'bootloader' (227 KB)...
OKAY [ 0.234s]
writing 'bootloader'...
OKAY [ 0.047s]
finished. total time: 0.312s
C:\Kindle Fire Restore>fastboot -i 0x1949 flash boot 10.2.1\boot.img
target reported max download size of 486539264 bytes
sending 'boot' (8192 KB)...
OKAY [ 0.515s]
writing 'boot'...
OKAY [ 0.905s]
finished. total time: 1.420s
C:\Kindle Fire Restore>fastboot -i 0x1949 flash recovery 10.2.1\recovery.img
target reported max download size of 486539264 bytes
sending 'recovery' (8192 KB)...
OKAY [ 0.515s]
writing 'recovery'...
OKAY [ 0.905s]
finished. total time: 1.420s
C:\Kindle Fire Restore>fastboot -i 0x1949 flash system 10.2.1\system.img
target reported max download size of 486539264 bytes
sending sparse 'system' (465730 KB)...
OKAY [ 17.940s]
writing 'system'...
OKAY [ 51.563s]
sending sparse 'system' (312222 KB)...
OKAY [ 12.293s]
writing 'system'...
OKAY [ 35.334s]
finished. total time: 117.161s
C:\Kindle Fire Restore>fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [191.877s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.127s]
erasing 'cache'...
OKAY [ 76.959s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.140s]
finished. total time: 269.108s

[Q] KFU Hung Up During Root

Hey everyone. Today I downloaded KFU, installed the drivers that came with it, and attempted to root the device. It's been hung up for a while and I'm not sure why.
Any advice or input would be much appreciated. Let me know if there is any more useful information I can provide.
The device is a stock Kindle Fire 1
Using KFU 0.9.9
The Kindle is currently displaying the "Kindle Fire" logo
Here is the output from KFU: (I was going to use pastebin but the forum wouldn't let me post a link so sorry if its a bit long)
Code:
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
6833 KB/s (510876 bytes in 0.073s)
The kindle has been told to reboot in Fastboot Mode.
twrp.img is missing.
So we will download it for you!
--2014-11-11 15:15:59-- hxxp://techerrata.com/file/twrp2/blaze/openrecovery-twr
p-2.6.3.1-otter.img
Resolving techerrata.com... 176.9.80.197
Connecting to techerrata.com|176.9.80.197|:80... connected.
hxxp request sent, awaiting response... 302 Found
Location: hxxp://techerrata.com/get/twrp2/blaze/openrecovery-twrp-2.6.3.1-otter.
img [following]
--2014-11-11 15:15:59-- hxxp://techerrata.com/get/twrp2/blaze/openrecovery-twrp
-2.6.3.1-otter.img
Reusing existing connection to techerrata.com:80.
hxxp request sent, awaiting response... 200 OK
Length: 6930432 (6.6M) [application/octet-stream]
Saving to: `recovery/twrp.img'
100%[======================================>] 6,930,432 1.45M/s in 7.7s
2014-11-11 15:16:07 (874 KB/s) - `recovery/twrp.img' saved [6930432/6930432]
Download successful.
fff.bin is missing.
So we will download it for you!
--2014-11-11 15:16:07-- hxxp://random.kennocha.com/kindle/firefirefire/fff-u-bo
ot_v1.4a.bin
Resolving random.kennocha.com... 108.61.31.94
Connecting to random.kennocha.com|108.61.31.94|:80... connected.
hxxp request sent, awaiting response... 200 OK
Length: 249532 (244K) [application/octet-stream]
Saving to: `recovery/fff.bin'
100%[======================================>] 249,532 376K/s in 0.6s
2014-11-11 15:16:08 (376 KB/s) - `recovery/fff.bin' saved [249532/249532]
Download successful.
***********************************************
* NOTICE *
***********************************************
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.067s]
writing 'bootloader'...
OKAY [ 0.054s]
finished. total time: 0.124s
Installing TWRP...
sending 'recovery' (6768 KB)...
OKAY [ 1.699s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 2.715s
Setting Recovery Bootmode.
...
OKAY [ 0.000s]
finished. total time: 0.002s
rebooting...
finished. total time: 1.014s
Please wait...

Lemern said:
Hey everyone. Today I downloaded KFU, installed the drivers that came with it, and attempted to root the device. It's been hung up for a while and I'm not sure why.
Any advice or input would be much appreciated. Let me know if there is any more useful information I can provide.
The device is a stock Kindle Fire 1
Using KFU 0.9.9
The Kindle is currently displaying the "Kindle Fire" logo
Here is the output from KFU: (I was going to use pastebin but the forum wouldn't let me post a link so sorry if its a bit long)
Code:
***********************************************
* Installing Permanent Root *
***********************************************
***********************************************
* Activating Fastboot (4002) *
***********************************************
6833 KB/s (510876 bytes in 0.073s)
The kindle has been told to reboot in Fastboot Mode.
twrp.img is missing.
So we will download it for you!
--2014-11-11 15:15:59-- hxxp://techerrata.com/file/twrp2/blaze/openrecovery-twr
p-2.6.3.1-otter.img
Resolving techerrata.com... 176.9.80.197
Connecting to techerrata.com|176.9.80.197|:80... connected.
hxxp request sent, awaiting response... 302 Found
Location: hxxp://techerrata.com/get/twrp2/blaze/openrecovery-twrp-2.6.3.1-otter.
img [following]
--2014-11-11 15:15:59-- hxxp://techerrata.com/get/twrp2/blaze/openrecovery-twrp
-2.6.3.1-otter.img
Reusing existing connection to techerrata.com:80.
hxxp request sent, awaiting response... 200 OK
Length: 6930432 (6.6M) [application/octet-stream]
Saving to: `recovery/twrp.img'
100%[======================================>] 6,930,432 1.45M/s in 7.7s
2014-11-11 15:16:07 (874 KB/s) - `recovery/twrp.img' saved [6930432/6930432]
Download successful.
fff.bin is missing.
So we will download it for you!
--2014-11-11 15:16:07-- hxxp://random.kennocha.com/kindle/firefirefire/fff-u-bo
ot_v1.4a.bin
Resolving random.kennocha.com... 108.61.31.94
Connecting to random.kennocha.com|108.61.31.94|:80... connected.
hxxp request sent, awaiting response... 200 OK
Length: 249532 (244K) [application/octet-stream]
Saving to: `recovery/fff.bin'
100%[======================================>] 249,532 376K/s in 0.6s
2014-11-11 15:16:08 (376 KB/s) - `recovery/fff.bin' saved [249532/249532]
Download successful.
***********************************************
* NOTICE *
***********************************************
Fastboot uses a different device than ADB.
You should check device manager for "Kindle" or "Amazon"
If you see it, rerun the driver installer that came packaged with KFU.
Installing FFF...
< waiting for device >
sending 'bootloader' (243 KB)...
OKAY [ 0.067s]
writing 'bootloader'...
OKAY [ 0.054s]
finished. total time: 0.124s
Installing TWRP...
sending 'recovery' (6768 KB)...
OKAY [ 1.699s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 2.715s
Setting Recovery Bootmode.
...
OKAY [ 0.000s]
finished. total time: 0.002s
rebooting...
finished. total time: 1.014s
Please wait...
Click to expand...
Click to collapse
Kindle fire utility no longer works to root as of update 6.3.3
See http://forum.xda-developers.com/showthread.php?t=2814955
[How To][Root] Kindle Fire 1 update 6.3.3 [2014]
Sent from my DROIDX using Tapatalk

[DEV][N][DP2][CRACKLING]Android N Developer Preview

Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Latest = DP2
Manual:
Unlock bootloader
Install TWRP
Install OEM
Download OEM oem.img
Enter commands into fastboot
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem oem.img
Download files from here (Only System and Boot)
Flash files
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Reboot into TWRP
Make wipe data & wipe cache
Reboot phone
All works fine.
Sorry for my bad english and russian site server.

FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech/ANDROIDN
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
IFlashed. Works fine so far. Gapps are included in preview. Many thanks

FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
Click to expand...
Click to collapse
Does it have OTA?
---------- Post added at 06:32 AM ---------- Previous post was at 05:55 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
Does it have OTA?
Click to expand...
Click to collapse
I am having an issue flashing. I flash using TWRP and when I reboot it says "No OS Installed". Also when I tried via fastboot. Is there any thing I am missing?

No root and OTA.
Before flashing via fastboot wipe data through twrp.

mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
Could you upload a screenshot?

mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
I did exactly that and still stuck in boot

http://4pda.ru/forum/index.php?showtopic=730213&st=120#entry47858392
Use Google translate to see instructions

Phew! some development on the Crackling!
:good:
Very impressed... TWRP method didn't wrk, fastboot worked fine! thankyou for bringing it here too, my Russian is non existent
My 1st impressions:
Very good, I haven't encountered any major issues..... I'll keep testing

Well, I just installed on my trusty Wileyfox Swift.
Overall I'm impressed, however the sensors are not working- gyro/ accelerometer/ proximity. There is some conflict with libraries when starting a game.
With a few more updates (fingers crossed) I can see myself using it as a daily driver
Everything else works and works really well. The phone seems a lot faster, the SDcard was formatted (haven't tested using an app from it but games are out of the question anyway), dual-window will be neat and is fine at the moment.
There is a lot to like here with few issues.
PS: After reading a bit from the older threads on XDA and from 4pda.ru , it seems the sensor issue is connected to the bridge to enable Android One roms with FindYanot's oem image on our crackling. Really impressive thus far. I wonder if we can flash General Mobile 4G firmware with QFIL?

I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.

cleversokol said:
I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.
Click to expand...
Click to collapse
I've had the opposite experience. Fastboot works without fail on Mac and Linux. Windows- not so much with the Swift.
Flash TWRP manually - fastboot flash recovery your_recovery_image.img (replace with the file name for TWRP)
You've just installed the patched oem.img (to allow code name "seed" images) along with boot and system. Can't boot to recovery if you don't have one
Steer away from flashing other files from the Android One stock image (it will be even messier hardbrick and you would have to follow the instructions from the other thread).
If you want to return to stock COS, follow the instructions from these awesome people : http://forum.cyanogenmod.org/topic/118287-manual-flashing-of-stock-cyanogenos/
PS: For some reason, unlocking the bootloader for me worked with: fastboot oem unlock-go
but not with:
fastboot -i 0x2970 oem unlock-go
Locking with: fastboot oem lock-go , worked as expected

Can I use this TWRP? I did not found Wileyfox Swift among supported devices.

cleversokol said:
Can I use this TWRP? I did not found Wileyfox Swift among supported devices.
Click to expand...
Click to collapse
I believe this is the one I've used.
In case the Windows tool for Wileyfox works for you (I'm missing some C# utilities on mine and can't deal with it atm), you can add TWRP from there as well.
PS: I used it only to install initially this preview. I haven't used it after.

Sucessfully installed TWRP3.0 (CM13-nightly-recovery did not work for me. Keep getting image of Android with red exclamation mark), wiped cache, data and installed CM13-nightly + GAPPS Mini. Booted into CM, did basic setup. After that I wanted to re-lock the bootloader.
With
Code:
fastboot oem lock-go
it worked, but after this command I got brick-phone again.
Only replacing the battery + re-unlocking the device helped to restore it.
Is there a way to keep device working with locked bootloader?

Lock the bootloader only if you'll be using stock signed images of CyanogenOS. That is in case you will have to return the device due to hardware fault- dead pixels, non functioning microphones/ speakers, etc. Another reason as of why you might want to relock, is to ensure that you'll be using CyanogenOS recovery and no problems with future OTAs (no guarantee there as encrypted devices had problems with first official update but things are looking nice for future official OTAs).
If you want to use custom recovery- TWRP/CMRecovery by itself or along with CyanogenMod13 or any other custom ROM- do not lock the bootloader.
These are your options Keep the bootloader unlocked unless you have the need/ desire to return it to true stock.

I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?

yasteellutch said:
I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?
Click to expand...
Click to collapse
System img is big and post propably your fastboot installer cannot handle it.
Try this fastboot installer
http://forum.xda-developers.com/showthread.php?t=2588979

This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
Click to expand...
Click to collapse
It keeps on saying sending sparse system img(0kb)

yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
It keeps on saying sending sparse system img(0kb)
Click to expand...
Click to collapse
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.

mermigas said:
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.
Click to expand...
Click to collapse
This is what I get