Not booting and flash recovery is hanging - Lenovo ZUK Z2 (Plus) Questions & Answers

My Lenovo Z2 Plus suddenly stopped booting. I get the initial screen that confirms unlock with the Start option at the top right corner and then get a blank screen. A long press takes me back to the same screen. I tried to get into the recovery, and though I though I was getting the same blank screen, one of the long presses on the power button did actually get me into the recovery. When I tried doing a wipe of Cache and Dalvik Cache, I saw a brief progress and I got the blank screen again. Then I got into the fastboot mode after a couple of tries (the experience was erratic, similar to the recovery), so I tried to flash recovery and it was stuck:
Code:
$ ./fastboot -i 0x2b4c flash recovery twrp-3.2.1-0-z2_plus.img
target reported max download size of 1610612736 bytes
sending 'recovery' (18452 KB)...
OKAY [ 0.414s]
writing 'recovery'...
Could someone please help me recover this phone?

This just turned out to be a boot loop triggered by the low battery charge (close to 0%) and the AICP ROM aborting the boot process. After leaving the phone connected to charger for sometime, it booted back up just fine.

Related

[Q] TIFU going from GPE5.1 Back to Sense, Please help :)

So, the instructions are below pulled out of the Back to Sense thread.(http://forum.xda-developers.com/showthread.php?t=2733523) got to the end of what i've pasted no problems......
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Everything went well until the after that... I stuffed up royally.. my failure is below...
PS C:\adb> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.014s
PS C:\adb> fastboot flash recovery TWRP_Recovery_2.8.6.2_M8_CPTB.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16804 KB)...
OKAY [ 1.515s]
writing 'recovery'...
OKAY [ 0.940s]
finished. total time: 2.455s
fastboot boot TWRP_Recovery_2.8.6.2_M8_CPTB.img
I realize i skipped the below steps...
Boot into stock recovery
Factory reset
Reboot into bootloader
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever.... one thing worth noting, i can see the internal storage(well some of it) the device is recognized in windows and then internal storage is 10.5gb free out of 10.6gb, Navigating to the internal directory shows 3 directories: 0, obb, and TWRP. 0 is a neverending folder. every 3rd layer deep click it shows the root directory again...
Help would be very very much appreciated!
cheers!
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Cameltoemcgee said:
It would seem that what i've gone and done is flashed TWRP into the Boot Partition or something? now whenever i boot up, it won't show the fastboot screen, it goes straight to "entering recovery" and sits there forever....
EDIT: Sorted! It turns out i'm an idiot and wasn't pushing volume down fast enough to get into bootloader. Sorry guys!!!!
Click to expand...
Click to collapse
If the bootloader was overwritten, damaged or corrupted, the phone would be bricked, and the screen would not come on at all.
This is the second post on the first page where the OP solved their own issue. You guys are getting good at fixing your own problems.

Stuck in bootloader, recovery and download not working

My phone randomly rebooted today and then got stuck in a bootloop.
After a few restarts the phone then sorted of booted but claimed that the data was encrypted and it asked for my lock pin. The phone then confirmed that the pin was correct but that the data was corrupted.
I then tried to boot to recovery. After doing POWER + VOL UP I get to the HTC FTM mode and then when selecting Reboot to Bootloader the phone just gets stuck in a bootloop and after a while it goes back to the "Your phone is encrypted" screen.
So I tried going to the download mode and it get stuck in a bootloop with the silver HTC logo (the one that pops up when you go into the download mode).
I cant seem to find a thread that deals with the issue I am experiencing. Any and all help will be appreciated.
So it got a little better and a lot worse.
I was able to get into recovery but download was still messed up.
I then tried a lot of things, including recreating the /data partition which didn't actually help.
I even tried flashing the hsod_signed.img from the RUU, that didn't help to fix the download mode.
I tried that because I can't get into RUU or download modes.
And now after flashing a stock recovery it then won't boot into recovery either.
This is the result after flashing twrp-3.0.2-0-hima.img
C:\adb>fastboot flash recovery twrp-3.0.2-0-hima.img
target reported max download size of 536870912 bytes
sending 'recovery' (19912 KB)...
OKAY [ 0.464s]
writing 'recovery'...
OKAY [ 0.253s]
finished. total time: 0.720s
Click to expand...
Click to collapse
So as it stands I can't boot into recovery or download mode.
Failed to boot to download mode
Failed to boot to recovery mode
I can fastboot, so I am hoping people can just tell me how to fix it... or have I completely bricked it.

Unable to change recovery

Hi All.
Just bought a Wileyfox Swift. I'd like to install Lineage OS.
Reboot into bootloader, fastboot sees correctly my phone.
I run "fastboot oem unlock-go", my data gets wiped, then "fastboot reboot" and Android starts optimizing apps. Fine.
I go back into bootloader, now I try to flash TWRP:
Code:
# fastboot flash recovery twrp-3.0.3-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16908 KB)...
OKAY [ 0.532s]
writing 'recovery'...
OKAY [ 0.284s]
finished. total time: 0.816s
I reboot, Android starts correctly, power off. Go back into recovery but I still have the original Cyanogen recovery, no TWRP. What I'm doing wrong?
Thanks in advance for any hint!
If you are on the fastboot screen after flashing you should just select recovery and go there
There's no selection menu in fastboot mode on this phone. To go back into recovery I have to power off the device and power on again with volume-down + power button; but the recovery I got into isn't the TWRP I flashed but still the original cyanogenos recovery.
Pull battery after flashing recovery via fastboot. Then boot straight into recovery (not fastboot, not normal ROM), TWRP should be there.

No BLOD... 5X just won't boot.

I was using my 5x today, and it froze, then suddenly shut off. After holding the power button for a period of time, I can get the initial "Google" boot logo to appear for a few seconds, but then the screen just goes black again. I can get it to boot into bootloader mode, and from there into stock recovery, but never to the colorful dots to showing that the OS is booting up... every time I try the screen just goes black after a few seconds of the Google logo.
I've seen the bootloop issue before (on a different 5x), and this seems to be a different issue. Before I do anything drastic, do any of you have any suggestions or experience with this type of behavior?
wrkerr said:
I was using my 5x today, and it froze, then suddenly shut off. After holding the power button for a period of time, I can get the initial "Google" boot logo to appear for a few seconds, but then the screen just goes black again. I can get it to boot into bootloader mode, and from there into stock recovery, but never to the colorful dots to showing that the OS is booting up... every time I try the screen just goes black after a few seconds of the Google logo.
I've seen the bootloop issue before (on a different 5x), and this seems to be a different issue. Before I do anything drastic, do any of you have any suggestions or experience with this type of behavior?
Click to expand...
Click to collapse
I just got the same issue with yours 2 hours ago. Did you managed to try if a factory reset could help the phone?
Billys20 said:
I just got the same issue with yours 2 hours ago. Did you managed to try if a factory reset could help the phone?
Click to expand...
Click to collapse
Not yet. There's some data on the phone I need to try to get off before I do that.
Also, after leaving the phone alone for a while, when I came back to it, it did start boot looping, so I guess that is the issue. I tried flashing the modified TWRP image, but I still can't even get it to boot into recovery without looping.
wrkerr said:
Not yet. There's some data on the phone I need to try to get off before I do that.
Also, after leaving the phone alone for a while, when I came back to it, it did start boot looping, so I guess that is the issue. I tried flashing the modified TWRP image, but I still can't even get it to boot into recovery without looping.
Click to expand...
Click to collapse
Same thing here. When I left it for a while I was able to boot to bootloader but when I choose the recovery mode it boots again with the google logo and then turns off. No hope here I guess.
Mine does not care, it does not carry, not the sign of life.:crying:
I might have a similar issue. I posted this in the Lineage OS thread earlier today: "Uhm ... so this just happened: I flashed the latest LOS 15.1 (Apr 30) and Francokernel v56, then tried to reboot into LOS as usual. The phone froze at the LOS boot animation, so I long pressed the power button to shut it down. It eventually did shut down. I then pressed power and volume down to start up the bootloader. The bootloader eventually came up. I then told the bootloader to start into recovery, but I never got there. The screen just stayed black. Now the phone won't respond to whatever I do to it. Holding power and volume down for a long time doesn't do anything; holding power alone for a long time doesn't do anything. Nothing happens whatever I do to the phone. Any suggestions?"
I have discovered by now that the trick with mine is to simply press and hold the power button, rather than power and volume down. That way I am able to get into the phone's bootloader, but that's about it. If I try to boot into recovery — no chance, I only get as far as the Google logo. Has someone tried yet whether flashing the 4 kernel boot.img from this thread — https://forum.xda-developers.com/nexus-5x/general/blod-8-1-0-opm2-171019-029-apr-2018-fix-t3784307 — does anything?
um.z said:
I might have a similar issue. I posted this in the Lineage OS thread earlier today: "Uhm ... so this just happened: I flashed the latest LOS 15.1 (Apr 30) and Francokernel v56, then tried to reboot into LOS as usual. The phone froze at the LOS boot animation, so I long pressed the power button to shut it down. It eventually did shut down. I then pressed power and volume down to start up the bootloader. The bootloader eventually came up. I then told the bootloader to start into recovery, but I never got there. The screen just stayed black. Now the phone won't respond to whatever I do to it. Holding power and volume down for a long time doesn't do anything; holding power alone for a long time doesn't do anything. Nothing happens whatever I do to the phone. Any suggestions?"
I have discovered by now that the trick with mine is to simply press and hold the power button, rather than power and volume down. That way I am able to get into the phone's bootloader, but that's about it. If I try to boot into recovery — no chance, I only get as far as the Google logo. Has someone tried yet whether flashing the 4 kernel boot.img from this thread — https://forum.xda-developers.com/nexus-5x/general/blod-8-1-0-opm2-171019-029-apr-2018-fix-t3784307 — does anything?
Click to expand...
Click to collapse
Here you tried just flashing the stock factory image? Flashing lineage may have messed something up. I bet if you do that everything will be fine.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Here you tried just flashing the stock factory image? Flashing lineage may have messed something up. I bet if you do that everything will be fine.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Tried, but flash-all failed due to the phone switching itself off in the middle of the process. Here's the relevant content from my terminal window.
Code:
target reported max download size of 536870912 bytes
sending 'bootloader' (4620 KB)...
OKAY [ 0.189s]
writing 'bootloader'...
OKAY [ 0.197s]
finished. total time: 0.387s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.463s]
writing 'radio'...
OKAY [ 0.534s]
finished. total time: 1.997s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (11 MB) to disk... took 0.033s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (17 MB) to disk... took 0.044s
archive does not contain 'recovery.sig'
extracting system.img (1909 MB) to disk... took 10.193s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (185 MB) to disk... took 1.107s
ERROR: usb_write failed with status e00002c0
archive does not contain 'vendor.sig'
ERROR: usb_write failed with status e00002c0
ERROR: usb_write failed with status e00002c0
ERROR: usb_write failed with status e00002c0
ERROR: usb_write failed with status e00002c0
wiping userdata...
ERROR: usb_write failed with status e00002c0
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (Invalid argument))
ERROR: usb_write failed with status e00002c0
--------------------------------------------
ERROR: usb_write failed with status e00002c0
getvar:version-bootloader FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
Where are you getting the factory image? There's stuff that's printed out I've never seen before. Try flashing each partition separately with fastboot.
Sent from my [device_name] using XDA-Developers Legacy app
jd1639 said:
Where are you getting the factory image? There's stuff that's printed out I've never seen before. Try flashing each partition separately with fastboot.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
From here: https://dl.google.com/dl/android/aosp/bullhead-opm2.171019.029-factory-c7ba966b.zip
I did flash each partition separately in the end, but to no avail. Phone doesn't boot.
Hello same issue here with LineageOS 15.1 (+xposed and ElementalX)
It won't boot anymore after three loop to Google Logo and black screen, I was suspecting hardware issue and now, I see I'm not alone.
I'll try to boot to the bootloader this evening and flash factory images. I hope it'll work.
OMG! What's going on? I'm in Scotland right now with our US Nexus 5X's. Afternoon of the 2nd of May, I was using Hangouts when it just went black. Battery had over 40%. I couldn't even get it to turn on for a while. Then, it started with the unlocked bootloader warning screen then the Google screen-looping those for a while. Occasionally, the colored balls would begin but not finish. Sometimes, it wouldn't do anything--nothing but a black screen. I could get to TWRP via bootloader but any action was impossible as it either locked up or just went black. I left it plugged in overnight and eventually, the OS started (stock April update) again. The phone & OS remained on overnight. This morning, I tried to put the main Fi sim back into it but it locked up (froze) again then started the two-screen loop. I honestly didn't think I'd find people with the same issue--esp just happening. I can't get back to my PC until near the end of May so I can't try very much. I probably have the last OS on my 5X storage since I use Flashfire to update, but I really didn't want to try flashing anything since the black screen issue seems inevitable. I hope someone out there gets to the root of this. So far, hubby's 5X is working. Of course, all of ours were working until they weren't! His is locked and stock. We're both on April update.
Has anyone gotten anywhere with correcting this issue?
FWIW, I just contacted LG support today since I'd read that the warranty had been extended to 30 months. I won't know the final results for a few weeks, but I set up a repair and eventually received a shipping label to Fort Worth, TX. As far as I can tell, these behaviors ARE the BLOD. We also have a 27 mos old 5X that is hardly ever used. It currently has no issue; but then, mine didn't either until is just went black and wouldn't restart.
EDIT: In case anyone is still searching solutions for this issue, my phone is on its way back from LG with a new motherboard. All (including shipping both ways) was covered under the new, 30 mos extended warranty.

Question I bricked my phone, any advice?

So, here I was thinking things couldn't hurt to do some customisation.
This evening, I flashed a custom logo... using fastboot. (fastboot flash logo logo.bin)
That was the last thing I saw on my device, it won't show anything anymore.
Any advice on how to get any connection to my device again?
Right... So as before I found the solution myself.
I used the BROM to reflash the logo with the proper image.
For whoever wants to know. I used the MTK bypass utility to bypass the authentication stuff, and the SP Flash tool to flash.
I did have to use libusb-win32 for the python part, took me some hours to figure that one out. All sources told me UsbDK would work for that.
Kind of relieved I actually managed to unbrick my phone.
Did you get solution?
As mentioned in the post right before you; yes.
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl_a xbl.elf
Sending 'xbl_a' (3449 KB) OKAY [ 0.105s]
Writing 'xbl_a' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone?
I would be very, very grateful for help
You could try this: fastboot --set-active=b

Categories

Resources