Hey Guys,
i had installed a Custom Rom with TWRP on my Honor 7. Yesterday, i wanted to go back to Stock. So I flashed the "boot.img" and "recovery.img" from Stock B330 with TWRP and then restarted the phone. Now, I am stuck in Rescue Mode (Boot.img / Recovery.img load failed). The phone is listed as "Unknown Device" (tried on multiple PCs, Windows 7 and Windows 10), so i am not able to do anything with Fastboot. I've tried every possible button-combination (Vol+,Vol-,Power - with or without USB Cable) and it's landing in Rescue Mode every time.
Do anyone got another idea? Maybe i hard bricked my phone and there's nothing to do? Thanks in Advance.
Hi,
Download the official firmware (b330 or newer) , extract the "UPDATE.APP" file and put it in a folder named dload at the root of your sd card. With your phone powered off press the power key, volume up and down all at once. It should start the update process and repair your phone.
Gsavas said:
Hi,
Download the official firmware (b330 or newer) , extract the "UPDATE.APP" file and put it in a folder named dload at the root of your sd card. With your phone powered off press the power key, volume up and down all at once. It should start the update process and repair your phone.
Click to expand...
Click to collapse
Hey,
thanks for the help. Unfortunately i'm still getting the same Error again (Func NO: 11 (recovery image) / Error NO: 2).
Does it not go to fastboot mode, when you plug it into a usb port while holding volume down?
Gsavas said:
Does it not go to fastboot mode, when you plug it into a usb port while holding volume down?
Click to expand...
Click to collapse
Exactly.
Housefr4u said:
Exactly.
Click to expand...
Click to collapse
When you plug in the cable while holding the volume down button it turns on and presents you with that error? Could you take a picture of that screen. The bootloader is responsible for fastboot, it's either a driver issue or you somehow borked the bootloader.
Gsavas said:
When you plug in the cable while holding the volume down button it turns on and presents you with that error? Could you take a picture of that screen. The bootloader is responsible for fastboot, it's either a driver issue or you somehow borked the bootloader.
Click to expand...
Click to collapse
Here you are. Func NO: 11 (recovery image) pops up when i'm holding all three keys.
Func NO: 10 (boot image) pops up when i'm holding Volume Down (tried with unplugged and plugged cable).
Housefr4u said:
Here you are. Func NO: 11 (recovery image) pops up when i'm holding all three keys.
Func NO: 10 (boot image) pops up when i'm holding Volume Down (tried with unplugged and plugged cable).
Click to expand...
Click to collapse
Well, I'm out of ideas. I once too had wiped the entire phone with twrp, and restarted (doh) but was able to recover through fastboot. In your case, it seems like something is wrong with the bootloader, I've did a quick search and it appears that various other huawei devices have encountered this (or similar problems).
Gsavas said:
Well, I'm out of ideas. I once too had wiped the entire phone with twrp, and restarted (doh) but was able to recover through fastboot. In your case, it seems like something is wrong with the bootloader, I've did a quick search and it appears that various other huawei devices have encountered this (or similar problems).
Click to expand...
Click to collapse
Too bad. Well, then I'll send it to Huawei I think.. Thanks for you help!
Housefr4u said:
Too bad. Well, then I'll send it to Huawei I think.. Thanks for you help!
Click to expand...
Click to collapse
Good luck :good:
.
Related
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
RaiderDuck said:
You'll probably need to flash a new recovery partition. Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1950307
Click to expand...
Click to collapse
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
ergotelis said:
Thanks, but the problem is that this guy can get into the recovery with powering up+holding volume down button, if i understood well.but I can't!
Click to expand...
Click to collapse
flasing a recovery is done via fastboot so you don't have to enter recovery but fastboot (hold power and volume down till it shows fastboot, then press up) .
look at this post: http://forum.xda-developers.com/showpost.php?p=33137046&postcount=10
Fix
ergotelis said:
Hi there guys, first of all thank you all so much for the support here.
I have a problem with my atrix, i googled a lot before posting, but i still can't find a solution:
I have a atrix 4G, unlocked, was running successfully neutrino 2,8 version.
After 2 months of being (almost) fully functional, the phone crashed(i didn't do anything particular at that time, i think that i was browsing google maps) suddenly and now i have continuous boot loop, i get only the classic red dual core logo, with the "unlocked" notification over it, and then after 10-15 sec it reboots.
I try to open it with holding volume down, to enter recovery, nothing happens. It reboots again. The computer doesn't see it, in this case.
I reboot it with holding volume up, says "starting RSD protocol suppport", and pc sees it and i get the cling-clong sound of usb.
I would do the recovery using rsd, but i read that it is not for unlocked devices, is this so? What can i do in this case? Thanks a lot!!!
Click to expand...
Click to collapse
hello i had this problem yesterday, it happens in neutrino rom to alot of people!
and btw i could not open recovery either
ill explain what i had to do
i had to use moto-fastboot and install a new recovery, basically your recovery is dead and your rom is unbootable
heres the steps
download the moto drivers and install
http://forum.xda-developers.com/attachment.php?attachmentid=1381183&d=1349549067
then download the motofastboot zip http://forum.xda-developers.com/attachment.php?attachmentid=1381414&d=1349555102
and create a new folder in C: (computer) called Android and then drag the files from the moto zip into android
Then download a new recovery http://www.mediafire.com/?6ww8wrjrdqq9m97
place the recovery.img into the android folder
now you have all the files needed to reflash your new recovery and fix your phone the whole idea is to reinstall recovery so you can access it and wipe and install the rom fresh again
now you need to do these steps
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
4) On your PC click the Start menu, then in the search box type "cmd"
5) In the command prompt type the following commands (no quotes, hit enter after each command)
6a) "cd c:/android"
6b) "moto-fastboot devices"
your CMD promt should show something like this
C:\Users\Me>cd c:/android
c:\Android>fastboot devices
TA20703SX9 fastboot
c:\Android>
now if that has all worked type the following phrases
moto-fastboot erase recovery
moto-fastboot flash recovery recovery-clockwork-6.0.1.4-maguro.img
moto-fastboot reboot
now the phone should reboot, unplug the usb and pull battery out.
put battery back in and then try to boot into recovery like you normally would (power button + Vol Down)
and your new recovery should load!
from here you can wipe your whole system which i would reccomended as your current one is corrupt and install a new rom or reflash your current on onto a clean wipe. if you dont understand how to clean wipe do all of these steps, factory reset, clear cache, clean dalvik cache then go to mounts > storage and format data + format cache + format system
now install new rom and let it boot up, should bootloop a couple of times then start! if not unplug battery from phone and ask for further assitance
Pixelguy said:
1) Attach your phone to the PC via USB (use a port closest to the power supply)
2) Reboot phone while holding volume down until you see "fastboot"
3) Press volume up to initiate fastboot
Click to expand...
Click to collapse
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
ergotelis said:
Thank you for your help, the problem is exactly here, i put on the usb, i power up the phone by pressing the volume down, and the phone does nothing,doesn't show the fastboot,and after 10-15 secs starts rebooting again. This is my problem!
The only response from my phone is when powering up, and pressing the volume up, it says "starting rsd protocol support"
Is there any case that my volume down is dead?
Click to expand...
Click to collapse
unplug usb
remove battery, then put battery back in make sure phone off (no green light)
then hold power button and vol down at the same time for a few seconds
Fastboot should appear in white writing then press up volume and it should say starting rsd protocal or something similiar
then plug in usb and follow the steps i have written above
i do exactly what you said, but doesn't show fastboot. from switched off, if i press volume up with power button, i see the message "starting rsd protocol support" .but no fastboot option!
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
jorno88 said:
Is there any chance that you can access adb after bootscreen? than you can use "adb reboot recovery" to get there...
Click to expand...
Click to collapse
When i start up phone, the only combination possible to stop restarting is by pressing power+vol up to show that with RSD. There is no other option then selectable. Power + volume down does not work, doesn't show anything, has anyone of you experienced this thing?
If the only working option you have is RSD, then I'm afraid you're stuck with having to flash a stock SBF. I hope you know/remember exactly what stock version you had installed before any modding or flashing, because the SBF has to match exactly. Choose wisely and read up as much as you can before flashing.
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
I will later also try to open it, to see if the side button "volume down" is not working,.
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
ergotelis said:
I have over a year now with custom roms, and i can't remember which version i had. Why do i have to find exactly the version that i had? The latest stock version won't work with rsd? It will make it hard brick?If i manage at least to recover the fastboot menus etc it would be great!
Click to expand...
Click to collapse
Yes, flashing a wrong SBF will most likely hardbrick your device.
ergotelis said:
I have another question, in your moto atrix, if you press on startup power+vol up, are you also seeing the "starting RSD" etc option??
Click to expand...
Click to collapse
Can't try right now, but as far as I know, yes, that is a standard way to enter RSD mode.
thank you, so, i know that at least my phone responds to some instructions.
Is there anyone else to suggest me to do anything else?
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
ergotelis said:
IN rsd mode, (other than flashing a stock random rom with chance of hardbricking,)the phone can be read by usb, can i do anything there?
Click to expand...
Click to collapse
Sadly no. The RSD mode can only ever be used to flash SBFs. That's it. Nothing less, nothing more.
I will now try to open it to see if vol down is not working well. If it does work, i will select a stock rom 1 year old and i will flash it using rsd, and whatever happens....:good:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
try this
ergotelis said:
I disassembled the phone, the button seems to operate fine(?).
I flashed with RSDlite the 2.3.6 version, the RSD stuck to waiting for phone to restart.
The phone restarted, the "unlocked" logo disappeared.
Starts normally, passes the red motorola logo, shows the graphic of AT&T, and after ~10sec starts restarting again. Bootloop again!
At boot, pressing power+vol up, i can still get the RSD support. Pressing power+vol down does nothing, I don't see any error messages, like the ones in hard brick.
What can i do now, any ideas please!!!
Click to expand...
Click to collapse
Yesterday I had a hard time getting my phone into fastboot mode, after loading a bad SV kernel,it only wanted to start the RSD protocol mode. I eventually got into fastboot by plugging into the wall charger, then removing and installing the battery while holding the vol button. When fastboot appears, unplug the charger to allow sd access.
Thanks for the suggestion, i tried even this,it didn't work. The funny thing is that it shows the battery charging level full screen if i connect the charger, as it starts.
I noticed also that when i press vol down now, it takes longer to start and continue to the moving red logo, it stays for a while stable red,feels like it is thinking whether to start or not lol (if i don't press vol down, on the power up the red moto logo immediately starts the classic "waving" effects)
Anyone having any kind of suggestion?I guess you don't, right?
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Why you did that? You can't update rooted phone
Idiocrate said:
Ok, I just want to know if my phone is hard bricked, or if I still have a chance...
I tried to install an update (121 to 170 for plk-l01) on my rooted phone, with local update. It didn't worked, twrp show errors everywhere, and after turning off know i can't access the recovery. when I press on vol+/- and power for 10-15 second, it vibrate but nothing else.
Is there anything I can do ? my phone isn't recognized by my computer, by the way...
Click to expand...
Click to collapse
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
piskr said:
Try to boot into fastboot (phone turned off - connect with data usb to the computer - vol down + power on). Extract rom which is currently installed or higher (for your respective model) and flash from it:
fastboot.exe flash boot BOOT.img
fastboot.exe flash recovery RECOVERY.img
fastboot.exe flash cust CUST.img
fastboot.exe flash system SYSTEM.img
Reboot.
Click to expand...
Click to collapse
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
james194zt said:
That is what my phone is doing, I tried to upgrade to marshmallow though with no root!! I put the zip in the dload folder and went through the upgrade process everything went through the phone rebooted and now its dead. Blank screen and if you hold power after a few seconds it will vibrate but that is it. I presume its hard bricked? no matter what combo of buttons I press I cannot get it in to fastboot.
Click to expand...
Click to collapse
ok I'm looking for a solution for hours now... so I just lokked how works our phone and I think the trouble must be in the preloader, because I can't even make my phone being recognized by any computer and I can't access to recovery.
I found this :
http://www.droidgyan.com/soft-brick-vs-hard-bricked-vs-broken/
Which could help. I'll leave that topic on for some days (if it could help someone) and I'll open a new one to know if there is any easier solution ! thanks and good luck.
I sorted mine, it was only 2 days old so I got it replaced by the shop I bought it on. I would say it was something like a pre loader from what I saw. I have never bricked an Android phone and I must have had 15-20 of them since my first HTC Magic and before that Windows Mobile which again I messed with tons reloading with all sorts of ROM's!! These phones are wayyyy too sensitive to being messed with, I always remember though that you never mess with the boot loaders, but it looks like these updates do to get it bricked to that point.
Idiocrate said:
Thanks, but unfortunately, it just 'boot' as others reboots. it vibrates, doesn't get recognize and doesn't turn on...
If anyone have any clue on how to force recognizing the phone storage, it might really help ^^
Click to expand...
Click to collapse
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
piskr said:
Do you have adb debugging activated on the phone? Did you try to hold phone buttons long enough?
Click to expand...
Click to collapse
Euuum..... maybe yes ? I used fastboot but I don't think it really matters now, there's nothing working on it. And I've sometimes hold the buttons for 30-40 second while praying lol
korenisko said:
Why you did that? You can't update rooted phone
Click to expand...
Click to collapse
local update
I just hard bricked my Honor 7 the same way. Is there really no solution? Other China-Phones are pretty much unbrickable, since you can always fix it via the preloader. No such luck here? Back to the shop and hope they actually replace it? While I admit it was stupid to just hastily start the OTA while having twrp and not stock recovery (no root, though), this is a terrible design flaw on Huaweis side.
Anyway... any hope or no chance?
i just hard bricked my honor 7 PLK-L01
it the same thing it is doing . not recognized by the computer
tried all the combination of buttons. but no hope
and it only vibrates when tried to turn on
Need urgent help please
@Idiocrate try to boot into bootloader mode just by pressing Vol DOWN button and simultaneously connecting it to a PC, don't press Power button, if it boots into it, then follow the method given by @piskr in third post.
Ok. I tried rooting Honor 7 earlier today. I did every step, but in the last step when I installed the SuperSU trough the TWRP, I noticed a big problem.
When I rebooted the phone, it just went into the chinese TWRP. Tried everything, only goes into TWRP. Any help?
My phone model is PLK-L01.
try follow this tutorial.
http://forum.xda-developers.com/honor-7/general/honor-7-button-combinations-clarified-t3320467
Connected to a computer:
Volume up + Power on: Huawei eRecovery (reboot / download / shutdown options - used for 'recovery loop' fix, see below)
hope it will solved your problem..
lockmunk said:
try follow this tutorial.
http://forum.xda-developers.com/honor-7/general/honor-7-button-combinations-clarified-t3320467
Connected to a computer:
Volume up + Power on: Huawei eRecovery (reboot / download / shutdown options - used for 'recovery loop' fix, see below)
hope it will solved your problem..
Click to expand...
Click to collapse
Nope. Volume up + power on only boots to TWRP
I tried downloading stock roms and instaling them trought TWRP, one rom was corrupted and another did not work, it still booted to TWRP. I found some other roms but they must be downloaded from mega.nz, which does not work on my computer
Jonni1 said:
Nope. Volume up + power on only boots to TWRP
Click to expand...
Click to collapse
connect with usb cable?
lockmunk said:
connect with usb cable?
Click to expand...
Click to collapse
The phone was connected to computer with usb cable (the computer did not regocnize it though).
Any quick help? I need my phone for the weekend...I would appreciate a lot if someone could help!
Jonni1 said:
Nope. Volume up + power on only boots to TWRP
Click to expand...
Click to collapse
Jonni1 said:
Any quick help? I need my phone for the weekend...I would appreciate a lot if someone could help!
Click to expand...
Click to collapse
you should read carefully the link given to you previously and you should be able to solve it yourself.
lockmunk said:
you should read carefully the link given to you previously and you should be able to solve it yourself.
Click to expand...
Click to collapse
Ok, this is what I did:
-Connect the phone to windows computer
-Go to TWRP, select reboot and system
-Try does the phone recognize the computer by using volume down + power. Worked.
-Try volume up + power on on boot (the phone goes black after a moment, vibrates and goes back to the white Honor text)
Does not work.
Omg guys thank you so much, it worked by pressing only the volume up button, thank you guys sooo much thank you i love you!!!
I've found a way to boot directly into bootloader/fastboot mode.
Press simultaniously the Vol+ and the power button until the red light lit up. Then instantly leave the two buttons and press the Vol- button until you see the fastboot menu. You're done!!
This trick to boot into Stock Bootloader/recovery has been known for years and is used on many different Android device
Still, it's great that you participate in this forum !
Boutchoo said:
This trick to boot into Stock Bootloader/recovery has been known for years and is used on many different Android device
Still, it's great that you participate in this forum !
Click to expand...
Click to collapse
I see you don't get it. Up to now the only way to get into fastboot was via "adb reboot bootloader". Or from a successfully installed TWRP.
The "for years" known combinations will get you only into Recovery (Power + Vol up), FTM (Power + Vol down), or into EDL respective the useless DFU mode (Power + Vol up + Vol down). In case you've killed your recovery and your bootimg you now have a additional option to come back to a functional system. Especially for the A2017g with the useless DFU mode.
Can anyone with bricked A2017G confirm?
Controllerboy said:
Can anyone with bricked A2017G confirm?
Click to expand...
Click to collapse
Confirmed NOT WORKING .
It doesn't matter if it's working or not. Thanks for the info anyway.
Neither stock recovery nor fastboot will help if you're stuck in DFU mode for G model. You can't do anything to recover the device in neither mode. All what helps is previously had enabled "allow BL unlock" in developer options. This gives you the possibilty to flash a stock ROM from external SD card. It still needs to be aproved from a bricked "DFU" user!
Stoicho87 said:
Confirmed NOT WORKING .
Click to expand...
Click to collapse
Would you kindly tell us what is not working? Don't you see the menu? Or don't you know what to do with fastboot?
In case you managed it to get into fastboot the next step would be to get into edl by using this trick. -->
http://forum.xda-developers.com/and.../guide-how-to-reboot-to-edl-fastboot-t3394292
@tron1, all this does not work. I tried cause I had a bricked (DFU) device. I needed to send it in for repair. And gues: they changed the motherboard.
Even the fastboot_edl results in "remote unknown command". Nearly all commands in fastboot for Axon 7 are disabled bei ZTE.
I will try if it's possible to reboot to edl with the fastboot from the unlock procedure from drakenfx.
forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
ZTE crippled the loader in a bad ass way. But they left the flash command inside. So it should be possible to flash at least a working recovery to the system if you manage it to get into bootloader. As long as my phone is working I won't try it on it. So volunteers!!
Hint -->
fastboot flash <partition> [ <filename> ] write a file to a flash partition
fastboot erase <partition> erase a flash partition
I there a way recover such a bricked device?
I could only boot into bootloader. If i choose boot recovery the phone only shows a red light.
If i choose start its the same red light.
Or should i contact ZTE for a new phone?
Stoicho87 said:
Confirmed NOT WORKING .
Click to expand...
Click to collapse
I have bricked my Axon 7 several times this weekend, but new Qualcomm chipsets are unbrickable!!!!
1. There is a way to enter directly to EDL on most Qualcomm devices and works also in the Axon 7. Just ensure your phone is off, then press the three buttons at the same time. The red light will blink once, after that blink release the three buttons (you must be very quick releasing the buttons, otherwise the phone will turn on.
2. Plug your phone to your computer. Windows 10 should detect a new USB device QUSB_BULK without any warning message. Then you can use axon7tool to flash the original boot and recovery (stock or tenfar's signed TWRP).
After that, you will be able to enter into recovery, do a factory reset and then you will be able to restore de initial image from an SD formatted as FAT32 (no, exFAT is not supported by stock recovery) in case of stock recovery. Sideload will not work, always stop before finishing the transmission.
Oki, this is fine for you because you have the US version of the Axon the rest of the axon World is f..ed up with an useless so called DFU mode. Happy Birthday for your Axon.
Sent from my ZTE A2017G using XDA Free mobile app
Oki said:
... unbrickable!!!! ...
... ress the three buttons at the same time. The red light will blink once, after that blink release the three buttons (you must be very quick releasing the buttons, o ...
... Then you can use axon7tool to flash the original boot and recovery (stock or tenfar's signed TW ...
Click to expand...
Click to collapse
That did the trick. Thanks
Any idea on why when i tried to enter bootloader mode on my Axon 7 (that i received 1 week ago), it stays on ZTE logo and nothing else happens... What is weirder is that there's a red light and my computer detect it when i do "fastboot devices" but i can't unlock the bootloader...
I tried to downgrade on B02 firmware and nothing... i'm beyond going insane right now.... :-/ It's like ZTE blocked on purpose the access to the bootloader mode...
I know that this thread is more of same, but I didn't found any answer that helps me.
The story is:
My Xperia 2363 M4 Aqua Dual recived a call and I lost it. Then when I took it and turn on the screen to see the caller, my device just restarted and went to the purple waves screen, but stuck there the system didn't start. Since this, the only thing that phone do is that, it never starts the android system.
I've tried everything that I read
So the things I've tried is:
Restart the phone by holding the power + vol up buttons
Turn off the phone by holding the power + vol up buttons until 3 vibes
Turn on the phone holdin the vol up + vol down buttons
Reinstall software by xperia companion but the software didn't start the process
reinstall software by flashtool but the device isn't found by the flashtool
connect the phone on pc holding vol up button
connect the phone on pc holding vol down button
connect the phone on pc holding vol up + vol down buttons
connect the phone holding all the buttons
the fastboot and bootloader modes don't enter and the pc says that usb device can't recognized by the windows.
I have no ideas of what i do
Can you help me?
Does it flash a blue screen briefly before restarting / crashing?
DarkerJava said:
Does it flash a blue screen briefly before restarting / crashing?
Click to expand...
Click to collapse
Thanks for reply. No, didn't flash a blue screen, it just restarted like when we hold the power +vol up buttons
And it not keep restartin, the phone turns on and stays on the waves screen. don't start the system so as don't restart.
If you device is not being recognized by you PC, Try fastbooting the device using a linux (Mint, what i used for similiar issue), it will hopefully recognize your device and you would be able to flash it.
sanjyot said:
If you device is not being recognized by you PC, Try fastbooting the device using a linux (Mint, what i used for similiar issue), it will hopefully recognize your device and you would be able to flash it.
Click to expand...
Click to collapse
Thank You, I'll try this.
sanjyot said:
If you device is not being recognized by you PC, Try fastbooting the device using a linux (Mint, what i used for similiar issue), it will hopefully recognize your device and you would be able to flash it.
Click to expand...
Click to collapse
I tried this one, but, is the phone that not enter on fastboot mode. I tried with my another devices and it worked well, but the M4 aqua, just refuse to enter in fastboot mode and only recharge the batt. to be more specifc, the green or blue lights don't lights
korkinova said:
I tried this one, but, is the phone that not enter on fastboot mode. I tried with my another devices and it worked well, but the M4 aqua, just refuse to enter in fastboot mode and only recharge the batt. to be more specifc, the green or blue lights don't lights
Click to expand...
Click to collapse
could you fix that problem bro?
advancel said:
could you fix that problem bro?
Click to expand...
Click to collapse
Unfortunately no. I couldn't fix this yet, it is because I' can't go fastboot mode on my device
have you any other suggestion?
no i have that problem by the way if you can fix the prob. then contact me pls
The other phone you tried was a Xperia?
And are you on Win8 or Win10 because if you are, you have to install the drivers in unsafe mode(Don't remember how it's really called).
Furthermore if you don't have anything important in the phone try flashing a new version of Android or the same but do a clean install I.E Wipe everything and leave like new by installing with Flashtool(unsafe mode too, because it needs drivers if you are on Win8>10 when installing)