Ever since I flashed TWRP 3.3.0 on one of my Z2 Pro devices, I can't actually get into recovery: the loading process halts on the ZUK screen, allowing no further progress.
Worse still, I can't get QFIL or adb to recognize the phone on my computer, meaning I can't flash a stock ROM to break out of this quandary.
Anyone experienced this problem, and, if so, how did you resolve it?
Related
Hello,
I am writing this thread for a friend of mine. He owns a Z1 - stock ROM, locked bootloader.
Today it started looping and I tried to fix it (telling him over a chat what to do). It goes through the bootanimation and then dies or while optimizing apps, or while starting them.
What we tried:
1) Wipe cache
2) Factory reset
3) adb sideload the current official CM onto it
Nothing helped, the error stays the same. We also tried this http://forum.xda-developers.com/showpost.php?p=64458076&postcount=4 but it never really recognised the phone (despite using the correct drivers and following the procedure) - it did not appear under ports (Windows 10?).
Is there any other way to unlock this goddamn phone? My Androids so far had an easily unlockable bootloader via fastboot. This would have, too, but in order to unlock the bootloader via fastboot you first have to allow this in the developer settings - which we can not reach due to the loop.
If you know some way to get a working ROM onto it, we would be very happy. In the end we will end up unlocking the bootloader and flashing another Recovery and ROM anyway. We only need some way to achieve this. I expect the way to do this will be the QPST thingy. Any ideas why it did not recognise the phone? He does not own a PC with another OS than Win10...
Thanks in advance for your help,
Moritz
EDIT: Looks like the sideload did work - after tens of reboots it finally succeeded and bootet straight into the ROM.
Took a lot of attempts, strangely.
Proceeding to unlock it
Mine does the same boot loop on CM13. After tons of different tries to fix it, i think it could have something to do with my fingerprint sensor which is not working anymore.
Maybe there is some kind of hardware malfunction and android crashes while initializing that piece of hardware.
So, I was following this procedure in wanting to get past the device's dead-end when going in a fastboot mode: https://www.youtube.com/watch?v=Wk5pl2aE8IQ
I had to go through this method in order to install TWRP to the phone and subsequently even be able to flash a custom ROM in it. The latest version of the stock OS caused my phone not to hold a stable Wi-Fi connection for some reason which Asus did not bother to fix. Otherwise, I will not even consider flashing a custom ROM.
As it appears, the hosted files needed for the flashing is incomplete in that the "asdf.img" is missing. This resulted to a brick that caused the phone not to charge, not to boot normally, or not go to recovery/fastboot mode.
However, I could still hear a sound whenever I try to connect the phone to the PC and automatically prompts to install a driver but would not.
Any idea on how to fix this?
Sending the phone to an Asus Service Center is not really an option for me right now. So, please, do not suggest that.
Hi, so I've been around here for a while and I've had pretty good success with flashing phones.
However, I have a Lenovo A6000 that is hardbricked with Resurrection Remix ROM:
https://forum.xda-developers.com/lenovo-a6000/development/rom-resurrectionremix-5-8-1-t3555184
Followed the destructions and now it is stuck rebooting. I'll see the neat RR logo start and then it will freeze, and then reboot.....over and over. I didn't wipe the phone and start new...thought I could install TWRP and wipe it, flash the new ROM and be done. Nothing like being confident.
So now, it is hardbricked after trying to flash the stock rom....and I cannot figure out how to fix it. Downloaded QFIL, and the stock ROM, installed the Qualcomm drivers, put the phone into Fastboot with VOLUME DOWN + POWER BUTTON and QFIL see's the phone but gets stuck on fail sahara error. I have done countless searches online and the videos I have found don't resolve the problem. Google search turns up no solution. There is a thread here that basically just dies with no solution.
The phone ready for the trash bin?
Also tried Lenovo Downloader and it also gets stuck on step Sahara.
The little cheap phone belongs to a girlfriend of mine (she's a single mom) who has no money to buy a new one, and everyone here knows how awful the stock ROM. So I'm trying to help her out and flash this bugger. I had an A6000 before I bought my MiMax2 and it wasn't a bad little phone after getting RR on it.
Will anyone be willing to help?
?
So no one is willing to help with this problem huh?
From what I can tell the phone is junk now....even though both QFIL and Lenovo Downloader will see it when I plug it in.
Well...thanks anyway.
So who wants to be paid to help fix this problem? You must have PayPal and must be able to solve the problem.
I guess the problem is that a lower version OS can't be installed via QFIL. For example if the phone got bricked in lollipop you can't install kitkat on it via QFIL. Although the same version OS might work (lollipop to lollipop) and of course higher version OS will work.
I have also had some version of QcomDLoader flash tool work where other flash tools simply failed or even older versions of QcomDLoader didn't work.
This is the one that worked for me https://androiddatahost.com/dt3gh9
move firmware (SW_LENOVO BLABLABLA) to loca disk :C
restart pc > then flash again.
Hello, Dear XDA-Developers.
I was trying some custom ROMs but when I installed Viper4Android and flashed it using Magisk the phone stucks on boot
However I have another problem, I found out that the internal storage of my phone got too small after upgrading into another version of Android, so I wanted to get back to Android 5 stock firmware completed to format the internal storage and not partitioning it as I thought so I tried to flash it in TWRP recovery but sadly after that I bricked the bootloader and the recovery. Next, I decided to flash a board image ALE-L02&L21&L23_MAA001077_Board_Software_general_05021SJN using IMAGE Download Software - IDTML01Ver1001, Still, the process got interrupted maybe because the phone was restarting itself and now I'm getting a screen that shows error after showing Huawei Ascend logo. Is there any chance to fix this dead phone but consider that my pc is no longer detecting the driver that I used to flash the board image, and I can't even turn off the phone now except if I let the battery dies.
Notice: I don't dare to use test points if there is no other choice how much it usually costs to fix it?
Hi,
I'm not sure I'm posting in the right section but, I had a really bad experience upgrading to android 10. Really sluggish and slow... so I tried to downgrade to android 9 by using Lenovo's Rescue and Smart Assistant.
What I did, is to find the stock ROM for my model, and replace the files downloaded by the Rescue Assistant (which downloaded the latest firmware). The process went through, but now the device wont power on.
When I plug in the USB, windows makes a sound, the charging light comes on, but The rescue Assistant nor SP flash tool is able to flash the latest firmware.
Is it bricked for good?
Model : TB-XF606F
Hardware number : 60
Maybe your computer doesn't recognize your tablet. Did you ever try using sp flash tool with your tablet before? You can try reinstall or install a driver for your table if you haven't done it yet.
Well the tablet is recognized as the "mtk vcom..." in device manager. I guess it is the driver that the lenovo rescue app installed.
I have never used sp flash tool with my tablet, just the lenovo rescue.
I tried on 2 different pc and it is the same thing. I think the problem is that I can't turn off the tablet properly, even though, all I can see is a black screen.
I will try to drain the battery by keeping the power button pressed with some scotch tape. I don't know what I can do else.
Edit: I tried a few other times with flash tool using different setting for the connection (with battery and full speed) and nothnig happened. But now windows says it does not recognize my tablet.
did the same thing exactly. . bricked lenovo m10 fhd plus x600v after i flashed a downgrade version. dont try to downgrade this thing. i had already flashed it with 3 or 4 versions the same way , but when i chose to flash the oldest version available with the model , this tab got completly unresponsive , no feedback when try to boot into recovery, fastboot, or system . neither does it gets recognised in windows or anything - device manager dowsnt recognise this usb device ( in device manager properties comments it reads- USB\DEVICE_DESCRIPTOR_FAILURE). if you find a way to reflash the device please let us know. good luck .
Bricked mine after being completely running smoothly on Lineage, then was messing around trying to get gapps installed and jacked up the partitions. TWRP said no OS. Kept messing around and mistakenly locked the bootloader again with apparently an unverified boot partition. . I couldn't get SP Flash tool to work ever either. Pretty sure it's a door stop now.