Database Users

[SOLVED]Advice on Soft brick

Hi guys,
i ****ed up and need some advice.
I soft-bricked my axon 7.
Situation was as follows.
I had installed AEX Oreo Rom (build from May somewhen) along with the according B10+B32 bootstack and exclusive TWRP 3.2.1.7.
This configuration ran fine. However, i decided that i wanted to upgrade and started to Flash B32 bootstack and TWRP 3.2.1.8 (with treble).
I recognized that this configuration wasnt able to boot the current rom, so i reverted to B10+B32 bootstack and TWRP 3.2.1.7 and make a full backup of current config.
After that, i wanted to Flash newer bootstack and twrp again and continue installing the newest AEX with treble.
HOWEVER i had the greatly stupid idea to Flash DrakenFX's universal Bootloader and modem. The BL states that my device is corrupt and wont boot into either recovery or System.
I still can boot into fastboot and EDL Registers as "Handset Diagnostic Interface(DFU)"....
Is there a way that i can flash the correct bootstack via fastboot? I have made a complete backup earlier using axon7tool.
Any help would be greatly appreciated.

Xadro said:
Hi guys,
i ****ed up and need some advice.
I soft-bricked my axon 7.
Situation was as follows.
I had installed AEX Oreo Rom (build from May somewhen) along with the according B10+B32 bootstack and exclusive TWRP 3.2.1.7.
This configuration ran fine. However, i decided that i wanted to upgrade and started to Flash B32 bootstack and TWRP 3.2.1.8 (with treble).
I recognized that this configuration wasnt able to boot the current rom, so i reverted to B10+B32 bootstack and TWRP 3.2.1.7 and make a full backup of current config.
After that, i wanted to Flash newer bootstack and twrp again and continue installing the newest AEX with treble.
HOWEVER i had the greatly stupid idea to Flash DrakenFX's universal Bootloader and modem. The BL states that my device is corrupt and wont boot into either recovery or System.
I still can boot into fastboot and EDL Registers as "Handset Diagnostic Interface(DFU)"....
Is there a way that i can flash the correct bootstack via fastboot? I have made a complete backup earlier using axon7tool.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Nope, i did +- same mistake with you. You need to make an edl cable. I made it in 2 mins and flashed full edl. No need fancy buttons etc. Just short green and black cable when you have to by pressing with your fingers.

Xadro said:
Hi guys,
i ****ed up and need some advice.
I soft-bricked my axon 7.
Situation was as follows.
I had installed AEX Oreo Rom (build from May somewhen) along with the according B10+B32 bootstack and exclusive TWRP 3.2.1.7.
This configuration ran fine. However, i decided that i wanted to upgrade and started to Flash B32 bootstack and TWRP 3.2.1.8 (with treble).
I recognized that this configuration wasnt able to boot the current rom, so i reverted to B10+B32 bootstack and TWRP 3.2.1.7 and make a full backup of current config.
After that, i wanted to Flash newer bootstack and twrp again and continue installing the newest AEX with treble.
HOWEVER i had the greatly stupid idea to Flash DrakenFX's universal Bootloader and modem. The BL states that my device is corrupt and wont boot into either recovery or System.
I still can boot into fastboot and EDL Registers as "Handset Diagnostic Interface(DFU)"....
Is there a way that i can flash the correct bootstack via fastboot? I have made a complete backup earlier using axon7tool.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
that's not a brick dude, that's a normal warning when using draken's bootstack
press power a couple of times and everything will be okay
to remove it, visit the los15.1 thread (second or third post)
and it registers as DFU because you're not entering EDL the correct way but instead you're entering into DFU mode.

Modding the cable by shorting the wires gives a deep edl flash ...
An edl flash can be done without modding the cable ...
Use the Miflash app ...
Edl mode is ...
Turn phone off ...
Press and hold ....volup + voldn + pwr buttons for 10 to 15 seconds ..
You will be stuck on a black screen ...led flash red ..
Open Miflash ...
Plug your phone into the cable ....
Miflash should detect ....if not hit refresh ...
Then flash an edl package to suit your phone ....there are several packages on XDA ....
I hope this helps in the future ...
BTW this is how I rescued mine after a bad flash

Voenix said:
I had the same problem a few days ago. When I booted to EDL Mode the red led was instantly on but the PC recognized it somthing like ZTE Handset Device Mode.
1. You can download TWRP Treble by NFound and flash it via your TWRP. Then reboot to recovery again and under the reboot tab its possible to boot to EDL/9008 Mode.
2. You build a EDL Cable to get the device from the red light to EDL mode. Just open some usb cable and connect the green and black (all four) together, plug it in the device and press the power button
until the red light is gone and hold on two additional seconds. Then remove the cable and plug another working cable in and the PC recognize it as Qualcomm in EDL mode.
This is literally how I unbricked my device.
Click to expand...
Click to collapse
Hope it helps

Thanks you guys on the advice!
I have made an EDL cable and was able to put the phone back into deep EDL.
I then restored my backups i took with axon7tool. Phone is in working order again!
Thanks again for pointing in the right direction to all of you! :good:

[Solved] No way to unbrick my A2017G ?

I have no idea how I managed to get into this situation.
My A2017G was on Oreo 8.1 RR with a treble partition. Since I wasn't happy with that I want to go back to the newest stock rom.
So i followed this Guide [GUIDE] [A2017G] Return to Stock from Custom ROM - Updated.
I flashed the bootstack, then I flashed the stock system and the result was a dfu brick. Meanwhile i have an Axon 7 teared down into pieces, so I'm able to flash with MiFlash.
I tried to flash these roms until now:
ZTE_A2017GV1.2.0B06_FULL_EDL_PACKAGE_BY_TURKDEVS
A2017G_B09_NOUGAT_FULL_EDL
A2017G_B10_NOUGAT_FULL_EDL
ZTE_A2017GV1.2.0B10_Stock_System_by_raystef66 (+ ZTE_A2017GV1.2.0B10_BootStack_by_raystef66)
(I also tried to flash the "Remove Bootloader Unlock Warning" zip afterwards...)
My only chance to get into the TWERP Recovery is to replace an original recovery.img with the twerp one and flashing with the test point method.
All of them result in a dfu brick or stuck in the Axon7 logo screen after the animation (if i force a shutdown, it will result in a dfu brick too).
I'm out of any ideas since every single try result in a broken device. Does anyone has a suggestion what to do now?

No need to disassemble the phone. You can always get back into EDL with this method:
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
I don't have a G model, and I don't run stock. So I can't help there except to recommend that you flash back to a supported Lineage build to unbrick.
Good luck.

I already tried the wire method and the EDL-cable method. Unfortunatly both of them failed.
imho, the axon 7 teardown is very easy and worked fine for me.
I'll try to flash the newest lineage, maybe it works for me. But I still think there is more corrupted than just the OS. All I can do is booting into recovery and getting stuck at the penuin screen or at the axon 7 screen at the end of the stock boot animation.
Edit: No luck with Lineage or any other rom. I think it's a wrong setting or something like that, but I don't know how to set everything back to default

tdm said:
No need to disassemble the phone. You can always get back into EDL with this method:
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
I don't have a G model, and I don't run stock. So I can't help there except to recommend that you flash back to a supported Lineage build to unbrick.
Good luck.
Click to expand...
Click to collapse
keep this in mind, not all G users can do the cable procedure. He's just one more on a pretty big list. It's okay to suggest that unbricking without disassembly is possible but it's nowhere near 100% (or even 50% i'd say) effectivity. Same with FTM mode, people reported that they could get there after draining the battery, well it didn't work for everyone
---------- Post added at 12:32 AM ---------- Previous post was at 12:29 AM ----------
Warcon said:
I already tried the wire method and the EDL-cable method. Unfortunatly both of them failed.
imho, the axon 7 teardown is very easy and worked fine for me.
I'll try to flash the newest lineage, maybe it works for me. But I still think there is more corrupted than just the OS. All I can do is booting into recovery and getting stuck at the penuin screen or at the axon 7 screen at the end of the stock boot animation.
Edit: No luck with Lineage or any other rom. I think it's a wrong setting or something like that, but I don't know how to set everything back to default
Click to expand...
Click to collapse
First flash a full EDL image, such as Nougat B10 or whatever new G package is available. Then you can install TWRP via EDL with "EDL Tool" by djkuz for example. After flashing you HAVE TO GET INTO TWRP or it'll get overwritten with the stock recovery. once you're there, to install lineage you'll need vendor, follow the procedures to get a working vendor and you're done

Choose an username... said:
First flash a full EDL image, such as Nougat B10 or whatever new G package is available. Then you can install TWRP via EDL with "EDL Tool" by djkuz for example. After flashing you HAVE TO GET INTO TWRP or it'll get overwritten with the stock recovery. once you're there, to install lineage you'll need vendor, follow the procedures to get a working vendor and you're done
Click to expand...
Click to collapse
After some failures I finally managed to flash the B12 Nougat full EDL. Best I can do with that is getting the Axon 7 logo after the boot animation. I'll try to install TWRP with the EDL Tool now.
edit: TWRP works for now. I'll backup the whole thing before it goes crazy again.
edit2:
TWRP: works
options menu: works
fastboot: stucks at black screen with a little penguin
booting after 5sec screen: stucks at black screen with little penguin
Does anyone has a step by step tutorial how to fix this ?

Warcon said:
After some failures I finally managed to flash the B12 Nougat full EDL. Best I can do with that is getting the Axon 7 logo after the boot animation. I'll try to install TWRP with the EDL Tool now.
edit: TWRP works for now. I'll backup the whole thing before it goes crazy again.
edit2:
TWRP: works
options menu: works
fastboot: stucks at black screen with a little penguin
booting after 5sec screen: stucks at black screen with little penguin
Does anyone has a step by step tutorial how to fix this ?
Click to expand...
Click to collapse
You have no fastboot, because N builds don't have it by default. If you select fastboot it simply boots into system. (in your case it attempts to, so it ends up in the same situation).
Try to install LOS14.1 maybe, since it's just modem, bootstack and ROM. I have zero hope that it'll work but it may as well do the trick. I have no idea why this is happening to you but it's just plain weird, I mean EDL should reflash most partitions

flashed TWRP 3.2.3
made a full edl backup
whiped data, system, cache, dalvik
flashed bootstack_O_b12
flashed oreo modem
flashed lineage-15.1-20180810
flashed pico gapps
it works now

Phone bricked after installing LinageOS 17.1 - System UI Crashing

Hi,
Today I tried to install LinageOS 17.1 on my Huawei P10 lite (at start, still completely Stock Rom).
Unlocked bootloader following procedure in https://forum.xda-developers.com/p10-lite/how-to/p10-lite-bootloader-unlock-june-2020-t4113315, worked great.
Installed TWRP following https://forum.xda-developers.com/p10-lite/development/recovery-twrp-huawei-p10-lite-t3953890 ; also here, no problem.
Then I tried installing LinageOS following this thread https://forum.xda-developers.com/p10-lite/development/rom-lineageos-17-1-huawei-p10-lite-t4064115 . Here I ended up with the Linage OS System UI that constantly crashes, restarts, crashes again etc.
This problem is mentioned in the same thread but none of the solutions seems to work for me.
I tried to downgrade the TWRP to the older 3.3.1 and then redo the entire installation procedure => No success
Then I tried wiping and formatting all the caches/data that was mentioned during the thread + re-executing the entire installation procedure => Still no success.
Can anyone help me?
What could also be relevant:
In TWRP I cannot seem to copy data to the device, whenever I try to do that via the File Manager (I am using Linux Mint 20) I can see the device and its internal storage but transferring data is horribly slow (it would take 5 hours 45 minutes to transfer a 3 MB file) or just fail. I also tried this in a (virtualized) Windows 10 installation with the same results.
When earlier today (before having installed LinageOS) I tried to transfer files, it worked very well. Also, I tried it with multiple USB cables just in case it might have been a faulty cable.
Pushing a file via adb push doesn't work as the device shows up as "unauthorized". The installation of the patches (magisk, los_patches_warsaw, opengapps etc.) I did using ADB Sideload which seemed to work nicely as well - really making me thing that the USB transfer issue is not hardware-related...
Furthermore, I know this is a noob question but anyway: the procedure says "flash los_patches_warsaw.zip". How exactly should this be done? Copying the file to the internal storage from a PC (which I cannot do, see above) and installing it via TWRP Install? Flash via Fastboot (to what destination)?
Tx in advance!

I've had this issue as well, what I did was disabled dm-verity and forceencrypt using https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 after flashing system in fastboot and then I flashed los_patches_warsaw.zip from SD Card (MTP is broken in older twrp, use 3.4.0, also try this at your own risk).

Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?

Bart80TR said:
Thanks. I solved it in another way meanwhile.
I reinstalled the stock recovery (which I was able to do by choosing the E-Recovery option in the "your device's bootloader has been unlocked" screen after startup. It reinstalled the stock recovery and ROM.
After that I installed the image from OpenKirin (it didn't need TWRP - even more, only the stock recovery is supported if using OpenKirin), and then it worked like a charm.
Just one thing, I cannot find how to update the OpenKirin installation except for flashing it via Fastboot (no option to auto-update). I wonder if it is even possible?
Click to expand...
Click to collapse
I think it's only possible by dirty flashing it, also a little correction for my last post, I meant internal storage not micro SD card.

it's a shame the original LOS 17.1 thread is closed.
My experience with WAS-AL00 (china version) on macOS:
After I flash LOS 17.1 ROM, "fastboot reboot recovery" doesn't reboot the device into recovery. Then I unplug the phone, and reboot into system, I came across system UI crashing constantly. After managing to get through to the main screen. Plug the phone, "adb reboot recovery", then flash los_patches_warsaw from microsd card (you need to copy the file to a microsd card and insert it into the phone). Then reboot system, this time the screen is black. only long press power button show three options "power off", "restart", and another one i don't remember. @KinteLiX 's method didn't work for me.
Then I tried stock recovery with openKirin (worked), Twrp 3.4.0.0 with openKirin (also worked, even though they state that only stock recovery works with their ROMs).
Last I tried twrp 3.4.0.0 with AOSP 10 from @DarkJoker360. It works.
Note: after flash the ROM, power off the phone, and long press three buttons volume up, volume down and power at the same time, and you will boot into twrp. If it shows update fail, then reboot and try to get into erecovery and wipe data/factory reset and then power off, long press three buttons simultaneously and you will be able to boot into twrp, if not, wipe data/factory reset again in erecovery (I accidentally found out about this. before this I was unable to boot into twrp after flashing any ROM, "fastboot reboot recovery" doesn't work). then do as the thread shows.
update: making a call doesn't work with AOSP 10 on my device.

The system crashing should come from the integratet AOD overlay....there should be a solution to solve that issue but i didnt rember the correct way how to. Just search in the p10 lite forum here on XDA.

MI A1 can't boot in either stock or custom rom

Hi all,
I hope someone can guide me through. My MI A1 device has suddenly stopped booting for no reason. To fix up I tried many thing but with no luck.
here is link to one of the thread I have followed
Reddit thread
This guy exactly had the same issue as mine but on different model and I followed all the instruction as in this thread.
Summary of things I tried so far (Including instructions from the thread I mentioned) :
- Try mi flash tool to flash stock rom (Which succeeds and nothing actually works )
- Tried my luck with lineage os 17 and GPAPPS but no luck. (Interestingly, when I Install LOS and I the reboot device, it boots in LOS recovery fine but when I try to boot system it just keep rebooting and then finally stops at charging screen.)
PS. One more observation, when I flash it with MIflash tool with stock rom and it boots up for the first time, an intermediate screen with circle logo and erasing text appears just like when we get update screen not sure why!
Guys, this is my last bet on XDA. I almost wasted my whole day searching for solution on #Youtube and other forums, nearly read a ton of things but still no luck!
Please Help!
UPDATE :
Here is a little more progress,
So, I tried flashing the original stock rom boot image with fastboot
Code:
fastboot flash boot boot.img
and as usual first it just got rebooted with no luck but later somehow booted the device. I tried the same with recursion OS ROM and then again flashed boot image and just like prev attempt it rebooted first & then booted normally.
Also, when device was booted normally, I received a call and when I tried to pick it, It just got rebooted and I am where I started!
I really don't get the point why it boot when I manually boot it with fastboot and its not able to boot itself.
Anyone knows, why this is happening? Is there a way to clean whole and then install? am I doing something wrong here?
Update :
Yes, confirmed when I flash the boot image from fastboot it does boots up. the only problem is after a few seconds/minutes it just reboot and goes back to problematic state.
This thing is really pissing me off! Can someone help?
Update:
After a few more attempts now, it seems like the device is completely broken! It only boots up in fastboot and does not even boot in recovery ( Volume up + Power)
I also tried with pushing twrp recovery image with fastboot but even though the command succeeds the device just reboots with MI logo continuously.

Bricked device can it be fixed?

So I had a OnePlus 5 laying around and decided to flash pixel experience with twrp and everything was fine until I decided to update ota. Then it took me to twrp but it wouldnt let me do anything. It was just stuck in the loading screen. So I managed to reflash twrp and got it working again with factory reset but then whenever I went into twrp it never asked for a password even tho I had one. I also tried backing up but it kept failing so I took a chance and saw a video on how to flash derpfest so I wouldn't have to deal with its problems again and so I followed the instructions and downloaded the ROM to the device and wiped everything except the internal storage and USB storage so I could flash the ROM but when I attempted to flash the ROM it wasn't there. I just had a bunch of files with different names and so I attempted to adb sideload oxygen os and it looked like it worked but when I was about to reboot it said there was no os even tho I flashed it so I took a chance and rebooted. Now I have no os recovery or bootloader and I keep getting a bootloop with the OnePlus logo. Am I screwed and if anyone can plz help

Your device does not fail anything, it just needs some more software. Follow my guide and your device is fixed in 10 minutes. Download the drivers on your pc. If you do not know how to do then open readme file. Run MSM some admin and set settings currect. Connect your phone to PC with USB. Press power and vol - an vol + buttons on same time. Look on PC new device registered. It's normal your phone s screen is black. Start MSM and select download mode and unbrick tool. Wait long time and your phone os is reinstalled. Official OnePlus tool.
Msm + Driver link:
I have compressed driver and MSM to gz file, for faster download and upload. Use 7zip file manager to open gz file.
Bad English Google translate.

Download.tar.gz
drive.google.com

Try to reflash recovery via fastboot. Then reboot in recovery. Connect device to your PC. If the device is not shown on your PC, enable mtp in recovery settings. Copy your ZIP-file to flash to your phone. Install it from recovery, reboot.
The important thing is to get a working recovery. If you can boot in a recovery, your phone is still working.

Just follow this. You can get your phone back to stock
How to Rollback any Oneplus Smartphone to OxygenOS from any Custom Rom
OnePlus has launched the stable OxygenOS 12 upgrade for the OnePlus 9 series, which is based on Android 12. Reworked icons, configurable dark mode, Work-Life Balance 2.0, updated Shelf, and more are among the new features included in the software upgrade. However, the update appears to be...
techibee.in