Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Drunkenmazter said:
Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Click to expand...
Click to collapse
Use one of the less archaic methods:
Download "EDL Tool" from the ROMs, kernels, development section, along with an EDL package that goes with your phone model. Put your phone in EDL and just flash it with that tool. after that, if it still doesn't boot you have to format data, because you might have conflicting data. If you can't do it from EDL Tool (i think you can, don't remember) just enter the recovery with Vol+ and Power and make a factory reset
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
From some other threads, I believe you could try to EDL flash Nougat instead of Oreo, it would work better.
https://forum.xda-developers.com/axon-7/help/help-edl-factory-restore-stuck-device-t4031619
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
xperiaatic said:
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
Click to expand...
Click to collapse
According to other threads, the problem could be due to "sparse" structure while flashing.
I suggest the following:
- Use Axon 7 EDL toolkit to flash latest official TWRP recovery (for Oreo a specific TWRP would be requied).
- Inside TWRP then wipe data/factory reset and at the utmost Format data. Then retry to boot.
- If not OK, reflash with EDL full ROM and try again.
Already done that for several times with O ja N EDL rom's but no luck. Can't get to recovery nor make system to boot.
Did you successful unlocked bootloader?
If not, I would recommended Axon 7 EDL Tool by djkuz, flashing nougat edl package and unlock it through the options.
Can you get into stock recovery after flashing EDL package? It supposed to have a format option for userdata and cache.
Did you try to get into fastboot mode? Power + Vol up buttons if i'm not wrong.
If so, you could try to format these partitions.
fastboot erase /cache
fastboot erase /data
I have experienced the same problem but I have resolved flashing, with Xiaomi MiFlash (sometimes I use this program because occasionally flashing EDL packages with AxonEDLTool, it gives me problems like this) this package Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL.
With this EDL, if the flash is successful, you will find NFound recovery 3.2.1-7 installed with which you can make a complete wipe and / or format them with the file system you prefer.
Afterwards, using MiFlash or EDLTool at your discretion, you can flash the EDL of the original system if you prefer.
I'm not an expert but this has solved my problem.
To unlock the bootloader, if the unlocking with EDLTool does not go well (it happened to me just yesterday while I was installing a Rom on another Axon 7), you can use Axon7ToolKit 1.2.1, it always worked well for me.
I hope it can help :fingers-crossed:.
xperiaatic said:
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
Click to expand...
Click to collapse
Hi, just want to let here my solution for the same problem, it may help others.
I tried to flash A2017G_B10_NOUGAT_FULL_EDL and A2017G_B02_OREO_FULL_EDL but always getting the Can't mount /cache/recovery/last_locale error, phone completely bricked.
So I flashed A2017_B13_FULL_EDL_UNBRICK_DFU using MiFlash through EDL, you can find this here: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 (if your EDL mode works fine there is no need to disassemble the phone as shown in that tutorial)
Now the phone is completely working, recovery and system, but everything in chinese.
Then I flashed A2017G_B02_OREO_FULL_EDL using MiFlash through EDL, and now everything is working and in english
Thanks a lot for the tip! A2017_B13_FULL_EDL_UNBRICK_DFU did the trick and unbrick the phone.
What i did:
1. used MiFlash to flash A2017_B13_FULL_EDL_UNBRICK_DFU
2. after that A2017G_B03_OREO_FULL_EDL
3. reboot to recovery and performed factory reset
First time I did not perform the factory reset and got stuck on the boot picture without the reset function (power button did not work). Drained the battery and performed factory reset and got the phone working again.
update:
Phone is not stable on B03, some apps crashing from time to time for no apparent reason and also soft reboots happening randomly.
Now I got stuck on the Axon boot screen again after rebooting the phone manually and waiting for the battery to drain ...
i did not install or perform any custom action to the system, just regular use and apps, but it is still acting up badly.
I was planning to use this phone as a secondary handset because it is actually a very nice piece of hardware but now i am starting to have second thoughts about that.
A little while ago I downgraded my phone. Today I tried to install magisk with a custom rom and TWRP. It didn't work now when I boot my phone it gets into fastboot I have tried formatting it with TWRP and reinstalling the rom but it doesn't fix it. Are there any solutions (downloading to stock via erecovery doesn't work but I can easily open the erecovery menu.
Fastboot says
Android reboot reason:
bootloader 1
no
NA
reboot_enter_fastboot_common_func
I think there is something wrong with the vendor
Solution:I used the dload trick to download stock firmware
Problem 2:I reinstalled TWRP with a custom rom now my phone keeps restarting and not opening the custom rom.
try this rom
https://forum.xda-developers.com/ma...havoc-os-huawei-honor-hi6250-devices-t3813738
Hi,
I Wanted to Install A Custom ROM Into My Oneplus 5 So I Flashed It Via TWRP Recovery And I Alslo Rooted My Phone To Do So, Then After A Few Days I Was Tired Of My Custom ROM And Wanted To Revert Back To The Orignal, So I Flashed My Orignal ROM To My Device And When I Tried To Relock The Bootloader Through Fastboot. Once Done, My device Refuses To Boot And Displays The Following Message: "Your Device Is Corrupt. It Can't Be Trusted And Will Not Boot".
Then I Got Very Scared And Unlocked The Bootloader Again + Wiped Everything (Including System) + Flashed TWRP Recovery + Flashed (Via TWRP Sideload) a Previous Version Of Oxygen OS And The Booted It Once Again Everything Went Fine And When I Tried Relocking The Bootloader The Device Once Again Started To Show The Same Message Again !!
I Have Lost Every Single Hope Of Recovering My Device Except You Guys.
Any Thought On How I Can Resolve?
Thanks!
SmokinSpectre said:
Hi,
I Wanted to Install A Custom ROM Into My Oneplus 5 So I Flashed It Via TWRP Recovery And I Alslo Rooted My Phone To Do So, Then After A Few Days I Was Tired Of My Custom ROM And Wanted To Revert Back To The Orignal, So I Flashed My Orignal ROM To My Device And When I Tried To Relock The Bootloader Through Fastboot. Once Done, My device Refuses To Boot And Displays The Following Message: "Your Device Is Corrupt. It Can't Be Trusted And Will Not Boot".
Then I Got Very Scared And Unlocked The Bootloader Again + Wiped Everything (Including System) + Flashed TWRP Recovery + Flashed (Via TWRP Sideload) a Previous Version Of Oxygen OS And The Booted It Once Again Everything Went Fine And When I Tried Relocking The Bootloader The Device Once Again Started To Show The Same Message Again !!
I Have Lost Every Single Hope Of Recovering My Device Except You Guys.
Any Thought On How I Can Resolve?
Thanks!
Click to expand...
Click to collapse
Why do you want to relock it? Life is better with Magisk and Blu_Spark in my opinion.
If you want your bootloader to be locked I find it easiest to use the MSM tool (hard brick recovery). It'll wipe your phone but restore it to a like new out of the box condition, just choose a firmware.
Cheers!?
SmokinSpectre said:
Hi,
I Wanted to Install A Custom ROM Into My Oneplus 5 So I Flashed It Via TWRP Recovery And I Alslo Rooted My Phone To Do So, Then After A Few Days I Was Tired Of My Custom ROM And Wanted To Revert Back To The Orignal, So I Flashed My Orignal ROM To My Device And When I Tried To Relock The Bootloader Through Fastboot. Once Done, My device Refuses To Boot And Displays The Following Message: "Your Device Is Corrupt. It Can't Be Trusted And Will Not Boot".
Then I Got Very Scared And Unlocked The Bootloader Again + Wiped Everything (Including System) + Flashed TWRP Recovery + Flashed (Via TWRP Sideload) a Previous Version Of Oxygen OS And The Booted It Once Again Everything Went Fine And When I Tried Relocking The Bootloader The Device Once Again Started To Show The Same Message Again !!
I Have Lost Every Single Hope Of Recovering My Device Except You Guys.
Any Thought On How I Can Resolve?
Thanks!
Click to expand...
Click to collapse
How about you try the MSM Tool to start again from scratch.
Link - https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
.........Once Again Started To Show The Same Message Again !!
I Have Lost Every Single Hope Of Recovering My Device Except You Guys.
Any Thought On How I Can Resolve?
Thanks! [/B][/QUOTE]
Just,read carefully : https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Hello
Sorry for my bad english
a few months ago, i decided to flash my first custom rom (One UI rom) and it worked fine
then i was testing a lot of other roms too until i tried lineage os 20
when i flashed lineage os 20, i decided to try another rom but i was stuck on the twrp logo screen. i tried methods of fixing it but none of them worked.
after trying a method of flashing twrp once again, it failed and i got stuck in a reboot loop and could only boot into download mode. so i booted into download mode and flashed a stock rom.
everything was working fine again until i wanted to try another custom rom. At first whenever i would flash twrp, they would always fail. but later i found the cause of that and fixed it. then, flashing twrp would always pass but my device would get stuck on a reboot loop once again and i had to flash stock rom again.
i tried rooting using auto root but it would show me a verification failed error and i had to reset my device. so now im stuck on a device which cannot flash twrp, nor can it be rooted. its been 1 month and i could not find a viable solution so any help would be extremely appreciated.
You have to just reflash your fastboot rom with fastboot mode unzip it and double click on flash_all.bat file or something like that
it is a samsung, there is no fastboot mode
Hello guys,
I broke my Suez - I need some help.
I went through all the pain of opening up and unbricking it with amonet-suez-v1.1.2.zip from https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/.
Then I was in TWRP, I think 3.2.sth.
I tried to adb sideload the latest lineage for my device from this thread: https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/
The installation finished with a red error message like /data partition not found.
I restarted the tablet, which is now stuck in a lineage os bootloop.
I thought the problem might be not having the most recent TWRP. So I brought the tablet into hacked-fastboot, and flashed TWRP 3.6.1.2, from https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/, which succeeded.
Not I can not even access my recovery anymore. When I try to with volume and pwr, the screen stays black and the tablet resets, ending in the TWRP bootloop.
A) why is the lineage in a bootloop
B) What about the /data partition missing error
C) How to get my TWRP to work again?
I can redo the unbricking stuff, but I would lang in the exact same situation. Where should I try different stuff?
I could think of replacing the old TWRP of amonet-suez with the most recent version, and then do the unbrick procedure with shorting again.
Push. I need help.