Hello everyone.
I got this problem today. My Mi A1 doesn't want to unlock the bootloader, and I follow all the instructions. In the cmd, when I type "fastboot oem unlock", this error appears "remote: unlock is not allowed".
Besides, the smartphone is frozen on the screen of initialization of Mi, making it impossible for me to go in the administrator options of the device.
Please describe what you did to the phone before it got to this state.
_mysiak_ said:
Please describe what you did to the phone before it got to this state.
Click to expand...
Click to collapse
I tried to install the gcam on the device and had to unlock the bootloader. At first work, I unlock it, and went to install gcam but it did not work so well. After that my device had some performance problems and I decided to reinstall the ROM using MiFlash.
As I was giving errors and I could not install by MiFlash, I searched for tutorials on Youtube, trying to install without MiFlash, I found some but did not work again. So, I decided to type in the cmd "flashboot oem lock" because I thought this would be the problem that I could not install the ROM by MiFlash and again, it worked, I managed to block it.
However, after searching again, I discovered that I had to unlock it, so I typed the "flashboot oem unlock" command and gave this error, and when I turn on the phone, just appear a white screen with Mi logo.
Are you sure that you have Mi A1 phone? What was the system version before you tried to install Gcam?
_mysiak_ said:
Are you sure that you have Mi A1 phone? What was the system version before you tried to install Gcam?
Click to expand...
Click to collapse
I sure, the system was Android 8.0. Android One.
Did you enable OEM unlocking from the Developer Options? Probably not. Enable it first and try again.
Chiggie14899 said:
Did you enable OEM unlocking from the Developer Options? Probably not. Enable it first and try again.
Click to expand...
Click to collapse
Like I said, I can't. My smartphone is in mode bootloop.
Connect your phone in fastboot mode and type in "fastboot getvar all" and share the output please.
nicobelic said:
Like I said, I can't. My smartphone is in mode bootloop.
Click to expand...
Click to collapse
Try flashing in edl mode, in fastboot type in cmd: fastboot oem edl, it will give you a fail. It's normal, you should have a black screen and the led blinking. Look if the drivers are installed and after install with MiFlash.
_mysiak_ said:
Connect your phone in fastboot mode and type in "fastboot getvar all" and share the output please.
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3828000
(bootloader) variant:QRD eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:MSM8953_TISSOT2.0_20180504180424
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1fe00000
(bootloader) slot-count:2
(bootloader) current-slot:_a
(bootloader) slot-retry-count:_b:7
(bootloader) slot-success:_b:No
(bootloader) slot-active:_b:No
(bootloader) slot-unbootable:_b:No
(bootloader) slot-retry-count:_a:7
(bootloader) slot-success:_a:Yes
(bootloader) slot-active:_a:Yes
(bootloader) slot-unbootable:_a:No
(bootloader) has-slot:userdata: No
(bootloader) has-slot:logdump: No
(bootloader) has-slot:dpo: No
(bootloader) has-slot:msadp: No
(bootloader) has-slot:apdp: No
(bootloader) has-slot:keymasterbak: No
(bootloader) has-slot:keymaster: No
(bootloader) has-slot:cmnlib64bak: No
(bootloader) has-slot:cmnlib64: No
(bootloader) has-slot:cmnlibbak: No
(bootloader) has-slot:cmnlib: No
(bootloader) has-slot:lksecappbak: No
(bootloader) has-slot:lksecapp: No
(bootloader) has-slot:mcfg: No
(bootloader) has-slot:syscfg: No
(bootloader) has-slot:mdtp: No
(bootloader) has-slot:dip: No
(bootloader) has-slot:mota: No
(bootloader) has-slot:limits: No
(bootloader) has-slot:config: No
(bootloader) has-slot:keystore: No
(bootloader) has-slot:misc: No
(bootloader) has-slotersist: No
(bootloader) has-slot:system: Yes
(bootloader) has-slot:devinfo: No
(bootloader) has-slot:boot: Yes
(bootloader) has-slot:abootbak: No
(bootloader) has-slot:aboot: No
(bootloader) has-slot:splash: No
(bootloader) has-slot:sec: No
(bootloader) has-slot:fsg: No
(bootloader) has-slotDR: No
(bootloader) has-slot:modemst2: No
(bootloader) has-slot:modemst1: No
(bootloader) has-slot:dsp: No
(bootloader) has-slot:devcfgbak: No
(bootloader) has-slot:devcfg: No
(bootloader) has-slot:tzbak: No
(bootloader) has-slot:tz: No
(bootloader) has-slot:rpmbak: No
(bootloader) has-slot:rpm: No
(bootloader) has-slot:sbl1bak: No
(bootloader) has-slot:sbl1: No
(bootloader) has-slot:ssd: No
(bootloader) has-slot:fsc: No
(bootloader) has-slot:modem: Yes
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache:
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0xcd3779e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) crc:1
(bootloader) serialno:349794d29805
(bootloader) kernel:lk
(bootloader) product:tissot
all:
finished. total time: 0.776s
mardrest said:
Try flashing in edl mode, in fastboot type in cmd: fastboot oem edl, it will give you a fail. It's normal, you should have a black screen and the led blinking. Look if the drivers are installed and after install with MiFlash.
Click to expand...
Click to collapse
This shows up:
>fastboot oem edl
...
OKAY [ 0.016s]
finished. total time: 0.016s
mardrest said:
Try flashing in edl mode, in fastboot type in cmd: fastboot oem edl, it will give you a fail. It's normal, you should have a black screen and the led blinking. Look if the drivers are installed and after install with MiFlash.
Click to expand...
Click to collapse
This shows up:
PHP:
>fastboot oem edl
...
OKAY [ 0.016s]
finished. total time: 0.016s
nicobelic said:
This shows up:
PHP:
>fastboot oem edl
...
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
If you have a black screen and the led blinks, then you are on edl mode, you can install the rom with MiFlash
mardrest said:
If you have a black screen and the led blinks, then you are on edl mode, you can install the rom with MiFlash
Click to expand...
Click to collapse
To be honest, nothing happened to the device, it still continues in "fastboot" mode after typing the command and no led blinks.
nicobelic said:
To be honest, nothing happened to the device, it still continues in "fastboot" mode after typing the command and no led blinks.
Click to expand...
Click to collapse
Try updating the driver, you can get from this sit: https://www.androidbrick.com/download/qualcomm_diag_qd_loader_2016_qfil_driver/
Is "allow OEM unlcking" enabled ?? If not you can enable from developer options .
Custom rom 243 said:
Is "allow OEM unlcking" enabled ?? If not you can enable from developer options .
Click to expand...
Click to collapse
As he said he can't get into the rom
ProchyGaming said:
As he said he can't get into the rom
Click to expand...
Click to collapse
Oh that's why I thought such a obvious reason was not told by anyone .
---------- Post added at 06:37 PM ---------- Previous post was at 06:35 PM ----------
nicobelic said:
I tried to install the gcam on the device and had to unlock the bootloader. At first work, I unlock it, and went to install gcam but it did not work so well. After that my device had some performance problems and I decided to reinstall the ROM using MiFlash.
As I was giving errors and I could not install by MiFlash, I searched for tutorials on Youtube, trying to install without MiFlash, I found some but did not work again. So, I decided to type in the cmd "flashboot oem lock" because I thought this would be the problem that I could not install the ROM by MiFlash and again, it worked, I managed to block it.
However, after searching again, I discovered that I had to unlock it, so I typed the "flashboot oem unlock" command and gave this error, and when I turn on the phone, just appear a white screen with Mi logo.
Click to expand...
Click to collapse
Could you follow that same procedure of locking OEM and then booting into the ROM ? (,Just asking,not giving a solution)
mardrest said:
Try updating the driver, you can get from this sit: https://www.androidbrick.com/download/qualcomm_diag_qd_loader_2016_qfil_driver/
Click to expand...
Click to collapse
I install the driver, write "fastboot oem edl" command, nothing changes.
I think I screwed up realy bad.
This is happening
I found a video that shows the SAME PROBLEM I'm having with my Mi A1.
Why can not I fix the problem? I can not unlock the bootloader.
https://www.youtube.com/watch?v=51LnEOrM3nQ
This shows up when I tried: https://imgur.com/uAVuFle
Related
Hello,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Sam to me. Any help?
ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.
typo - fastboot, not fasboot
fastboot oem fb_mode_clear
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.
With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...
Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?
XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s
I have my 6P connected via USB to my PC. I see the device in Device Manager as Android Bootloader Interface. I on the 6P, in bootloader mode, listed at the bottom is "Connect USB Data Cable". I know the USB cable works as I was able to boot into Android and see it as a drive on my PC.
Other items listed:
Product/Variant: ANGLER-VN2
Device is locked
Qfuse Status: ENABLED
Download Mode: Disabled
Should still be working. Try running fastboot getvar all, or just fastboot devices, on it and see if it works. I know mine always shows the "Connect USB Data Cable" text regardless.
eragon5779 said:
Should still be working. Try running fastboot getvar all, or just fastboot devices, on it and see if it works. I know mine always shows the "Connect USB Data Cable" text regardless.
Click to expand...
Click to collapse
fastboot devices:
84B5T15A29016374 fastboot
C:\WINDOWS\system32>fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:no
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-03.84
(bootloader) version-bootloader:angler-03.75
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x66257ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:84B5T15A29016374
(bootloader) kernel:lk
(bootloader) product:angler
all:
finished. total time: 0.190s
I was able to unlock it this try.
C:\WINDOWS\system32>fastboot flashing unlock
...
(bootloader) Please select 'YES' on screen if you want to continue...
(bootloader) Unlocking bootloader...
(bootloader) Unlocked!
OKAY [ 11.930s]
finished. total time: 11.930s
C:\WINDOWS\system32>
Hello, I am totally lost... I've been trying to solve this problem but no luck... I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (stuck on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
###########
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.017s
##############
any one can help me plz.
anyone can help
t.zennad said:
anyone can help
Click to expand...
Click to collapse
I'm also in the same condition...
fastboot not accessible...
Help!!!
Axon 7 mini 7.1.1 build B2017gV1.2.0B14
Still waiting too.
Get a stock recovery (not TWRP), flash it with fasboot flash recovery recovery.img
I think tdm has a thread with all stock images, flash the one for your country
https://forum.xda-developers.com/axon-7-mini/development/firmware-stock-firmware-t3696538
If this doesn't work, maybe the verity check fails, making the device unable to boot, then go ahead and flash system and boot via fastboot.
fastboot flash system system.img
fastboot flash boot boot.img
Good luck
just a hailmairy here but...
"(bootloader) Charger screen enabled: 'false'"
in Advanced Settings ->Developer Options->Stay Awake (while charging) [ ]
should possible be switched on as it does mentions that charging screen set to off?
Probably would only sort one item though but you never know and if it does your one more step forward.
sonnettie
HEEEEELP! From Liquid tried to flash Lineage16.....flashed bootloader...I'm stuck on fastboot. The down volume key is broken. Only up volume works but not in fastboot. Tried to adb/flash a sock recovery....only can reboot in fastboot dialogue. Any solution? Thank you.
Hello
any one can help please, i am still in same problem
fastboot getvar all
(bootloader) version:0.5
(bootloader) battery-soc-ok:yes
(bootloader) battery-voltage:3447000
(bootloader) variant:TULIP eMMC
(bootloader) secure:yes
(bootloader) version-baseband:
(bootloader) version-bootloader:
(bootloader) display-panel:
(bootloader) off-mode-charge:0
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x12c00000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x5ebb79e00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0x100000000
(bootloader) serialno:bc13c89a
(bootloader) kernel:lk
(bootloader) product:TULIP
all:
finished. total time: 0.022s
------
fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.007s
-------
I relocked my bootloader. Since that day, I can only access : fastboot.
It seems I can flash recovery with fastboot, but the phone never boots into recovery (loop on ZTE logo B2017G ).
I've tried to put my device in EDL mode with DeepFlash cable but without success.
Thanks
I tried to unlock my b2017g with fastboot commands but not luck, i tried use Hydra too... i hope will find a solution soon :/
Hi Everybody, I think I have a similar issue. After many years with regular stock system I decided to change to a custom ROM, hoping I can use my phone with my native language, which was not in the stock rom.
But now I stucked in the fastboot, and I can not get out of it. I can access my phone via fastboot, I have already flashed the TWRP, but the phone can not boot into the recovery and the system. How can I fix this? Please help me, I like this phone, I would like to get it back to life.
I bricked my Axon mini n2015 by flashing No verity boot.img and a custom recovery. Now phone is stuck in fastboot mode. Help guys, what do i do?
Looks like no solution
hey,
I am a noob when it comes to rooting devices and I kinda ****ed up on my 2 year old device.
When I try to start my device, I get this error:
Start up failed:
Your device didnt start up successfully. Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Volume key pressed
USB connected
cmd: getvar:slot-count
cmd: getvar:slot-suffixes
cmd: getvar:slot-suffixes(note: yes, 2 times)
cmd: getvar:has-slot:recovery
cmd: getvar: partition-type:recovery
cmd: getvar:max-download-size
cmd: download:009ff000
cmd: flash:recovery
Error: failed to load kernel!
Boot up failed
my problem is, that no matter how I try to start or factory reset my phone, I sooner or later land on that screen. I can use fastboot commands just fine, but I dont know which I need to use. TWRP cant be started, because I need to press "Recovery Mode" at one point which sends me back to the above error.
I am stuck since half a day and I honestly cant figure it out myself. I hope you can help me to root my phone. many thanks,
Termii
Edit 1: trying the following commands:
C:\Users\Desktop\reboot\platform-tools>fastboot devices
ZY2245QMTN fastboot
C:\Users\Desktop\reboot\platform-tools>fastboot erase recovery
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
erasing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.007s
C:\Users\Desktop\reboot\platform-tools>fastboot flash recovery recovery.img (note: recovery = TWRP 3.1.1-0 Moto G5S Plus [sanders])
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (10236 KB)...
OKAY [ 0.284s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.231s]
finished. total time: 0.519s
C:\Users\Desktop\reboot\platform-tools>fastboot reboot
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
rebooting...
finished. total time: 0.007s
the error my moto shows me:
Start up failed:
Your device didnt start up successfully. Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
AP Fastboot Flash Mode (Secure)
Error: failed to load kernel!
Fastboot Reason: Fall-through from recovery boot mode USB connected
Edit 2:
C:\Users\Desktop\reboot\platform-tools>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8953-C0.8A(*)
(bootloader) product: potter
(bootloader) board: potter
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 3
(bootloader) storage-type: emmc
(bootloader) emmc: 32GB SAMSUNG RX1BMB RV=08 PV=07 FV=0000000000000007
(bootloader) ram: 3GB SAMSUNG LP3 DIE=6Gb M5=01 M6=05 M7=00 M8=7B
(bootloader) cpu: MSM8953
(bootloader) serialno: ZY2245QMTN
(bootloader) cid: 0x0032
(bootloader) channelid: 0x40
(bootloader) uid: 24F61D6D00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Fall-through from recovery boot mode
(bootloader) imei: ********
(bootloader) meid:
(bootloader) date: 05-16-2017
(bootloader) sku: XT1685
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sun Jun 14 3:14:15 UTC 1970"
(bootloader) ro.build.fingerprint[0]: motorola/potter_n/potter_n:7.0/NPN
(bootloader) ro.build.fingerprint[1]: S25.137-33-11/11:user/release-keys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.25.226.11.potter.ret
(bootloader) ro.build.version.full[1]: ail.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-01900-89xx.0
(bootloader) version-baseband: M8953_02.03.07.06R POTTER_EMEADSDS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g64ca40a-0012
(bootloader) kernel.version[1]: 8-g77c6b6b ([email protected]) (gcc ve
(bootloader) kernel.version[2]: rsion 4.9 20150123 (prerelease) (GCC) )
(bootloader) kernel.version[3]: #1 SMP PREEMPT Tue Aug 8 08:37:28 CDT 20
(bootloader) kernel.version[4]: 17
(bootloader) sbl1.git: git=MBM-NG-VC0.8A-0-gc33529e
(bootloader) rpm.git: git=MBM-NG-VC0.C0-1-g202d600
(bootloader) tz.git: git=6c4172f-dirty
(bootloader) devcfg.git: git=6c4172f-dirty
(bootloader) keymaster.git: git=6c4172f-dirty
(bootloader) cmnlib.git: git=6c4172f-dirty
(bootloader) cmnlib64.git: git=6c4172f-dirty
(bootloader) prov.git: git=6c4172f-dirty
(bootloader) aboot.git: git=MBM-NG-VC0.8A-0-gc90d6a9-dirty
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: reteu
all: listed above
finished. total time: 0.177s
solution
it seems I got my phone fixed with this guide: https://forum.xda-developers.com/g5...romfactory-t3691396/post74221633#post74221633
termii10 said:
it seems I got my phone fixed with this guide: https://forum.xda-developers.com/g5...romfactory-t3691396/post74221633#post74221633
Click to expand...
Click to collapse
You might want to edit out your IMEI from the post.
thanks. what is it for btw?
termii10 said:
thanks. what is it for btw?
Click to expand...
Click to collapse
It uniquely IDs a mobile phone, used by carriers to identify stolen devices and disconnect them from the network. If someone else gets a hold of it, they could use it for their illegal device rendering your phone unusable.
termii10 said:
it seems I got my phone fixed with this guide: https://forum.xda-developers.com/g5...romfactory-t3691396/post74221633#post74221633
Click to expand...
Click to collapse
This worked for me as well.
Failed to load Kernel.
Hi dear team,
here's my situation,
When phone is just starting appears a N/A symbol, after that I receive "Start up failed: Your device didnt start up successfully. Use the Software Repair ... etc" message, as well I get the "failed to load kernel". and "fastboot reason fall-through from charger boot mode" message on red letters.
I tried to do the flash stock rom(factory image) via fastboot but when process finish and I reboot phone, still happens the same, I selected the correct stock rom according to my phone model. Phone has bootloader unlocked.
Idk what else I can do. I really appreciate if you can give me a hand.
Greetings
Tropicalvibes said:
Hi dear team,
here's my situation,
When phone is just starting appears a N/A symbol, after that I receive "Start up failed: Your device didnt start up successfully. Use the Software Repair ... etc" message, as well I get the "failed to load kernel". and "fastboot reason fall-through from charger boot mode" message on red letters.
I tried to do the flash stock rom(factory image) via fastboot but when process finish and I reboot phone, still happens the same, I selected the correct stock rom according to my phone model. Phone has bootloader unlocked.
Idk what else I can do. I really appreciate if you can give me a hand.
Greetings
Click to expand...
Click to collapse
I suggest you to use lenovo moto smart assistant app to flash the device, as it will flash your device for you.
riyan65 said:
I suggest you to use lenovo moto smart assistant app to flash the device, as it will flash your device for you.
Click to expand...
Click to collapse
thanks for your answer, I did it already, it does not work cuz it cannot get enough information from the phone.
Tropicalvibes said:
Failed to load Kernel.
Hi dear team,
here's my situation,
When phone is just starting appears a N/A symbol, after that I receive "Start up failed: Your device didnt start up successfully. Use the Software Repair ... etc" message, as well I get the "failed to load kernel". and "fastboot reason fall-through from charger boot mode" message on red letters.
I tried to do the flash stock rom(factory image) via fastboot but when process finish and I reboot phone, still happens the same, I selected the correct stock rom according to my phone model. Phone has bootloader unlocked.
Idk what else I can do. I really appreciate if you can give me a hand.
Greetings
Click to expand...
Click to collapse
hello, could you solve it?
Hello,
I want to know if someone can help me unlocking the bootloader of this device for installing custom rom/apps
It has an Intel Cherry Trail Processor
I can boot to fastboot using the Vol- and Power together and tried the following commands
fastboot oem unlock - returns OKAY but doesn't unlock the bootloader
Code:
fastboot oem lock
- returns that the device is already in the required state
Code:
fastboot flash twrp.img
- returns that it cannot be possible since the device is locked
Code:
fastboot boot twrp.img
- goes to the amazon logo and then right to fastboot again
Code:
fastboot getvar all
(bootloader) serialno: ------------------------ [hidden for purposes]
(bootloader) board: Intel Corp. Cherry Trail CR 0
(bootloader) device-state: locked
(bootloader) boot-state: GREEN
(bootloader) firmware: Intel Corporation CH2T.BSHP.X64.0005.R09.18091217
(bootloader) product-name: CHERRYVIEW D1 PLATFORM
(bootloader) secureboot: yes
(bootloader) off-mode-charge: 1
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:vendor: 0x0000000016C00000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000000FA800000
(bootloader) partition-type:data: ext4
(bootloader) partition-size:data: 0x00000000FA800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x000000008CC00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000020000000
(bootloader) partition-type:factory: none
(bootloader) partition-size:factory: 0x0000000002000000
(bootloader) partition-type:recovery: none
(bootloader) partition-size:recovery: 0x0000000002000000
(bootloader) partition-type:boot: none
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-type:metadata: none
(bootloader) partition-size:metadata: 0x0000000001000000
(bootloader) partition-type:config: ext4
(bootloader) partition-size:config: 0x0000000000800000
(bootloader) partition-type:misc: none
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-type:persistent: ext4
(bootloader) partition-size:persistent: 0x0000000000100000
(bootloader) partition-type:bootloader2: none
(bootloader) partition-size:bootloader2: 0x0000000004000000
(bootloader) partition-type:bootloader: vfat
(bootloader) partition-size:bootloader: 0x0000000004000000
(bootloader) max-download-size: 0x0000000010000000
(bootloader) battery-voltage:
(bootloader) version-bootloader: kernelflinger-02.19
(bootloader) device-type: PROD
(bootloader) product: bishop
all:
Finished. Total time: 1.098s
I can also boot into DNX FASTBOOT MODE using all 3 buttons, but I can't do anything in that mode, but the device is recognized using fastboot devices
Does anyone know how to use dnx fastboot mode? Or what is it?
Thank you
Wrong command
Hey! You should be using fastboot OEM unlock, not fastboot OEM lock. Also the unit doesn't have a way to enable adb from what I can tell.
Note: I have NO experience hacking amazon echo
Could you use the same method we use to hack the fire HD8 or HD10 with the brick.sh, then flash the bootrom, then enter a hacked fastboot? From what it looks like, recovery mode on the show looks like the same one used on the HD10.
Echo Show need to unlock
Hello
I tried with the following commands.
I tried with "fastboot oem unlock", but command is not working.
I want to unlock my amazon echo show devices. Or is there any way to open echo show without login with amazon account.
Please help me to solve the issue.
arcanandrei said:
Hello,
I want to know if someone can help me unlocking the bootloader of this device for installing custom rom/apps
It has an Intel Cherry Trail Processor
I can boot to fastboot using the Vol- and Power together and tried the following commands
fastboot oem unlock - returns OKAY but doesn't unlock the bootloader
Code:
fastboot oem lock
- returns that the device is already in the required state
Code:
fastboot flash twrp.img
- returns that it cannot be possible since the device is locked
Code:
fastboot boot twrp.img
- goes to the amazon logo and then right to fastboot again
Code:
fastboot getvar all
(bootloader) serialno: ------------------------ [hidden for purposes]
(bootloader) board: Intel Corp. Cherry Trail CR 0
(bootloader) device-state: locked
(bootloader) boot-state: GREEN
(bootloader) firmware: Intel Corporation CH2T.BSHP.X64.0005.R09.18091217
(bootloader) product-name: CHERRYVIEW D1 PLATFORM
(bootloader) secureboot: yes
(bootloader) off-mode-charge: 1
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) partition-type:vendor: ext4
(bootloader) partition-size:vendor: 0x0000000016C00000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0x00000000FA800000
(bootloader) partition-type:data: ext4
(bootloader) partition-size:data: 0x00000000FA800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x000000008CC00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x0000000020000000
(bootloader) partition-type:factory: none
(bootloader) partition-size:factory: 0x0000000002000000
(bootloader) partition-type:recovery: none
(bootloader) partition-size:recovery: 0x0000000002000000
(bootloader) partition-type:boot: none
(bootloader) partition-size:boot: 0x0000000002000000
(bootloader) partition-type:metadata: none
(bootloader) partition-size:metadata: 0x0000000001000000
(bootloader) partition-type:config: ext4
(bootloader) partition-size:config: 0x0000000000800000
(bootloader) partition-type:misc: none
(bootloader) partition-size:misc: 0x0000000000100000
(bootloader) partition-type:persistent: ext4
(bootloader) partition-size:persistent: 0x0000000000100000
(bootloader) partition-type:bootloader2: none
(bootloader) partition-size:bootloader2: 0x0000000004000000
(bootloader) partition-type:bootloader: vfat
(bootloader) partition-size:bootloader: 0x0000000004000000
(bootloader) max-download-size: 0x0000000010000000
(bootloader) battery-voltage:
(bootloader) version-bootloader: kernelflinger-02.19
(bootloader) device-type: PROD
(bootloader) product: bishop
all:
Finished. Total time: 1.098s
I can also boot into DNX FASTBOOT MODE using all 3 buttons, but I can't do anything in that mode, but the device is recognized using fastboot devices
Does anyone know how to use dnx fastboot mode? Or what is it?
Thank you
Click to expand...
Click to collapse
All Amazon echo show devices required unlock code which is generated from the serial number to unlock the devices.
Unfortunately this unlock code can be only retrieved inside amazon corp network through their internal tool for developing purpose.
Hello! I bought a second hand show 5 and the former owner has the account locked out. I can not do anything. When I go into configuration it tells me that it does not recognize the account in amazon.
I have thought that if I can change the serial number of the device, I could finish the configuration correctly.
Code:
fastboot getvar all
(bootloader) antirback_tee_version: 0x0103
(bootloader) antirback_lk_version: 0x0001
(bootloader) antirback_pl_version: 0x0001
(bootloader) rpmb_state: 1
(bootloader) lk_build_desc: cd178e6-20190703_190118
(bootloader) pl_build_desc: d14f08f-20190512_232119
(bootloader) secure: yes
(bootloader) prod: 1
(bootloader) otu_code: +QdtQ0mzlUklt9mtCmRNAYIKNnfW6akA
(bootloader) unlock_status: false
(bootloader) unlock_code: 0x???????????????????? [hidden for purposes]
(bootloader) serialno: ???????????????? [hidden for purposes]
(bootloader) max-download-size: 0x6d00000
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) kernel: lk
(bootloader) product: CHECKERS
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.018s
I have tried this:
Code:
sudo fastboot oem unlock 0xMy_onlock_code
FAILED (remote: 'the command you input is restricted on locked hw')
fastboot: error: Command failed
I cannot access adb.
Any ideas to root or start adb from fastboot?
Any ideas to unlink the old user's account?
I already did a factory reset. Sorry for my english.
Hello , have any sucess?
halfblood* said:
Hello , have any sucess?
Click to expand...
Click to collapse
I got the bootloader unlock code just now using power and both volume buttons to boot fstboot then plugged my phone into micro USB on back running bugajager app
I have had some success using Bugjaeger on my android phone while attached to a couple of uncooperative devices, namely my Tesla style head unit, as well a "Class VR" headset I picked up on eBay . The headset was locked down fairly well, but it was no match for Bugjaeger. I ended up able to load my own launcher, and now it acts like any other rooted android. There may be other tools that can help, I am just sharing my experience with one app. Hope this helps. R*
memorixo said:
Hello! I bought a second hand show 5 and the former owner has the account locked out. I can not do anything. When I go into configuration it tells me that it does not recognize the account in amazon.
I have thought that if I can change the serial number of the device, I could finish the configuration correctly.
Code:
fastboot getvar all
(bootloader) antirback_tee_version: 0x0103
(bootloader) antirback_lk_version: 0x0001
(bootloader) antirback_pl_version: 0x0001
(bootloader) rpmb_state: 1
(bootloader) lk_build_desc: cd178e6-20190703_190118
(bootloader) pl_build_desc: d14f08f-20190512_232119
(bootloader) secure: yes
(bootloader) prod: 1
(bootloader) otu_code: +QdtQ0mzlUklt9mtCmRNAYIKNnfW6akA
(bootloader) unlock_status: false
(bootloader) unlock_code: 0x???????????????????? [hidden for purposes]
(bootloader) serialno: ???????????????? [hidden for purposes]
(bootloader) max-download-size: 0x6d00000
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) kernel: lk
(bootloader) product: CHECKERS
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.018s
I have tried this:
Code:
sudo fastboot oem unlock 0xMy_onlock_code
FAILED (remote: 'the command you input is restricted on locked hw')
fastboot: error: Command failed
I cannot access adb.
Any ideas to root or start adb from fastboot?
Any ideas to unlink the old user's account?
I already did a factory reset. Sorry for my english.
Click to expand...
Click to collapse
Hi! Have you managed to do anything with it? I have a locked echo show 8, which I'm trying hard on finding a way to unlock it... Would very much appreciate any help on this matter, thanks!