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...
hi guys
i have lg g3 D855 after update its dead and now its only stay on lg logo i tried to flash new rom but when i try to go the download mode its going to fastboot mood then i try to flash laf.img its give me this error
C:\New folder\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 2147483648 bytes
sending 'boot' (12800 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 10.470s
C:\New folder\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (17408 KB)...
OKAY [ 0.552s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 10.617s
C:\New folder\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.036s
also i get the same error with flashing the recovery file
so whats wrong and what should i do to fix this?
Run fastboot boot laf.img
Plug G3 into LGFlashTool and flash KDZ using CSM flash
itsbighead said:
Run fastboot boot laf.img
Plug G3 into LGFlashTool and flash KDZ using CSM flash
Click to expand...
Click to collapse
thx for replay me
i did that (fastboot boot laf.img) its say done with showing some words on the phone monitor but nothing happen also still cant go the flash mode
Try this
Boot into TWRP
Enable MTP and copy laf.img to sdcard
Go to Terminal Command in Advanced
Run the commands below using TWRP
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf
Hi,
i unlocked my bootloader using the original LG tool (unlock.bin).
fastboot getvar unlocked:
[[email protected] Desktop]# fastboot getvar unlocked
unlocked: yes
finished. total time: 0.004s
[[email protected] Desktop]#
Then i booted into bootloader using adb reboot bootloader.
fastboot flash recovery twrp-2.8.6.1-h815.img
gave me no error.
[[email protected] Desktop]# fastboot flash recovery twrp-2.8.6.1-h815.img
target reported max download size of 536870912 bytes
sending 'recovery' (32060 KB)...
OKAY [ 1.022s]
writing 'recovery'...
OKAY [ 0.287s]
finished. total time: 1.309s
[[email protected] Desktop]#
Now when i restart the phone using adb reboot recovery i get the "dead android" logo. No key combination works.
When booting using the Power+Vol-Down, the phone enters the reset menu. I select twice "YES", but TWRP is not started, and the phone is empty
Any idea?
Thanks
i went through the exact scenario, and found the solution myself, you're typing the wrong command, take the battery out, plug your phone into bootloader/fastboot mode or do it via adb
adb reboot bootloader
then flash the recovery again just to be safe
then either type fastboot boot twrp-2.8.6.1-h815.img
or adb boot twrp-2.8.6.1-h815.img
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
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Norah1838 said:
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
Click to expand...
Click to collapse
Use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
First off: don't go punching in commands you don't understand.
You literally flashed an incompatible image to your boot_a.
You could try and set the active partition to b using: fastboot --set-active=b.
Other option, if you have the firmware image for your boot partition, flash that image to boot_a.
you only need to flash the original boot.img from firmware lol it's so easy