Database Users

[Q][SOLVED] Bricked ZTE Libra

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

asus tf300t bricked

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.

[Q] [VS980 32GB brick] - No download mode, some form of TWRP

Hello,
I've done a lot of looking through these forums, so I can say that the following doesn't work:
* The solution where and adb command from the TWRP terminal (starting with if=dev/zero) does not work. It does not have the files/directories those commands look for.
* I will be currently trying the solution that boots into Linux and uses gdisk to manage partitions. I have hope in this one, but I am making a head start of looking for advice in case it doesn't.
Any .tot or .kdz methods are useless as my phone /cannot/ get into download mode. If there is a way of telling it to over a cable, like you can with fastboot, I would love to know.
How the problem happened:
Ironically when I finally settled with a rom and wasn't going to do any flashing in the near future, I decided to make a nandroid backup.
I watched its progress now and then and it was working regularly.
Once it finished, I slid to reboot, and walked away. When I came back, the phone was on the LG logo with pulsating blue/green LED.
I went to restore from the backup I had just made, and that's what really messed things up. Ever after, all directories are shown as empty, and if you tell TWRP to do any function like flashing or recovering, it starts, but then crashes and reboots.
To begin with, occasionally it /would/ show my directories populated as they had been... but the crash and reboot thing. Now it never shows anything in the directories.
Since then, I /did/ manage to get into Fastboot ONE TIME, but things didn't work out on the computer end for Flashtools because I was on my campus network.
I have held out for a similarly low odd since, but I have spent hours, and almost all the battery, holding the power up button different times and ways and plugging the USB cable in at different times and ways.
I had Xdabbeb's stock variant installed, XCeed kernel, latest TWRP (thank God for heat control or I would have a screwed screen by now!) and let me know if any other details would be helpful.
I'm about to boot into Linux, I'll see how far I can follow this solution:
http://forum.xda-developers.com/showthread.php?t=2582142
Has anyone been in this spot? What worked?
EDIT: Ubuntu solution no good - my device does not show up as qhsusb_bulk or in sda or sdb tables.
EDIT: I MIRACULOUSLY got into fastboot! Instead of selecting power off or just holding power etc. in TWRP I said to reboot as system - holding the VolUp, even with the cable already plugged in, got me into FastBoot!
Trying the .tot method.
EDIT: I could weep. .tot failed because of
[ 8:50: 3] LAF_READ_GPT_FAILED
[ 8:50: 3] LAF_READ_GPT_FAILED.
[ 8:50: 3] LAF retrieveGPT() failed.
So I thought I should reboot it into download mode (which it was already in...) and I'm back to it being impossible to attain. What worked from TWRP the other time was just lucky.

Here's what I did when I royally screwed up my ls980:
I grabbed SRKTool and nuked my download mode. Then when attempting to enter download mode I was instead kicked into fastboot. From there I flashed stock partition images (in my case aboot, boot, laf, and recovery), rebooted into download mode (which should be restored when the laf partition is flashed), and then was able to flash a stock tot with the LG software. If your tot flash fails because of a device name mismatch I can help you with the hex editing of the tot file as well.
All data lost, but phone was unbricked.
Sent from my LG-LS980 using Tapatalk

dgranillo said:
Here's what I did when I royally screwed up my ls980:
I grabbed SRKTool and nuked my download mode. Then when attempting to enter download mode I was instead kicked into fastboot. From there I flashed stock partition images (in my case aboot, boot, laf, and recovery), rebooted into download mode (which should be restored when the laf partition is flashed), and then was able to flash a stock tot with the LG software. If your tot flash fails because of a device name mismatch I can help you with the hex editing of the tot file as well.
All data lost, but phone was unbricked.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
dgranillo, I greatly appreciate your reply.
I managed to get it into download mode one more time (the rate must have been 1 in 80 or fewer, but I had no choice!), and flashed a .tot file (an old one... Jellybean!)
Ever since then, I have been able get into download mode as easily as it should be. One or two things to note though.
Any further flashing of .tot files ends at 6% with the exact same errors as pre-"fix".
Even the successful flash didn't boot successfully at the end, but had a red-triangle android figure
Sometimes it boots successfully into the stock rom, but others it goes into LG logo and blue/green LED, as before.
After a successful boot, it will die/go back into a boot loop some time soon after.
This leads me to think that a significant part of this all happening (I mean, I only did a nandroid backup to start this all off...) is a hardware issue, maybe to do with the flash storage.
By huge luck, I am withing the last 2-3 days of the 30 day period after buying it refurbished from a seller who gives full refunds including postage. Convinced something's not quite right with the hardware, I will be sending it back. I simply can't waste any more time I could be spending with my wife, or out of a returnable period, seeing if there is a fix to it.
Like I said, it means a lot that you would respond to help. Maybe parts of this are useful to someone. Thank you!
Any advice on removing the "rooted" red writing from the download mode screen? Especially as I'm pretty sure it isn't any more.

That is beyond my knowledge. I'm sorry. Haven't seen or read about anything like that before.
Sent from my LG-LS980 using Tapatalk

dgranillo said:
That is beyond my knowledge. I'm sorry. Haven't seen or read about anything like that before.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
dgranillo, I am sincerely thankful for the time and consideration that you have given my problem.
I will mark this as solved because I did get past the initial problem, and I am thinking the further problems might be hardware.
Thank you again.
EDIT: I can't see how to edit the topic title, perhaps a mod has to mark it as solved.

Zte axon 7 mini edl backup needed - lost stock recovery!

Hi Guys,
I would greatly appreciate any help. I have somehow lost the TWRP & Stock recovery to my ZTE ANXON 7 MINI.
I had a custom rom and decided to flash a stock update zip and that rendered my phone unusable. I have managed to get it too boot to 6.0.1 B9 Spanish rom. However i have NO RECOVERY to flash the original update for the UK B12 Rom.
Im using the EDL Tool to flash. If anyone has the stock recovery to the B9 6.0.1 Rom that would be a big help. Or a EDL full backup.
All links to the ZTE website are down as they are no longer allowed to use ANDROID.
Also to note i have tried to reinstall TWRP however im left with either a white screen or nothing just bootloop.
Unable to unlock bootloader also as i have no fastboot option as recovery is dead
Thanks.

This are (full flash)EDL roms(need to extract to folder "flash\full ",and flash(not recovery ))B12.6Android.EDL.EU.Version
B13.Android7.EDL.EU.Version

A18xcn said:
Hi Guys,
I would greatly appreciate any help. I have somehow lost the TWRP & Stock recovery to my ZTE ANXON 7 MINI.
I had a custom rom and decided to flash a stock update zip and that rendered my phone unusable. I have managed to get it too boot to 6.0.1 B9 Spanish rom. However i have NO RECOVERY to flash the original update for the UK B12 Rom.
Im using the EDL Tool to flash. If anyone has the stock recovery to the B9 6.0.1 Rom that would be a big help. Or a EDL full backup.
All links to the ZTE website are down as they are no longer allowed to use ANDROID.
Also to note i have tried to reinstall TWRP however im left with either a white screen or nothing just bootloop.
Unable to unlock bootloader also as i have no fastboot option as recovery is dead
Thanks.
Click to expand...
Click to collapse
If you have white screen or ZTE logo then I know how to solve it.
Funny enough, hook the phone to the pc, open adb command and type adb devices.
You will see you pc recognises the phone in adb as recovery.
If this happens let me know and I'll show you how to push the entire bootstack to data/media, then write all these files to each partition. After that your twrp will work and you are done.
These happened to me about 10 times now and I even created a bat file which I double click and it does all the operations at once then reboots straight into twrp. Quite cool actually.
Nevertheless I'm also interested in an edl ROM to umbrick another axon 7 mini I have which is totally, utterly bricked.
I have opened the phone (still opened) and I managed once to get the test point to work and connect to qcn configurator but since then I never got it to be recognised again.
Good luck
Cheers

bius88 said:
This are (full flash)EDL roms(need to extract to folder "flash\full ",and flash(not recovery ))B12.6Android.EDL.EU.Version
B13.Android7.EDL.EU.Version
Click to expand...
Click to collapse
Mate, you don't know how helpful this post was.
I have bricked this [nasty] phone about 10 times.
but yesterday I learn yet another lesson, after trying to flash a new splash screen, the phone went totally dead, connecting directly in DFU mode.
I sort of panicked because I didn't have a fresh data backup and there aren't full EDL ROM for this phone easily found on the web.
After focusing in making sure my laptop had the correct drivers (loader/bulk/adb) and after I got confident to use the deepflash cable to move from DFU to EDL, bulk device recognised, right click on it and update the driver to show the loader (901D) then I though what would be the next step.
I did not understand the MIflash tool and the version I had didn't seem to work at all I scratched my had for a while.
I then used the EDL tool, placed your files into the FULL folder and ran through the steps...….mate.....that was beautiful.
I ended up flashing the full B13 on top of the B09 and the system works perfect without any loss of data.
Having learnt all this, I went brave and confident I could rescue my other axon 7 min, which had been dead for over 2 months. Although I had to open it to access the test point, after about 50 or more attempts, I had tried lots of combinations, test point again etc.
It turned out I have left the phone plugged in to the PC with every plug disconnected except the usb board and went to do the washing up. 2-3min later my pc gave a sound, loader 901D was already ready and I repeated the exact process.
You basically saved both of my phones!!!! THANK YOU

Stuck in rescue mode after tried flashing stock firmware

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.