My ZTE Blade AF3 (T221) can't boot into fastboot nor normal mode (so I could use adb). I can only use recovery mode. I tried to flash the stock firmware through apply update option, but the latest available firmware online is 1.0.4 and the recovery is on 1.0.5 (DIS_RU_QB18D_P731A20V1.0.5). That wouldn't be a problem if the update-script didn't check for the version of the current firmware and abort the installation because it's newer. I tried to delete the checking code from the script, but then the file verification check fails. I didn't find an option to turn that check off and I can't flash a custom recovery due to the lack of fastboot mode.
There is also another mode to which it can go into if I just let it boot without pressing any buttons. The ZTE logo appears, then disappears and the white screen remains. In Device Manager it's identified as "Gadget Serial". I don't know if I could use it somehow.
Is there anything I could do to flash the stock ROM or another recovery to the device?
Thanks for help!
Edit: If someone knows a method to boot into fastboot other than holding down the volume - key and plugging in the USB cable the advice is more than welcome, I just think I tried every kind of button combinations (although I wouldn't have guessed myself the process to go into recovery mode, so there's always the chance).
You already solved it? Maybe i can help you!
codeblvnc said:
You already solved it? Maybe i can help you!
Click to expand...
Click to collapse
Nope, I abandoned it. I even wrote to ZTE support, but they said I should wait for the newer firmware to be uploaded to the site (which I kept checking for a while, but nothing happened, so I eventually stopped). I haven't used that phone since, it now lives in the bottom of a drawer somewhere .
If you have any tips, I can try to make it work, but it's not that important anymore, so don't bother if it's too much work.
geiszla said:
Nope, I abandoned it. I even wrote to ZTE support, but they said I should wait for the newer firmware to be uploaded to the site (which I kept checking for a while, but nothing happened, so I eventually stopped). I haven't used that phone since, it now lives in the bottom of a drawer somewhere .
If you have any tips, I can try to make it work, but it's not that important anymore, so don't bother if it's too much work.
Click to expand...
Click to collapse
I had this phone, i need to check but have some firmwares in my personal computer. I will try make a easy-understanding tutorial to you
Related
Hi! I have a bricked ZTE Libra (Sapo A5 in Portugal) and no mather how much I search for solutions I only seem to make things worse, so I was hoping someone here could help me.
Things started to go wrong after flashing a CyanogenMod rom. Everything worked except two things: I couldn't use anything that required my SIM card (so no phone or messaging) and I could not access the recovery screen (clockworkmod).
Without the recovery screen, I turned to ROM Manager but since it uses clockworkmod to do its work it didn't help.
Then I started trying other ways to recover my phone, until I tried ADB which allowed me a shell in my android. But then I broke it all by doing "wipe system" which cleaned my system of everything that was still working and left me with an expensive brick.
Now all I can do is boot until I see the green droid. If I don't press the volume buttons it goes into "device" mode and I can see it listed under "adb devices" but have no idea what to do with it.
If I press the volume button down to go into recovery mode it keeps flashing but never really goes anywhere.
If I press it up to go into the bootloader it stays the same and the only thing I can use to tell me something is different than the normal mode is that lsusb reports the vendor as "Google Inc." instead of what it reports in normal mode: "ONDA Communication S.p.A.".
With this I'm not even sure if I can get to the bootloader or not, but even if that is the bootloader, I have no idea what to do with it that might help me recover my phone.
By the way, I'm trying all this on Linux, although I could try solutions in Windows if required.
Can anyone tell me what can I do in this situation?
Ok, maybe my first post wasn't that easy to answer, so I'll make a simpler question to see if someone can help me.
What can be done at my android's bootloader? What is it for and what tools do I need to use to do it?
You could try installing ClockworkMod recovery using wbaw's guide here http://forum.xda-developers.com/showthread.php?t=1319257 Once that's installed you should be able to flash a new rom with it.
In bootloader mode you can flash a new kernel or recovery image using fastboot.
If you follow that guide that I wrote & Amphoras linked to then you should be able to get a working clockworkmod installed and then you can use that to flash a working rom, or restore a backup.
Thank you both, I'll try what you said as soon as I can and then I'll let you know if it worked!
Ladies and gentleman, today a miracle happened, my ZTE came back from the dead!
Apparently the problem was that I installed some GEN2 applications on my GEN1 model.
I found this while reading the tutorial you suggested, after which I upgraded my ZTE to GEN2 which allowed me to slowly recover everything else.
So, I have to say, thank you very much, and I hope I won't need your help again anytime soon! xD
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Few questions first... (I am an Android n00b, but have had issues and flashed custom ROMs about 9 times now.)
Did you make sure to see if the device was properly detected in your OS of choice beforehand? Installed all the software to do so?
Did you install either CWM or TWRP to the device?
Make a recovery in case of issue?
I followed the topic (in this very forum) about flashing. I had some issues being new and all, but got it right... BEFORE I did an actual flash.
[GUIDE] TF300T Unlock/Root/Flash for Factory JB Devices (newbie friendly)
I am using the latest TWRP instead of the guides CWM advice. Due to CWM failing to create a backup for me. I felt not having a backup plan, was something similar to going to a redlight district without a rubber. Which means... What if something goes wrong, how will I fix it?
Does the device detect? Can you move files to the device from your computer?
techknewz1 said:
kinda of a new at this. basically my tablet boots with asus logo and top left says "the device is UnLocked"
tried to flash cyanogen mod and put some wrong files.
i know its bricked but cant do much. Vol- + Pwr doesnt get me anywher
Vol+ + Pwr makes some recognition on my computer but cant do much. like fastboot wont recognize as a device.
pls help\
UPDATE: Got it to go in APX mode. and got drivers installed. dont know whats next...
thanks in advance
Click to expand...
Click to collapse
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Xynergy said:
Hey there, just curious as to how you managed to 'put some wrong files', what exactly did you do to achieve this?
If you can still get into recovery and you have fastboot hooked up, you can proceed to either:
re-flash the correct CWM version if your recovery is broken, or
upload the CyanogenMod package you want to install to your device and simply wipe & flash!
I don't recommend installing last week's nightlies, rotation is still broken. Not sure as to what version last worked.
Good luck!
Click to expand...
Click to collapse
So here is what happened. Basically i tried flashing files and put it for the wrong tablet. Now i can only get into apx mode and fastboot doesnt recognize it and neither does adb recognize it.
Hello, I am a new member and I'm having a hard time trying to fix my phone.
Currently, I can't go into any mode. I have neither fastboot or download mode.
I also can't get into my twrp through factory reset since it tries to reboot my phone.
However, whenever it tries to reboot, I get error: Boot certification verify and the screen goes dark.
I have tried to solve it by following this thread:
http://forum.xda-developers.com/showthread.php?t=2582142 but nothing has worked so far.
Can anyone please help me?
rawtomato said:
I also can't get into my twrp through factory reset since it tries to reboot my phone.
Click to expand...
Click to collapse
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?
iowabowtech said:
By that do you mean you can't even get to the factory reset screen at all? Or you do get there but when you select the option to reset, it simply reboots at that time?
Click to expand...
Click to collapse
I get there and selecting reset reboots the phone. However, an error about phone ceritication verify pops up
If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?
iowabowtech said:
If you have access to a Windows machine, plug it in while on that dark screen and open device manager. Does anything show up relating to Android, Qualcomm, etc? If need be, unplug it while watching device manager then replug. Is the device showing up at all and if so, what's it called?
edit: also try long pressing power for 15 seconds to turn off the device completely. Then short press power (2-3 secs) as though restarting the phone from an off state. Does it boot into the OS then or no?
Click to expand...
Click to collapse
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all
rawtomato said:
Thanks for the reply! I have tried that and my computer recognizes my phone as LGE Android Phone. It seems like I can't get into any mode at all
Click to expand...
Click to collapse
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.
iowabowtech said:
Hmm, that's not so good. Most of the people who've been experiencing this have accepted either willingly or unknowingly, the new vzw ota update. But others have still been able to boot into the OS normally. It's booting to system from recovery that's been the only problem for them which makes sense considering aboot and boot were updated with the ota. That will break the loki <>TWRP connection since we need a downgraded aboot (JB) and a patched kernel for proper function. Hence the secure boot error.
Click to expand...
Click to collapse
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.
Be very careful
rawtomato said:
Where should I go from here to fix my phone? Sorry for no knowledge but I am still new to rooting an android phone..
Click to expand...
Click to collapse
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors
iowabowtech said:
I would hold tight for awhile and see if anybody else has a more simple plan because I do not. The only thing I can think of with no boot, no recovery, no download mode AND no bulk mode, is to try and force bulk mode as described here:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
...then use Linux to fix as described here:
http://forum.xda-developers.com/showthread.php?t=2582142
(though I would ammend those intructs slightly to include the dd writing of boot and laf also to restore download mode)
...and then use a restored download mode to return to stock using a vs980 tot as described here:
http://forum.xda-developers.com/showthread.php?t=2432476
An unfortunately long and less than simple path back to a booting phone, especially for someone new to root. Again, hopefully somebody else can offer up a better plan.
Click to expand...
Click to collapse
It seems like i have messed my phone up really badly.. Thank you for the ideas but yes, I will continue to look for more options for now
Edit: I have never tried the first method you showed me before but I have tried the second and the third method and did not work. Would I be able to fix it if I take it to a shop?
virginwidow said:
I was in exact same spot, until I got into the dd / phone partitions part under Linux. AN ERROR THERE COULD BE FATAL.
Please be very careful, look for a thread on recovering from "Secure Boot Error" (havent found one specific for that yet) Alot of people had success using the Linux method, I did not (vs980) probably because of a typo (keyboard error, mine) using the dd command.
I'm not saying don't try it, I AM saying use extreme care make no keyboard errors
Click to expand...
Click to collapse
Thanks for your reply but I absolutely have no idea how to get into the dd / phone part using linux. I'll continue to look for more threads close to my problem but I have no clue as of yet.
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
So my cousin has Poco M3, and it is affected by the deadboot problem. The phone did an update and she restarted it. Well since its affected by deadboot, it didnt really boot up. And now, when we open it (we were able to open it up by following some youtube videos), its saying "System has been destroyed". I tried connecting it through the usb cable to my pc but its not detected (since its not really booted up). Its showing as Quectel. Please help us fix this. We cannot afford to go to a tech. Please help
aerith01 said:
So my cousin has Poco M3, and it is affected by the deadboot problem. The phone did an update and she restarted it. Well since its affected by deadboot, it didnt really boot up. And now, when we open it (we were able to open it up by following some youtube videos), its saying "System has been destroyed". I tried connecting it through the usb cable to my pc but its not detected (since its not really booted up). Its showing as Quectel. Please help us fix this. We cannot afford to go to a tech. Please help
Click to expand...
Click to collapse
I assume that you didn't unlock the bootloader, and you simply take the update and then the update failed to be installed.
Not sure what you mean with: "when we open it (we were able to open it up by following some youtube videos"
Assuming that my guess is right, then the first you could try is booting to the stock recovery manually, from the device power off, pressing volume up + PWR buttons, on the recovery screen, tap on wipe data, this will completely erase your data and settings. Try to reboot.
If this doesn't solve it then download the latest firmware for the device to be flashed through recovery (zip format) https://xiaomifirmwareupdater.com/archive/miui/citrus/ transfer it to your SD card and apply the update from it, unfortunately not all the recovery versions offer a menu to do that, check first if in yours, this feature is included.
SubwayChamp said:
Not sure what you mean with: "when we open it (we were able to open it up by following some youtube videos"
Click to expand...
Click to collapse
Oh i meant when we boot it up. the phone is affected by deadboot, so we had a hard time booting it.