I think my PC doesn't have the proper Fastboot Drivers. Can someone lead me to them?
My problem is, every Custom ROM with a Fastboot ROM doesn't work. Their Install&Format.bat scripts don't work properly.
Their script would do its tasks, until "fastboot reboot fastboot". It would hang at "Waiting for any device", because my PC doesn't detect Fastbootd devices, I'm highly sure.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.674s]
Writing 'boot_a' OKAY [ 0.259s]
Finished. Total time: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.399s]
Writing 'vendor_boot_a' OKAY [ 0.125s]
Finished. Total time: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.003s]
Finished. Total time: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Edit: Shortly after making this post, I solved my problem. I was correct. The problem was indeed a missing or failing Fastboot driver in Windows.
Xiaomi Community
c.mi.com
I followed that website, and disabled Driver Signature Enforcement, downloaded the linked driver & installed it. Now Fastbootd works
Edit #2: Turns out Mi Flash has the same drivers! You just need to disable Driver Signature Enforcement before installing the drivers, otherwise it won't install *all*.
tomxyz said:
I think my PC doesn't have the proper Fastboot Drivers. Can someone lead me to them?
My problem is, every Custom ROM with a Fastboot ROM doesn't work. Their Install&Format.bat scripts don't work properly.
Their script would do its tasks, until "fastboot reboot fastboot". It would hang at "Waiting for any device", because my PC doesn't detect Fastbootd devices, I'm highly sure.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.674s]
Writing 'boot_a' OKAY [ 0.259s]
Finished. Total time: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.399s]
Writing 'vendor_boot_a' OKAY [ 0.125s]
Finished. Total time: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.003s]
Finished. Total time: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Click to expand...
Click to collapse
Try to reset using MIUNLOCK application.
There is a tool to set first time fastboot setting .
tomxyz said:
I think my PC doesn't have the proper Fastboot Drivers. Can someone lead me to them?
My problem is, every Custom ROM with a Fastboot ROM doesn't work. Their Install&Format.bat scripts don't work properly.
Their script would do its tasks, until "fastboot reboot fastboot". It would hang at "Waiting for any device", because my PC doesn't detect Fastbootd devices, I'm highly sure.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.674s]
Writing 'boot_a' OKAY [ 0.259s]
Finished. Total time: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.399s]
Writing 'vendor_boot_a' OKAY [ 0.125s]
Finished. Total time: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.003s]
Finished. Total time: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Edit: Shortly after making this post, I solved my problem. I was correct. The problem was indeed a missing or failing Fastboot driver in Windows.
Xiaomi Community
c.mi.com
I followed that website, and disabled Driver Signature Enforcement, enabled Test Signing & downloaded the linked driver & installed it. Now Fastbootd works
Click to expand...
Click to collapse
I think this is exactly my problem. I have tried many roms but was only able to get the roms that had fastboot installation to work.i was thinking of trying arrowos next. Why didn't you like it?
Edit this was not my problem i had to assign drive letter in-order to install twrp.
jackscagnetti said:
I think this is exactly my problem. I have tried many roms but was only able to get the roms that had fastboot installation to work.i was thinking of trying arrowos next. Why didn't you like it?
Edit this was not my problem i had to assign drive letter in-order to install twrp.
Click to expand...
Click to collapse
"Was only able to get Fastboot ROMs to work" So they worked for you? Or typo?
I did try out ArrowOS, it's really nice and simple. I saw that it has Blur effects in the UI compared to the other ROMs which don't. But it doesn't have many other features, it doesn't have *any* Sound effects at all, unfortunately.
I tried out Xiaomi.eu, ArrowOS, Havoc OS and Syberia OS. Lastly I'll try out crDroid.
I think of going back to Xiaomi.eu which is my daily driver. I don't like MIUI, but I really like all the Camera features, the Dolby Atmos Sound (important for me), and the Font thiccness setting
your thread helped me a ton. wasn't able to flash fastboot roms before
thx a ton!
m0lly. said:
your thread helped me a ton. wasn't able to flash fastboot roms before
thx a ton!
Click to expand...
Click to collapse
Awesome! I'm glad it helped you!
dreamytom said:
Penso che il mio PC non disponga dei driver Fastboot corretti. Qualcuno può portarmi da loro?
Il mio problema è che ogni ROM personalizzata con una ROM Fastboot non funziona. I loro script Install&Format.bat non funzionano correttamente.
Il loro script farebbe i suoi compiti, fino a "fastboot reboot fastboot". Si bloccherebbe su " In attesa di qualsiasi dispositivo ", perché il mio PC non rileva i dispositivi Fastbootd, ne sono molto sicuro.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Invio 'boot_a' (196608 KB) OKAY [ 4.674s]
Scrivendo 'boot_a' OKAY [ 0.259s]
Finito. Tempo totale: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Invio di 'vendor_boot_a' (98304 KB) OKAY [2.399s]
Scrivendo 'vendor_boot_a' OKAY [0.125s]
Finito. Tempo totale: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Impostazione dello slot corrente su 'a' OKAY [ 0.003s]
Finito. Tempo totale: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Riavvio in fastboot OKAY [0.003s]
< in attesa di qualsiasi dispositivo >
[/CODICE]
[B]Modifica: [/B] poco dopo aver pubblicato questo post, ho risolto il mio problema. avevo ragione. Il problema era infatti un driver Fastboot mancante o guasto in Windows.
[URL unfurl="true"]https://c.mi.com/oc/thread-3312019-1-0.html[/URL]
[B]Ho seguito quel sito Web e disabilitato l'applicazione della firma del driver, abilitato la firma di prova, scaricato il driver collegato e installato. Ora Fastbootd funziona[/B] :)
[/QUOTE]
GRAZIE! Ho usato il metodo che hai usato tu. Funziona! ora win10 riconosce il mio poco f3 in fastboot e fastbootd. grazie per averlo condiviso! grande!
[ATTACH type="full" alt="Icona di Verificata con community"]5399187[/ATTACH]
Click to expand...
Click to collapse
THANK YOU! I used the method you used. it works! now win10 recognize my poco f3 in fastboot and fastbootd. thanks for sharing it! big up!
dreamytom said:
I think my PC doesn't have the proper Fastboot Drivers. Can someone lead me to them?
My problem is, every Custom ROM with a Fastboot ROM doesn't work. Their Install&Format.bat scripts don't work properly.
Their script would do its tasks, until "fastboot reboot fastboot". It would hang at "Waiting for any device", because my PC doesn't detect Fastbootd devices, I'm highly sure.
Code:
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash boot_a Images/boot.img
Sending 'boot_a' (196608 KB) OKAY [ 4.674s]
Writing 'boot_a' OKAY [ 0.259s]
Finished. Total time: 5.818s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot flash vendor_boot_a Images/vendor_boot.img
Sending 'vendor_boot_a' (98304 KB) OKAY [ 2.399s]
Writing 'vendor_boot_a' OKAY [ 0.125s]
Finished. Total time: 2.536s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot --set-active=a
Setting current slot to 'a' OKAY [ 0.003s]
Finished. Total time: 0.007s
D:\Library\Software\Android\Poco F3\Custom ROMs\Havoc-4.6-official-alioth-Gapps-fastboot>.\platform-tools-windows\fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
Edit: Shortly after making this post, I solved my problem. I was correct. The problem was indeed a missing or failing Fastboot driver in Windows.
Xiaomi Community
c.mi.com
I followed that website, and disabled Driver Signature Enforcement, enabled Test Signing & downloaded the linked driver & installed it. Now Fastbootd works
Click to expand...
Click to collapse
Hi
also found the same Guide....
Did you also use the latst instruction or not ?
bcdedit /set testsigning off ... ?
So far i have only ever managed to get into FastbootD by conection via ADB.
open Power_Shell - via "shift + Right mouse klick"
Run Command : adb reboot fastboot.
phone (mi11lite5g) is then in FastbootD mode.
Could this be because i already flshed miui-eu 12.5.3 via fastboot ( non stock Recovery ? )
still get some partition not found error...
If i use the "fastboot reboot fastboot" method (as described in the How_To)... nothing happens...
FYI.. also its impossible to connect to the phone with the MiPCSuite or the Mi-Flash tool
The Mi-Flash tool recognises the device, But i cannot flash any stock image to the phone, as this results in an Error.
any advice Much appreciated.
dont use cmd command to reboot into fastboot it will surely reboot to fastbootd try manuall pressing power and volume down in order to get fastboot spelling
metaxo said:
Hi
also found the same Guide....
Did you also use the latst instruction or not ?
bcdedit /set testsigning off ... ?
So far i have only ever managed to get into FastbootD by conection via ADB.
open Power_Shell - via "shift + Right mouse klick"
Run Command : adb reboot fastboot.
phone (mi11lite5g) is then in FastbootD mode.
Could this be because i already flshed miui-eu 12.5.3 via fastboot ( non stock Recovery ? )
still get some partition not found error...
If i use the "fastboot reboot fastboot" method (as described in the How_To)... nothing happens...
FYI.. also its impossible to connect to the phone with the MiPCSuite or the Mi-Flash tool
The Mi-Flash tool recognises the device, But i cannot flash any stock image to the phone, as this results in an Error.
any advice Much appreciated.
Click to expand...
Click to collapse
Yes, I got FastbootD only through ADB, but there might be other ways as well.
I found out that enabling Test-Signing is not necessary.
dreamytom said:
Yes, I got FastbootD only through ADB, but there might be other ways as well.
I found out that enabling Test-Signing is not necessary.
Click to expand...
Click to collapse
Yep.. Finally got it working..:
Had to put the adb folder on C:
And run it from there using CMD..!!
Not power-shell..like I was
Everything worked fine after that...
Thanks..
Thanks for the tutorial. It finally worked and solved my issue.
Related
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
if anyone online. kindly help ,me..
so i unlock my botloder. i was on global 12.3.0
i downloaded the xiaomi eu rom from https://androidfilehost.com/?w=files&flid=321331.
and tried to flash it with windows_fastboot_first_install_with_data_format command and now my phone is on fastboot for last half hour..
and last line on command prompt are these..
Finished. Total time: 0.047s
Sending 'cust' (418624 KB) OKAY [ 8.975s]
Writing 'cust' OKAY [ 0.000s]
Finished. Total time: 13.371s
please help me what to do now.. what went wrong?
Better read MIUI 12.5 (Xiaomi.EU) thread and ask your question there.
Just reboot into bootloader with volume down and power. Repeat the process. Better yet change or replug your USB from PC. Happens to me sometimes on ryzen
TheBURAQ said:
if anyone online. kindly help ,me..
so i unlock my botloder. i was on global 12.3.0
i downloaded the xiaomi eu rom from https://androidfilehost.com/?w=files&flid=321331.
and tried to flash it with windows_fastboot_first_install_with_data_format command and now my phone is on fastboot for last half hour..
and last line on command prompt are these..
Finished. Total time: 0.047s
Sending 'cust' (418624 KB) OKAY [ 8.975s]
Writing 'cust' OKAY [ 0.000s]
Finished. Total time: 13.371s
please help me what to do now.. what went wrong?
Click to expand...
Click to collapse
Install 15sec adb and retry
Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10
stephane_p said:
Dear all,
I'd like to install LineageOS on my Xiaomi Mi 10 Lite (monet).
I'm following the instructions here : https://wiki.lineageos.org/devices/monet/install.
Everything is going well until step "fastboot flash recovery <recovery_filename>.img".
I type "fastboot flash recovery <recovery_filename>.img" and everything seems to be good.
Sending 'recovery' (131072 KB) OKAY [ 4.907s]
Writing 'recovery' OKAY [ 0.571s]
Finished. Total time: 5.484s
But my phone does not power down. And when I try to reboot into the recovery mode (Volume Up + Power), the fastboot screen appears instead of recovery mode.
I also try with "fastboot boot <recovery_filename>.img".
Sending 'boot.img' (131072 KB) OKAY [ 5.044s]
Booting OKAY [ 0.154s]
Finished. Total time: 5.266s
The phone turns off and I reboot into recovery mode with success. I apply "Wipe Data" and go back to Main Menu after, as described.
But I don't find the "Apply Update" option.
Thank you for your help.
Stephane
Windows 10
Click to expand...
Click to collapse
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup
Spuffyffet said:
Use platform tools instead of Minimial adb and use the flash recovery command, it should work. and be careful if you need to disable
dm verity, i don't know Mi 10 Lite but yup
Click to expand...
Click to collapse
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.
stephane_p said:
Thank you for your help.
I downloaded and used platform tools as described in LineageOS Wiki. And then, I used windows cmd for the adb and the fastboot commands.
Click to expand...
Click to collapse
However, it's still not working. I have the same issue.
stephane_p said:
However, it's still not working. I have the same issue.
Click to expand...
Click to collapse
well use "fastboot reboot recovery"
Spuffyffet said:
well use "fastboot reboot recovery"
Click to expand...
Click to collapse
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here
stephane_p said:
I used reboot recovery. I got:
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But the fastboot screen is still here
Click to expand...
Click to collapse
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)
Spuffyffet said:
Use this brother: https://developer.android.com/studio/releases/platform-tools
you probably used Minimial ADB, it's the same but just use Platform tools (The one's i just sent)
Click to expand...
Click to collapse
I downloaded platform-tools zip file (r33.0.0 for windows) and extract it in C:\Android\platform-tools
Then, I retry
C:\Android\platform-tools>fastboot flash recovery recovery.img
Sending 'recovery' (131072 KB) OKAY [ 5.415s]
Writing 'recovery' OKAY [ 0.586s]
Finished. Total time: 6.017s
C:\Android\platform-tools>fastboot reboot recovery
Rebooting into recovery OKAY [ 0.000s]
Finished. Total time: 0.000s
But, I still get the fastboot screen instead of recovery mode.
Thank you for your help.
Have you tried with another recovery image, like TWRP ?
mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
well i have and it worked for me
mgkdv said:
Have you tried with another recovery image, like TWRP ?
Click to expand...
Click to collapse
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
stephane_p said:
I've tried with twrp but I get:
C:\Android>fastboot boot twrp_recovery.img
Sending 'boot.img' (131072 KB) OKAY [ 4.944s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Click to expand...
Click to collapse
You are using the wrong command bro, don't use boot. Use "fastboot flash recovery twrp_recovery.img". Why are you flashing recovery.img as boot bro?
OK guys I've found my mistake. I thought the model of my phone was Monet. But it's not. It's Toco... A stupid error showing that I have to be more rigorous.
I thank you again for your help. All the best for xda.
See you
Looking for a custom recovery I found this page where it contains a TWRP that is supposedly compatible with the Moto G20.
Download TWRP 3.5.2 For Moto G20- How to install » The TechGyan Gadgets
How To Install TWRP Recovery on Moto G20-Step 1. Bootloader Unlock on Moto G20.Step 2. Install TWRP Recovery on Moto G20.
mytechgyangadgets.com
Link TWRP:
motorola twrp recovery.img
drive.google.com
I did not want to risk trying it since I do not know much about this and what can happen if it is not correct. Someone to solve my doubt? or know of a compatible custom recovery? Gracias. :XX
Hey!
I tried booting directly into twrp in fastboot mode using ./fastboot boot twrp recovery.img and get this:
Sending 'boot.img' (26460 KB) OKAY [ 0.688s]
Booting OKAY [ 0.000s]
Finished. Total time: 0.717s
But the Phone only restarts into normal Motorola OS.
Robyn_232 said:
Hey!
I tried booting directly into twrp in fastboot mode using ./fastboot boot twrp recovery.img and get this:
Sending 'boot.img' (26460 KB) OKAY [ 0.688s]
Booting OKAY [ 0.000s]
Finished. Total time: 0.717s
But the Phone only restarts into normal Motorola OS.
Click to expand...
Click to collapse
hello! Thanks for replying, I guess we have to wait. :c
voy a intertar
it can not i put this .\fastboot.exe flash recovery "C:\Program Files (x86)\Minimal ADB and Fastboot\motorola twrp recovery.img"
and this appears
Sending 'recovery' (26460 KB) OKAY [ 0.748s]
Writing 'recovery' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
and when I enter the recovery the default revorey appears
Watch the Thread called "Building TWRP for Moto G20" there is someone with a working twrp but theres no download link until now.
Hi. I think I did a soft brick and this my device:
xiamoi redmi note 8 pro
Android version: 11 RP1A.200720.011
MiUi version: 12.5.7.0 (RGGEUXM) Global Stable
I downloaded latest platform-tools and latest twrp-3.3.1-0-begonia.img.
I connected via USB 3.1 and pressed volume-down + power to enter fastboot mode.
After flashing twrp the smartphone just reboots in a bootloop showing redmi, black screen, rebooting.
Entering Fastboot Mode Power + Volume-Down still possible.
Entering Recovery Mode Power + Volume-UP no visible response and device is still rebooting.
What was my mistake and how can I fix it? What happens, if the device runs out of power in state boot looping oder fastboot?
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.694s]
Writing 'recovery' OKAY [ 0.089s]
Finished. Total time: 0.877s
E:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
E:\platform-tools>fastboot devices
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.709s]
Writing 'recovery' OKAY [ 0.070s]
Finished. Total time: 0.813s
E:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (31380 KB) OKAY [ 0.684s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.630s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.634s]
Writing 'recovery' OKAY [ 0.082s]
Finished. Total time: 0.748s
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.633s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
< waiting for any device >
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.645s]
Writing 'recovery' OKAY [ 0.066s]
Finished. Total time: 0.742s
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>
liltechie said:
Hi. I think I did a soft brick and this my device:
xiamoi redmi note 8 pro
Android version: 11 RP1A.200720.011
MiUi version: 12.5.7.0 (RGGEUXM) Global Stable
I downloaded latest platform-tools and latest twrp-3.3.1-0-begonia.img.
I connected via USB 3.1 and pressed volume-down + power to enter fastboot mode.
After flashing twrp the smartphone just reboots in a bootloop showing redmi, black screen, rebooting.
Entering Fastboot Mode Power + Volume-Down still possible.
Entering Recovery Mode Power + Volume-UP no visible response and device is still rebooting.
What was my mistake and how can I fix it? What happens, if the device runs out of power in state boot looping oder fastboot?
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.694s]
Writing 'recovery' OKAY [ 0.089s]
Finished. Total time: 0.877s
E:\platform-tools>fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.002s
E:\platform-tools>fastboot devices
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (31380 KB) OKAY [ 0.709s]
Writing 'recovery' OKAY [ 0.070s]
Finished. Total time: 0.813s
E:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (31380 KB) OKAY [ 0.684s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.630s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.634s]
Writing 'recovery' OKAY [ 0.082s]
Finished. Total time: 0.748s
E:\platform-tools>fastboot boot twrp3310.img
Sending 'boot.img' (29044 KB) OKAY [ 0.633s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
E:\platform-tools>fastboot flash recovery twrp3310.img
< waiting for any device >
Microsoft Windows [Version 10.0.19045.2788]
(c) Microsoft Corporation. Alle Rechte vorbehalten.
E:\platform-tools>fastboot devices
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>fastboot flash recovery twrp3310.img
Sending 'recovery' (29044 KB) OKAY [ 0.645s]
Writing 'recovery' OKAY [ 0.066s]
Finished. Total time: 0.742s
E:\platform-tools>adb reboot bootloader
error: no devices/emulators found
E:\platform-tools>fastboot devices
j7n7hmeq9x69heeq fastboot
E:\platform-tools>
Click to expand...
Click to collapse
Your mistake is that you used twrp that support Android 9 only. If you want to use TWRP for A11, find unofficial one. You can find "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1)
Kirasu2080 said:
Your mistake is that you used twrp that support Android 9 only. If you want to use TWRP for A11, find unofficial one. You can find "brp begonia pling" and choose the one for Miui A11 (v3.6 or v3.5.2_3.1)
Click to expand...
Click to collapse
Thank you. Helped solving the bootloop issue.