Database Users

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

P9 lite stuck at "Your device booting now screen..."cant enter fastboot

Hi!
So i treid to install the twpr recovery via srk tool huawei
after i unlocked the bootloader and reboot the phone i got the ÿour device is booting now screen and i cant do anything
i tried to restart the phone then press the vol down + the usb cable and doesnt work i still get the same screen
can't acces erecovery, can't enter fastboot, i can't do anything
what do i do now?

Nickoll_no1 said:
Hi!
So i treid to install the twpr recovery via srk tool huawei
after i unlocked the bootloader and reboot the phone i got the ÿour device is booting now screen and i cant do anything
i tried to restart the phone then press the vol down + the usb cable and doesnt work i still get the same screen
can't acces erecovery, can't enter fastboot, i can't do anything
what do i do now?
Click to expand...
Click to collapse
Device stuck in device is booting now ? or the 3 option screen ?

Kcetin20 said:
Device stuck in device is booting now ? or the 3 option screen ?
Click to expand...
Click to collapse
The device is stuck in the "device is booting now':crying:

Same Problem...
Nickoll_no1 said:
The device is stuck in the "device is booting now':crying:
Click to expand...
Click to collapse
BLN-L24N - Honor 6x
Sooo, I have the same problem , here's my story. Please help I've resorted to using a SGH-T599N... Its embarrassing... I'd almost rather have an iPhone...
So Little ol' me was messing around/ deleted google play services/ reboot to twrp to recover but device ended up bricked. At the time, still able to access fastboot. I flashed recovery and firmware. I then tried dload roll back method and when it cleared the phone bootloader locked. So I unlocked bootloader again but when device re-booted the following screen came up and still remains:
" ' Your device has been unlocked and cant be trusted. ' -- ' Your device is booting now... ' " (No options are available.)
I eventually tried to restart to fastboot or erecovery BUT Everytime I try to power down the device, it tries to power up again but needs to charge for a minute before trying to boot itself back up. .(even after being on the charger for hours this happens). The problem with that is I can't get into fastboot or force dload because it automatically starts itself/ has to be plugged in until it turns back on. (Yes i've tried button mashing/ button holding/ etc. did not help)
How do I get the phone to charge, without it booting up? I have a feeling that if I can get it to start (without it first having to charge) I can get it to fastboot/ or erecovery. I have already tried to let the battery COMPLETELY drain.
Outside of that, I know the whole roll back and dload stuff. Currently it flashes the honor logo screen and then sits at "Your device is booting now..."
Bootloader is unlocked
OH! I should clarify, it boots on its own. I've tried disconnecting the battery, having it on the charger without the
battery. With the battery, Starting phone up by re-connecting the battery. No positive results
I'm about to start messing around with firmware flashing utilities, I just don't know of any. I wish there was a way to flash without being in fastboot mode. (I know very little of perl/python/linux, but I am a quick learner if you point me in the right direction.
Thank you in advance

MSDB714 said:
BLN-L24N - Honor 6x
Sooo, I have the same problem , here's my story. Please help I've resorted to using a SGH-T599N... Its embarrassing... I'd almost rather have an iPhone...
So Little ol' me was messing around/ deleted google play services/ reboot to twrp to recover but device ended up bricked. At the time, still able to access fastboot. I flashed recovery and firmware. I then tried dload roll back method and when it cleared the phone bootloader locked. So I unlocked bootloader again but when device re-booted the following screen came up and still remains:
" ' Your device has been unlocked and cant be trusted. ' -- ' Your device is booting now... ' " (No options are available.)
I eventually tried to restart to fastboot or erecovery BUT Everytime I try to power down the device, it tries to power up again but needs to charge for a minute before trying to boot itself back up. .(even after being on the charger for hours this happens). The problem with that is I can't get into fastboot or force dload because it automatically starts itself/ has to be plugged in until it turns back on. (Yes i've tried button mashing/ button holding/ etc. did not help)
How do I get the phone to charge, without it booting up? I have a feeling that if I can get it to start (without it first having to charge) I can get it to fastboot/ or erecovery. I have already tried to let the battery COMPLETELY drain.
Outside of that, I know the whole roll back and dload stuff. Currently it flashes the honor logo screen and then sits at "Your device is booting now..."
Bootloader is unlocked
OH! I should clarify, it boots on its own. I've tried disconnecting the battery, having it on the charger without the
battery. With the battery, Starting phone up by re-connecting the battery. No positive results
I'm about to start messing around with firmware flashing utilities, I just don't know of any. I wish there was a way to flash without being in fastboot mode. (I know very little of perl/python/linux, but I am a quick learner if you point me in the right direction.
Thank you in advance
Click to expand...
Click to collapse
So on ny phobe the mainboard is dead so i guess the internal storage is corrupted
I need to change that and i guess you need too...
It's not so expensive(like 40$ for my phone)

Nickoll_no1 said:
So on ny phobe the mainboard is dead so i guess the internal storage is corrupted
I need to change that and i guess you need too...
It's not so expensive(like 40$ for my phone)
Click to expand...
Click to collapse
do you have a part number?

MSDB714 said:
do you have a part number?
Click to expand...
Click to collapse
I dont think i was to a local service...it' s not so expensive but it's not cheap either

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

bootlooped mate 9 lineageOS at booting

Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?

Mate 9
dekraan said:
Hi all,
I've installed LineageOS on my mate 9, using their own tutorial, and with a stock recovery.
Everything ran smoothly for a couple of weeks. Today however my phone would not turn the screen on, just minutes after it worked fine. So, I rebooted manually by holding the power button.
Did not work, but instead: my phone is stuck on the 'your device has been unlocked and can't be trusted' + your device is booting now... screen. But it does not boot.
I can't go into the stock recovery mode, using power + volume up.
I can get into fastboot mode, but my pc (which I used to root my phone) does not recognise it using adb, while it did earlier. sometimes a fastboot command (fastboot devices) works and lists a code.
But if I try fastboot flash system and the filename for the lineageOS img, it sends the first package but does not seem to write, writing system 1/4 lasts for ever without anything happening. The phone also stays in the white fastboot screen during this event.
Can someone help me solve this? Is there a solution?
Click to expand...
Click to collapse
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?

Newrooter22 said:
In fastboot mode does it tell you the phone is still unlocked and frp is unlocked?
Click to expand...
Click to collapse
Did not try that! It is at a repairshop at the moment, they feel it is a software problem, but I guess mainly because I dropped the word 'custom rom'.
I've got a couple clues that suggest it might be a fried chip: I get Command not allowed errors when trying several fastboot commands, and I also get a remote:flash write failure when I try to flash a ramdisk.img or system.img.
Hope to hear from the shop today or tomorrow, and will update afterwards!

I have this exact issue on my huawei y6 2018, i can access to the emui recovery mode, and have bootloader unlocked.

Ticwatch c2 stuck in boot loop after factory reset.

Hey all, I recently flashed a new rom on my phone, which required me to factory reset my ticwatch I'm order to reconnect.
Upon doing to the first time, everything seems to have gone well, but had trouble connecting to the device. So I ran another factory reset. Since that one, I've been stuck in a boot loop.
I see the "device software can't be checked for corruption" screen for about 20 seconds, and then it vibrates, screen turns off, then I see the same screen again. And so on.
I tried letting the battery go to nothing and trying again, seems to be the same issue. I'm letting it charge and bootloop for now in case maybe I just don't have enough juice to make it through boot.
It is rooted, with custom ROM (followed a guide on this forum somewhere about half a year ago, was running great) and TWRP installed (at least it was, I've been unable to get to the recovery screen since the boot loop started). Cannot see it in adb ever in this process.
Anyone have any other suggestions? I remember the Samsung notes had a special USB tool that would bridge a couple pins to immediately go to recovery, is there a similar option here?

Can you get in usb mode,or fastboot or recovery maybe?There is solution..dont worry.I ghuess adb dont work,but you cant go to fastboot mode and boot twrp image and get in twrp recovery..in twrp recovery you need backup file..If you cant do that,we are going to another solution..

Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .

nieminen432 said:
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
Click to expand...
Click to collapse
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.

KristijanKG3 said:
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
Click to expand...
Click to collapse
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.

nieminen432 said:
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
Click to expand...
Click to collapse
Maybe it wont work,but if doesnt,we figure out something..Bootlop is not the end of your device..

No go on either command. Nothing shows up.
I'm half wondering if it's my battery at this point. I think I'm getting a new watch for Christmas anyway, so not a huge loss. But happy to keep trying if anyone else has any ideas.