I had EliteTWRP 3.2.1-0 and restored the official rom from twrp recovery but it was stuck when trying to first-time configure the phone(it wouldn't get past the wifi setup). So I went into twrp to try and format everything and try to flash a different ROM and I faced another problem. Internal storage couldn't be mounted. I wanted to fix that by flashing the twrp 3.1.1 because that worked for me before. I got in the fastboot mode but it said that the phone is locked. That was strange to me so I tried unlocking the bootloader with "fastboot oem unlock [my unlock code]". The prompt came on screen asking me if i wanted to unlock boot loader and factory reset and I said yes. Then my phone restarted and is stuck on "Your device has been unlocked and cant be trusted. ...mod=restore page... Your device is booting now...". From that point it's stuck on that screen and I can't get into the recovery or fastboot mode. I tried the dload method(holding volume up volume down and power button) but that did nothing.
Please help.
So i wanted to finally install custom ROM on my LG G6 H870, needed twrp... obv, followed all the instructions:
adb devices - showed my device all was good
2nd: adb reboot bootloader
3rd: fastboot flash recovery twrp.img
4th: fastboot reboot + holding volume down and power button, on logo released power button and pressed it down again, finally got to factory data reset 2 YES options and saw the Teamwin bootup logo, but then phone just booted up normally...
5th: Tried to open recovery once more, but then it did regular Data erease.
What could be wrong?
Razexay said:
So i wanted to finally install custom ROM on my LG G6 H870, needed twrp... obv, followed all the instructions:
adb devices - showed my device all was good
2nd: adb reboot bootloader
3rd: fastboot flash recovery twrp.img
4th: fastboot reboot + holding volume down and power button, on logo released power button and pressed it down again, finally got to factory data reset 2 YES options and saw the Teamwin bootup logo, but then phone just booted up normally...
5th: Tried to open recovery once more, but then it did regular Data erease.
What could be wrong?
Click to expand...
Click to collapse
Which TWRP did you flash ? Bootloader unlocked ?
Razexay said:
So i wanted to finally install custom ROM on my LG G6 H870, needed twrp... obv, followed all the instructions:
adb devices - showed my device all was good
2nd: adb reboot bootloader
3rd: fastboot flash recovery twrp.img
4th: fastboot reboot + holding volume down and power button, on logo released power button and pressed it down again, finally got to factory data reset 2 YES options and saw the Teamwin bootup logo, but then phone just booted up normally...
5th: Tried to open recovery once more, but then it did regular Data erease.
What could be wrong?
Click to expand...
Click to collapse
I had exactly same problem when I did this = only Teamwin bootup logo and then boot into android (I hope your bootloader is unlocked first).
Solution was you have to use TWRP 3.1.1-0 and u get into recovery. I tried more versions of TWRP (3.2.1-0 , 3.2.2-0 , 3.2.3-0) but ONLY 3.1.1-0 works and I dont know why.
Anyway I got another issue after because I didn't want to install root yet (first I wanted to backup).
An issue was I got into restarting loop by installing no-verity-opt-encrypt 6.0 which should be a solution for boot into android without losing TWRP (considering to one walkthrough I found).
I was lost for a while but I found a solution = install another boot.img (in my case I installed one dm-verity or dm-verity & forceencrypt zip file - btw what is a difference between them?).
Oh wow.. Well thanks, ill try your solution as soon as i get time. Bootloader is unlocked indeed, used latest twrp. I'll try 3.1.1-0.
@ Razexay
that happened to me also with Official TWRP take that from Eliminater74 that's where backup and encryption work with dm-verity & forceencrypt look here in the forum everything is well described
https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
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.
I used TWRP to flash official lineage os 16, it was working fine but a new update came and it booted directly into recovery to install firmware. It could not install it . I was stuck in recovery. when I flashed my backup of lineage os it indicated some error saying /system not found. I then searched over and run some command in unlocked bootloader fastboot to fix it. I found a thread on xda to fix system error in TWRP and run cmd "fastboot erase system "also erased boot and recovery then clean installed boot and recovery but my bootloader was gone.
Now it's stuck at powered by android only and with no asus logo. I used asus flash tool with raw image file
to get into stock rom but failed.
THE UNLOCKED BOOT LOADER IS LOST
when I press volume up and power key the system bootloader comes but the deafult bootloader and the unlocked screen message is not showing.
and when i press only the power button there is no asus logo the phone is stuck at screen saying "Powered by android"
please help !!
Please HELP
I am writing here the whole story.
I unlocked the bootloader of my Asus zenfone max m1 (3/32GB) using the unlock tool which I downloaded from Asus's website.
Then, I went to fastboot mode and flashed TWRP recovery and then tried booting into it through the cmd screen using fastboot boot twrp.img command and it worked.
Then I followed a really good tutorial and flashed the pie firmware, Pixel Experience and magisk and ZIPs in order.
And it showed no error, everything was fine and then I clicked on the reboot system button, it rebooted the system but the phone was stuck at the google logo with a loading bar and didn't go beyond that even when left for 30 mins and I tried rebooting the phone multiple times and that did not help. the phone was stuck at the google logo every time.
Then I turned off the phone and tried going to TWRP to flash the pixel rom again but the phone only went into fastboot mode, it never booted into recovery even though I tried multiple times(I was trying to boot into the recovery through the volume and power buttons, not through fastboot mode).
I flashed the phone's recovery multiple times and also the boot image (I even tried flashing the stock recovery) but the problem is that everything goes fine in the terminal, it shows that it flashed the img file successfully and it is finished but the commands like fastboot reboot recovery don't work at all, they all just reboot the phone normally and the phone just shows the ASUS logo for few secs and then turns off.
Note: I used fastboot erase commands to remove the pixel experience rom and now I'm only left with a phone which boots only into fastboot with no rom and I don't know about the recovery because it shows that it flashed but it never opens.
Hi
I am having a similar problem in that I can oly get into recovery mode with adb reboot recovery. I researched and tried all possibilities with the phone key but I can only go into bootloader mode.
After flashing recovery successfully (?) I can only boot the phone normally and that seems to reinstall the default recovery manager.
While researching I found that there are some discrepancies with the ID out there. While my phone is a Zenfone Max (M1) with the ID X00PD some places (TWRP) confirm that but others refer to Z555KL.
Did you get any further?