ZTE Axon 7 wont turn on - ZTE Axon 7 Questions & Answers

Hello my ZTE axon worked fine.
Then i entered in EDL mode with an EDL cable.
Then i pulled it out and now i cant start my ZTE.
No signal of life

UltraBackfisch said:
Hello my ZTE axon worked fine.
Then i entered in EDL mode with an EDL cable.
Then i pulled it out and now i cant start my ZTE.
No signal of life
Click to expand...
Click to collapse
There are a couple of ways to get out of EDL when this happens, you can either discharge the battery (the freeze is an option, but it might damage it. people did it siccessfully though) or you can take the phone apart and unsnap the battery, then connect it again and it's done.
p.s. watch JerryRigEverything's video on how to take the phone apart, after unsnapping the FP cable you can go straight to the battery connector holder and take it out, then disconnect the battery, connect it, and put it all together again

Choose an username... said:
There are a couple of ways to get out of EDL when this happens, you can either discharge the battery (the freeze is an option, but it might damage it. people did it siccessfully though) or you can take the phone apart and unsnap the battery, then connect it again and it's done.
p.s. watch JerryRigEverything's video on how to take the phone apart, after unsnapping the FP cable you can go straight to the battery connector holder and take it out, then disconnect the battery, connect it, and put it all together again
Click to expand...
Click to collapse
GOD THANK YOU xD
I was pretty scared.
And now it workes.
I removed the battery with the help of this video : https://bit.ly/2Tqxlba

What happened to holding down the power button for ~30 seconds? That worked for me last time I needed to get out of EDL.

gpz1100 said:
What happened to holding down the power button for ~30 seconds? That worked for me last time I needed to get out of EDL.
Click to expand...
Click to collapse
I don't know. I believe it is EDL because the driver is QDLoader 9008, but the firehose doesn't work and you can't get out of it even by holding the button for 5+ minutes. Happens sometimes, i guess it has to do with the newer b12 bootstacks

Choose an username... said:
I don't know. I believe it is EDL because the driver is QDLoader 9008, but the firehose doesn't work and you can't get out of it even by holding the button for 5+ minutes. Happens sometimes, i guess it has to do with the newer b12 bootstacks
Click to expand...
Click to collapse
I believe I was on B19 (from the old MM firmware) with unlocked bootloader when this happened. I was trying an old version of miflash which didn't take. Ended up installing a newer version and power cycle the phone to get it back into EDL. I'm not sure if a power cycle was absolutely necessary but I did it anyway. Nothing got flashed from the older miflash so phone was likely still in edl mode.
There is an edl los package by oki that had the newer bootstack needed for oreo/pie. I was hoping to start out (from 9/2017 LOS) by first making a thorough backup. Phone would not boot with the modded twrp until bootstack got updates.
By some miracle I didn't brick the thing and went from an 18 month old firmware to something much more current.

gpz1100 said:
I believe I was on B19 (from the old MM firmware) with unlocked bootloader when this happened. I was trying an old version of miflash which didn't take. Ended up installing a newer version and power cycle the phone to get it back into EDL. I'm not sure if a power cycle was absolutely necessary but I did it anyway. Nothing got flashed from the older miflash so phone was likely still in edl mode.
There is an edl los package by oki that had the newer bootstack needed for oreo/pie. I was hoping to start out (from 9/2017 LOS) by first making a thorough backup. Phone would not boot with the modded twrp until bootstack got updates.
By some miracle I didn't brick the thing and went from an 18 month old firmware to something much more current.
Click to expand...
Click to collapse
You don't get it though... We're talking about EDL because it seems to be it, but it doesn't have to be. It might even be DFU only with the EDL drivers, or EDL freezing up and staying that way... Thing is this happens, I've seen it happen to two other people, think @runninghamster was one of them, and it also happened to me, and the solution is to turn the phone off somehow (battery out or frozen basically). There's no way to flash anything on it, I tried EDL Tool and many miflash versions, plus multidl to see if it did anything, no dice
also, EDL sometimes stops working after a bad flash, and you have to restart it for it to work, that's something that happens often. but that's something different, because you CAN restart it by hitting all the buttons

Related

Axon 7 can't boot, stuck on update screen then shuts down

So, I downloaded the A2017G B08 from this thread onto my SD card and went into the settings to update. All was fine until the phone got to the update screen and to 25% on the progress bar. Then the screen turned off, along with the phone. If I try to boot it, it's the same story. I see the ZTE screen, get to the update progress bar but it gets stuck on 25% and turns off. Kind of like a manual boot loop.
The phone isn't rooted or anything, I was downgrading to marshmallow to try and fix mic issues I was having earlier but never expected this.
Please help.
Thanks.
*deleted*
vesheljinn said:
So, I downloaded the A2017G B08 from this thread onto my SD card and went into the settings to update. All was fine until the phone got to the update screen and to 25% on the progress bar. Then the screen turned off, along with the phone. If I try to boot it, it's the same story. I see the ZTE screen, get to the update progress bar but it gets stuck on 25% and turns off. Kind of like a manual boot loop.
The phone isn't rooted or anything, I was downgrading to marshmallow to try and fix mic issues I was having earlier but never expected this.
Please help.
Thanks.
Click to expand...
Click to collapse
Ouch. We can try stuff but I never read anything like this here.
First try to access the recovery directly. I think it's Volume up and power, but if you get into FTM mode just try with volume down. If you can, then download B10 from the download center (it's weird that we have everything there and nobody uses it, it's frickin stickied on the Guides section for God's sake) or Nougat B04 and try to install it from an SD card.
If it doesn't work you have two ways to go: if the bootloader is unlocked, install TWRP via Controllerboy's guide (using axon7tool, it works every time)
OR
put your phone on EDL mode (Connect the USB cable to the PC, then hold both Volume buttons (NOT POWER) and insert the cable on the phone, and use MiFlash to get a working B10 on your phone. (there's a B10 package on 4pda)
If you choose the TWRP way you can install MiFavor 5.0 and be done with it. Or maybe a custom ROM, but if you didn't have any problem staying stock as it seems that you did, then you'll probably not like custom ROMs and their bugs
This is what I thougth as well. But his link only refers to B08 in MM. So he didn't want to install B08 on Nougat. As his bootloader is still locked he cannot install this ROM in no way.
Choose an username... said:
Ouch. We can try stuff but I never read anything like this here.
First try to access the recovery directly. I think it's Volume up and power, but if you get into FTM mode just try with volume down. If you can, then download B10 from the download center (it's weird that we have everything there and nobody uses it, it's frickin stickied on the Guides section for God's sake) or Nougat B04 and try to install it from an SD card.
If it doesn't work you have two ways to go: if the bootloader is unlocked, install TWRP via Controllerboy's guide (using axon7tool, it works every time)
OR
put your phone on EDL mode (Connect the USB cable to the PC, then hold both Volume buttons (NOT POWER) and insert the cable on the phone, and use MiFlash to get a working B10 on your phone. (there's a B10 package on 4pda)
If you choose the TWRP way you can install MiFavor 5.0 and be done with it. Or maybe a custom ROM, but if you didn't have any problem staying stock as it seems that you did, then you'll probably not like custom ROMs and their bugs
Click to expand...
Click to collapse
Hey, thanks for the response.
I downloaded MiFlash and got a working B10 but when I went to reboot the phone the screen wouldn't turn on, just the red LED was on. If I tried to go into recovery mode the phone vibrates and the LED flashes but it goes back to the same state. Also if I connect it to the PC and try and enter EDL mode there are sounds from windows that a USB device is being connected but that's it. MiFlash can't recognise the phone.
vesheljinn said:
Hey, thanks for the response.
I downloaded MiFlash and got a working B10 but when I went to reboot the phone the screen wouldn't turn on, just the red LED was on. If I tried to go into recovery mode the phone vibrates and the LED flashes but it goes back to the same state. Also if I connect it to the PC and try and enter EDL mode there are sounds from windows that a USB device is being connected but that's it. MiFlash can't recognise the phone.
Click to expand...
Click to collapse
I just had this issue, I plugged the phone into the orginal charger and for a legit 60sec held volume up and power button it will eventually power on .
jjallday said:
I just had this issue, I plugged the phone into the orginal charger and for a legit 60sec held volume up and power button it will eventually power on .
Click to expand...
Click to collapse
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
vesheljinn said:
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
Click to expand...
Click to collapse
hmm well idk i had this problem earlier today, even when i had mine connected to the pc the pc would make a noise as if the phone was turning on, but when i connected to the actual charger is when the 60sec thing actually worked , also i noticed that when i finally got it on the battery was down to 1% maybe some sort of battery issue. maybe let it set on the actual wall charger for awhile and try again.
vesheljinn said:
Did that for ~2 minutes, still nothing. Forgot to mention, when I connect it to the PC I get Handset Diagnostic Interface as a connected device.
Click to expand...
Click to collapse
Do the 4th category brick repair guide. Yes,you have to tear apart the phone, but I did this and didn't break it idk
No USB jigs or weird cables will work, you need to use the test pad to get into EDL.
There is another way though: it seems that if you discharge the phone completely, then hold vol down and power, and try a bunch of times, you might be able to get into FTM mode. You'll have adb from there, so you can do 'adb reboot edl' and use MiFlash to fix the software. But I haven't tried

Bricked phone

Hey guys, i made a major mistake and bricked my phone. I need to get this working badly but think I am screwed. Here is where I am:
The phone had stock B32 and stock recovery. completely stock phone. From this thread: https://community.zteusa.com/discus...safe-method-unlock-bootloader-usa-axon-7-only
A2017UV1.0.0B29_MoveToSDCard.zip
I got some error message when I try to flash A2017UV1.0.0B20_MoveToSDCard.zip... so I rebooted the phone and it seemed fastboot was enabled finally so I figured I was good to go.
Then I used the Axon7toolkit to lock the bootloader but I think it flashed the FASTBOOT_UNLOCK_EDL_N , and thats what bricked my device. After it sucessfully flashed, i rebooted the device and
it seems to be stuck in FDU mode.
Currently:
Nothing ever shows up on the screen, no bootloader screen, ZTE logo, nothing. The red power light will flash on and off and in Windows it will only show up in DFU mode. I have tried to boot into EDL mode many times and have had no luck.
Seems like I am stuck, any way out?
thanks :crying:
4th brick category
yea thats what i thought...
spacemanvt said:
yea thats what i thought...
Click to expand...
Click to collapse
Ouch... Read all my comments on the dfu repair manual, they seem to have been useful for many people
Choose an username... said:
Ouch... Read all my comments on the dfu repair manual, they seem to have been useful for many people
Click to expand...
Click to collapse
Sorry i am bit a confused... is there anyway to do this without opening the phone?
spacemanvt said:
Sorry i am bit a confused... is there anyway to do this without opening the phone?
Click to expand...
Click to collapse
Yeah but i haven't been able to pull it off. What I was saying up there is that the 4th category brick repair manual was kinda badly explained, so when I had to follow it, I shared all that I had to figure out on my own so that others could do it faster (I had to pry the battery off, and try like 40 times until miflash decided to install stuff on my phone).
The theoretical way to fix your phone without opening it up is by entering FTM mode somehow. Some people were able to get there, they say they drained the battery completely first (no idea how, given that not even the display fires up) and then they held the key combination to enter FTM (vol down+power i think). It's unclear if you have to have the phone connected to the PC but I believe that's the case since the battery should be dead and you need to use adb after FTM appears on the screen.
If you manage to enter FTM mode (a box with 'FTM' should appear [or 'Factory test mode', i don't remember]), you have ADB. So you simply issue 'adb reboot edl' and voila, you are on EDL. Then you install a FULL_EDL package for your device through MiFlash and you're done
Choose an username... said:
Yeah but i haven't been able to pull it off. What I was saying up there is that the 4th category brick repair manual was kinda badly explained, so when I had to follow it, I shared all that I had to figure out on my own so that others could do it faster (I had to pry the battery off, and try like 40 times until miflash decided to install stuff on my phone).
The theoretical way to fix your phone without opening it up is by entering FTM mode somehow. Some people were able to get there, they say they drained the battery completely first (no idea how, given that not even the display fires up) and then they held the key combination to enter FTM (vol down+power i think). It's unclear if you have to have the phone connected to the PC but I believe that's the case since the battery should be dead and you need to use adb after FTM appears on the screen.
If you manage to enter FTM mode (a box with 'FTM' should appear [or 'Factory test mode', i don't remember]), you have ADB. So you simply issue 'adb reboot edl' and voila, you are on EDL. Then you install a FULL_EDL package for your device through MiFlash and you're done
Click to expand...
Click to collapse
Right, i read that post also... it was only one guy though... sounds like a weird lucky guess.
i think i will have to send it back to ZTE... hopefully they will not be mad and fix it

no OS, no TWRP, no fastboot..... no chance?

when reinstalling a ROM earlier today, I got an error 7 ... no problem. probably TWRP problems... so, i go to reboot phone to recovery to begin fresh, and now, TWRP boots, but the screen flashes blank every couple seconds, for a second, then the TWRP splash screen comes back up. blank screen, then TWRP splash screen again. never gets further than that. because I dont have an OS installed, i cannot access debugging for adb. because i deleted my OS, i cannot allow fastboot, to flash a new recovery and begin again. ..
I am broke, and cannot afford to pay for a new replacement thru insurance or to just go buy a junker phone and make do with that.
am i ****ed, or is this recoverable...? ive been searching the forums, but cannot seem to find the answer, and im starting to get nervous enough that its sorta beginning to compound my problems more than i can deal with.
edited to add again: .... battery removed + volume dn then insert battery will not enter fastboot. im about to paperweight this ****.
again edited - Sprint LS997 is phone model. no TOT'ing for me.
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
XblackdemonX said:
What about if you remove the battery, put it back in, hold volume down and then plug the usb cable?
Click to expand...
Click to collapse
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
elijah420 said:
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
From fastboot you can reflash TWRP which from where you can reflash the OS which would unbrick the phone.
elijah420 said:
i have access to: LAF (download mode)
Click to expand...
Click to collapse
If you have access to download mode, can't you reflash your phone using the LGUP with the backup that did in the first place?(you did a backup of the original OS right?)
elijah420 said:
tried this. still a no-go. phone screen does not power on when trying this or any other combo of steps. LAF works, which is vol+ and plug in USB cable. odd that vol- and plug in USB cable does nothing. maybe faulty vol+ button? never had a problem with that button functioning before now. i have access to: LAF (download mode), and TWRP. However, TWRP 'flashes' off n on... i see the splash screen for a second, then screen goes blank, but still powered on. then splash screen again. rinse, and repeat. no response to touch or vol/pwr buttons. tried pulling battery upon TWRP splash hoping this clears cache, but still just same story afterwards.
would having access to fastboot even matter, since I have no OS install with which to give fastboot/adb access anyway?
Click to expand...
Click to collapse
Sounds like empty or bad battery to me. When did your phone start acting up upon ya? Right after root or you had it working with root etc before u ended up into such situation.
Also, as XblackdemonX pointed out, you can still use LGUP to stock.
I'm pretty sure that happened to me. And I fixed my H990DS by flashing kdz file in download mode with LG BRIDGE.
There's a guide about how to unbrick any v20 around here.
@elijah420 What software version were you on before this started? Why does it matter? If you were on ZV7 or earlier, then you can flash a VS995 KDZ in download mode, root it, and then fix your phone. If you were on ZV8 or later, then you still might be able to salvage your phone, but you will have to run firmware from another model since you will not be able to root and flash back to Sprint firmware if you were ARB 1 or later. Better than having a totally busted phone though.
Last possibility is to use the debug firehose that I have, but that is an even bigger unknown than running firmware from another model.
-- Brian

edl mode; cannot receive hello packet

Mi A1 bricked, hard resetted it by opening the back cover and shorting two points.
It gets detected by mi flash tool but I cannot flash the stock room. It is giving me "cannot receive hello packet" and then it times out.
Any help will be appreciated.
Thank you.
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
foggs said:
I'm in the same boat, it's showing up in device manager under ports (COMS & LPT) and in flash tool, yet i cant flash anything
Any help for us?
Click to expand...
Click to collapse
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
foggs said:
I've also tried different ports, still the same message of the hello packet thing. Also when I have the phone connected to the computer I've a white led light blinking.
From reading other threads here and Xiaomi site the deep flash cable opens the com port, I already have this but won't work. There was something about a loader.img, flashing this to an sdcard and holding power and vol down button it then should boot the loader IMG and rescue the phone, this also fails for me.
Click to expand...
Click to collapse
Yup, I ruined one of my usb-C cable trying do do deep flash that way. I failed, so I went to one repair shop and open up the device and did the "two point short thing", which helped to be recognized by the flash tool. Then it showed me that "hello packet" thing.
Then I dug around the Internet for couple of hours and changed the USB port on laptop. I also restarted the laptop after I reinstalled the drivers. Then it actually flashed that ROM I mentioned above. But just that ROM. I tried the latest to oldest versions and all of those ROM would flash but then they will brick the phone again. Only that one worked, i.e. helped me to get to bootloader. But alas it is stuck there, no matter how many times I clean flashed it, it is refusing to boot to system. It gives me "Your SYSTEM HAS BEEN DESTROYED" message on every boot. It only goes to bootloader if I press Volume Up + Power button while booting. And it's a dead end for now. I don't know what else to do.
Also this phone was bought in Hong Kong and its warranty won't work where I am right now. I already took it to the authorized service center and those lazy people told me to change the motherboard and it will cost around $180. So I took it back. lol
Disable driver enforcment to get the hello packet.
TrueMS said:
Disable driver enforcment to get the hello packet.
Click to expand...
Click to collapse
still no hello packet
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
:victory: Held the power button, clicked flash.. Success :good: it's in the process of flashing now. Thank you
Edit: successful flash now to just let it charge up. Thanks again guys for the help/suggestions ?
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
foggs said:
Update, i flashed the Oreo stock it gave my a successful flash, let the phone charge to near full. Booted the phone up, got as far as sending information to Google option and the screen became non responsive and the phone rebooted, it did this a few times and I gave up and put it in fastboot mode.
I did another flash using a different option clean flash still with Oreo ROM, I think first time I did it with keeping data not 100% though.. but ended up with the same result of it going into random reboots at different points in the setting the phone up stage.
I've now tried two 7.1.2 stock ROMs with the same results ???
I'll try a custom ROM tomorrow see if that sorts it, if not I'm out of ideas. So freaking close ?
Click to expand...
Click to collapse
Ur presist partition is damaged..thr are many guides here about recovering it
Do the "factory flash" mode in MiFlash under EDL mode as a last resort. May wipe your IMEI and MAC's, not sure.
Could not receive magic packet is solved by using USB2 port, Windows 7 x86 (32-bit) in a VM, or power-cycling the device and starting over, any or all of the above.
Deep flash cable is only for kicking the phone out of diagnostic mode and into QDFlash mode. Not necessary if using test point. I had to use testpoint method myself, couldn't get deepflash cable to work for getting out of diagnostic mode. I hope I can get it working next time though when I inevitably brick it from repartitioning; as I broke my screen when disassembling
apexashwin said:
Ur presist partition is damaged..thr are many guides here about recovering it
Click to expand...
Click to collapse
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Did you find the guide about fixing constant reboot? It's around somewhere, might be on MIUI forum.
foggs said:
No luck with flashing the persist.img either from 7.1.2 or 8.0 stock ROMs. I used the fastboot method and twrp with both ROMs.
I've tried the factory flash with 8.0 ROM in miflash tool this to hasn't solved the problem. It reboots on the set up I unlocked the bootloader to boot twrp flashed persist it reboots as far as bootloader unlocked screen and it stays there. ?
I'm guessing even flashing a custom ROM will do nothing either?
Click to expand...
Click to collapse
Please try presist resurrector from guides section
I think i've got it back to life.
first tried to flash 7.1.2 stock the earliest one (tissot_images_7.8.23_7.1), it hung on flashing it for nearly an hour with no success, closed the miflash application then tried another 7.1.2 (tissot_images_7.10.30_7.1)flash successful, then in stalled twrp did the persist command and reboot nearly got to the home screen just never getting over the line. then i flashed January 8.0 oreo (tissot_images_8.1.10_8.0) and was able to get on to the home screen/go into settings/enable developer options but it would eventually reboot itself, went back into twrp and did the persist command again and reboot.. success (fingers crossed) now downloading/applying April security update as i type this.
Boo installation problem with the update
looks like i lost my imei, https://forum.xda-developers.com/mi-a1/how-to/guide-how-to-restore-imei-permanently-t3759190 this is going to be a pain.. i'll post back when i try this. need a break from this mess ive made lol
thanks for the help/suggestions appreciated big time.
edit: up to the latest update April 1 security patch.
all done, down to 7.8.23 rom, did the stuff to get the imei back then flashed latest oreo rom
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
Man, I was trying to fix my Redmi Note 4X for the past 6 hours and you were the ONLY guy to talk about this. Thank you so much. :victory:
THANK YOU
udaan said:
it was solved after i changed the usb port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then twrp. But after flashing aosp extended rom it gave me "the system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
man you just solved my problem and saved for me like 180 eur thank you you are a god !!!! Thanks for using this site !!!!!!!!!! <3 <3 <3
udaan said:
It was solved after I changed the USB port on laptop. I got far as installing tissot_images_7.8.23_20170823.0000.00_7.1_61cf97d794 image and booting to fastboot and then TWRP. But after flashing AOSP extended rom it gave me "The system has been destroyed" screen. And somehow recovery is not staying. It apparently gets wiped after reboot.
Click to expand...
Click to collapse
I was unable to flash on MiFlash and after changing USB port I managed to do it!.
Many thanks!
emprazol said:
Your timeout for edl mode has passed
You must press power button for 10-15 sec to power cycle the phone
Or open it up and remove battery socket
Or wait for battery drained out
And after that edl will accept hello package
Click to expand...
Click to collapse
I love you!

HELP! Stuck in Boot Logo w/ no Recovery Mode

Ok so before I started writing this I had only one problem now I'm worried my problem has gone from bad to worse.
I updated my 6T to 10.3.2 from the latest Beta after the process it prompted for a restart, upon restarting it got stuck in the boot animation. I tried going into Recovery and Download mode unsuccessfully so I went through the forums a bit and saw that someone who had the same problem successfully entered Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on! :crying:
Has anyone experienced this or know how to fix this? Any help will be much appreciated. Tia!
theDUD3 said:
Recovery mode by pressing VOLUME UP+DOWN+POWER buttons simultaneously, I tried to do the same and my phone turned off and now it doesn't turn on!
Click to expand...
Click to collapse
These should be clarified:
Volume Up + Power while turning on will boot to fastboot.
Volume Down + Power while turn on will boot to recovery.
Holding Volume Up + Power should force the phone to turn off.
Volume Up + Volume Down should put your phone in Download mode for the MSM Tool.
Turn the phone off, let it sit. Then try turn it back on. Any response?
try to shutdown phone ...hold vol+ and power button for like 15 sec and restart your phone if this didnt work then u can try MSM tool
Thanks guys, got it working using MSM Tool!
regarding oneplus 6 got stuck on logo screen and recovery mode not working
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
You are likely going to lose your data. Know that going in if its not already backed up.
If you have the fastboot menu you can use the fastboot roms.
Or my least favorite option or what I would try last, MSM Tool (Tmobile 6Ts use a different tool).
IMPORTANT if you want to try and recover and data off your phone first, go to fastboot, and try and "boot" the TWRP img (not the installed one, one from your PC using the fastboot command). If that works you might be able to recover data. If that does worm, try dirty flashing the last ROM you were running and see if it boots.
No worries!
frankynehemimah said:
was just going through some random stuff on my phone and suddenly my device automatically restarted and not it is stuck on logo screen. i and when i tried to open recovery mode, nope its is just not working either. i even tried the fastboot menu to open recovery settings but still no progress help me here...its urgent going though lockdown in country so no service either cant communicate with the fam also. HELP...!!!!
Click to expand...
Click to collapse
Hello, I am sorry to hear of you having this issue, I just went through 3 1/2 days (off and on) of recovering my T-Mobile OnePlus 6t which I found a way to get my unlock code within 2 weeks of having it, so I rooted it and put a custom kernel on it, stuck on 9.0 never let me update as I was not familiar with A/B partitioning, yet! The answers I saw to your questions were spot on, I just had a little to add to it and I'm sure I am not alone. Real quick let me list what has gone wrong on the rare occasion it hit the fan with the 6t...
- When I would accidentally and rarely let my battery die it seemed like it took forever to get it to reboot, I mean it sat on my desk of DOA devices for 2 weeks!
- It often seems like the buttons do not always respond properly and never have when I needed them to. Been through this before, I've bricked and unbricked and flashed and re-flashed and wiped all weekend and I like Android 10 and all but seems everything is different for every build, and everything seems to have to go in the right order with the exact right file or you wind up in a jam, period..
- That said, the previous person that answered your question has likely encountered similar, I've heard of right down to the buttons not physically working, but I have been a Smart Device Master III Technician for over 5 years, i know my buttons were not broken.
- Most likely culprit that I just handled and worked, i did have to use the MSM tool, several times - and re-unlock the BL, several times I would not even get the chance to get to fastboot, just a screen saying Build and Hardware not a match"" in yellow letters and it just bootlooped. No fastboot is no good, but when you said the tool would show some signs of working but then not, I have 2 solutions that I needed on diffrent occcasions.
1 - As mentioned fully try other USB cables, and ports, if you pull the usb-c out of the port and hold <power + vol up + vol down> eventually it will do something, very picky, sometimes gotta move your fingers to different spots on the buttons and also after 15-20sec let go of power and hit and hold it again... after a few seconds before it vibrates stick the cable in connected to your PC and the screen will be black (obv) but the msm tool will pick up on it. I know about the cables because I take good care of my phones and cables and charging ports, however on my final fix today it showed in msm tool it was connected but waiting for device.... Fed up i put the phone down and moved the usb cable a little bit and it picked up on it and did its thing! That part was just the cable, getting into qualcomm mode or w.e. is a bit tricky sometimes.
- Also someone said set it down for a while and come back to it.. THAT WORKS!! Let it fully charge and often just plugging in charger turns it on, bootloop soft brick or however have you, very simiilar to an Apple device and their DFU (don't f up mode cause screen is black..)
I hope that helps you get in touch with your family and friends.. Whatever you do, don't give up bc if you have not got it yet, you will! One other note, there are a few different msm tools available and they look the same some same size, but the one that supposed to work on my phone didn't and one that they say only a fool would attempt to try actually saved me, so if all else fails, use a different msm tool/usb cable and you will get it! I don't think I can post links yet I am on here very rarely, but plan on more! I have received so much help from XDA throughout the years on thousands of phones with just software issues alone, aas well as guides to my own phones. I would be honored to give back as I also have some extensive knowledge on many devices but I am a noob in comparison to many! Stay safe, good luck and please update and let us/ me know how it worked out for you. If i can help further I will, I have every firmware file for the OP6t, recovery, tools, software, this is not new to me but I feel your frustration!

Categories

Resources