Hello.
I requested help on wrong forum, first person that responded redirected me here.
Here's the copy-pasted contents of that post.
I have a Motorola. I typically leave my cellphone attached to my computer with USB so it can charge, slowly but surely.
When I wanted to get on my way I noticed my phone wouldn't start which I found interesting.
I left it on a charger for some time and when I held the power button to power up, I noticed it got stuck at boot.
What it typically does is open boot screen with Motorola logo, vibrate, start an animation and after mid-boot say "halo Moto" and then leave me at home screen.
But this time, it just get stuck on a boot screen. It shows the boot screen with Motorola logo, vibrates and then does nothing (until battery dies, I left it for an hour?)
I pressed the volume down and power button to enable debugging.
I get a "FastBoot AP Flash Mode" menu.
The options are:
Start (which puts me back into stuck boot)
Restart Bootloader (which restarts the FastBoot)
Recovery Mode (which gives me this: "No Command" with an Android icon, does nothing more]
Power Off (which powers off the phone)
Bootloader Logs (which changes some text to: "Fastboot Reason: Reboot mode set to FastBoot" or "Volume button down")
Switch Tools Mode (which toggles text between Tools Mode Config: DISABLED and ENABLED, no idea of other effects)
BARCODES (which probably shows scannable code so that professionals needn't type the ID)
I wanted to send it back to the seller, but they claim that they take no responsibility for loss of information, all my data is stuck on 128GB on the internal memory.
I would like to go to service for data recovery, but I due to COVID-19 everything's closed.
What could I potentially do to restore my phone? And if I can't, I can send it back, but how do I backup my data?
It's Motorola One Zoom.
Click to expand...
Click to collapse
I suggest we try the following solution to your problem.
First, check which boot slot the phone is in. It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot.
Command to verify:
Code:
fastboot getvar current-slot
Make active Slot A:
Code:
fastboot --set-active=a
Then reboot the bootloader:
Code:
fastboot reboot bootloader
Perform user data wiping:
Code:
fastboot -w
And install the latest firmware for your model via fastboot.
ilia3367 said:
I suggest we try the following solution to your problem.
First, check which boot slot the phone is in. It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot.
Command to verify:
Code:
fastboot getvar current-slot
Make active Slot A:
Code:
fastboot --set-active=a
Then reboot the bootloader:
Code:
fastboot reboot bootloader
Perform user data wiping:
Code:
fastboot -w
And install the latest firmware for your model via fastboot.
Click to expand...
Click to collapse
I tried getting fastboot installed, but it got stuck at "waiting for any device" on the first command. After some painful entire hour of investigation I found out that I need USB debugging enabled, which I haven't done when the smartphone was working.
" It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot."
I didn't update anything, nothing's changed about hardware and it had no access to Internet, so it couldn't update itself. Neither I nor any of my apps had the means to flash the phone.
yeetusAAA said:
I tried getting fastboot installed, but it got stuck at "waiting for any device" on the first command. After some painful entire hour of investigation I found out that I need USB debugging enabled, which I haven't done when the smartphone was working.
" It happens that in case of unsuccessful flashing the phone is loaded into a non-working slot."
I didn't update anything, nothing's changed about hardware and it had no access to Internet, so it couldn't update itself. Neither I nor any of my apps had the means to flash the phone.
Click to expand...
Click to collapse
USB debugging has nothing to do with fastboot.
If it's in fastboot mode, and fastboot commands are not working could be a driver issue.
How is is it listed in Device Manager?
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
USB debugging has nothing to do with fastboot.
If it's in fastboot mode, and fastboot commands are not working could be a driver issue.
How is is it listed in Device Manager?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
The situation changed slightly since I came back from work.
Previously device appeared as unknown device.
With name "fastboot parker S", I have it in search history.
After rebooting (and installing 50 drivers) my device appears as "Motorola ADB Interface", however execution of commands don't end successfully.
Code:
X:\Applications\MinimalADBFB>fastboot -help
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw <bootable-partition> <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader|emergency] Reboot device [into bootloader or emergency mode].
reboot-bootloader Reboot device into bootloader.
oem <parameter1> ... <parameterN> Executes oem specific command.
stage <infile> Sends contents of <infile> to stage for
the next command. Supported only on
Android Things devices.
get_staged <outfile> Receives data to <outfile> staged by the
last command. Supported only on Android
Things devices.
help Show this help message.
options:
-w Erase userdata and cache (and format
if supported by partition type).
-u Do not erase partition before
formatting.
-s <specific device> Specify a device. For USB, provide either
a serial number or path to device port.
For ethernet, provide an address in the
form <protocol>:<hostname>[:port] where
<protocol> is either tcp or udp.
-c <cmdline> Override kernel commandline.
-i <vendor id> Specify a custom USB vendor id.
-b, --base <base_addr> Specify a custom kernel base
address (default: 0x10000000).
--kernel-offset Specify a custom kernel offset.
(default: 0x00008000)
--ramdisk-offset Specify a custom ramdisk offset.
(default: 0x01000000)
--tags-offset Specify a custom tags offset.
(default: 0x00000100)
-n, --page-size <page size> Specify the nand page size
(default: 2048).
-S <size>[K|M|G] Automatically sparse files greater
than 'size'. 0 to disable.
--slot <slot> Specify slot name to be used if the
device supports slots. All operations
on partitions that support slots will
be done on the slot specified.
'all' can be given to refer to all slots.
'other' can be given to refer to a
non-current slot. If this flag is not
used, slotted partitions will default
to the current active slot.
-a, --set-active[=<slot>] Sets the active slot. If no slot is
provided, this will default to the value
given by --slot. If slots are not
supported, this does nothing. This will
run after all non-reboot commands.
--skip-secondary Will not flash secondary slots when
performing a flashall or update. This
will preserve data on other slots.
--skip-reboot Will not reboot the device when
performing commands that normally
trigger a reboot.
--disable-verity Set the disable-verity flag in the
the vbmeta image being flashed.
--disable-verification Set the disable-verification flag in the vbmeta image being flashed.
--unbuffered Do not buffer input or output.
--version Display version.
-h, --help show this message.
X:\Applications\MinimalADBFB>fastboot -getvar current-slot
fastboot: unknown option -- g
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.016s
X:\Applications\MinimalADBFB>fastboot -set-active=a
fastboot: usage: no command
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: -0.000s
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.000s
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: -0.000s
X:\Applications\MinimalADBFB>fastboot -set-active=a
fastboot: usage: no command
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (remote failure)
finished. total time: 0.016s
X:\Applications\MinimalADBFB>fastboot reboot bootloader
rebooting into bootloader...
FAILED (command write failed (No such file or directory))
finished. total time: 0.016s
X:\Applications\MinimalADBFB>
About all those "remote" failures, the commands do appear in "Bootloader Logs", and the text is something like:
"cmd: getvar:slot-count" and "cmd: set_active:a". As someone with Android unrelated programming background I see nothing that would indicate an error on the phone.
Manually rebooting to fastboot doesn't change anything, rebooting the device in general doesn't solve the issue.
After rebooting I redid my steps:
Code:
X:\Applications\MinimalADBFB>fastboot getvar current-slot
current-slot: a
finished. total time: 0.004s
X:\Applications\MinimalADBFB>fastboot --set-active=a
Setting current slot to 'a'...
FAILED (status read failed (Too many links))
finished. total time: 0.005s
X:\Applications\MinimalADBFB>
Too many links? Corrupted file system?
Try to update the adb & fastboot drivers.
Phone is downloading into Recovery?
Ejects from the attached archive adb folder to the root of the C:\ drive.
I didn't have a problem with these drivers.
ilia3367 said:
Try to update the adb & fastboot drivers.
Click to expand...
Click to collapse
How? There doesn't seem to be official link to fastboot, every next website I visited has different edition. Half of links are dead, others have viruses. Even manufacturers of phones seem to have different drivers.
Phone is downloading into Recovery?
Click to expand...
Click to collapse
No, the phone is stuck at boot. It doesn't automatically fallback into Recovery, nothing changed since last time I entered "Recovery Mode".
Ejects from the attached archive adb folder to the root of the C:\ drive.
Click to expand...
Click to collapse
I placed the files in plain C:\, executing your commands invoked following response:
Code:
C:\>fastboot getvar current-slot
< waiting for any device >
current-slot: a
Finished. Total time: 0.001s
C:\>fastboot --set-active=a
fastboot: error: Device does not support slots
How is a device determined by a computer in Device Manager?
What does the "fastboot devices" command say?
---------- Post added at 13:57 ---------- Previous post was at 13:55 ----------
Your phone is in the correct boot Slot A, where you should install the firmware.
---------- Post added at 13:58 ---------- Previous post was at 13:57 ----------
Is the bootloader unlocked?
ilia3367 said:
How is a device determined by a computer in Device Manager?
What does the "fastboot devices" command say?
---------- Post added at 13:57 ---------- Previous post was at 13:55 ----------
Your phone is in the correct boot Slot A, where you should install the firmware.
---------- Post added at 13:58 ---------- Previous post was at 13:57 ----------
Is the bootloader unlocked?
Click to expand...
Click to collapse
Device Manager calls my phone "Motorola ADB Interface".
fastboot devices says:
Code:
C:\>fastboot devices
ZY226KZGT5 fastboot
"Your phone is in the correct boot Slot A, where you should install the firmware."
Is there a way to recover data first?
"Is the bootloader locked?"
I have no idea.
Screen mentions:
"oem_locked"
"AP Fastboot Flash Mode (Secure)"
Code:
C:\>fastboot flashing get_unlock_ability
(bootloader) use "oem get_unlock_data" and web portal
(bootloader) http://motorola.com/unlockbootloader
OKAY [ 0.005s]
Finished. Total time: 0.008s
"Is there a way to recover data first?" - Are you sure there's something left? Then remove the line "fastboot erase userdata" from the .bat executive file and your data will be saved.
ilia3367 said:
"Is there a way to recover data first?" - Are you sure there's something left?
Click to expand...
Click to collapse
I had 120GB of data on it, before it crapped out on me.
Then remove the line "fastboot erase userdata" from the .bat executive file and your data will be saved.
Click to expand...
Click to collapse
Which file? Tehre's no bat file in the zip you provided.
yeetusAAA said:
I had 120GB of data on it, before it crapped out on me.
Which file? Tehre's no bat file in the zip you provided.
Click to expand...
Click to collapse
I have written some instructions for flashing firmware
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
I have written some instructions for flashing firmware
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
- After four subsequent link clicks to "[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot", the post mentions "Your Cedric will boot normally again", but I have Motorola, other of your post say that you shouldn't downgrade flash, also the adb shell dd if=/dev/zero of= writes null to the given partition. No further instruction on how to get into "TWRP" boot. No way of knowing if it will preserve my data.
- Verizon Tool detects my cellphone but after half an hour its still not done initializing.
- Lenovo Assistance requires USB debugging.
- RSD Lite's instructions say: "WARNING Restoring your Motorola firmware will factory reset your device and you will loose all data on the device and have to set it back up like a new phone.", can I recover my data before hand?
No recovery instructions, tree of links and still no answer, can I restore the data?
It seems that people read only first 10 words and then copy link on "I've written tutorial on how to fix failed flashing" and they skip past "I want to backup my data" and "I haven't flashed my smartphone, it just happened".
Every next poster seems entirely oblivious of the main post and every post that comes before the post they respond to.
I get it, you're educated on the topic and have everything figured out, I don't. Why do you assume I would know how?
yeetusAAA said:
- After four subsequent link clicks to "[FIX] Phone Reboots Into Recovery Mode & Can Only Be Started From Fastboot", the post mentions "Your Cedric will boot normally again", but I have Motorola, other of your post say that you shouldn't downgrade flash, also the adb shell dd if=/dev/zero of= writes null to the given partition. No further instruction on how to get into "TWRP" boot. No way of knowing if it will preserve my data.
- Verizon Tool detects my cellphone but after half an hour its still not done initializing.
- Lenovo Assistance requires USB debugging.
- RSD Lite's instructions say: "WARNING Restoring your Motorola firmware will factory reset your device and you will loose all data on the device and have to set it back up like a new phone.", can I recover my data before hand?
No recovery instructions, tree of links and still no answer, can I restore the data?
It seems that people read only first 10 words and then copy link on "I've written tutorial on how to fix failed flashing" and they skip past "I want to backup my data" and "I haven't flashed my smartphone, it just happened".
Every next poster seems entirely oblivious of the main post and every post that comes before the post they respond to.
I get it, you're educated on the topic and have everything figured out, I don't. Why do you assume I would know how?
Click to expand...
Click to collapse
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
sd_shadow said:
What does getvar all say?
Code:
fastboot getvar all
Post it here after you remove the IMEI line.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
Code:
C:\>fastboot getvar all
getvar:all FAILED (Status read failed (Too many links))
Finished. Total time: 0.005s
yeetusAAA said:
What does getvar all say?
Click to expand...
Click to collapse
As I said in your other thread.
You cannot backup data with locked bootloader.
If you want to save the data, take it to a shop that has the special tools required.
Sent from my ali using XDA Labs
sd_shadow said:
As I said in your other thread.
You cannot backup data with locked bootloader.
If you want to save the data, take it to a shop that has the special tools required.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
I see. Thanks.
bricked phone
so i tried installing firmware on the one zoom and ended up having problem where now it wont boot at all i get no connection from computer and only the logo lights up is there any way to revive my phone ,also holding down the volume down and power button wont do anything is there anything i can do?
death1426 said:
so i tried installing firmware on the one zoom and ended up having problem where now it wont boot at all i get no connection from computer and only the logo lights up is there any way to revive my phone ,also holding down the volume down and power button wont do anything is there anything i can do?
Click to expand...
Click to collapse
Does it show up in device manager?
Sent from my Moto E (4) using Tapatalk
does not show up in device manager
sd_shadow said:
Does it show up in device manager?
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
no unfortunately it does not already tried placing it in edl mode with a cable but no to avail also installed Qualcomm drivers just to be sure uncertain what i can do at this point
Related
I was using a kingroot(One click root) app to root my moto E2 (4G-LTE) and it crashed in the middle and my phone is not booting up
when ever i m trying to switch it on i m getting message" hab check failed for boot". its getting stuck to it after displaying motorola logo. I tried other boot options such as
normal powerup
recovery
factory
barcodes
bp tools
qcom
but all this didnt worked.
messages i m getting are
hab checked failed for boot
failed to validate boot image
Fast boot reason : Fall-through from normal boot mode .
then it displays following
AP Fastboot FlashMode (Secure)
BL: 80.20(sha-76fb222, 2015-12-09 07:35:50)
Baseband: M8916_2020629.41.03.21.51R SURNIA_EMEA_DSDS
Product/Variant: surnia XT1521 8gb P3
Serial Number: TA38501LL4
CPU: MSM8916
eMMC: 8GB Samsung RV=07 PV=01 TY=57
DRAM: 1024mb Samsung S8 SSRAM DIE=4gb
console [null]: null
battery: ok
Device is LOCKED. Status code: 0
Software status: official
Transfer Mode: USB Connected (Connected the USB)
and i toggled up and down volume button and enter in to recovery mode but it doesn't have any command only image of Android with red ! on it belly and after few minutes it goes back to the starting screen automatically
after googling the issues, i installed adb and fastboot to unlock the bootloader
fastboot oem get_unlock_data
I pasted the lock code in Motorola’s official page and received the unlock code
fastboot oem unlock UNIQUE_KEY_FROM_EMAIL
but it showing this error
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.025s
As I can't boot and entered into GUI of android. is there is anyway to enable the "Allow OEM unlock" from developer optiont through some other source
And i tried this too
fastboot -w -u
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.096s]
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.121s
Or Is there any way to bring my phone back in working condition
Thanks
rupeshchan said:
I was using a kingroot(One click root) app to root my moto E2 (4G-LTE) and it crashed in the middle and my phone is not booting up
when ever i m trying to switch it on i m getting message" hab check failed for boot". its getting stuck to it after displaying motorola logo. I tried other boot options such as
normal powerup
recovery
factory
barcodes
bp tools
qcom
but all this didnt worked.
messages i m getting are
hab checked failed for boot
failed to validate boot image
Fast boot reason : Fall-through from normal boot mode .
then it displays following
AP Fastboot FlashMode (Secure)
BL: 80.20(sha-76fb222, 2015-12-09 07:35:50)
Baseband: M8916_2020629.41.03.21.51R SURNIA_EMEA_DSDS
Product/Variant: surnia XT1521 8gb P3
Serial Number: TA38501LL4
CPU: MSM8916
eMMC: 8GB Samsung RV=07 PV=01 TY=57
DRAM: 1024mb Samsung S8 SSRAM DIE=4gb
console [null]: null
battery: ok
Device is LOCKED. Status code: 0
Software status: official
Transfer Mode: USB Connected (Connected the USB)
and i toggled up and down volume button and enter in to recovery mode but it doesn't have any command only image of Android with red ! on it belly and after few minutes it goes back to the starting screen automatically
after googling the issues, i installed adb and fastboot to unlock the bootloader
fastboot oem get_unlock_data
I pasted the lock code in Motorola’s official page and received the unlock code
fastboot oem unlock UNIQUE_KEY_FROM_EMAIL
but it showing this error
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.025s
As I can't boot and entered into GUI of android. is there is anyway to enable the "Allow OEM unlock" from developer optiont through some other source
And i tried this too
fastboot -w -u
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.096s]
erasing 'cache'...
OKAY [ 0.018s]
finished. total time: 0.121s
Or Is there any way to bring my phone back in working condition
Thanks
Click to expand...
Click to collapse
this is moto e1 section in forum this is not for moto e2..and you have to unlock bootloader if u want root or install custom rom..this is not mtk devices in mtk devcies this kingroot works ..u cant root or install using kingroot ...just ask in moto e2 section:silly::silly:
Flash (through fastboot)stock image for your device.
That's it.
I hope there must be a stock image for your variant in moto e 2015 forum.
-z3r0- said:
Flash (through fastboot)stock image for your device.
That's it.
I hope there must be a stock image for your variant in moto e 2015 forum.
Click to expand...
Click to collapse
Thank you very much for this! Worked perfect
Found the stock image (MOTO E2 (4G-LTE)) Indian Version here : motoe2015customs.blogspot.ae/2016/02/stock-rom-60-marshmallow-surnia-xt1521.html
I flashed only following and my phone boot up back to normal
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
rupeshchan said:
Thank you very much for this! Worked perfect
Found the stock image (MOTO E2 (4G-LTE)) Indian Version here : motoe2015customs.blogspot.ae/2016/02/stock-rom-60-marshmallow-surnia-xt1521.html
I flashed only following and my phone boot up back to normal
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
One question dude, were you on marshmallow before trying kingroot?
Yes bro!!
rupeshchan said:
Yes bro!!
Click to expand...
Click to collapse
Okay then flash Systemless SuperSu to root.
Will you explain "how to" step by step? If possible?? Or share the link, please
First of allunlock your phone's bootloader, here's a guide : http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Then download latest twrp recovery from here : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Flash it through the commands you used for stock recovery.
Download latest supersu from here and flash it in twrp : http://download.chainfire.eu/supersu
-z3r0- said:
First of allunlock your phone's bootloader, here's a guide : http://forum.xda-developers.com/moto-e-2015/general/guide-unlock-bootloader-moto-e-2015-t3045748
Then download latest twrp recovery from here : http://forum.xda-developers.com/devdb/project/?id=10398#downloads
Flash it through the commands you used for stock recovery.
Download latest supersu from here and flash it in twrp : http://download.chainfire.eu/supersu
Click to expand...
Click to collapse
Thanks a lot. :fingers-crossed:
help me
rupeshchan said:
Thank you very much for this! Worked perfect
Found the stock image (MOTO E2 (4G-LTE)) Indian Version here : motoe2015customs.blogspot.ae/2016/02/stock-rom-60-marshmallow-surnia-xt1521.html
I flashed only following and my phone boot up back to normal
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
same problem happened to me
model is moto e xt-1521
i am not able to go dev settings
jhn
So i just unlocked the device and Re-flashed it with mi flash tool, now the Phone is stuck at Fastboot mode.
i get this
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
finished. total time: 0.001s
Click to expand...
Click to collapse
is my bootloader unlocked?
also when i do set active a, this happens
C:\Users\user>fastboot -set active=a
< waiting for device >
I have tired every solutions i found online still no luck.
Connect the phone to pc and type in "fastboot devices" - do you see any device listed?
Also the correct command is:
fastboot --set-active=a
_mysiak_ said:
Connect the phone to pc and type in "fastboot devices" - do you see any device listed?
Also the correct command is:
fastboot --set-active=a
Click to expand...
Click to collapse
Yes i do but the command doesn't exist in fastboot please help
PS C:\tmp\platform-tools> fastboot --set active=a
C:\adb\fastboot.exe: unrecognised option `--set'
Click to expand...
Click to collapse
Also it says waiting for device it has been more then 30 minutes.
Now the Phone is rebooing at Andriod One Logo.
SpectreZ said:
Yes i do but the command doesn't exist in fastboot please help
Click to expand...
Click to collapse
Again, type it correctly.
In other words, spot the difference
fastboot --set-active=a (what I wrote)
fastboot --set active=a (what you wrote)
Do you see android/fastboot device in your device manager on the PC when you connect it to the PC in fastboot mode?
Edit: also replace fastboot.exe and adb.exe in c:\ADB\ folder as this one is being used. Or remove this folder from Windows PATHS.
_mysiak_ said:
Again, type it correctly.
In other words, spot the difference
fastboot --set-active=a (what I wrote)
fastboot --set active=a (what you wrote)
Do you see android/fastboot device in your device manager on the PC when you connect it to the PC in fastboot mode?
Edit: also replace fastboot.exe and adb.exe in c:\ADB\ folder as this one is being used. Or remove this folder from Windows PATHS.
Click to expand...
Click to collapse
I see Kedacom USB Device - Andorid Bootloader interface.
and i cannot remove the folder from C adb.
I have used mi Flash tool and while checking the log i saw boot was flashed at B so i erased the b boot useing fastboot also a
then I Reflash the B as 1st and A as 2nd the phone was able to make thru Recovery but when i restarted i went back into 0 again
SpectreZ said:
I see Kedacom USB Device - Andorid Bootloader interface.
and i cannot remove the folder from C adb.
I have used mi Flash tool and while checking the log i saw boot was flashed at B so i erased the b boot useing fastboot also a
then I Reflash the B as 1st and A as 2nd the phone was able to make thru Recovery but when i restarted i went back into 0 again
Click to expand...
Click to collapse
Are you sure that phone is in fastboot and not in recovery? What do you see on the phone screen?
You are doing too many things at once, focus on one thing and once you get it solved, move to another one. Also please provide answers to all questions, they are essential for troubleshooting.
1. Reinstall drivers and ADB - https://forum.xda-developers.com/showthread.php?t=2588979
2. Reboot phone in fastboot, connect it to the PC and type in "fastboot devices" - do you see any device connected?
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no
(bootloader) slot-count:2
(bootloader) secure:yes
(bootloader) serialno:35a1981490a2
(bootloader) product:laurel_sprout
(bootloader) max-download-size:804261888
(bootloader) kernel:uefi
all:
finished. total time: 0.438s
C:\Users\fahim>
Click to expand...
Click to collapse
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-a
Click to expand...
Click to collapse
SpectreZ said:
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-a
Click to expand...
Click to collapse
I guess you again did not follow given advice. You are still using old fastboot. In this case use "fastbot set_active a"
_mysiak_ said:
SpectreZ said:
Phone is now Started so what i did was.
* erased system_a
* erased system_b
also
* erased boot_a
* erased boot_b
I think the system is in B now.
and now the device started successfully still i think i messed up and i did everything you said.
Answer: i was on the Bunny screen Fastboot and yes " Fastboot devices " showed my device,
Can you kindly Guide me how do i factory set it? so i won't have any problem i Messed up because i didn't saw the note at StockRom in this forums where something is wrong in slots
C:\Users\fahim>fastboot --set-active-a
fastboot: unknown option -- set-active-aI guess you again did not follow given advice. You are still using old fastboot. In this case use "fastbot set_active a"
Click to expand...
Click to collapse
My Apologies, My Mind was rushing
Which one is the latest? can you tell me? please
Click to expand...
Click to collapse
Click to expand...
Click to collapse
1) update your ADB/Fastboot from the link I provided and use "fastboot --set-active=a"
or
2) keep what you have and use "fastboot set_active a"
_mysiak_ said:
1) update your ADB/Fastboot from the link I provided and use "fastboot --set-active=a"
or
2) keep what you have and use "fastboot set_active a"
Click to expand...
Click to collapse
Oh God thanks it worked, Can you tell me why there is A and B ? i mean 2 slots? also how do i get the device into factory fresh ?
Like the 1st time when i bought this. thank you soo much + Liked
If i use Mi Flash tool again, So am gonna be in Danger again too?
You can use MiFlash, but before flashing you need to make sure that your active partition is A (with commands mentioned before).
To restore to 100% stock:
1. set partition A as active
2. run MiFlash WITHOUT locking bootloader (or run script flash_all.bat)
3. start the phone, if everything works, move to the next step (ONLY IF PHONE WORKS)
4. run MiFlash with bootloader lock (or run script flash_all_lock.bat) or run "fastboot flashing lock"
5. after reboot, your phone should start as if it came from a factory
_mysiak_ said:
You can use MiFlash, but before flashing you need to make sure that your active partition is A (with commands mentioned before).
To restore to 100% stock:
1. set partition A as active
2. run MiFlash WITHOUT locking bootloader (or run script flash_all.bat)
3. start the phone, if everything works, move to the next step (ONLY IF PHONE WORKS)
4. run MiFlash with bootloader lock (or run script flash_all_lock.bat) or run "fastboot flashing lock"
5. after reboot, your phone should start as if it came from a factory
Click to expand...
Click to collapse
Thanks Everything is now great. However what is slot count? and what happens when it hits 0? also i locked the device via fastboot flashing lock.
It should be number of slots. 2 = boot_a + boot_b
It it hits 0, I guess you have serious problem as bootloader doesn't see any boot partition.
More info in the source code: https://android.googlesource.com/pl...otctrl/+/refs/heads/nougat-dev/boot_control.c
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
dary1361 said:
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
Click to expand...
Click to collapse
See this thread:
[Moto G Play](2021)(guamna) Stock firmware
Moto G Play (2021) Stock Firmware Codename: guamna Model: XT-2093 Rescue and Smart Assistant (LMSA) https://mirrors.lolinet.com/firmware/moto/guamna/official/ https://t.me/s/MotoUpdatesTracker?q=#guamna [Index] Motorola Stock Firmware...
forum.xda-developers.com
residentorca said:
See this thread:
[Moto G Play](2021)(guamna) Stock firmware
Moto G Play (2021) Stock Firmware Codename: guamna Model: XT-2093 Rescue and Smart Assistant (LMSA) https://mirrors.lolinet.com/firmware/moto/guamna/official/ https://t.me/s/MotoUpdatesTracker?q=#guamna [Index] Motorola Stock Firmware...
forum.xda-developers.com
Click to expand...
Click to collapse
This might be a stupid question. But isn't stock firmware what the device comes with? I'm trying to "de-google" my phone.
dary1361 said:
This might be a stupid question. But isn't stock firmware what the device comes with? I'm trying to "de-google" my phone.
Click to expand...
Click to collapse
You can root it and use Magisk to clean things up but no de-Googling. Check out the thread.
Any device that launched with Android 8 or newer is compatible with GSIs. Any device that launched with Android 10 or newer use super.img, which require the extra step of repacking rather than flashing directly. This is what I would recommend if you want ROM support on a brand new device.
dary1361 said:
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
Click to expand...
Click to collapse
https://drive.google.com/file/d/1DydHY_Q_paR4QcLhhyE8ih3hYZpqK3RM/view?usp=drivesdk is a device tree with a build error bootctrl if we get this working we can build ROMs and twrp
I have a TWP I ported it from the stock recovery and one from Guamp which is the G9
svoc said:
https://drive.google.com/file/d/1DydHY_Q_paR4QcLhhyE8ih3hYZpqK3RM/view?usp=drivesdk is a device tree with a build error bootctrl if we get this working we can build ROMs and twrp
Click to expand...
Click to collapse
Hey I can’t access the file for some reason. Care to reupload? I’m trying to get a port started but I can’t find the device tree anywhere and can’t find a good guide to make one myself.
Hey you go I got a few more errors fixed but don't have time I'm on a new phone right now sorry hope you get it working by the way look at the trwp it will have some device trees you can use to get started
I want to know if there's a custom ROM for this device.
Hold on, there is a custom ROM for this device.
[ROM][13][guamna] AOSP 13 [Monthly Builds]
AOSP 13 This is a moto-common project release under the codename guamna /* * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...). * Please do some...
forum.xda-developers.com
dary1361 said:
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
Click to expand...
Click to collapse
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
WolfHunter16 said:
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Click to expand...
Click to collapse
Now, if I were to download a rom from the site, would it be A only? B? A/B?
They are all A/B, just check the filenames. If you read the release notes, they state there is no A-only build yet.
WolfHunter16 said:
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
Click to expand...
Click to collapse
I haven't been able to get my sim card to be detected, is this a known issue or am I missing something?
Download your stock rom and flash radio.img to restore cell signal
svoc said:
Download your stock rom and flash radio.img to restore cell signal
Click to expand...
Click to collapse
Thanks for the tip! I knew I was missing a detail.
WolfHunter16 said:
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
Click to expand...
Click to collapse
It works! This has been kicking my butt left right and sideways for weeks but this worked. Thanks!
WolfHunter16 said:
You can use a Treble system Image! <See below for files>
To flash,
Step #1: Use the treble info app to see if your phone supports treble (Optional, I know the moto g play 2021 is compatible)
Step #2: Download any treble OS from here: https://github.com/phhusson/treble_experimentations/releases/ (Or use files below)
Step #3: Download 15-second adb installer (I Prefer this because its fast than searching for drivers) Download Here: https://androiddatahost.com/wp-content/uploads/15_Second_ADB_Installer_v1.3.0.zip
Step #3.5: I assume you enabled oem unlock and bootloader, but if not, instructions are below
Step #4: Unlock your bootloader
(Step #1: Enable OEM by going to about phone and tap build number 7 times (I'm sure you know the rest )
Step #2 Hold Vol down, (While holding Vol down) connect to PC.
Step #3: Go to https://accounts.motorola.com/ssoauth/login?TARGET=https://motorola-global-portal.custhelp.com/cc/cas/sso/redirect/standalone/bootloader/unlock-your-device-b
Sign into google or moto id, and follow steps to get unlock code (For bootloader unlock))
WARNING!! DATA ON DEVICE IS GONE!! WARANTY NOW VOID!!
Step #5: Run the command in CMD (as admin): adb devices (Starts ADB service)
Then run: fastboot devices (Your device should be connected)
Then run: fastboot oem unlock <unlock code here> (From website provided)
Then: You should get a message saying: Warning Blah Blah Blah. Just read the message
DONE! (Should reboot to factory settings)
Step #6: Turn device off, then hold Vol down, and connect to PC
Step #1: Make sure to have put the <imagename>.img you downloaded earlier in the adb folder in your windows local disk (and renamed it to "system.img" to make flashing easier)
Step #7: Reboot to fastbootd by running: "fastboot reboot fastboot" in CMD
Then run: fastboot erase system
Then: fastboot flash system system.img (Might get error message!) (To fix, run "fastboot delete-logical-partition product_a" Then run "fastboot flash system system.img" again)
Then wait. . .
After, run "fastboot -w"
Then: "fastboot reboot"
DONE!!!!!! Enjoy
Files Below!!!
Click to expand...
Click to collapse
Each time I try this I get to 6/7 flashing system_a and then it says operation not permitted... banging my head against the wall here.
sending sparse 'system_a' 5/7 (262084 KB)...
OKAY [ 7.256s]
writing 'system_a' 5/7...
OKAY [ 3.463s]
sending sparse 'system_a' 6/7 (262124 KB)...
OKAY [ 7.248s]
writing 'system_a' 6/7...
FAILED (remote: Operation not permitted)
finished. total time: 61.098s
Any ideas?
Edit: I'm in fastbootd mode but delete-logical-partition still doesn't work.
stoag said:
Each time I try this I get to 6/7 flashing system_a and then it says operation not permitted... banging my head against the wall here.
sending sparse 'system_a' 5/7 (262084 KB)...
OKAY [ 7.256s]
writing 'system_a' 5/7...
OKAY [ 3.463s]
sending sparse 'system_a' 6/7 (262124 KB)...
OKAY [ 7.248s]
writing 'system_a' 6/7...
FAILED (remote: Operation not permitted)
finished. total time: 61.098s
Any ideas?
Edit: I'm in fastbootd mode but delete-logical-partition still doesn't work.
Click to expand...
Click to collapse
Make sure you have the current version of fastboot, AND that it's the one that you're using. Ran into that problem mysself, updated my PATH incorrectly and had it pointing to the wrong fastboot.exe.
So my buddy has a Moto E7 that randomly started crashing and then got stuck in Fastboot mode. I tried LMSA and it won't detect the phone. I have tried manually flashing, RSDlite, followed a video to turn the XML file into a bat file, and it won't let me flash anything. I've spent hours googling different methods and even looking on these forums at other devices and following those steps and have had no luck. The phone is oem locked, when I use the command fastboot getvar all almost every field is blank. The ones that aren't are just the information about the components inside and serial number. Values like imei are blank, but I have the number. When I try a command like fastboot flash logo logo.bin I get:
Sending 'logo_a' (1292 KB) OKAY [ 0.034s]
Writing 'logo_a' (bootloader) Failed to erase partition
as a response. This is the same response I get for every situation of trying to flash something and when I try to erase I get met with:
\fastboot erase userdata
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
What am I missing? I just get a failed response from everything. I'm guessing the internal storage isn't formatted but I can't find a solution to format it from this state, and like most things I've search it gives me what to do when I can access the phone but not what to do when the phone is stuck here.
if the bootloader is not unlocked you can't flash a rom via fastboot...
Korokyblin said:
So my buddy has a Moto E7 that randomly started crashing and then got stuck in Fastboot mode. I tried LMSA and it won't detect the phone. I have tried manually flashing, RSDlite, followed a video to turn the XML file into a bat file, and it won't let me flash anything. I've spent hours googling different methods and even looking on these forums at other devices and following those steps and have had no luck. The phone is oem locked, when I use the command fastboot getvar all almost every field is blank. The ones that aren't are just the information about the components inside and serial number. Values like imei are blank, but I have the number. When I try a command like fastboot flash logo logo.bin I get:
Sending 'logo_a' (1292 KB) OKAY [ 0.034s]
Writing 'logo_a' (bootloader) Failed to erase partition
as a response. This is the same response I get for every situation of trying to flash something and when I try to erase I get met with:
\fastboot erase userdata
Erasing 'userdata' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
What am I missing? I just get a failed response from everything. I'm guessing the internal storage isn't formatted but I can't find a solution to format it from this state, and like most things I've search it gives me what to do when I can access the phone but not what to do when the phone is stuck here.
Click to expand...
Click to collapse
Hi, Have you already tried flashing using SP FlashTool?
Check the version of FlashTool and the ROM that LMSA downloads are correct.
In theory you should be able to flash the ROM without unlocking the bootleader. ^^'
FlashTool must be set to "Download Only" or "Firmware-Update"
"Format and flash", or something similar, delete the IMEI, which I would not want.
Hello there,
A newbie here, trying to unlock a TCL 20B (6159K) phone.
Android 11, November 2021 security patch (MTK Easy Su doesn't work with that, reportedly some vulnerability was patched), fastboot accessible but acting weird.
1. Got fastboot from here.
For some reason it doesn't understand the -i option, but connects with the only phone I'm trying to unlock attached anyway.
VID is 0x0e8d, btw.
2. Got adb from don't remember where about a year ago (for my previous Lenovo phone)
3. Unlocked the Developer Options
4. Checked "Allow bootloader unlock" and "Enable USB debugging" options there (not sure how those are named exactly in English, but I 100% guarantee, I've checked the right ones)
5. Sent phone into fastboot with
Code:
adb boot bootloader
6. Checked the unlockability with
Bash:
fastboot flashing get_unlock_ability
(bootloader) unlock_ability = 16777216
OKAY [ 0.005s]
Finished. Total time: 0.006s
7. Tried to unlock the thing, but
Code:
fastboot flashing unlock
FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
and
Code:
fastboot flashing unlock_critical
FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
8. Searching here, on XDA forums revealed there's no TCL 20B sub-form.
9. While there are tons of topics on not allowed in locked state, none of those helps.
fastboot oem unlock is seemingly an old way to do things (TCL 20B is a rather new device released WAY past 2015)
TCL is an Alcatel device, not a Xiaomi or some ZUK one, to require an account (haven't found anthing on "alcatel account")
trying to load some recovery from PC that might work failed as well (for the same reason)
Code:
[/LIST]
./fastboot boot twrp-3.6.1.img
Sending 'boot.img' (8932 KB) OKAY [ 0.212s]
Booting FAILED (remote: 'not allowed in locked state')
fastboot: error: Command failed
I've read some TCL 10 phones don't even have a fastboot, but TCL 20B clearly does.
Any Ideas how to unlock the bootloader?
P.S. Maybe a new sub forum for 20B? This got placed into the "TCL 20 5G" one, which doesn't seem right.
EDIT:
Ok, have found how to proceed on my own.
Even rooted the thing.
Go here https://github.com/bkerler/mtkclient, grab the ISO, backup, install patched magisk, patch the boot_a, flash patched boot_a and empty vbmeta_a, erase metadata, userdata and md_udc. Reboot, reinstall pathched magisk.
Don't lock the bootloader to avoid red state.
Huge kudos to mtkclient devs
Hello, i been trying to root my tcl 20b (6159a) but i cant figure how, i follow the instructions of mtkclient. Install it in windows, python, mtk repository, all the process, but when i try to replace boot_a.img it doesnt work from the cmd command, but in the python mtk_gui i can replace boot_a.bin and erase vbmeta_a.bin when i do it from there the cellphone keep in bootloop, i can fix the bootloop but cant root it. If u read this, can you plz be more specific with the steps, and made a little tutorial, its not necessary images or video just some more in deep info how you achieve root, thx