Database Users

Bricked MX4 ... Bootloop with no recovery image

So guys I guess I have tried all I know to get my device back to life after it has bricked while I was trying to flash the TWRP.
situation is like this MX4 international version with Flyme (Unrooted).
I am now have the device in boot loop for the past week with no end.
I have no recovery image so nothing happen when Volume UP + Power.
when I go to fastboot mode I have no devices in ( adb devices ) command..... but I do have the device listed using ( fastboot devices ) command.
I tried : fastboot flash recovery recovery.img using all kind of images original and twrp and patched with the same result ( Security Deny error 2017)
I tried : fastboot update update.zip using flyme or even Cm12.1 and in both cases I get error: update package has no android-info.txt or android-product.txt ... I have tried pushing missing files into the zip file but at the end of the day I got again : FAILED (remote: not support on security).
tried erase and again security deny as well.
tried to unlock the bootloader by the well known command : fastboot oem unlock .. unfortunately FAILED (remote: unknown command).
it would be great if someone tell me I can get my device back to life... I am searching for a solution for a week now with no luck.

Bricked. Go to the customer service. You can't do nothing...

SOLVED[ALE-21 rooted] Only able to access eRecovery and Fastboot when cable connected

EDIT: Issue has been resolved
I managed to get the bootloader unlocked and root the phone before. But then i got a bit carried away and installed adAway incorrectly. Which got me into a bootloop.
I freaked out, and i ended up messing things up even further by trying to restore the phone.
I did perform a backup in TWRP. But this backup did not help at all.
Then i tried using fastboot to relock the bootloader. The reason for this would be so that i could use the eRecovery.
That did not work.
I have used both Minimal ADB and P8lite Multitool.
None of these tools detect my phone unless i put it into fastboot manually.
If i try to reboot through the tools, it will reboot, but only to the Huawei logo and stay there.
I have been able to flash the very latest rom from Sokkoban http://forum.xda-developers.com/p8lite/general/rom-emui-4-0-android-6-0-ale-t3505108
(thank you by the way for all the hard work)
But when i try to relock (with update.app in the dload folder) i keep getting errors.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb.exe reboot recovery
error: no devices/emulators found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem lock XXXXXXXXXXXX
< waiting for any device >
...
FAILED (remote: Command not allowed)
finished. total time: 0.019s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem relock XXXXXXXXXXXXX
...
FAILED (remote: root type is risk)
finished. total time: 0.901s
Click to expand...
Click to collapse
My stock buildnumber is (was?) ALE-L21C432B574. I still haven't found the proper stock rom.
I can see 2 IMEI numbers, so i guess this is a dual sim?
I have already got the phone replaced once. I don't know if i would be so lucky as to have it replaced once again, even though it is under warranty. Well technically it isn't. Nor was the other one.
I just wish to have this paperweight back in working order again.
TL;DR:
Power + Volume down = Fastboot
Power + Volume up = Nothing.
Volume up when in Fastboot = eRecovery. eRecovery will not download anything as the phone is rooted.
Reboot = Stuck in Huaweilogo.
Phone is not detected by HiSuite.
Edit: I did manage to find the stock rom (i think)
http://www.carbontesla.com/2016/07/download-huawei-p8-lite-b574-full-marshmallow-firmware-europe/
And i am back in business. The phone is no longer a brick, but it is not rooted.

brickwd nova?

i did all ok for some weeks. But one day phone was discharged and after charge i got a black screen. Sometimes it flashes a bit depending on the boot and i can get some sound if i push volume down or up.
i tried fastboot or adb but no devices. (how can i force connection?). I went to the huawei shop they somehow restarted it and i could the the different booting option but they reboot it and they told me they couldn t do anything about because of the rom. I asked to redo what they have done and leave it to the reboot option so i could probably manage it from this point, but they told me it was not possible. So back home i tried everything but no success. How do i force the reboot from my computer with which softs?
tks
update
i do
adb devices
List of devices attached
GGXDU1721001169 recovery
if i do adb reboot-bootloader
i still have black screen
and fastboot devices gives
no permissions f astboot
how can i grant permission?
what command should i use? i tried a recovery but didn t work either think i t is an permission issue
tks

update
so i did
$ sudo fastboot devices
[sudo] password for xxxx:
GGXDU1721001169 fastboot
[email protected] ~ $ cd Downloads
[email protected] ~/Downloads $ sudo fastboot devices
GGXDU17210001169 fastboot
[email protected] ~/Downloads $ sudo fastboot flash recovery recovery.img
target reported max download size of 532676608 bytes
sending 'recovery' (34228 KB)...
OKAY [ 0.848s]
writing 'recovery'...
OKAY [ 0.785s]
finished. total time
[email protected] ~/Downloads $ sudo fastboot reboot
rebooting...
finished. total time: 0.053s
and still black screen?????
is it hardware issue?
is it possible somehow to reinstall a rom but usting the computer?

yes you can like you have flashed recovery, do the same thing with boot.img and system.img
extract them with update extracter from the full rom

Same with my CAZ-AL10, I guess it's because of missing drivers(*.so)

zaabolla said:
yes you can like you have flashed recovery, do the same thing with boot.img and system.img
extract them with update extracter from the full rom
Click to expand...
Click to collapse
ｔｋｓ
sorry i m not clear about the method. do i use the same recovery img? from this image i extract the boot ant the system img? and once i use fasboot? same commands?
tks

fastboot flash (system system.img) (boot boot.img)
Yes, extract from the same file you got the recovery from.

if your Nova be supported by fast boot command so it can be fix. don't worry. just find the correct rec , boot , system ...
my Nova l11 bricked like u before , i try many many method ... and help by mod hen.... in 2 day ... done ... everything alrigth ... now i can change 2 rom stock , LOS 14 so easy ....
good luck bro .

do you use image extractor? it seems it only use update image, or do you use another soft to extract it?
tks

Is there a way to wipe or reset TWRP from fast boot. i m also trying to see where the error comes from. how can i see the logs with my computer?
tks

If you want to get rid of twrp then flash stock recovery.img in fastboot.

babysocola1x said:
if your Nova be supported by fast boot command so it can be fix. don't worry. just find the correct rec , boot , system ...
my Nova l11 bricked like u before , i try many many method ... and help by mod hen.... in 2 day ... done ... everything alrigth ... now i can change 2 rom stock , LOS 14 so easy ....
good luck bro .
Click to expand...
Click to collapse
bro my nova l11 bricked update installing stuck at 5% fastboot mode status is phone locked can you please guide me to unbrick my phone?

abuapka said:
bro my nova l11 bricked update installing stuck at 5% fastboot mode status is phone locked can you please guide me to unbrick my phone?
Click to expand...
Click to collapse
1st get unlock code from huawei site for your phone
( need serial number..., find them)
Second, find the appropriate firmware for your model
Third extract update.app with huawei update extractor
Now you will have boot.img, recovery.img and system.img
In fastboot mode unlock the bootloader with your code
Then flash each file with it's fastboot command

i
zaabolla said:
1st get unlock code from huawei site for your phone
( need serial number..., find them)
Second, find the appropriate firmware for your model
Third extract update.app with huawei update extractor
Now you will have boot.img, recovery.img and system.img
In fastboot mode unlock the bootloader with your code
Then flash each file with it's fastboot command
Click to expand...
Click to collapse
where can i use the code? because on fastboot mode there is no option except
phone locked
and second connect hisuit using usb cable etc.
but when i try to connect hisuit with usb phone didnt recognized by hisuit in laptop
one more thing when i connect my phonr with dsta cable on fastboot mode adb devices didnt show any device jyst because i didnt enable usb debugging in developer mode because my phone is new i didnt change anything just try to update using firmware finder app and stuck on 5% cant even start my phone its stuck on bootloop i can go to fastboot mode recovery mode. also try to update using sd card but didnt work kindly guide me

Question Nothing Phone 1 hangs in bootloader/fastboot mode. Not rooted and bootloader unlocked. bricked

Hello,
I have a Nothing Phone 1 that hangs in bootloader/fastboot mode.
The bootloader is unlocked.
Unfortunately, the phone can no longer be booted into recovery mode.
With fastboot the device is still recognized.
So you could still flash files via fastboot.
The phone was not rooted.
The phone previously ran with the original stock firmware 1.1.7 hotfix.
It is an EEA device.
Is there anything that can be done?
Or is it now an expensive paperweight?

Try running "fastboot reboot recovery" in the terminal with your phone connected.

Unfortunately this does not work.
Thanks for the quick reply.

The device then boots back into the bootloader

It looks like they have Nothing OS downloads here. You could just try reflashing the phone through fastboot.

Looks like someone else is having the same problem. Keep an eye on that thread in case a solution comes up there.

so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').
After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).
Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.

Sapphire86 said:
so, i have the unpacked payload.bin image files. Here fastboot tells me several errors with odm.img FAILED (remote: '(odm_b) No such partition'), with product.img FAILED (remote: 'Partition not found'), with system.img FAILED (remote: 'Partition not found'), with system_ext.img FAILED (remote: '(system_ext_b) No such partition') and with vendor.img FAILED (remote: 'Partition not found').
After a restart, the error remains.
There is also the fastbootD mode, but this does not work or does not boot.
After this command the device hangs in bootlogo (nothing).
Unfortunately very sad that there is still no solution for this. let's hope that there is soon a solution for this.
Click to expand...
Click to collapse
Type "fastboot reboot fastboot" in the terminal, with your phone connected, and then run "fastboot flash <yourimagename>.img".

yes, when i enter this command the device restarts and hangs in the bootlogo and in the terminal it says then wait for any device. That means the Nothing Phone does not start the fastbootD mode.

And if he doesn't do this, I think it looks really bad.

Are you using Windows to flash it?

Yes windows 11 with the latest drivers, but I have already considered using linux.

Which linux distribution would be best. Then I will download it and try it out.

I would recommend Ubuntu, if you have a spare computer to install it on (or dual boot). Just make sure you install the tools needed from here (Scroll down to the "Command line tools only" section and download the Linux version)
I only use Linux, so let me know if you have any questions.

Ok thanks. I will have a look and install it on a notebook later.

You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)

ziptric1805 said:
You have to be very careful. I had the same problem (bootloop in fastboot) and by dint of manipulation, no more fastboot, my smartphone is hard brick (black screen with logo and message key to shutdown)
Click to expand...
Click to collapse
If your phone has a Qualcomm processor, you still have EDL mode.

It is not bricked. Just flash any cutom rom, I recommend Paranoid Android. Then revert back to stock NOS.

@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?

Ostry10 said:
@MakDroid
I just installed Topaz 1 (A13) to save my bricked phone. How can i revert back to stock NOS from A13? There is any option or i have to wait for full rom with A13?
Click to expand...
Click to collapse
Download NOS 1.1.7 full from here.
Extract payload.bin and place all the extracted .img files inside a folder named "images".
Copy the images folder and the attached bat file (extract the zip to get the bat file) to the platform-tools folder.
Run the bat file and it will start flashing. Wait for it to complete and then simply update to latest version using stock updater.

[HELP] Z00TD/ZE551KL soft-bricked? No recovery mode, no OS, locked bootloader.

Hey guys, I need help with this Asus Zenfone 2 Laser that:
Cannot boot to any OS (asus logo pops up, freezes, and then a blue screen flashes for a really short period, before it powers off, see video here.)
Can't download the unlock app to unlock bootloader
Can't access ADB
Cannot access Recovery mode
Can't "factory reset", apply update over ADB, etc.
Bootloader is locked
Can't flash custom recovery, boot TWRP, or really anything...
See fastboot reference below for more info
Code:
$ fastboot boot twrp-3.7.0_9-0-Z00T.img
Sending 'boot.img' (31066 KB) OKAY [ 0.987s]
Booting FAILED (remote: 'unlock device to use this command')
fastboot: error: Command failed
$ fastboot flash recovery twrp-3.7.0_9-0-Z00T.img
Sending 'recovery' (31066 KB) OKAY [ 0.987s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flash boot boot.img # (Original boot.img from factory image)
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 17980722).
Sending 'boot' (17559 KB) OKAY [ 1.478s]
Writing 'boot' FAILED (remote: 'Permission denied, phone is protected')
fastboot: error: Command failed
$ fastboot flashing unlock
FAILED (remote: 'unknown command')
fastboot: error: Command failed
$ fastboot oem device-info
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.003s]
Finished. Total time: 0.003s
As someone who has only worked with Google Pixel phones in the past, I'm very frustrated for a few reasons.
Firstly, why the hell is the ONLY WAY to unlock a bootloader through an app that was released in such a clandestine, under-the-table way?
Second, why is the manufacturer gatekeeping the recovery files? The only way I was able to find the stock recovery.img is through a comment on a Reddit post (ironically posted by an ASUS Employee).
Third, I've been scouring the internet for many, many days trying to find any kind of emergency recovery method, but every single tutorial acts on the assumption that the bootloader is unlocked, and that boot.img, recovery.img, etc. can be flashed.
Enough about the frustration. Now let's talk about what I've tried so far.
I tried ASUS Flash Tool (Finding ADB drivers was a whole different fiasco for this device), and came up empty handed, as it doesn't detect the device when in fastboot mode.
I tried using fastboot to flash boot, recovery, system, fastboot, and dnx/ifwi, to no avail.
I tried booting into recovery via `fastboot reboot recovery`, `fastboot reboot-recovery`, `fastboot oem reboot-recovery`, and by holding Vol Down while booting up. They all give the same result, which is just an instant (<1 second) reboot. My best guess is that recovery.img is either missing or badly corrupt, so the bootloader just gives up and exits immediately.
Please help. I don't want an expensive paperweight sitting in my drawer just because of a bootloop that wasn't my fault (seriously this device just bootlooped itself one day, I didn't flash a custom rom, root or anything like that).
Any help is appreciated,
Thanks in advance

you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417

alecxs said:
you can flash on locked bootloader in EDL mode. search in the forum, don't hesitate to ask for clarity on search results. I give you a starting point.
(don't read the whole thread, it will only confuse you)
https://forum.xda-developers.com/t/...image-dump-file-raw-bin.4543217/post-88139417
Click to expand...
Click to collapse
Probably a dumb question, but how can I put my device into EDL mode?
I've tried many key combinations in conjunction with plugging it into the computer, and I've tried connecting it without a battery.

if nothing else works you need to figure out test points
https://forum.xda-developers.com/t/...ed-to-unlock-bootloader.4531349/post-87944673

you still have fastboot? try this for EDL mode.
Code:
fastboot oem enter-dload

Good news and bad news. Good news is: I was able to enter EDL mode.
Bad news is, apparently my entire partition scheme was messed up, and upon running "edl w gpt gptboth0.bin", fastboot no longer works.
I have tried flashing aboot using edl ("edl w aboot emmc_appsboot.mbn") and it's not working.
Not to mention that it is almost impossible to find the firmware file with all the factory files such as "emmc_appsboot.mbn". The place where I got my file seemed very sketchy and I'm not surprised if the reason it's not working is because it's the wrong file.
Once again, this is a result of ASUS gatekeeping their recovery files to service centers to drive up repair sales.
If anyone has a link, or would like to provide a donor file, it would be VERY much appreciated.

what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios

alecxs said:
what is inside official download?
https://www.asus.com/supportonly/asus zenfone 2 laser (ze551kl)/helpdesk_bios
Click to expand...
Click to collapse
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...

OS were
sj-dan said:
So yes, I was able to get fastboot back. However, I am now facing another issue.
In order to get fastboot back, I had to run this command
Bash:
edl qfil rawprogram0.xml patch0.xml image_dir
This seemed fine at first, but now, running "edl printgpt" returns nothing. Somehow, the phone is able to boot to fastboot without any GPT partitions visible.
However, when I try to flash gpt_main0, or gpt_both0, the phone now becomes unbootable.
This means, if I try to create a partition table to flash recovery onto, appsboot (and by extension, fastboot) no longer works.
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (18115 KB) OKAY [ 0.581s]
Writing 'recovery' FAILED (remote: 'partition table doesn't exist')
fastboot: error: Command failed
"partition table doesn't exist"
If I try to create the partition table, the phone refuses to boot...
Click to expand...
Click to collapse
So we're you able to find a fix in any way? I find myself in just about the same situation tho for different reasons. I have a radiant max 5g att device i moronicaly tried to download a gsi using the dsu updater, but forgot to unlock bootloader or even enable USB debugging before attempt. So OS system is crashing an saying 'device corrupted' on boot attempt. Recovery mode gets the same result. Was able to use the bugjaegar app to connect ad run the bootloader but every repair attempt is blocked by the fact the USB debugging isn't on. To make matters worse I accidentky hit boot fastbootd command instead of normal and whatever that did wiped out my ability to even connect with bootloader so I'm kind of stuck.

faisaliteb said:
Mod. edit: spammer gone. alecxs
I found many tutorials about fixing bootloops on the Nexus but they all seem to require an unlocked bootloader.
The bootloader on the device is locked. I can see the device in fastboot devices but I can't unlock it.
Any idea how to repair this? Can I somehow flash a factory image onto the device even though OEM unlock is disabled? There is no data on the device that would need to be preserved. I'm ideally looking for a Linux-based solution. more info... ***
Click to expand...
Click to collapse
Yeah man I've been looking at this problem for over a week now and can't find much online at all to help. Except for this EDLmode some devices can boot into, and apparently you can flash a locked system using this emergency download mode. I dunno still researching.