yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 Guides, News, & Discussion] sportfuchs:
same problem here. how to make the send configure command succeed?

---------- Post added at 03:11 PM ---------- Previous post was at 02:33 PM ----------

OK I FINALLY GOT IT AFTER ENDLESS TRIES!!! The trick is the timing. You need to release the copper wire exactly when elapse counts 3s. That's it. Good luck!!
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
You could've used a clip. Poor USB cable
[ZTE Axon 7 Guides, News, & Discussion] sportfuchs:
Got it to work. System boots. Now I got another problem: The power button would not work... damn it. Could that be a hardware or software problem? Maybe it happened by disassembling the case, but I was actually quite careful. Any ideas are welcome
[ZTE Axon 7 Guides, News, & Discussion] jacobtordjman10220:
how do i "circuit"?

---------- Post added at 12:07 PM ---------- Previous post was at 11:53 AM ----------

and how you connect it to pc? the parts arent connected just connecting one part of the phone doesnt make sense
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Read all that I posted on the 2nd or 3rd page, it's very useful. Also be VERY careful because you definitely don't know what you are doing

First of all, the motherboard should have the BATTERY and USB-C MODULE connected. I had to pry the battery off to do this because it was extreemly bothersome otherwise. But be extremely careful if you do this. If you can avoid prying the battery off, then just don't do it.

After that you have to get a clip or some other small metal thingy, and shortcircuit the testpad (connect the testpad and the SIM/SD housing with the clip).
[ZTE Axon 7 Guides, News, & Discussion] p82maarj:
Help!!!

Impossible! about 10h of tries and nothing, I always get "send configure command failed":crying:

I have tried:

- Keeping the test point, removing when "send configure command", removing at elapsed 3s(1s,2s,3s,4s,5s, intermitent...), with and without battery connected, with different wires, connected to different housing parts.... thousand of tests.

For more info, Before opening the phone it always connected in DFU mode, but now my phone always enters int EDL when connected, no matter if test point is connected to the ground or not. Is it normal?

I attach the las log

Any advice? Thanks!
[ZTE Axon 7 Guides, News, & Discussion] HVMan01:
All I can say is, frustrating as it can be, it works. Yes, it took ages and many tries. I did disconnected the battery. My friend held the wires to the right points and I hit the PC keyboard at the right time (many times!). I'm using that very phone to send this. It's worth the effort. Apologies if this sounds patronising, it's not intended to be. Good luck.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Use my guide, I did it because there are some things that aren't clear on this one.

The battery HAS to be connected
[ZTE Axon 7 Guides, News, & Discussion] portugt30:
Test point

O old the test point with watt ?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Use my guide, it's explained there
[ZTE Axon 7 Guides, News, & Discussion] portugt30:
It does not say what I should press the test point.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
what?
[ZTE Axon 7 Guides, News, & Discussion] portugt30:
This way?
[ZTE Axon 7 Guides, News, & Discussion] portugt30:
Sorry for being boring but this is how you press on the test point, with electric wire to make base on the metal of the sim card? I'm sorry for my English. Google translator. Lol
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Yes. Also you can use a clip and make it touch the metal piece that is right beside it, which may be easier.
[ZTE Axon 7 Guides, News, & Discussion] HighSierra:
Hello i want to give feedback after try this.

i flashed my A2017G and after flash couple of roms ive only came into DFU Mode. FTM, ADB, Recovery .... not working anymore. Then i see this Guide and give it a try (the axon is only 2 Weeks old after buy it) :)

Open the Phone, Test Point to Ground (SIM Housing) and after many times it recognized at Qualcomm and MiFlash can flash the Phone. 5 Times i need to flash before it works. 2 Seconds holding the Test Point then release and what should i say: IT WORKS AGAIN. Thanks to the Master of this Thread, i love you :silly::silly::silly:
[ZTE Axon 7 Guides, News, & Discussion] reticuli:
Maybe someone knows where the TEST-Point is located on the Axon 7 mini? Model: B2017G-EU. I got one that are bricked with DFU-mode showing up.
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Well in the Axon 7 it is on the other side of the PCB. Look at our pictures and compare.
[ZTE Axon 7 Guides, News, & Discussion] reticuli:
This is puzzle to figure out! =)
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Not good, not good at all.

Does it have an RGB led tho?
[ZTE Axon 7 Guides, News, & Discussion] reticuli:
Yes it has RGB led.
[ZTE Axon 7 Guides, News, & Discussion] madsud:
Hi, I can see you have helped out many friends here. Thanks for that.

Looking for some help guidance. Have a 2017G model. Did the circuiting as instructed. Device was recognised as Qualcomm HSB Q loader 9008 as in the OP in device manager. What was surprising to me after reading the entire thread was that that I was able to flash the EDL firmware B10 downloaded from links in the OP in the first attempt. May be a stroke of luck. The flash was successful. However, the device is still not booting up. And goes back to be recognised as 'Handset Diagnostic tool' in device manager. Repeated the process using B 09 as well with the same result.

Not sure if the option at the bottom right corner of Mi Flash tool makes any difference. First i chose the option of 'clean all and lock' and the next time just with 'clean all'.

Not sure what I am doing wrong. Any help appreciated. Thanks! Happy to provide further information where required.

---------- Post added at 04:33 AM ---------- Previous post was at 04:29 AM ----------

Hi, I can see you have helped out many friends here. Thanks for that.

Looking for some help guidance. Have a 2017G model. Did the circuiting as instructed. Device was recognised as Qualcomm HSB Q loader 9008 as in the OP in device manager. What was surprising to me after reading the entire thread was that that I was able to flash the EDL firmware B10 downloaded from links in the OP in the first attempt. May be a stroke of luck. The flash was successful. However, the device is still not booting up. And goes back to be recognised as 'Handset Diagnostic tool' in device manager. Repeated the process using B 09 as well with the same result.

Not sure if the option at the bottom right corner of Mi Flash tool makes any difference. First i chose the option of 'clean all and lock' and the next time just with 'clean all'.

Not sure what I am doing wrong. Any help appreciated. Thanks! Happy to provide further information where required. Sorry for the duplicate post not sure how to delete earlier post
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Well I think I said it around but i made a new guide based on this one.

You shouldn't have locked the bootloader, but okay. Just keep trying to short the testpad and doing the procedure, don't change the option below, leave it in default.
[ZTE Axon 7 Guides, News, & Discussion] madsud:
Thanks for your swift response. I tried and searched for your guide. The only guide i could see was that in the OP. Is that what you are referring to? if not please point me to the correct post please?

Which one is the default option please. If I recollect right it was in 'clean all and lock' option which i later realised. I could not see any mention on the specific option anywhere here. So which option should i use of the other two? Thanks
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
I guess it's clean all, idk. Lock sounds a lot like bootloader lock.

My guide is around the guides section called DFU unbrick, but it's essentially the same though better written overall (not translated)
[ZTE Axon 7 Guides, News, & Discussion] ehab517:
A DIY deep flash cable fixed it for me

I just followed a DIY deep flash cable from YouTube, made my own and used it to start my Chinese Axon 7 into EDL and it worked first attempt and I did not need to disassemble the device :cool:.

I guess the timing is important.

1- Make sure your phone is shutdown and Device Manager is open in your PC

2- Now connect the cable to your phone and press the button on the cable

3- Connect the cable to the PC

4- Release the button and you should hear a sound of USB device plugged

5- Check the device manager for a new hardware (USB_BULK) or under COM ports you will see Qualcomm 9008

6- The rest is as explained in the original post.
[ZTE Axon 7 Guides, News, & Discussion] HansWursT619:
I rigged together a deep flsh cable.

But I am still not quite sure what the sequence is.

I can get my phone show up correctly in device manager, but only with button not pressed.

When I release the button the connection will always go away?

When plugging it in with the button pressed, it will still vibrate and blink. Not just make the usb sound as decribed?

EDIT:

Do I have to use the Driver from the russsian forum? I cant figure out how to download that.

The drivers provided with the EDL Tool, Axon7Toolkit or directly within MiFlash wont work?
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
you don't have to install any driver. If you do, it'll be nonsense, because your PC will recognize the phone as if it was on EDL while it isn't there.

I don't even know if that works, I used the disassembly process. But the "USB sound" that you mentioned is the same as having device manager open and checking the com tab

You probably have to keep the button pressed until you start flashing or something. at least it's like this with dfu testpad unbricking - release 2 seconds after "sending programmer" appears on miflash
[ZTE Axon 7 Guides, News, & Discussion] Predatorhaze:
I think they still fix your Phone if its bricked, because no hardware is damaged.
[ZTE Axon 7 Guides, News, & Discussion] Syberclone:
Nice work, very comprehensive fix

The Miflash app has a couple of settings in the lower right corner

"Clean all and lock" cleans all un-needed install files and locks the bootloader.

"Clean all" just cleans all un-needed install files and leaves the bootloader unlocked.

(If I understand this correctly from the Miflash sites via translation)

I have read that the Deep flash Edl cable needs to be grounded as well to work (some say just short 2 wires) I haven't had the need to test this?

Some Edl packages won't work properly in Miflash (error messages when installing, I haven't had time to compare Edls to see why this happens) but maybe will work in the Edl tool?
[ZTE Axon 7 Guides, News, & Discussion] Evil0verlord:
Possibly, Once you have a working phone though, you can always unlock it manually again.

The EDL cable didn't work for me, and I'm apprehensive about it as well since I tried two methods.

1. The DIY video one, where the guy shorts the 3rd pin to the shielding. The jacket of the USB plug. Didn't work. The link to the youtube video and the post mentioning it is on XDA somewhere.

2. Stripping apart the cables and shorting the two wires. Didn't work either. This post too is on XDA from what I recall.

3. Now that you say it, I could've tried shorting the two wires and connecting it to the shielding or grounding it to a metal. Didn't try that, as it was getting too frustrating.

Here's my EDL history.

1. Soft brick - Rebooted to EDL, Flashed A2017U B35 on MiFlash 2016.04.01.0 (64bit) - Worked in one go.

2. Soft brick - Rebooted to EDL, Flashed A2017U B35 on MiFlash 2016.04.01.0 (64bit) - Worked in one go.

3. Hard brick - Shorted to EDL, Flashed Chinese B13 on MiFlash 2016.12.22.0 (Release) 64bit - Worked in one go.

4. Chinese to US ROM - Rebooted to EDL, Flashed A2017U B35 on MiFlash 2016.04.01.0 (64bit) - Worked in one go.

Every time I am successfully in EDL and stayed there, MiFlash worked perfectly.

Everytime I got an error, i.e. was hard bricked, I wasn't in EDL.

I haven't used the Axon 7 toolkit to flash EDL. Mainly cos I didn't bother to look up how to and where to save the EDL zip in the toolkit folder. Lazy.

MiFlash worked for me everytime I did it correctly, i.e., when I was in EDL

I don't think using any genuine A2017 U/G/C EDL package with a MiFlash that can access EDL successfully would fail. I wouldn't try it out though. I got my Axon back. I'm happy.
[ZTE Axon 7 Guides, News, & Discussion] taufikthexfader:
Let me share my story...

I have been following this thread for a month now and today i just can't wait to try it myself, i had my a2017g dfu bricked after trying to flash stock b12 over custom trebel rom (with treble partitions still intact).

Tools i used:

1. Axon7 EDL tool (super useful tool)

2. MiFlash build 30.06.18 (iirc)

3. A2017G B12 Full EDL

4. A2017G V1.0 B10 Full EDL by djkuz

5. Some old name cards and kitchen knife for prying tools.

6. A metal SIM ejector to short the test pin.

* The hardest part for me was opening my a2017g from its superglued speaker grills (had to use my wife hair blower) and its aluminium back case (i cracked some clips but idc).

* Follow the instruction on this thread, i only had to remove mother and daughter board and turn em upside down without pulling out the battery.

* Shorted the test pin (EDL mode), flash B12 via mi flash, short again and release when send configure command showed up. (Failed 3 times, had to recycle power by disconnect battery and reconect it).

* Repack my axon back, but failed to boot.

* Redo the steps above but this time i use axon 7 edl tool to fix my missing EDL config, flash B12 again and still failed to boot.

* Since i fixed my EDL, i no longer need to reopen my axon, i did the usual EDL buttons combination and it worked.

* Decided to flash A2017G B10 and voila it booted!

Some tips:

1. Once you have regain EDL (via deep flash cable or short test pin), always fix your EDL config via Axon 7 EDL tool.

2. Always unplug the battery first, and replug it the last.

3. Use a SIM ejector instead of paper clip, it provides you more control and accuracy.
[ZTE Axon 7 Guides, News, & Discussion] Syberclone:
MiFlash:

Each time I've flashed an Edl package I've left it at its default "clean all and lock"

I always test all apps via its default so I know it works before I modify and settings.

With my next flash I'm going to try the "clean all" and see if the bootloader is left unlocked.

Yes, I can always be unlocked later.

Edl packages:

The Edl I was using at the time was an Edl by Turkdevs, it would start flashing it would get to exactly 133 seconds into the flash then I'd receive an error.

I swapped it for the B12 beta Oreo that's posted here by Raysteff66 and it flashed with no issue at all.

Since then I've flashed :

B13, B15 and B16 (all Oreo) and all worked perfectly.

Maybe there was an incompatiblity issue with the Turkdevs Edl?

The deep Edl flash cable:

I read where I guy said he had to short the 2 cables and then ground it, I'm not sure if this method works though. I wouldn't short too much out unless I knew for sure.

Long story short I got mine running again which I'm thankful for, mines a daily driver and I think I'll buy another phone and then start messing with it more.

Nice to see your feedback too btw. :)

---------- Post added at 08:28 PM ---------- Previous post was at 08:09 PM ----------

Thank you for sharing your story with us.

This could help someelse with their Axon 7.

I thought I was going to have to disassemble my Axon to get it working, however messing with a couple of apps and Edl packages I managed to get mine running. :)
[ZTE Axon 7 Guides, News, & Discussion] Misiantowski:
I was doing everything like in this guide. I was made about 200 attempts and everytime the same result (and yes i have read all topic and all posts) "send command configure failed" in about 14-16 second of procedure. Trying on MiFlash 2016.12.22.0(Release) with turksdev edl and also b10 and b16 full edl. Trying to break circut instalty, within 2,3,4 seconds even till error message appear - always the same. Any ideas ?
[ZTE Axon 7 Guides, News, & Discussion] Voenix:
I need help my Axon 7 is bricked.

I can boot to stock recovery but oem unlock and usb debugging is disabled,

but cannot perform any update via sd card and no system is installed "Sorry, No Oem Unlock"

Botting to EDL Mode works but I really cant flash anything it gets stuck on flashing and the timer counts endless

Edit: I just send it to warranty
[ZTE Axon 7 Guides, News, & Discussion] juniorD:
DO NOT BUY A CABLE OR OPEN YOUR DEVICE!!!

Go here https://xdaforums.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229

TOTALLY WORKED AND I DIDNT HAVE TO OPEN MY PHONE OR BUY AN EDL CABLE!! Follow the setup carefully as the instructions arent perfect but I managed and BOOM! Phone booted from DFU to Qualcomm and MiFlash flashed with ease and my phone is totally working. Before I could only get it to boot to fastboot mode and thats it.

The DFU Tool totally works!! Im so happy!! I had ordered an EDL cable and had to wait a week for it to reach. Found this tool and followed all the steps and my phone is back!!
[ZTE Axon 7 Guides, News, & Discussion] Zel0teS:
Thank you so much! This got me my phone back after i nearly gave up! I opened it and got to the Testpoint. I struggled very hard to get it to being detected as " Qualcomm HS-USB QDLoader 9008".

Sometimes i got there, tho. Then i just needed to flash FULL_EDL and it worked like a charm afterwards.

Thank you so much!
[ZTE Axon 7 Guides, News, & Discussion] Choose an username...:
Ouch... There's this tool that someone posted here like 3 months ago, that fixed your phone without the need to open it...

Well if it works then good for you anyways
[ZTE Axon 7 Guides, News, & Discussion] standal.10:
Hi,

my phone is bricked, can you help me? I tried everything. It happens, after that I flashed recovery. I wanted to decrypt phone, but after pin entry it did nothing. So I begin to flash another recovery, after that it showed only ZTE logo and did nothing, so I again flashed another recovery, after that it shoved only red LED, so I tried also this 4th category unbrick, but after that it shows nothing only QDloader at windows. No red LED nothing.

This is what miflash shows. DFU unbrick tools shows disconnected.

Did somebady found a solution to this kind of brick?
[Samsung Gear S3] veletron:
Hi

Does anyone else have issues with the auto-pause facility on S-Heath running on the watch.

I was out mountain biking last weekend, stopped for a rest, tracking paused (good), started riding again, and after another half an hour of riding noticed that the tracking had not auto-started. It seems that after an auto-pause, I have to remember to press the back button to get the damned thing to start tracking again? I will never ever remember to do this! - if it auto-pauses then it should also auto-start! The only solution would appear to be to disable auto-pause, and not stop for any rests!

So, is this normal behaviour? Also, sports wise, there are hundreds on s-health on the phone, but only a tiny subset on the watch. I can start 'cycling' on the watch, but not 'mountain biking' - the S-Health app on the phone has both. If I start the activity on the phone, then the watch does not get used at all? I would have expected the phone app to realise there was a gear S3 attached and prompt 'start activity on watch?'. Also, if I edit the sports on the phone app to just those that I actually do (which I have done), I would expect these to be synced to the watch, replacing the activities shown on the watch.

Usual deal, Samsung makes decent hardware, but can't write decent software for toffee...

Nigel
[Samsung Gear S3] guitareth:
Agreed. It's a recurring bug which also affects UnderArmour's apps such as MapMy Run. I'm submitting a ticket to UnderArmour today to see if they can find a solution.
[Samsung Gear S3] veletron:
This weekend I was out road cycling, used manual-pause instead. Paused it for lunch, and when I went to restart it found workout had ended. Cant guarantee that I did not accidentally press the finnish button though. Ended up with two separate workouts in s-health each one 2 hours long.
[Samsung Gear S3] guitareth:
Yesterday I reported to Under Armour support my ongoing problems with MapMy Run stopping tracking and locking up/ They have responded as follows:
[Samsung Gear S3] neils31:
So i was out on my bike today, first time with the S3, set of S health for the ride after about 45 mins I checked and the ride had stopped recording at 35 mins ... had my garmin running also so all was not lost.

I restarted s health to record the rest of the ride.

When I got home, my phone had recorded the full ride but in 3 sessions all from the s3.

I have workout detection enabled which seemed to have worked today, so is there any point in starting an exercise on the watch if workout detection will do it anyway?
[Samsung Gear S3] troxter:
Hi,

How I can manually start cycling session with autopause on Gear S3 using S-Health?

EDIT: Found it, I will test it tomorrow ;)
[Samsung Gear S3] Bizmaniz:
Have you figured out how to log mountain biking using the watch yet? I just got the gear sport and was surprised it doesn't have a mtb option on the watch. Any suggestions?
[Samsung Gear S3] timrock:
sorry to piggyback on this one, but on my watch, when i go into SHealth, all i see is Calorie stats. However, on my phone, under the "ME" section, i have selected various routines, but none show on my watch. I uninstalled and reinstalled, reset the watch after the update, still nothing. Any suggestions?
[Samsung Gear S3] arumughan.balabalan@gmail:
Hi

My mobile S5 not showing steps counting during my walking activity , it is observed that frquently having the issue of pauses when i start walking in the morning. The counting starts once the phone swith off and on,but now it paused and not showing the steps counting accordingly distance and callorie burn. I am look forward the valuable suggestion at the earliest.

Balan A
[Samsung Gear S3] ruva:
Ridiculous that Samsung have not fix this yet 2019. But they are always hurry to put out new lines and abounded the old stuff. Her a video on this problem:

https://youtu.be/1kp69WNk_9Y
[P3600 Software Upgrading] sebastianmc:
hello friends.. Please tell me... Can P3600 and P3600i use the same cooked roms? How? Where? lol just changing the bootloader?

Thx
[P3600 Software Upgrading] tnyynt:
Absolutely not, at least not yet!

Read here: http://xdaforums.com/showthread.php?t=328147
[P3600 Software Upgrading] nephos:
It's possible to use P3600i rom on P3600

I'm using the latest Dopod release, it's for P3600i but using the olipro's SPL 3.03 (if i'm not wrong this was) and changing the OS base address from 0x400 to 0x401 in the nbh generator you'll haven't any problem.
[P3600 Software Upgrading] sebastianmc:
So P3600i is worse... cos p3600i without xda cooked roms is NOTHING lol

Now I know why I dont see cooked roms to p3600i,,, :(

thx friends
[Fire Q&A, Help & Troubleshooting] discman017:
Hi! I have a 5th gen Fire tablet running 5.1.1, rooted with the Supertool, lock screen ads turned off.

I'd like to get Alexa. I understand that Alexa is available in firmware 5.3.2.

I see here that 5.3.2 can't be rooted but can be downgraded to 5.3.1, which can be rooted. So I think 5.3.2 is the version that I want, rather than 5.3.2.1, to preserve the option to root in the future.

What is the process to upgrade my tablet to 5.3.2? Based on experience with other devices, I would expect that I'd need to do some combination of unrooting, factory reset, clear data and cache, etc.

But I'm reading the instructions for restoring stock firmware here, it looks like all I need to do is an adb sideload in stock recovery. Is it really that simple? No need to do anything else?

I'm assuming the result of that will be a fresh install of 5.3.2 with Alexa, and then I'll want to use the Supertool to install the Play Store.

Can anyone just provide a quick confirmation that I have this right? Thanks for any help!