Database Users

Need Help Unbricking!!!!!!

Hey guys! So my phone is bricked. Not sure what I did wrong. I tried out several roms and decided to stick with Exodus. When I flashed Exodus I forgot to flash Gapps and now phone stays stuck on boot screen and can't boot into recovery but can get into fastboot mode.
What I've done so far:
I've checked to makes sure bootloader is still unlocked and it is.
From fastboot I've re-flashed TWRP using the fastboot flash recovery twrp.img command and it says it flashes successfully.
However, I still remain stuck on boot screen and when I use the volume+ power button it won't boot in TWRP recovery.
Is there a fastboot firmware zip for the OnePlus 2 that I can flash via fastboot the way we could with the OnePlus One?
I've tried all three methods of unbricking described in this thread https://forums.oneplus.net/threads/mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
None of them have worked for me. First of all my driver does not come up as Qualcomm in device manager, it comes up as "RELINK HS-USB QDLOADER 9008." I have no idea what that's about. Secondly, when I run the Chinese recovery tool it does nothing, just sits there when I press start.
Helppppppppppp please

Try running "fastboot boot twrp.img" from fastboot.

jbw716 said:
Try running "fastboot boot twrp.img" from fastboot.
Click to expand...
Click to collapse
Thanks for the reply! After some digging realized I was having some problems with my qualcomm driver and kept trying to install but stupid windows 8.1 was blocking it so I followed this guide and I am now unbricked. So for anyone who has the "Relink" instead of "Qualcomm" this is how to fix it and unbrick:
http://forum.xda-developers.com/showpost.php?p=64674951&postcount=46

adb device unauthorized

Hey, I'm on A2017U stock B19 bootloader unlocked,
I want to backup my stock recovery and boot using axon7tool (I want to flash twrp after that),
When I type: "adb devices" I get my device number and next to it: "unauthorized",
And when I type "adb reboot edl" I get: "error: device unauthorized."
USB debugging enabled.
What am I missing?
(also when I try to go to edl mode (vol up + vol down + power) nothing happens...)
Thanks

I think u need to be root in order to backup those files using adb and you have to have the bootloader unlocked in order to root even tho theres a thread showing how to root without bootloader unlocked

Thanks,
My bootloader is unlocked...
Is there any other way to backup stock recovery and boot before flashing twrp?

Hello, do you have the proper drivers installed for the phone usb wise and in edl mode it won't do anything, that's normal.

Hi, Thanks,
I think so, as I say, it does recognize my phone number on "adb devices" , and I successfully unlocked my bootloader using fastboot

Can't get into bootloader?

Hey guys, I've been trying to unlock my bootloader so that I can try and root my Maven 3 via Magisk. The problem is, I can't get into the bootloader. If I try to reboot to the bootloader from recovery mode, it just restarts like normal. Same thing when I try using adb commands in the cmd prompt. I am on Windows 7.

I think it could be unlocked trought EDL mode. But we need some expert help

I unlocked my phone with at&t but I think it only unlocked the SIM.
I enabled usb debugging and oem unlock, but when I issue the command (in ubuntu term)
adb reboot bootloader
Click to expand...
Click to collapse
is just boots into the android system.
Any clue on what to do?

I have the same question - bootloader mode will not load when I issue "adb reboot bootloader", nor will it go into bootloader when I go into recovery mode (via POWER + VOLUME UP) and then I choose the "Bootloader" option. The phone just boots into the system. When I use "adb reboot recovery" it does go into recovery mode, and I am able to get a shell and copy files via adb just fine. I am using the latest platform-tools.
This is a ZTE Z835 (Maven 3), AT&T, carrier unlocked phone.

I don't think there is a bootloader... I have not found any fastboot-compatible mode on this device nor have I heard anyone else find one. You have FTM mode (Power + Volume Down) and EDL mode (adb reboot edl). EDL mode lets it work with QFIL, and with QFIL, you can literally dump and modify any partition on the device you want... I'm not sure what else you want. There's a new method for unlocking the bootloader https://www.xda-developers.com/unlock-bootloader-zte-phones/. I found that my devinfo partition was already unlocked, but you may need to check. I'm going to try and figure out how to create a recovery.bin partition able to be flashed in QFIL.

your device is corrupted and cannot be trusted and may not work properly

Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command

amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely

As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?

amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done

If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214

Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images

For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.

Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?

Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)

Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted

Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time

amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.

Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also

amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!

I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...

Back to stock, relock bootloader problem waiting for device

Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.

Stevie123 said:
Hi,
i used Miflash in edl mode to get back to stock rom. after flash and reboot I used the recovery mode to do a factory reset.
It seems to work. It shows Android Recovery, but the bootloader is still unlocked.
What mode do I need to enter to use the "fastboot oem lock" command? I always see "waiting for device" and nothing happens
When I type "adb devices" I can see the phone. I saw there is a command "fastboot devices", too. but it shows me no result.
Click to expand...
Click to collapse
Reboot to fastboot using
adb reboot fastboot
Click to expand...
Click to collapse
Then, try to use fastboot cmd

Thanks, before I can try that I have to solve another problem.

That doesn't work. The phone isn't entering a special mode. I can choose fastboot from the bootmenu, too. But nothing happens. The phone does a restart, shows the bootmenu again and boots android after 5 seconds.

@Stevie123
You need to enable fastboot (bootloader) mode since it is disabled by ZTE, so that the selection from menu to be effective (after enabling it, in fastboot mode, your command "fastboot devices" (to check) and "fastboot oem lock" (to lock bootloader) will be accepted).
You can use Axon 7 EDL tool to unlock the bootloader.

It's already unlocked. I have to make another unlock procedure again to get access to fastboot? The EDL Tool tells me that I have to wipe and reset the phone after it. So it seems I can't keep my data and just lock the bootloader.

Either Lock or Unlock will wipe your data. And yes, the unlock procedure by Axon 7 EDL tool includes the enabling of fastboot. So you have to re-unlock if you want to relock.

I think this EDL tool doesn't work very good. It flashed something to make fastboot available, but I had a green ZTE Logo screen and this screen also had errors like white spots. The original ZTE logo is in cyan. But the fastboot worked and I could lock the phone. But I couldn't do anything else anymore. I couldn't reach Android and reflashing also didn't work. So I tried to use the EDL Tool to unlock my bootloader again. It said success, but it didn't work. It was still locked.
Well, I had to wait until the phone was empty. Luckily I could reach EDL Mode again. I used the MiFlash again to Downgrade to Android Nougat B12. I read somewhere that the fastboot is included there. So I had the right ZTE Logo back and it worked. I could leave the Bootloader locked. The final update I did with a SD Card to the lastest Android Software for Axon 7. Luckily without a brick. It's a pity that they don't offer any Updates anymore.