Develop Bugs

[Q] Stuck at stock bootloader

I am such a noob and suck at rooting.I got problem during rooting my kindle fire,here's the stories.I try to search all the way in the forum. But,all of it not working. Could you guys help me ?
1) follow root instruction and downloaded KFU
2) successfully installed superuser and go launcher
3) TWRP or CWR or FFF doesn't appear when i reboot back my device to flash custom rom.
4) I tried to run install_driver and run it again and select bootmode menu
5) I choose 3 for recovery.and its brick.luckily i could switch off my kindle.but when i wanna turned it on,its doesnt return to home menu.its stuck at the stock bootloader.
I'm hoping you guys could help me and suggest me the way how to solve it.
I also attach some screen shot of the kindle and my notebooks when i plugged in usb cable in.
Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

b63 said:
it seems to be in fastboot mode - you have to fix your windows driver for fastboot mode, then you can continue with kfu.
driver (under android phone):
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
detailed explanation here: http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
thanks for the advice.I will try it after this and inform you back. Btw, do i need kindle usb cable? for fastboot, since i purchased used kindle so the seller didnt gimme those cable. im currently using sony micro usb cable.

no - every micro usb cable will work

b63 said:
no - every micro usb cable will work
Click to expand...
Click to collapse
i will try to read all of it, try to understand it.and get you know once i already figure it out okay?:cyclops:

i already update my driver.and why in KFU,my device is offline.

21th century apes said:
i already update my driver.and why in KFU,my device is offline.
Click to expand...
Click to collapse
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.

i finally able to install bootloader and twrp.i thought i never make a mistakes.but unfortunately,during time im backing up stock rom,(nandbackup).i check all the boxes (for the left side) and for right side nothing.its running,when completed.its show huge amount of data (around 780 mb).i really think dat tis is normal for backup.in twrp,and video by tom gt,time for backup for 10 minutes.but me,already 5 hour still stuck in twrp.cant go anywhere.

b63 said:
your device seems to be in fastboot mode - you have selected the wrong driver.
normal & recovery boot: -> android composite adb interface
fastboot: -> android adb interface
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
if the device is in fastboot mode "adb status" is allways "offline".
if you have installed the right driver you can check manually
with "fastboot devices" and "fastboot getvar product".
if you get response to this commands you are good to go.
Click to expand...
Click to collapse
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.

21th century apes said:
bro i hope you can help me solve tiz things off.during backup nand.for the first time.its stuck and as i mention previously its stuck 5 hours but for almost 2 days.its still not finish.am i brick my fire?am i miss out something?later i'll attach picture for your preferences.i think when i already booted up kindle fire,its consider no such big issues.maybe for me that not familiar.
Click to expand...
Click to collapse
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.

b63 said:
if you managed to install bootloader and twrp then you are good to go.
you tried to make a backup of the stock firmware and now the twrp is stuck.
i don't know what options you checked, but this should be no problem.
just hold the power button for ~20sec till it turns off and try again.
check only options which exist on your device then the backup should be done in ~10min.
Click to expand...
Click to collapse
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.

21th century apes said:
Thank you dude.Finally im able to use custom rom.oh,yeah .Btw,i got one last question.Why i cant connect my kindle with computer.instead its show my kindle,its only charging.coz i need to backup all my stuff inside my kindle to computer.
Click to expand...
Click to collapse
that depends on the rom you used. some have a option to enable this function.
the best advise would be to search or ask in the section of the rom you used.
great that it's working now - much fun with your kf

hey dude.im already killed my kindle fire and now its dead.here the stories :
i try to backup all my stuff to my computer.as what you told me before,i try to follow.pick ROM that have usb debugging option for transfering data.okay done.but when i transferring my data from kindle to pc.(i dunno what happen) accidentally my kindle fire hang and i disconnect all the cable hoping that my kindle fire will be okay.but thats the end of my kindle fire.its failed to boot.just plain black screen.when i plugged in the cable.led light blinking.like normal.red and yellow.but there's nothing i can do.i open up device manager on my pc,instead of android phone appeared during time im connecting my phone with pc,its appeared usb mass storage (code 10).device cant start and load.hope you could guide me.anybody.
all guide will be kindly appreaciated.thanks.

[Q] Bootloader access but no PC access - Help!

Hi guys,
Sorry if this is in the wrong forum. I've searched around but can't find anyone with quite the same issue as myself.
I returned to my desk at work to find that my nexus 7 2013, latest stock Android OS installed, was stuck on the Google logo screen. It was switched on previously and charging via my work PC at the time.
A few points about what is happening with the Nexus:
I can get to the bootloader but it says "E: failed to mount /cache (invalid arguement), E: can't mount /cache recovery log, E: can't open /cache recovery/log..." you get the idea
The third line from the end says "e: failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (i/o error), e: failed to mount cache (invalid arguement).
if I select wipe cache from the bootloader I see the same error
I selected wipe data and this seems to work, before giving me the above error again
I've seen about the Wugfresh and Unified toolkit and I have tried them. But the big problem seems to be that neither my work PC or home laptop detects that my Nexus is plugged into them via USB. If I could solve that I think I'd be able to restore, right?
I'm also really intrigued as to how this happened. I've never rooted this Nexus. The most advanced thing I've done with it is to install Nova Launcher and that was over 6 months ago. Weird how it can just suddenly go wrong.
Any help would be greatly appreciated.

Just to add, with the Wug/Nexus Toolkit I've been through the driver installation program and whilst I can get the ADB Interface driver to install, when I'm in the bootloader the Nexus doesn't show in Device Manager and using the "Soft-bricked" option and then "Flash Stock + Unroot" I get an error that no fastboot device could be found.

Have you checked your control panel inside device manager? Your nexus 7 could be listed as a unknown device under other devices, or listed as a nexus 7.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If so. it's a matter of just installing the right drivers, you can install the official Google drivers and choose the bootloader driver when installing.
http://developer.android.com/sdk/win-usb.html
If you get some compatibility error while installing the drivers, just ignore it and continue.
edit: just noticed your 2nd post. nevermind.

Maverick-DBZ- said:
Have you checked your control panel inside device manager? Your nexus 7 could be listed as a unknown device under other devices, or listed as a nexus 7.
If so. it's a matter of just installing the right drivers, you can install the official Google drivers and choose the bootloader driver when installing.
If you get some compatibility error while installing the drivers, just ignore it and continue.
edit: just noticed your 2nd post. nevermind.
Click to expand...
Click to collapse
Thanks for trying! Yep, nothing shows up if I'm in bootloader mode.
I've installed the adb interface driver and if I reboot the Nexus and leave it for a while *sometimes* an "Android Device" will display in Device Manager.
All the instructions say enable USB debugging, disable MTP but I can't do that because it won't turn on! I am pretty much saying this - "I installed the drivers but it still says ADB/Fastboot device not found! What should I do?" which is a page on wugfresh, but I'm new and can't post links- but even this doesn't cover if the device won't boot at all.

teamcooperuk said:
Thanks for trying! Yep, nothing shows up if I'm in bootloader mode.
I've installed the adb interface driver and if I reboot the Nexus and leave it for a while *sometimes* an "Android Device" will display in Device Manager.
All the instructions say enable USB debugging, disable MTP but I can't do that because it won't turn on! I am pretty much saying this - "I installed the drivers but it still says ADB/Fastboot device not found! What should I do?" which is a page on wugfresh, but I'm new and can't post links- but even this doesn't cover if the device won't boot at all.
Click to expand...
Click to collapse
Ok, I was being dumb.
I was starting up using power+volume up. Realised power+volume down gets me to bootloader and that I was in recovery mode before.
So I used the Wugfresh "Flash Stock and Unroot" option. This seemed to be going well except I get told my bootloader is locked.
The I tried to use the Unlocker tool in Wugfresh. This tells me it can't detect an ADB device, but when I hit cancel the unlock bootloader screen opens. And then hangs when I select unlock!
What can I try next?!

Do you know how to use ADB manually with a dos prompt? Kits are nice and they help a lot, but sometimes they don't work right and get in the way.
Code:
fastboot oem unlock
The above command is what you need to unlock your bootloader. If you see a little lock below the Google logo at startup, you've unlocked your bootloader. You're on a Nexus 7 2013 Wi-Fi right?
If it still freezes when unlocking, you could try opening the tablet and disconnecting the battery for a little bit, and then putting everything back together again. For some reason it seems to work for some people.

Maverick-DBZ- said:
Do you know how to use ADB manually with a dos prompt? Kits are nice and they help a lot, but sometimes they don't work right and get in the way.
Code:
fastboot oem unlock
The above command is what you need to unlock your bootloader. If you see a little lock below the Google logo at startup, you've unlocked your bootloader. You're on a Nexus 7 2013 Wi-Fi right?
If it still freezes when unlocking, you could try opening the tablet and disconnecting the battery for a little bit, and then putting everything back together again. For some reason it seems to work for some people.
Click to expand...
Click to collapse
I don't - do I just open a cmd prompt window, navigate to where fastboot is and run that command with the Nexus connected via USB and in the bootloader?
I tried an alternative toolkit, the unified one. The UI of that is a cmd prompt window. That shows me that it hangs during the unlock bootloader process where it is "erasing user data", I left it for 8 hours overnight and it was still hanging.
Does it sound totally bricked?

teamcooperuk said:
I don't - do I just open a cmd prompt window, navigate to where fastboot is and run that command with the Nexus connected via USB and in the bootloader?
I tried an alternative toolkit, the unified one. The UI of that is a cmd prompt window. That shows me that it hangs during the unlock bootloader process where it is "erasing user data", I left it for 8 hours overnight and it was still hanging.
Does it sound totally bricked?
Click to expand...
Click to collapse
Yes, correct.
As a possible solution, run the below fastboot command. Must be in bootloader menu for this to work. See image below.
Code:
fastboot format cache
Then boot to recovery and do a factory reset.
If it still hangs, try downgrading to a lower android version, 4.3 is a good start. If the process fails, post on what step it failed.

Maverick-DBZ- said:
Yes, correct.
As a possible solution, run the below fastboot command. Must be in bootloader menu for this to work. See image below.
Code:
fastboot format cache
Then boot to recovery and do a factory reset.
If it still hangs, try downgrading to a lower android version, 4.3 is a good start. If the process fails, post on what step it failed.
Click to expand...
Click to collapse
I'm getting an error when I try to run these commands. It complains that ADBwinAPI.dll isn't installed. Tryed using regsvr32 to do so but that also gives me an error.
Trying to use Eclipse to run these commands now but it looks like this could be a wormhole of settings beyond my technical ability!
Just to add, I tried to format the cache using the power+volume up screens. I just get the cache errors listed in the original post.

Maverick-DBZ- said:
Yes, correct.
As a possible solution, run the below fastboot command. Must be in bootloader menu for this to work. See image below.
Code:
fastboot format cache
Then boot to recovery and do a factory reset.
If it still hangs, try downgrading to a lower android version, 4.3 is a good start. If the process fails, post on what step it failed.
Click to expand...
Click to collapse
teamcooperuk said:
I'm getting an error when I try to run these commands. It complains that ADBwinAPI.dll isn't installed. Tryed using regsvr32 to do so but that also gives me an error.
Trying to use Eclipse to run these commands now but it looks like this could be a wormhole of settings beyond my technical ability!
Just to add, I tried to format the cache using the power+volume up screens. I just get the cache errors listed in the original post.
Click to expand...
Click to collapse
Ok, found the adb client in the platform-tools sdk directory. Running the unlock I get the same problem, the hang on erasing userdata:
Code:
C:\Users\xxxxxxxx\Documents\Google_Drivers\adt-bundle-windows-x86_64-20140702\sdk\pl
atform-tools>fastboot oem unlock
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
Just kicked off the erasing cache command...looks like that's hanging too after 30 seconds....should finsih pretty quickly, right?
Off to Asus I go I think!

No need to run the bootloader command. If it still hangs after the below command and nothing else, then it's time to call Asus and RMA it. :crying:
Code:
fastboot format cache
Part of your NAND is likely toast and why the cache partition won't erase.

Huawei Watch Update 1.4 is here!

Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
Make sure you are connected to your charging dock.
Make sure you are running the latest update LCB43B.
I did all this on Win 10.
1. Just be fully stock including recovery. Refer to Skin1980's guide here to return to stock if you used his previous kernel or did any other mods like TWRP or root. (http://forum.xda-developers.com/huawei-watch/general/guide-return-to-stock-huawei-watch-t3219596)
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339) (People have reported PDANET drivers are working if the naked drivers do not work for them and are somewhat easier to install.)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip and make sure its located inside the root directory of your adb installation.
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Don't forget to hit the thanks button! I appreciate it!

Thank you. Can you please create a step by step guide for idiots like me, who have never used adb etc..?

hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there

chachin said:
hey when i try to go to recovery and do the "adb devices within stock recovery.. i see this
c:\android\hwatch> adb reboot bootloader
c:\android\hwatch>adb devices
list of devices attached
c:\android\hwatch>
even though when i was on the main menu of the watch before rebooting to recovery and all that
list of devices attached
FFS7N15B06003222 device
i go to bootloder reboot recovery adb devices... get nothing in there
Click to expand...
Click to collapse
I updated OP check the steps again. adb commands won't work in bootloader. Once in recovery swipe down and select apply update from adb then issue the "adb sideload update.zip" command.

so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
Make sure the update file is inside your root adb directory on your hard drive.

chachin said:
so i cant be in the recovery mode to apply update you mean i can do it while the watch is on? cause when i try going to recovery it does this
c:\android\hwatch>adb sideload update-601.zip
loading: 'update-601.zip'
error: device not found
c:\android\hwatch>
and yes im in the recovery with the android with open chest and its got yellow letters telling me to do the adb sideload<filenam>
Click to expand...
Click to collapse
It looks like your device is still not visible to adb. Make sure you don't have any other devices connected like a phone with debugging turned on also. And you do need to be in recovery with it awaiting the sideload update.zip command. You seemed to be in the correct place.

Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk

xceebeex said:
Mine got pushed to me, I just have to charge it
Sent from my VS990 using Tapatalk
Click to expand...
Click to collapse
YAY! Always the best way to go. Where are u located?

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
But... the phone must be connected on the pc? I can't detect the watch with adb devices..

I was wondering why I couldn't boot to the recovery directly so thanks a ton for the help! Also dayum, the speaker sure is quite loud for a smartwatch!
To the person above no, you do not need to have the phone to your pc connected for it to work.

got it installed like it so far, to me the speaker sounds alot better then the one in the gear s

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk

Tried installing the naked drivers in the link but that fails, any suggestions?

str8spir said:
Thank you dear XDA members for your advice on how to adb sideload
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
Very glad we could help! Just wanted everyone to be as happy as I was when I saw the file drop!

RngrYogi said:
Thanks to Ali_Alex for the link!
The Update https://android.googleapis.com/pack...866b47.signed-sturgeon-MEC23L-from-LCB43B.zip
I used the latest minimal ADB and Fastboot here http://forum.xda-developers.com/showthread.php?t=2317790
1. Just be fully stock including recovery.
2. Make sure you have debugging turned on inside developer settings. (If the menu is not there tap your build number in about menu 7 or 8 times and it will appear)
3. Run command "adb devices" and make sure your device appears. (If it says unauthorized check watch screen and accept you pc as trusted) (If nothing appears make sure you have the correct drivers installed I use the universal naked driver here http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339)
4. Run adb command "adb reboot bootloader"
5. Reboot recovery from inside bootloader using the button's short and long taps to change selection and select reboot recovery.
6. Scroll down and select apply update from adb.
7. Rename zip to update.zip
8. Run command "adb sideload update.zip"
Wait
Enjoy! :highfive:
Click to expand...
Click to collapse
Thanks worked flawlessly...

ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
Let me test mine and see if it is visible while waiting on the adb sideload update.zip command

No luck for me installing these drivers

chachin said:
ffs i still dont get it why cant my watch be recognized when its inside the damn recovery with android open chest where you say "adb sideload.zip" i do adb devices when it's on that option and on cmd it doesnt show up at all.. but if the watch is normally running and i do adb devices it shows up there.. i go to fastboot and then fastboot devices. shows there too exept when i click to reboot into recovery is when it gets lost
Click to expand...
Click to collapse
C:\ADB>adb devices
List of devices attached
MQB7N15914000616 sideload
This is what I see while in sideload mode inside recovery. Not sure why its not working for you.:crying:

No succes trying to unlock my Swift 2x

Hi, I spent several hours trying to unlock my phone. Tried following steps:
* I made a full backup
* I did full reset to original settings: Androïd 8.1.0
* I got myself developers rights
* in settings turned on 'usb debugging' , 'OEM unlock' and 'advanced restart'
After turning off device and restart ('power/vol up' buttons), device started in recovery mode
* downloaded 'ADB + Fastboot-package' on Win10-PC and tried in every conceivable way to install but phone would not not connect; recovery boot indicated device was locked; PC did not recognize phone
and impossible to flash TWRP-recovery
* I installed Magisk-manager on phone with succes to avoid having to use a PC; but then flashing TWRP did not succeed
What did I wrong, what do I wrong? Suggestions VERY welcome. after all this I had rather not return to original OS. Thanks for your help.

With the phone in fastboot mode issue "fastboot devices" make sure you get a response.
Then "fastboot oem unlock - go"

Thank. you very much for your answer. Problem is that after rebooting with <power + volup> I get a menu with ao START (in green), Power off (i n white), Recovery mode (in red) and Restart Bootloader (in red). Further on I read FASTBOOT MODE (in red), product name etc., SECURE BOOT -enabled (in white). and DVEICE. STATE - locked (in red). How do I get my phone in 'fastboot mode'?
Thanks for help.

hepkeb said:
How do I get my phone in 'fastboot mode'?
Thanks for help.
Click to expand...
Click to collapse
First you select Fastboot
Spoiler: Fastboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then you get in Fastboot Mode, then connect your cable to your Pc
Spoiler: Fastboot Mode
THIS IS FASTBOOT !

Thank you for trying to help. Of course I know how to get in fastboot mode. My problem is that in 'every' mode my telephone is locked, and I do not succeed in unlocking it. I cannot connect to another device, Magisk installation not complete etc. Again: I have developers right, I unlocked OEM, I did allow USB-debugging but no unlocked device!? What is going wrong, or has Wileyfox blocked the normal unlocking-procedure?

hepkeb said:
Thank. you very much for your answer. Problem is that after rebooting with <power + volup> I get a menu with ao START (in green), Power off (i n white), Recovery mode (in red) and Restart Bootloader (in red). Further on I read FASTBOOT MODE (in red), product name etc., SECURE BOOT -enabled (in white). and DVEICE. STATE - locked (in red). How do I get my phone in 'fastboot mode'?
Thanks for help.
Click to expand...
Click to collapse
That is fast boot mode

robin0800 said:
That is fast boot mode
Click to expand...
Click to collapse
I have exactly the same problem. I do not have access to the phone and a hard reset leads me to having to enter a googe account synced with the device which I do not have the details of. I can enter the mode that you describe above and the FASTBOOT MODE is in red below. Now when I'm here and plug into my laptop wth USB and fire up fastboot.exe and issue 'fastboot device' it just says '< waiting for device >'.
Did you manage to make any progress on this issue at all, I'm really stuck!

download adb and fastboot from here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
unzip the file and then install adb and fastboot, no drivers needed on win ten.
enable debugging and debugging notifier on phone.
open a command prompt and do "adb Devices"
the first time you do this you should get a notification on your phone accept it.
do "adb Devices" again and the phone should be seen.
do adb reboot bootloader
you should be in fastboot now
do fastboot devices and then fastboot oem unlock - go.

robi0800 said:
download adb and fastboot from here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
unzip the file and then install adb and fastboot, no drivers needed on win ten.
enable debugging and debugging notifier on phone.
open a command prompt and do "adb Devices"
the first time you do this you should get a notification on your phone accept it.
do "adb Devices" again and the phone should be seen.
do adb reboot bootloader
you should be in fastboot now
do fastboot devices and then fastboot oem unlock - go.
Click to expand...
Click to collapse
Thanks robi0800 but I don't have access to the phone so I can't enable USB debugging which means I can't use adb. I am trying to use fastboot but when I issue the command 'fastboot device' it can't connect to the phone and just displays '< waiting for device >'. Any other advice on how to make my Win10 laptop recognise the device when I plug it in so I can use fastoot successfully?

Sounds like you are missing a driver you could try the driver from the package in post #8 above?

Thanks robin0800, I've tried that package with the original Wileyfox red USB cable, no luck unfortunately. My Win10 laptop can see the device in Device Manager but adb Devices will not list anything, neither will fastboot. I don't have access to the phone to enable usb debugging.

Bermudan said:
Thanks robin0800, I've tried that package with the original Wileyfox red USB cable, no luck unfortunately. My Win10 laptop can see the device in Device Manager but adb Devices will not list anything, neither will fastboot. I don't have access to the phone to enable usb debugging.
Click to expand...
Click to collapse
Adb will not see it if debugging is not enabled but fastboot does not need this but the phone must be in recovery mode

robin0800 said:
Adb will not see it if debugging is not enabled but fastboot does not need this but the phone must be in recovery mode
Click to expand...
Click to collapse
Thanks - and to put it in recovery mode is this just Powebutton + Vol Up for several seconds or Vol Down, I can't recall...

How To Guide Get yourself out of bootloop in case of faulty magisk module without TWRP

So I have been spending a good afternoon getting the phone out of bootloop because of a fault magisk I install , and there's no TRWP to save my ass
Magisk - Installation and troubleshooting:Magisk and MagiskHide Installation and Troubleshooting guide
didgeridoohan.com
What doesn't work :
-Safe mode (click volume down key the second loading to the system (5G screen) , pass the MIUI.
What make mine works:
1. Get the original boot.img, flash this with like how you root your phone initially in rooting magisk.
Code:
fastboot flash boot boot.img
2. Now that you can go in the phone , but you don't have root access to remove the magisk module that's nested within root. You would need to get the ADB by going to
Additional Setting> developer option> enable USB debugging to have access to ADB
3. Either go to magisk and patch the boot.img again, or use to the one you have patched previously , go to fastboot and flash the patched boot.img
4. Reboot your phone (or type fastboot reboot) and continue to plug in your phone, now that you are in boot loop but 1. Have root access 2. Able to use ADB
5. In the ADB cmd console (probably same as your fastboot cmd console)
Type in ADB devices to check if you have ADB connection to your phone .
If yes, type the code below which would remove all the magisk module
Code:
adb wait-for-device shell magisk --remove-modules
6. It will reboot on its own , I have tried the process two times but I am able to get my phone out of loop.
I have spent a good afternoon figuring out, hopefully this could save anyone a headache

Not working here, I run the command but after reboot stills at bootloop, so I will stay without root because I can boot if I flash stock boot.img, I will wait to any twrp to flash magisk unistaller. (Advice: dont try to install 2019 modules)

Before running the command ,make sure you are in adb mode by typing adb devices .
It would not work in fastboot environment.
It would work in normal boot environment after you enabled usb debugging in developer option and in normal environment (after the MIUI boot screen, it works out even you are in bootloop status )

Yeah I know, I do it like you say, flashed magisk patched boot , wait for adb devices working, run the command for remove all the modules, but after the reboot stills on bootloop.
Can you send me the list of modules that you have after run the command? I have 3 modules
use this to see the installed modules
adb wait-for-device shell magisk -list

I believe your code is abit wrong there. Theres two -
Code:
adb wait-for-device shell magisk --remove-modules
Do reference the initial link I provided earlier .
Is all the info you need.

Dude, ofc I know what command is, I didnt type it wrong, I tell you if you can send me your installed module list

The modules that failed is pix3lify .
And below is my current module list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Not sure if that helps

Mahoro.san said:
The modules that failed is pix3lify .
And below is my current module list.
View attachment 5299085
Not sure if that helps
Click to expand...
Click to collapse
I need that you runs the command that I'm telling to you.
Code:
adb wait-for-device shell magisk -list
This will display your module list

Pretty much
1.
Code:
Fastboot flash boot boot.img
on flashing the original and patched IMG ( you get that right )
2. After enabling the usb debugging when you flash the original IMG, you need to flash the magisk patched IMG again. (I believe you missed this part)
Code:
Adb devices
To check if you have ADB access to the devices
Code:
adb wait-for-device shell magisk --remove-modules
To remove the module

Mahoro.san said:
Pretty much
1.
Code:
Fastboot flash boot boot.img
on flashing the original and patched IMG ( you get that right )
2. After enabling the usb debugging when you flash the original IMG, you need to flash the magisk patched IMG again. (I believe you missed this part)
Code:
Adb devices
To check if you have ADB access to the devices
Code:
adb wait-for-device shell magisk --remove-modules
To remove the module
Click to expand...
Click to collapse
Dude, without the intention of disturbing. I know what I have to do. I'm able to boot if I flash stock boot.img, if I flash magisk patched boot.img I can use adb devices command but the device is in bootloop, then I use adb devices and adb wait-for-device shell magisk --remove-modules
The problem is that nothing happens when I use the last command, just reboots but still on bootloop

this command @Mahoro.san

Btw I get magisk working, just entered in safe mode (vol - and vol+ before boot animation) and then used the command that removes all modules. This time after reboot, no bootloop and magisk working fine