Database Users

[Q] Bell D803 constant re-boot

A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!

Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.​
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"​
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next

I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...

do you have nandroid backup from previous rom?

I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.

or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497

zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?

I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?

asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.

I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?

Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803

Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)

natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.

ALL FIXED UP
WORKING 110%
:good:

natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.

zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?

natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:

zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?

natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.

zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!

Amazfit - boot into fastboot directly

Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex

OMG!
edit:
how the hell do i get those files inside with only wastboot mode ... FFS
2nd edit: @Neuer_User, I have the pulled mmcblk0p7 on the storage, is there any possible way of pushing it back into the system via fastboot?

Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!

Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.

MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
Interesting. See if you can make it reproducable. That would be great!
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
I wrote some unbricking instructions and a flash script to recover bricked watches with @kiralex1995 method of entering fastboot.
Hope, it helps recover the small number of watches known to be bricked through flashing.
https://forum.xda-developers.com/sm...tches/tutorial-unbrick-huami-amazfit-t3547300

Neuer_User said:
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Click to expand...
Click to collapse
You're welcome

@kiralex1995 , Thanks a Gazillion !!!
it worked and with @Neuer_User help, the watch came back to life !!!

My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.

MyriaBoa said:
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
Click to expand...
Click to collapse
maybe you need to explain a little bit more detailed? is the watch running and completely booted when you connect to usb and type those adb commands or is it switched off? when you turn it on, how fast do you turn it off? i didn't get it yet. please explain a bit more.

MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
It is interesting. Does it work with out th.e adb kill-server and adb start-server commands? I do not see, how they could be involved...
The adb wait-for-server might be the key. So, when the watch is started, there is some USB communication on-going. I'd love to do some testing on that. Will do that for sure, when I get the development watch

I' m not near my computer, so I can't do more tests now.
As I wrote in my first post, it wasn't my intention to open fastboot, when it accindentally happened for the first time.
The kill and start commands were given, because my Windows 7 machine pretended not to see the watch in adb (only as usb), and I thought, maybe it's detected, when I turn it on while adb is waiting for device and the usb notification 'kicks in'.
But nothing happened, so I pushed the button, to turn the watch off again.
To my surprise the result was fastboot.
I repeated the same steps today on my Windows 10 computer that always detects the watch in adb and it opened fastboot again.

Could you specify for which build or version you tried this? I (unfortunately) had the update to 1.3.5 and there seems to be no way to enter fastboot. It also is not recognised as an adb device

I have a amazfit pace but he is stucked on a update screen and when I try entring in fast boot mode he doesn´t enter and goes to update again and don´t conclude that. What can I do?

Did anybody managed to get Amazfit 2 (stratos) to fastboot using this method? thx...
EDIT: Yes, I can confirm it works! However it is really kind of tricky. Embrace yourselves!
Many thanks to you guys for finding this out, you are the best!

Thanks.

kiralex1995 said:
Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
Click to expand...
Click to collapse
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...

Hello my device is waiting for the logo, it is not opening.

endrancer said:
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Click to expand...
Click to collapse
Hi all together,
yes I can confirm that plugging the cable is not neccessary. Went back to stock yesterday. Got into fastboot on first try.

I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?

E-lian said:
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
Click to expand...
Click to collapse
Hello
I've bricked my Pace and cannot enter fastboot.
When I try to enter fastboot I have the same behaviour on my Amazfit Pace. Have You managed some how to enter the fastboot without connection to the PC?

Bricked Chinese version, only ADB sideload is working. Appreciate any help.

Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.

tretayuga said:
Hi,
Messed up badly Furious that ZTE made the phone incompatible with Daydream, decided to root the device. Tried various ROMs, but could never get the modem to work in the UK. Eventually tried to reinstall Chinese stock ROM and, to my surprise, the modem still didn't work. Attempted to restore the modem files from TWRP backup and bricked the phone completely. Can only boot into Chinese recovery where only ADB sideload enables the phone to be seen by Windows as Android ADB Interface. EDL mode cannot be seen and Axon7toolkit cannot see the phone even in ADB sideload mode. Attempts to update software result in this message: Package expects build fingerprint of ZTE/P996A03/ailsa_ii:6.0.1/MMB29M/20161027.021856:user/release-keys or ZTE/P996A03/ailsa_ii:7.1.1/NMF26F/20170224.135053:user/release-keys ; this device has ZTE/P996A03/ailsa_ii:7.1.1/NMF26V/20170912.013327:user/release-keys. Most likely, updates won't work anyway, because when the phone was running, updates resulted in a mismatch. Any feedback would be much appreciated.
Click to expand...
Click to collapse
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone

Choose an username... said:
You messed up real bad. I assume you forgot to flash the modem files when you flashed the custom ROMs?
EDL mode cannot be seen? What do you mean by that? Keep the Device Manager open, phone disconnected; then hold both volume buttons, wait 5 seconds, connect the USB cable while you are holding them, and wait 3 seconds more before releasing them. The device manager should refresh.
The phone should appear under Ports (COM & LPT) or under USB devices as QUSB_BULK. If it is under USB devices you have to right click on it, Uninstall -> Delete driver software. After that hold all 3 buttons for a long time (both volume buttons and power) and device manager should refresh itself. It should install the Qualcomm driver then. If the driver is ZTE handset diagnostic interface, you'll have to disassemble the phone
Click to expand...
Click to collapse
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.

tretayuga said:
Thanks. The phone is listed as ZTE Handset Diagnostic Interface(DFU) (COM10) in Ports. It is listed as Unknown USB Device in USB Controllers and following the procedure you described doesn't install the Qualcomm driver. I take it, then, that an engineer would have to disassemble the phone.
Click to expand...
Click to collapse
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?

Choose an username... said:
Or you. Follow the 4th category brick repair manual. I'm just rewriting it but it'll take time
Where are you getting adb sideload from?
Click to expand...
Click to collapse
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.

tretayuga said:
Well, with your help I may snatch victory from the jaws of defeat. I'll ask one of the local engineers to dismantle the phone according to your guide and we'll see what we can do. The adb sideload screen is in this photo.
Thanks again.
Click to expand...
Click to collapse
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart

Choose an username... said:
You still have one other option though. May save you.
Do you have an SD card? If not, get at least a 4 GB one (or one with 3gb free), download an official A2017 update package, unzip it and put the update.zip in the sd card. (If you get a bunch of folders instead of a file called update.zip just take the original zip and put it in the SD).
after that, put it in the sd card and select the option that says 'sd'.
It may work. Right now it's your best shot at not taking it apart
Click to expand...
Click to collapse
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.

tretayuga said:
That's forbidden. When I've tried to update from the SD card using that option, I get a message saying I don't have permission to update from the SD card. I will, however, try again because you've mentioned some things that are slight variations on what I've done before.
Click to expand...
Click to collapse
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash

Choose an username... said:
Yeah, it's possible. But I have one more idea. Can you try one other thing?
There's a way to get to EDL if you have only DFU mode, which is by getting adb (not adb sideload, just normal adb) and issuing "adb reboot edl". If you can get adb (i think you may have adb from the main recovery screen) then you can get to EDL and flash stuff with MiFlash. Try to issue 'adb reboot edl' when you are on the main screen of the recovery mode.
The other way, which might work on your state, is turning the phone off and holding volume down + power. It might open FTM mode (it's a white rectangle in the middle of the screen with the words FTM written on it, can't miss it). If you get there just issue 'adb reboot edl' and flash with MiFlash
Click to expand...
Click to collapse
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.

tretayuga said:
Thanks, but I've already tried it. The phone only communicates with the computer in adb sideload mode, so trying adb reboot edl results in an "error:closed" message. If not in sideload mode, adb cannot even register a device. Occasionally, I've seen a small Linux penguin in the middle of the screen and today it hung on the MiFavor logo for some time. If those are significant, I don't know how to get them back. The ZTE engineers have been very thorough. It's frustratiing because the adb sideload thing might work with the right software package, and I can clear the cache and wipe the system; but then I'm back to square one. Your suggestion about dismantling the phone sounds like the most promising path forward and I will have a go tomorrow.
Click to expand...
Click to collapse
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.

Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
I do indeed get the 5 seconds screen, but the reason I didn't mention it is that it does nothing from what I can see. The phone "boots" after five seconds, but if I press the volume buttons to enter options, Bootloader is not one of them. The Fastboot option just makes the phone reboot and the Recovery option sends me to the screen in the photo upthread. Like I say, they've been very thorough.

Choose an username... said:
So you get the 5 seconds screen? Have you tried to enter fastboot?
If I'm right, you get the Linux penguin when you hit the power button when you are on the 5 seconds screen (the 'Your device can't be checked for corruption' screen). If it appears, use a volume button to get to the options, select 'Bootloader' and try to enter Bootloader mode. It should have fastboot, being an A2017.
If you get to fastboot you can issue 'fastboot boot twrp.img' and your phone will boot into TWRP. Take Lineage, the Universal Bootloader and the A2017 modem and flash them, then format data, and you'll be good to go.
Click to expand...
Click to collapse
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?

tretayuga said:
Curioser and curioser. I went through the steps to short circuit the test point on the motherboard and MiFlash successfully flashed the Unbrick ROM which you advised. Obviously, the Qualcomm drivers were recognised e.t.c. The state of the phone now is that it is caught in a boot loop. It shows the ZTE screen and the 5-second screen. Going into recovery on the 5-second screen causes the ZTE logo to appear again, then the battery icon keeps showing, switching off and showing again. The Fastboot mode on the 5-second screen now takes me to the Fastboot screen, but entering recovery causes the same battery loop. Did I make a mistake reassembling the phone perhaps? Should I try to flash a different ROM from the test point?
Click to expand...
Click to collapse
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2

Choose an username... said:
So now you have fastboot? Put the TWRP-3.2.1-0.img on the adb folder, then open CMD, navigate to that folder, write 'fastboot boot TW" and press Tab, the filename should appear, if it does hit Enter
If you get to TWRP don't turn the phone off, and flash the universal bootloader, Lineage, the A2017 modem, and Magisk 15.2
Click to expand...
Click to collapse
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.

tretayuga said:
Sorry, I didn't make that clear. The 5-second screen directs me to Fastboot, but there are only four options there: Start (doesn't work, obviously), Restart Bootloader (brings you back to the same place), Shut down and Recovery (goes to battery icon). Don't know what went wrong--maybe a connection got damaged when the phone was dismantled--but I discover I can't repeat the short circuiting thing and, even though the phone is seen on the system as Qualcomm 90.., MiFlash cannot flash anything different. I despair. I'll send the phone for recycling. Making the Axon 7 incompatible with Daydream was the last straw. I very much appreciate your help just the same.
Click to expand...
Click to collapse
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?

Choose an username... said:
No, when you are on the screen with the 4 options you have Fastboot. That is the bootloader mode. Get there and issue 'fastboot devices' and you'll see that you got fastboot from there.
Don't repeat the 4th category manual, just turn the phone off and hold volume up and down, then connect the USB. If it appears as Qualcomm HS-USB QDLoader 9008 you're in EDL.
What's the name of the package that you flashed?
Click to expand...
Click to collapse
You star! I've followed your advice and now it is exactly the phone I was looking for. (I had made a mistake and forgotten to reconnect something in the internals, but the ROM worked just fine once that was sorted and I've flashed all the things you recommended.) Your name will be sung down the ages in my household, Choose an username. Many thanks

[SOLVED] A2017G Hard brick, Unauthroized ADB and DFU Only.

Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.

Ouh....DFU? I think this thing is totally bricked.

I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?

Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !

raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.

Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.

stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!

Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....

stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!

Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable

Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!

Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...

twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.

Issues with Recovery Mode, Bootlooping, Flashing, EDL, and ADB Commands

Not sure how to title this forum post, but this is the best I got. Forgive my ignorance and lack of knowledge on these topics.
I was trying to root my Axon 7 mini. After some searching to find out how to unlock the bootloader (like needing JDK, older Android SDK version to run android.bat, etc.), I finally got it to work. Ran Recovery to "apply update from SD Card" (can not remember the file right now) and was then ready to load TWRP Recovery. When I rebooted to the recovery TWRP image, it told me something failed and the phone had to be factory reset. I took my SD card out in fear of my data being deleted and "accidentally" clicked the power button. It then reloaded with a password prompt where I typed some random password (1234 because I never set a pin password nor knew what to do here), clicked submit, and then gave me some error; now my phone doesn't work.
The Problem:
- I can enter bootloader, sometimes, but can only run fastboot commands; adb device does not detect phone so can't run adb commands (always says the server is old or something and reloads daemon successfully but never finds my device regardless). Also, I don't think I can get it to run in EDL mode; MiFlash gives out errors too when trying to flash recovery images.
- Recovery mode doesn't appear or work; not sure if the MiFavor command prompts on the phone is recovery or not, but it's safe to say this no longer appears. This is also where I believe the phone bootloops. I can get the fastboot commands to flash a TWRP recovery, but it never actually enters the TWRP dashboard.
- Can not turn off the phone... I think. None of the command options that appear on-phone shut it off; however, when the screen does stay black, I'm not sure if it's in EDL mode or plainly off.
- Device Manager shows the phone as different stuff (namely Kedacom USB Device and Portable Devices/MTB USB Device). Sometimes Qualcomm appears, but it depends. More often than not, when my device does appear, there's either an error code (like Code 10, Code 43) and/or the device is grayed out.
Conclusion:
I just want to get my phone to work normally again, if possible. Currently, I locked the oem to see if fastboot commands could still work and now I'm stuck at the ZTE logo, so can't try to unlock it right now. What are the proper tools, drivers, programs, etc I need to get this phone back to normal? I've scoured the web and these forums for 2 days now with no luck and lots of either missing info or obscure info.
I bought this at Best Buy, so I'm assuming it's US Axon7 Mini version in terms of drivers (not sure if the box specifies any info that could be useful here).

Un-brick Axon 7 Mini
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,

mariegalante55 said:
Dear all,
I experienced the same issue with my phone after I tried to flash it with custom ROMs and recovery.
I thought I lost it as I was not able to enter adb mode (not recognized on the PC) or even not able to enter EDL mode with the button combination so not able to do anything with it.
Only watch it boot and display the ZTE logo.
After some research, here is what I had to do to get it recovered.
First thing you need to get is an EDL cable.
I let you search on your favorite site. Mine was a Generic eDL Deep Flash Qualcomm 9008 Cable 2 in 1 for Z3 X/Octopus.
Until you receive it, make sure you have the latest Qualcomm drivers installed on your PC.
You can find it easily.
Then, connect your phone and your PC with the EDL cable.
Press the button on your EDL cable (there should be one) for a few seconds and keep it pressed.
Then, press the power button and keep it pressed for at least 20 seconds.
At this stage, you should have both buttons pressed and after some time, you should feel the phone rebooting.
After 20 seconds, release the power button.
Then, after 10 other seconds, release the EDL cable button.
At this stage, your phone screen should stay black and your phone should appear in the device manager as Qualcomm USBHUB (or somehting similar)
You are in EDL mode and should be able to perform a recovery flashing using tuliptool.
Then I followed the steps I found here:
https://forum.xda-developers.com/axon-7-mini/how-to/updating-uk-version-zte-axon-7-mini-to-t3717933
If you are still stuck, pm me.
Be patient, all will be fine,
Click to expand...
Click to collapse
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.

Kuma21 said:
I had a feeling an EDL cable was my only option left given everything I've looked up and the multiple methods I've tried. Wanted to avoid spending money on one but doesn't look like I have a choice given the circumstances - oh well. Regardless, thank you for the response and advice. Have to wait a while, though, to get the cable and test to see if this works.
If anyone else ever ends up in the same royally screwed situation as me, getting an EDL cable - or DIY one if you wanna be cheap and are confident enough to do so - is probably your saving grace.
Click to expand...
Click to collapse
K, I can get tuliptool to work and run command, but i keep getting a "Failed: Unkown Error" response everytime i run a command. Can't unlock my bootloader, nor write a recovery disk due to this error. does anyone have any idea why this happens?