Hi guys,
So I have made the mistake of relocking the bootloader after unlocking it. Now my phone is bricked, and the bootloader is locked.
I have downloaded the stock rom XT1524_RETEUALL_MOTOE2(4G-LTE)_5.0.2_LXI22.50-13_cid7_subsidy-DEFAULT_CFC.xml, the cid and product reference are matching, also my phone was on 5.0.2.
But my phone won't flash, for example, I get :
"C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system system.img_sparsechunk.3
target reported max download size of 268435456 bytes
sending 'system' (254911 KB)...
OKAY [ 8.012s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 8.072s"
when I input some of the commands for flashing.
My bootloader logs show :
"failed to validate system image"
I don't understand why it would be doing that as the stock is matching, I have checked on several threads and I can't find any concrete solution for fixing this.
Please help.
Thanks,
No one has a clue ?
Having the same prolem with my XT1521 please somebody helppppppppppp
up..
try to use mfastboot, its included in my modem flash zip (https://mega.nz/#!pglHWQ6B!zYNHtO9qERuFqrbv40M62kgpULS2TK53m_vB3msCC6g ), Windows only.
also there is a guide here: http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3044936
and flash in order as shown in the guide
Is Your Fastboot working or your phone completely bricked ?
Hi Gentlemen,
Thanks for the replies.
Sorry, all the above I've tried with mfastboot. It just won't flash it. Probably cause the phone is locked now.
The above is what it's returning.
Also I cannot unlock the phone anymore, it returns "FAILED (remote failure)"
"Check 'Allow OEM unlock' in Developper options"
Mine its also bricked, same situation, same problems :c
A couple of days ago, I got an error on my phone (Motorola XT1033) saying that it cannot load the home screen. So, I restarted it in order to resolve the issue. However, it didn't reboot and since then it has been stuck in the Motorola logo.
I tried to do recovery or factory reset, but all the options lead to the same Motorola logo with no luck.
The only option that is working is AP Fastboot. I managed to unlock the bootloader by getting an unlock code from Motorola's website and using the mfastboot command. So I assume that the fastboot command is working since it detects the devices; however, I couldn't make ADB command to work since it give the error: 'device not found'.
Anyway, the second step is to flash the phone. According to this question, I should be able to do that. However, when I am running the command fastboot flash partition gpt.bin, I am getting the following result:
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32 KB)...
OKAY [ 0.022s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.154s
I have been searching for days to solve this problem, but nothing yet! I don't know which part I am doing wrong.
I have been trying for the past few days to try to recover my CMR-W09(C00) device with no luck.
What it looks like now?
At the moment there is nothing showing on the screen regardless of what button combinations I've tried (Vol Up+Vol Down+Pwr/Vol Up + Pwr/Vol Down + Pwr, and each with USB power cable plugged in and without). The phone is able to get into fastboot mode (detected by running fastboot devices) automatically, fastboot reboot would get it to fastboot again (i.e., doesn't go to any other mode). The screen is completely dark with nothing at all.
From fastboot I can even see the current firmware version is 195. (CMR-W09C00B195 (8.0.0.195))
What did I do?
Flashed the 160 (CMR-W09C00E160R1P160B160 (9.0.1.160)) firmware which I found on firmware finder, and used EMUI Flasher to flash the firmware. (Found here: https://forum.xda-developers.com/mate-20-pro/how-to/guide-manual-updating-firmware-t3893171) Flash seems to have worked and at 100% it said something along the line of checksum failed, rebooted, and never came back to life again.
What I have tried?
1. No eRecovery (that would be easy)
2. Use HiSuite to repair devices, received unsupported device error.
3. Flashed recovery-ramdis, recovery-vbmeta and recovery-vendor and ramdisk that were extracted from 195 OTA (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v225819/f1/full/update.zip) and 160 OTA(http://update.hicloud.com:8180/TDS/data/files/p3/s15/G3776/g1699/v234512/f1/full/update.zip). Nothing happened. In Fastboot I can flash these three partitions and system, anything else would return command not allowed.
4. Tried DC Unlocker, when flashing xloader I got command not allowed error, in the end DC Unlocker refunded me.
5. Tried dload method with UPDATE.APP in dload folder only as well as the entire contents (META-INF/tags files and mbn files together with UPDATE.APP) in dload file, reboot using three button combo
6. In desperation I even tried to buy some "factory flash" image which was supposedly to be used by Huawei repair centres internally (with two zip files) to extract to dload folder. Again didn't do anything.
7. Tried to contacted FH to see if they support unbricking this and didn't hear a response.
8. Went to local Huawei authorized repair centre and they don't seem to have seen this device. They told me they can only fix devices bought locally.
9. Tried to flash in TWRP by flash the recovery_ramdisk partition.
All of above leads to nothing (i.e., it goes back to the blank screen with fastboot, however I can hear the USB connected and disconnected sound and HiSuite popped up again which tells me the reboot actually took place).
Some output from fastboot command:
E:\Android\M5>fastboot devices
HYY6R189********** fastboot
E:\Android\M5>fastboot oem get-product-model
...
(bootloader) CMR-W09
OKAY [ 0.013s]
finished. total time: 0.013s
E:\Android\M5>fastboot getvar vendorcountry
vendorcountry: all/cn
finished. total time: 0.013s
E:\Android\M5>fastboot oem get-build-number
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.014s]
finished. total time: 0.015s
E:\Android\M5>fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.027s
E:\Android\M5>fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :CMR-W09 8.0.0.195(C00)
OKAY [ 0.015s]
finished. total time: 0.016s
Click to expand...
Click to collapse
I think I am pretty much out of options right now, but if there is anything
Just wondering if there is anything else I haven't tried that I should?
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
thref23 said:
I think "command not allowed" indicates that your bootloader is locked. If I am right about that, you will need to unlock your bootloader again before you flash anything via fastboot.
Click to expand...
Click to collapse
Thanks for your input, I am able to write to recovery_ramdisk, recovery_vbmeta and recovery_vendor, as well as system partitions, however XLOADER and ERECOVERY* and FASTBOOT partitions seems to be out of touch.
Here are some more output from fastboot:
fastboot oem check-rootinfo
...
(bootloader) status : RISK
(bootloader) version : v1.1
(bootloader) current status: SAFE
(bootloader) old status : SAFE
(bootloader) change_time : 0
(bootloader) item: root-prop, status: SAFE, credible: Y
(bootloader) item: setids, status: SAFE, credible: Y
(bootloader) item: verifyboot, status: SAFE, credible: N
(bootloader) item: verity-enable, status: SAFE, credible: Y
(bootloader) item: fblock, status: locked, credible: Y
(bootloader) item: userlock, status: unlocked, credible: Y
OKAY [ 0.031s]
finished. total time: 0.032s
fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.009s
Click to expand...
Click to collapse
Are there multiple lock? What is the fblock? Would unlock that allow me to write to the XLOADER partition?
THE MAXIMUM POWER said:
Download ONLY the Chinese hisuite, it support CMR-W09C00 as i have already checked
consumer.huawei.com/cn/support/hisuite/
Then reconnect the device with your pc, go to system recovery and follow the instructions
The global hisuite support only few devices
Plz report back to me if it worked
This happened to me once in my CMR-W09C432 i stucked in fastboot mode ( black screen) while i was trying to install the emui 9 beta, but i sent it to huawei service centre, they replaced the whole motherboard and i had to unlock the bootloader again.
But first of all do what i wrote above (the chinese hisuite)
Regards
Click to expand...
Click to collapse
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
zhuanyi said:
Thanks for your response, I've tried that and unfortunately it failed at 99% at the step Writing Recovery. (Simply said failed to repair with no other error).
Click to expand...
Click to collapse
Im sorry about that, try to send it to china huawei service as they might repair it their for free because yours is C00
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
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