yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 3 Q&A, Help & Troubleshooting] Mantics:
I can get into Download Mode, and Odin will tell me it is flashing things, I even get the little progress bar along the bottom and it will reboot the device once finished...it just never boots into the OS, and I can't get it to boot into the recovery once flashed...so I have no idea what is going on. It makes me angry, like a clown! (Also, clowns are angry.)

I haven't played around with anything today since I'm a little bummed out since they shorted me about 96 hours from my last 3 paychecks at work, so I'm kind of on strike. Anyway, I will play around with it on Monday and post everything I try, and get back to you. Maybe I'll even pull the battery out again and let it sit all weekend before I duck out 2 hours early.

---------- Post added at 02:24 PM ---------- Previous post was at 02:16 PM ----------

So, I just pulled off the back, undid the battery, and plugged a USB cable into the device for power. Do you happen to know if these will boot without a battery? I ask because it appears to be doing the same thing, so it may well be the battery, but the battery doesn't look swollen or anything, so idk? Thought?
[Galaxy Tab 3 Q&A, Help & Troubleshooting] RealWelder:
I'm sure you've probably tried this but just wanna be sure... I've been watching this thread to see what things were tried.

When you boot to recovery it is by holding power, vol+, and home...but once the splash screen shows up let off of power but keep vol+ and home pressed...if not it will just reboot. Hope this helps, though I know it is unlikely.
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
Hello everyone,

So I've read that I can re-lock the bootloadder and tried to do it.

First I have flashed b10 and flashed the su so I wont loose TWRP. I entered fastboot with adb and then I typed fasstboot oem lock, I got a message on the pc with ok.

Since then I cannot boot to the phone.

The phone shows the zte logo for 0.5 seconds but not booting and with constant red led.

Tried power + vol up, power + vol down, all three buttons, vol up + vol down and then connect to pc - nothing at all. The phone wont get past this 0.5 second zte logo.

In all connections I have listed above the phone shows in device manager as QUSB_BULK. At first it was with yellow acclamation mark and then I installed the zadig driver. Now it is connected "normally".

What can I do?

Please refer me to the right tutorial or guide me.

Thanks
[ZTE Axon 7 Questions & Answers] dnlilas:
I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.

This said, I suggest two methods:

Method A)

Revert back to bootloader unlocked so you will be back as before.

Your current situation with recognized QUSB_BULK driver is good.

Always have Device Manager running to monitor.

- try "adb devices" command. If device recognized: good.

- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?

Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.

And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.

Then the phone should be back operational again as before.

Method B)

Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery

(TWRP if possible), you are saved since with TWRP you can reflash everything.

Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.

Always have Device Manager running to monitor.

- try "adb devices" command. If device recognized: good.

- try "adb reboot recovery": does it boot to recovery?

If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed

TWRP for daily operation) is not accepted.

- so you need to reflash tenfar's signed TWRP mentioned in this guide:

https://xdaforums.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379

using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).

tenfar's signed recovery is accepted even if the bootloader is locked.

- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!

(reunlock, upgrade TWRP, flash ROM, root...)
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
I'll try to do it but yesterday tried to go to edl or recovery in cmd no device found. Tried to flash recovery but it hangs on "waiting for device" so I don't thing I can get to these edl, recovery, fastboot status.
[ZTE Axon 7 Questions & Answers] dnlilas:
[MENTION=7330783]ItsNewDroid[/MENTION]

Bootloader relock could also be done with Axon 7 Toolkit https://xdaforums.com/axon-7/development/tool-axon7toolkit-t3573108

Other topic:

https://xdaforums.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
I'll try all these guides and update with results
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
So for sure I'm doing something wrong. Can you please guide me with this tool?

Ironically you helped me unlock the bootloader and I need your assistance relocking it.

Edit: I have the 3 files backed up from the unlocking procedure they should help no?

The phone is not recognized in any adb status edl or fastboot
[ZTE Axon 7 Questions & Answers] QuantumFluxx:
I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
I don't want to keep twrp or anything. I want to sell the phone so all I want.t is to go back to locked stock phone.

I cannot boot to recovery or fastboot or edl. If I could I would use miflash and flash b10 and be done with it
[ZTE Axon 7 Questions & Answers] QuantumFluxx:
I think that the initial problem arose when you flashed SU and tried to relock the bootloader with TWRP installed :(

What does Windows Device Manager show when you connect the phone to your PC?

Update: sorry bud. I totally missed that bit in your OP. DOH! Will update.

Update:

Have you seen this?

https://xdaforums.com/axon-7/help/a2017g-totally-bricked-t3537990

https://xdaforums.com/showpost.php?p=70948893&postcount=28

Sorry that I can't be of more help...
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
I think what went wrong with my device is that after flashing stock b10 I flashed su so I won't lose twrp. Now when I tried to lock the boot loader made a conflict as I could not have locked bootloader and this version of twrp (for unlocked device). Now I just need to find a way to flash stock recovery (I have a backup from the unlocking procedure) without edl or fastboot as I cannot seem to find a way to enter these states (cause I have no recovery:eek:) I'm hoping it makes sense (pretty early in the morning)
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
So no one can help?

I can't believe the phone is beyond repair
[ZTE Axon 7 Questions & Answers] dnlilas:
[MENTION=7330783]ItsNewDroid[/MENTION]

Sorry I do not have solution, just some idea.

It "seems" that you cannot boot to either system, recovery, bootloader, EDL! adb/fastboot commands are not recognized.

There is still hope since your phone is still recognized somehow as QUSB_BULK (not unknown device) with Zadig driver under USB device.

So you can try to uninstall Zadig WinUSB driver and use Qualcomm bulk drivers so that the phone appears under COM port as Qualcomm HS-USB QDLoader 9008.

If you get 9008 then you are in EDL mode, and MiFlash could be used to flash.

Qualcomm bulk drivers, MiFlash... are available from Download center:

https://xdaforums.com/axon-7/how-to/download-center-factory-images-ota-t3606547

The problem is to find available "EDL packages" recognized by MiFlash to flash.

These packages could be stock recovery, signed TWRP, or full ROM (any version, MM, or Nougat).

This would allow booting to either recovery or system.

The problem is that I did not see many such packages for A2017G, but only for A2017U.

You may have to ask other members how to build such "EDL packages" (for ROM, sometimes it is called "fastboot ROM").
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
[MENTION=3393704]dnlilas[/MENTION]

First, let me thank you for your help. It is much appreciated.

I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.

Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?

Thanks again
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
[MENTION=3393704]dnlilas[/MENTION]

First, let me thank you for your help. It is much appreciated.

I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.

Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?

Thanks again

Edit:

Miflash is not recognized in any key combination.

Edit 2: So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?
[ZTE Axon 7 Questions & Answers] dnlilas:
Oh no, you unfortunately got the dreaded DFU (device firmware mode).

Looks like it a serious brick. Some topics and articles:

https://xdaforums.com/axon-7/help/2017g-dfu-mode-investigation-t3511191

https://community.zteusa.com/thread/14699

https://www.reddit.com/r/Axon7/comments/5oqgfj/a2017g_bricked_cannot_get_past_dfu_mode/

https://www.youtube.com/watch?v=nqF3nr3y-Eg
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
[MENTION=3393704]dnlilas[/MENTION]

Man there are changes!

So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?
[ZTE Axon 7 Questions & Answers] dnlilas:
Excellent! Try to remember how you get to this menu.

Does "adb devices" command recognized? Status "xxx recovery"?

Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:

"fastboot oem unlock"

It should ask on phone to erase data (like factory reset). Then say yes.

Edit: the screen capture you took is the bootloader menu (equivalent to come into with "adb reboot bootloader").

When in bootloader, I believe you can use Volume-Up and Volume-Down to navigate (to go to recovery, system, bootloader or other mode). Validate with Power button. It is important to remember how to get to this bootloader menu.
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
I held the 3 buttons not connected to power or pc. As soon as I felt the vibration before zte logo I let go of the vol up button and it booted to fastboot.

I dont want to unlock the bootloader I want to sell the phone ( this is the reason I came to this situation) I tried to boot to recovery from this menu but it could not.

My guess is that I have twrp recovery and as the bootloader is locked it can not boot.

I need either a twrp for LOCKED bootloader or a stock recovery.

I'm searching the forum but could not find.

You are a wizard! Every time you reply I have good news :good::laugh:
[ZTE Axon 7 Questions & Answers] dnlilas:
[MENTION=7330783]ItsNewDroid[/MENTION]

Download tenfar's signed TWRP here:

TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://xdaforums.com/axon-7/how-to/download-center-factory-images-ota-t3606547)

Important: check md5 6eeb1a9d02470a840bc68019184d9a72

A2017G-TWRPrecovery3.0.2.2tenfar.img

to insure correct download.

Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).

Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.

The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.

In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://xdaforums.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),

make a copy of it with the name recovery.bin:

copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin

Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.

If OK, then issue the command:

axon7tool-1.5-win64.exe -w recovery

If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).

Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).

Good luck to you!
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
So this is the new situation: adb devices phone is not recognized. Fastboot devices device IS recognized. Issuing axon7tool - w recovery I get device not connected failed to connect. Any idea?
[ZTE Axon 7 Questions & Answers] dnlilas:
"fastboot devices" => "(deviceid) fastboot" string as result if phone recognized. Is it the case? You do have Zadig driver reinstalled, do you?

If recognized, then it is weird that axon7tool cannot communicate. Maybe you need to retry several times to restart to bootloader again (to have a fresh state),

then retry "fastboot devices" (for check), then issue "axon7tool -w recovery".
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
So I've unlocked to boot loader and will try to relock it again using the links you sent me. I have a problem with the camera. The photos are coming very blurry around the edges. Very disappointing. Thank you for all you're help man you're a life saves!!!!
[ZTE Axon 7 Questions & Answers] jw1985:
Why did u want to re-lock the bootloader? Don't do such things that is a risk to brick your phone..
[ZTE Axon 7 Questions & Answers] ItsNewDroid:
[MENTION=7846741]jw1985[/MENTION]

I want to sell the phone. The camera is really bad imho, plus the vibration motor high intensity drives me crazy.
[ZTE Axon 7 Questions & Answers] jw1985:
What is bad with the camera? It's awesome :p

Yhea the vibration is to loud I agree with that
[ZTE Axon 7 Questions & Answers] Munish_9:
Hard Bricked Qualcomm QDloader 9008

Hi guys, I have a similar problem.

My device is " 10 or D (3gb) " :

Chipset :- Qualcomm Snapdragon 425

OS :- Stock android was 7.1.2 but, upgraded to 8.1 (Oreo).

Before 10 days i executed a command -- fastboot oem lock -- this command was executed successfully, But after this my device was not booting, when i long press lock button than there was a boot logo for just 0.5 sec and nothing.

After this my device was recognized as -- QH_BULK -- when i installed qualcomm drives, then it was shown as --Qualcomm_Qd_loader 900E -- . I tried some combinations of buttons then finally got --Qualcomm_QD-loader 9008 .

When i searched about "Qd loader 9008" then i found to flash my Stock firmware by QFIL tool. I flashed my Stock rom many times but, also after a successful flash my phone is not booting, also now there is no boot screen after pressing power button. Its now completely black, but charger LED is glowing.

I have still a hope. I searched about my problem, then i found that either my --emmc storage-- is corrupted or the command i executed --fastboot oem lock-- is preventing partitions from overwriting .

Now if my emmc storage is corrupted than i think i have to boot my device from SD Card. Is someone have " emmc.img " of " 10 or D " then please share with me.

Now the situation is, my phone have totally blank screen, LED indicater is glowing red, on connecting to PC Device manager shows it as "Qualcomm_QDLoader 9008",

Also i tried to give a command --fastboot oem unlock-- at this moment. But fastboot is not recognizing my device. On typing --Fastboot devices-- no device is listed.
[ZTE Axon 7 Questions & Answers] Choose an username...:
wrong forum bro, i don't think there's a forum for your phone considering that it is called "10 or D (3gb)" but if you expect to receive any help just know that it won't be here

It should be obvious that none of our flashable files or EDL files will be useful to you.
[ZTE Axon 7 Questions & Answers] Cryptodiver:
Axon bricked, EDL mode not entered - stuck at fastboot

Hi everyone!

I know this thread is quite old, but nevertheless I hope to get some advice here...

I think I just completely f****ed up my beloved Axon 7... So here ist the complete story, and finally my question:

I had Lineage OS 14 flashed. Then I wanted to update to Lineage 15 - quite an odyssey and did not work out. Phone was stuck in a boot loop and nothing worked. Fortunately I got it back to stock using MiFlash. I tried to flash Lineage 14 but could not succeed, so I just left it running on stock.... Still cheaper than buying a new phone, I thought :D

Until today things were working fine... Bootloader was still unlocked.

So an OS update arrived when I was on the couch watching Netflix and without a thought I accepted. Stupidity at its best!!! Of course the phone went dead in the middle of the installation. After some time I got it back to life using MiFlash (phone was in EDL mode, so it worked out quite neatly). I felt on top of things and wanted to try flashing TWRP and Lineage 15 again, because stock is somehow garbage..... :D All this bloatware is quite annoying.

So I flashed TWRP. But then I thought "Well actually now this was quite a lot of work to get back to "normal" so why not just leave it like this. At least you got a working phone again!".

Because I got a smartwatch the other day that I could not pair to my Axon (Samsung apparently checks for the bootloader state) I thought I will just lock the bootloader and happily live with my Axon running stock Android.

I locked the bootloader using the Axon7Toolkit and the phone is dead since then... Dumbest decision ever...

I followed this thread and could get to the fastboot menu eventually (my procedure vs. the one suggested here: Phone is connected to PC > Keep the power button pressed > as soon as the phone vibrates let go of the power button and keep the vol up & down buttons pressed) - something at least. But now I am 100% completely and absolutely stuck.

My computer does not recognize the Axon but as an Android device. If the phone is not in fastboot it returns to DFU (Dramatically F***ed Up? :D) mode.

fastboot devices lists the device, but adb devices does not show any devices. I reinstalled the driver using Zadig already, but no success...

The phone DOES NOT go into EDL mode so I cannot just run MiFlash again and return to stock.

Do you guys have any suggestions? I would really like to continue using my Axon, it's such a great phone!

Might one of these EDL cables do the job? If so, which one do you guys recommend?

Cheers,

Felix
[ZTE Axon 7 Questions & Answers] Choose an username...:
well, as a start reading before doing anything dangerous is good... all of the bl lock guides should say that you cannot lock if you're not fully stock (stock recovery, stock system).

First of all, the ZADIG driver is useless. It's only meant for axon7tool. Uninstall the device and tick Uninstall driver for this device. You HAVE to have the "ZTE Handset Diagnostic Interface" driver.

Then use either EDL Tool alone (should work) or MultiDL+MiFlash to get to EDL. Flash any EDL package for your model (G? Marshmallow B10 is the way to go to unlock).

Then use EDL Tool to unlock, or use Controllerboy's guide (with the signed TWRP from raystef's download center since the link is dead). axon7toolkit is hardly okay...

Just keep trying to get to Treble, it won't kill your phone. As long as you have EDL you can get out just fine, and if you have fastboot too you can enter that and install the signed TWRP (NEVER backup with it) and you can flash stuff from there. Use the LOS 16 guide for example.
[General Questions and Answers] Kazarslan:
Hello, so my Samsung galaxy j7 (SM-J700F with android version 6.0.1) goes on bootloop after I tried to install xposed updates after rooting the device using odin and installing custom recovery twrp without much thinking (my bad). I tried to go to recovery mode by pressing volume up, power, and home buttons, but failed because it says "can't boot on normal mode invalid kernel length" , also I can't boot the device normally because it says the same thing and goes on bootloop. I searched for guides but all of them tell me to go to recovery mode which I can't. I can only go to download mode by pressing vol down, power and home buttons. I already backed up important files to external drive before the whole process, if I have to do a factory reset to fix this it doesn't matter. I'm very noob I'm not familiar with the language also I really appreciate your help asap thank you very much
[General Questions and Answers] ramiabouzahra:
You have to factory reset. Since your bootloader is still working (download mode), download your device firmware from sammobile and flash using odin.

Welcome to the android community and good luck!
[Samsung Galaxy S8 Questions and Answers] gilad215:
As title suggests, voice recognition has been really unreliable through my daily usage.

If the phone is locked - "Ok Google" never works, yes i have set Smart unlock to unlock through voice.

if the phone is unlocked - "Ok Google" works, but if connected to my car's Bluetooth, it doesn't.

any of you guys can share their experience?
[Samsung Galaxy S8 Questions and Answers] chinabear13:
I have the same issue...
[Samsung Galaxy S8 Questions and Answers] AdrianE46:
Same issue here. I think it's because of Samsung's aggressive management that won't allow Google Now to run in the background when the screen is off. :(
[Samsung Galaxy S8 Questions and Answers] golgothagecko:
Same issue here
[Samsung Galaxy S8 Questions and Answers] s4shield:
I normally have to reboot to get "Okay Google" command to work.
[Samsung Galaxy S8 Questions and Answers] electric0ant:
for me ok google works for while, then stops working and a reboot is the only way to fix it. only annoying thing is i need to reboot every other day. this issue doesn't seems to be covered much?
[Samsung Galaxy S8 Questions and Answers] Sikrik:
fix for the OK Google issue on S8 & S8+ is to have the software re-flashed by Samsung or one of their retailers such as Best Buy. Other than rooting the device, there is nothing that can be done at the consumer level nor with tech support assistance that will resolve the issue.
[Samsung Galaxy S8 Questions and Answers] electric0ant:
what difference would re-flashing the software achieve?

flashing stock firmware can be achieved using odin.

and after rooting what can be done to fix this issue?
[Samsung Galaxy S8 Questions and Answers] Sikrik:
I don't know why re-flashing it worked but, it did. I also don't care. The phone works perfectly now. I keep seeing the same remedies over and over on forums such as this and NONE of them worked. Now that my phone is working, I shared what I did to get it fixed. I'm not a techie, I'm a truck driver so, if you said that I can flash stock firmware with Odin, you'd be wrong. Besides, why would I? Samsung screwed it up, they can fix it. It was free and it worked.
[Xiaomi Redmi Note 3 Questions & Answers] sarveshrulz:
Hello XDA,

I have a redmi note 3 kenzo 32gb

But its only showing as of 9.23 gb

It must be at least 24 GB I think

When I tried to check in settings/storage, it is showing that my system is of 19.90 GB

Plz help me configure this issue

Please help me!!!
[Xiaomi Redmi Note 3 Questions & Answers] deepjyoti30:
Same issue here though with my letv le 1s and after flashing Lineage. Did you also flash lineage?? If you did then after wiping internal storage you might not have booted the system back to MIUI which i think is the issue. Anyways please tell me if you get any solution.
[Xiaomi Redmi Note 3 Questions & Answers] JLius:
In twrp, select format data (under wipe). Then flash rom + gapps.