ZTE Axon 7 min bootloop - ZTE Axon 7 Mini Questions & Answers

I have ZTE Axon 7 mini and after successfully flashing the lineage OS onto my device it started to have some issues and so i booted into TWRP and accidentally checked all the boxes when erasing the previous OS so i deleted everything on my phone. Now when i try to boot my phone it is stuck on the ZTE logo and i cannot do anything besides boot into android recovery mode where it gives me 8 options. when i try to update from adb it gives me the error (assert failed:getprop("ro.product.name") == "P852A12"). When i try to update from SD card it says (sorry you can't SD card upgrade). What should I do to fix it?

Related

[Q] ZTE Blade G V880G Problem (maybe soft bricked)

Hi all,
I have ZTE Blade G (mts telekom) phone and I've installed CM 10.1 from here http://forum.xda-developers.com/showthread.php?t=2591092 it all went well but my phone was still locked to my provider's network (I thought it would be unlocked for all networks in CM but it wasn't ) and the secret codes did't work because its wasn't ZTE android so I wanted to go back and install official android from ZTE for my network from here http://tw.gs/XaRd0Y so I put original stock recovery back from CWM and put the update.zip file on my SD card but when i tried to update this error occurred assert (getprop ("ro.build.product") == "ZTE-BLADE-G"); so I've done some searching and found out that you need to change build.prop in android to match this description so I've changed it and restarted the phone... of course it didn't help the update and now it can't boot CM because of the change in build.prop and it cant boot CWM because it doesn't have one it's on the original factory recovery... (catch 22). So to sum it up I can't boot my CM or any other android system on my phone, I can only get into factory recovery with (Power+Vol up button)
So my questions are:
Can I go back (install) into CWM recovery from factory somehow when I can't boot up my phone I can just go in factory recovery and nothing else?
Can I somehow change build.prop in my phone without booting up android?
I have an LG phone and I have used LG KDZ updater and with an official firmware I can unbrick my phone is there anything similar to that with ZTE that I can use on this phone?
Please help me boot up my phone with any kind of android I'm stuck with nothing
Just do a factory reset from your recovery. hit thanks if i helped!

Weirdly bricked ZTE Blade Q Lux

K, so i was attempting to install cwm recovery, as my ZTE's recovery practically commited suicide. i try to install it and was succesful. Using this to my advantage, i decide to downgrade from android 5.2 to cyanogenmod 7. every time i attempted to do it from my phone, file verification failed. this file was from the site and i attempted many times with redownloads. i boot my device into fastboot using adb. now, it wont respond to anything. ADB sees nothing, Recovery has yet again commited suicide, and i cant power it up. I've removed the battery and put it back in. i've taken out storage as well and tried. so, is my phone f**ked? or can i save it.
details:
Recovery: CWM 6.x.x.x
ROM: Stock
Device: ZTE Blade Q Lux
All drivers were installed correctly. all files were built for the phone and official.
i am happy to add more if needed.

I think I brinked my phone. Please help [SOLVED!]

Hello. I tried downgrading from the latest ASUS firmware to Android 6.0.1
I used this tutorial to install the raw firmware: http://www.asus-zenfone.com/2016/12/asus-zenfone-3-raw-firmware-and-asus.html
Went all the way to the last step when the app hanged. ASUS Flash tool went all the way saying
Code:
Run flash image script ...
It was hanged there. And as per this video, went all the way to the end where it showed the "code bar" on the right (https://www.youtube.com/watch?v=P8xg7A-P7Ak)
This is when the "Android" uninstalled driver showed up in Windows. This is under "Other devices - Android". I tried updating this driver using the ASUS_Android_USB_drivers_for_Windows found here: https://www.asus.com/Phone/ZenFone-3-ZE552KL/HelpDesk_Download/ but it wouldn't install the drivers.
Note that I used these ASUS USB drivers to get the ASUS ADB Interface installed. As per the tutorial I showed in the very first paragraph, I never got the "ASUS Android Bootloader Interface". This is what I think this "Other devices - Android" is found under Computer - Manager - Device Manager.
Most tutorials on the internet shows that the "ASUS Android Bootloader Interface" should be installed using these drivers found on ASUS website, the ASUS_Android_USB_drivers_for_Windows.
Now of course because I unplugged the phone, it will continously stay on the Android splashpage showing the loading circle infinitely.
As a last attempt I tried installing the "stock", not "raw" firmware (the one I wanted to install WW_13.16.5.49 but ASUS would not let you downgrade using the recovery "power+volume down" and using "Apply update from microSD card". It would give the
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
)
Well, after it brinked, I tried it again and this time it DID install WW_V13.16.5.49. Was succesfull. But after the ASUS splashscreen it's still stuck in the booting process.
I am very sorry if my post is convoluted but I tried explaining everything I did. Any way to un-brink it? I think maybe if I figure out how to properly install the ASUS Android Bootloader Interface, I can try again ASUS Flash tool and install the raw image and maybe that will fix it?
Please help. Any questions if my thread is too confusing, please let me know and I will answer it. I can't even turn off the phone. While it's stuck into the load splash screen, if I press the power button it just restarts, not turn off.
I still have access to fastboot (pwr + volume up) or recovery (pwr + volume down)
EDIT: Phone won't get recognized anymore in ASUS Flash Tools. Serial number won't show up to select
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
wang1chung said:
Factory reset and delete cache/dalvik through recovery and post back. It'll take 5-10min to boot up after that. You should always delete cache/dalvik after flashing.
Click to expand...
Click to collapse
Thank you, this actually worked!!
Aaaand, it's actually on the version 13.16.5.49!!!! THIS IS EXACTLY WHAT I WANTED!
So apparently by brinking my latest nougat 7.0 update from ASUS via the ASUS Flash Tool trying to flash the .RAW 13.20.10.137, the standard recovery system (power+volume down) allowed me to install the 13.16.5.49 version. Then I assume remnants files didn't allow to properly boot, and your idea to wipe cache and factory reset fixed that!
What is so great is that I was scared that because the .RAW firmware was newer than the version I needed (13.16.5.49), I wouldn't have been able to install it. It was the same problem initially, when I tried to install 13.16.5.49 directly via recovery over the latest nougat 7.0 version from ASUS, but it was giving me
Code:
Warning- No file-contexts. This package is for "ww-phone" devices, this is a E:error in /side load/ package.zip (status 7) Installation aborted.
I think this error was due to the fact that ASUS won't allow older firmwares to be installed over newer ones, as per their webpage
https://www.asus.com/support/faq/1009748
Code:
You can not change the SKU from one to another, e.g., WW -> TW, and also can not downgrade your firmware, e.g., V2.20.40.13 -> V2.19.40.18
So in the end, what allowed the 13.16.5.49 stock firmware to be succesfully installed? The installer not detecting a proper firmware anymore because of the damaged update due to ASUS Flash Tools hanging because my computer won't install ASUS Android Bootloader Interface?
Glad you got it going :good:

Need help unbricking my Axon 7

So I'm quite a noob when it comes to flashing/recoveries/bootloaders and things like that, and that's most likely the reason why I got myself into this situation. Anyways my axon 7 (which I bought in China a year ago) was running fine yesterday, just a little bit slow. I had installed TWRP on it, and flashed the US rom along with SuperSU root. However last night was when things all went wrong.
I tried to flash the xposed installer from twrp which caused me to not get stuck on the AXON boot screen when I tried to restart.
Seeing that my phone was now softbricked, I thought since my phone was already running so slow, maybe I should take this opportunity to install lineage os and at the same time unbrick my phone. Win win right?
But when I tried to flash lineage os, I got the red error 7 message and problems with mounting /system. I went into the zip and changed the updated script and tried reflashing the new lineage os zip. That didn't worked and I still got error 7 messages.
So I this point I was quite desperate to get my phone back so I tried to reinstall the stock axon 7 rom which didn't work as I ended up with unable to mount /system errors.
I tried to reinstall twrp but my pc wouldn't recognize my phone while it was in fastboot mode.
I tried this tutorial IGNORETHISTEXTCASUEICANTPOSTLINKSYETJUSTCOPYTHELINKTHATCOMESAFTERhttps://m.youtube.com/watch?v=T-7neHzSIvc but got stuck on the step where I needed to reformat my data partition as exfat (the progress bar just kept going). After waiting 3 hours for it to format, I thought it was frozen or something because the guy in the video was able to format it instantly.
So I force restarted my axon 7 and now I'm here:
1. Most of the time when I restart my phone, it gets stuck on the zte logo
2. occasionally it gives me the option menu (with power off, fastboot, recover, etc.)
3. If try to use fastboot, my pc won't recognize my phone
4. If I use recovery, I get stuck on the teamwin screen, but my computer seems to recognize my phones presence, in the fastboot command prompt the "adb devices" command displays my phone as "10109dd offline", if I run any other command such as reinstalling TWRP, the command gets stuck at "waiting for device"
5. Obviously can't boot into android cause my whole system partition is wiped
Anyways that's the state I'm currently in (all because I wanted to install xposed installer ) and I would appreciate any suggestions!
Make sure all your phone drivers and adb are up to date.
Also try the Zadig drivers these might help too.
In Windows device manager it should show as,
Qualcomm HS-USB QDLoader 9008"
If you get stuck you can always try using an Edl package.
I have and Edl help page here>
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
Syberclone said:
Make sure all your phone drivers and adb are up to date.
Also try the Zadig drivers these might help too.
In Windows device manager it should show as,
Qualcomm HS-USB QDLoader 9008"
If you get stuck you can always try using an Edl package.
I have and Edl help page here>
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
Click to expand...
Click to collapse
Holy moly, you saved my life Syberclone! I was able to flash back my rom through EDL mode and my A7 is saved! :angel: Thanks a million!:good:

Huawei P8 Lite Bricked

I've recently repaired my Huawei P8 Lite after it's screen was mutilated and such and I decided to try flash a different ROM onto the device, I wiped my entire device and restarted it instead of flashing the ROM I needed to and I got led into a bootloop which presented me with the Huawei logo until the device just died from battery loss.
I was able to get myself into TWRP before the bootloop occured everytime the phone auto-restarted and I tried flashing the ROM which was Resurrection Remix V.6 and in the end near its installation I did notice it printed out two lines saying "Unknown command" and then continued to say it finished the installation succesfully but when I restarted my phone, there was nothing but the bootloop.
I ended up getting frustrated at left my phone on my desk untouched and now I'm presented with a Rescue Mode panel when I try to boot into TWRP to try and flash a stock ROM. The panel presents me with a message asking me to
Please update system again
Func NO : 11 (recovery image)
ERROR NO : 2 (load failed!)
I'm able to hold my power button and volume button up to boot into Huawei eRecovery but it's as useless as this phone currently. Please note I've tried methods involving connecting my phone to my PC and troubleshooting it from here but my PC does not recognize my phone at all, it never did whilst it was running the stock firmware either. Any help is gladly appreciated.
My phone model for anyone wondering : Huawei P8 Lite ALE-L02
Update :
I've managed to flash TWRP onto my device again after enough times battling the rescue mode, I no longer get the function errors however I have discovered a problem that runs deeper than just a few missing .img's. I've re-flashed Resurrection Remix again with gapps and no errors were presented within the installation processes, I rebooted my system and got put straight back into a boot loop. I decided to go back into recovery and to my surprise there's nothing inside my internal directory besides an empty TWRP folder.
I'm assuming that my device is not properly installing/saving the files where they need to be.

Categories

Resources