Bootloop after fingerprint sensor and ROM died - Zuk Z1 Q&A, Help & Troubleshooting

Hello,
problem above, maybe it's a hardware malfunction which would be awful.
I tried:
- whipe everything in the CyanogenRecoveryMenu
- sideload via Minimal ADB / Fastboot
- a lot more commands and helps on this site and on the internet (push,
Details:
- fingerprinter died, then the phone always crashed with blue and green flashing lights on the screen and now a bootloop
- "stock" CyanogenOS installed, but no TWRP
- the phone gets detected by my computer (sound)
- i don't remember if usb debugging is enabled (probably not)
- the command "adb devices" shows my phone when its in ADB mode (recovery menu)
- i sometimes get the error "error:closed" on my computer
Thank you for any help
doebelfish

doebelfish said:
Hello,
problem above, maybe it's a hardware malfunction which would be awful.
I tried:
- whipe everything in the CyanogenRecoveryMenu
- sideload via Minimal ADB / Fastboot
- a lot more commands and helps on this site and on the internet (push,
Details:
- fingerprinter died, then the phone always crashed with blue and green flashing lights on the screen and now a bootloop
- "stock" CyanogenOS installed, but no TWRP
- the phone gets detected by my computer (sound)
- i don't remember if usb debugging is enabled (probably not)
- the command "adb devices" shows my phone when its in ADB mode (recovery menu)
- i sometimes get the error "error:closed" on my computer
Thank you for any help
doebelfish
Click to expand...
Click to collapse
Did you also tried factory reset already?
If you have adb access you can only try to get bootloader unlocked which wipes all if not happened yet. Then you can try installing twrp and another rom and see if boot is OK.
If your bootloader is still locked go to service center if you have warranty!

strongst said:
Did you also tried factory reset already?
If you have adb access you can only try to get bootloader unlocked which wipes all if not happened yet. Then you can try installing twrp and another rom and see if boot is OK.
If your bootloader is still locked go to service center if you have warranty!
Click to expand...
Click to collapse
Thanks for a reply,
After a full reset I have downloaded a twrp.img file for my device
I tried:
- command "fastboot devices" while in fastboot-mode (I pressed reboot to bootloader in the recovery menu to get there)
-> no device detected despite a sound after connecting
- command "fastboot flash twrp.img" -> "waiting for device" without any further reaction
My device is only detected in ADB mode, not in fastboot mode, how can I change that? I must unlock the boot loader in fastboot mode right?

doebelfish said:
Thanks for a reply,
After a full reset I have downloaded a twrp.img file for my device
I tried:
- command "fastboot devices" while in fastboot-mode (I pressed reboot to bootloader in the recovery menu to get there)
-> no device detected despite a sound after connecting
- command "fastboot flash twrp.img" -> "waiting for device" without any further reaction
My device is only detected in ADB mode, not in fastboot mode, how can I change that? I must unlock the boot loader in fastboot mode right?
Click to expand...
Click to collapse
Did you have actually drivers installed for fastboot? See guides like this http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
Also qfil method can help http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But consider service center in case of warranty.

same problem. fingerprint died. then after a empty battery shutdown i face bootloop. but hopefully i have TWRP installed and i could recover my data. but i dont know how to access factory reset menue or install another fresh rom

Related

re-locking boot loader & restore

How can I relock the boot loader and restore my Stylo 2 to factory default? Provider is T-mobile.
fastboot flash oem lock.
Note however if you used twrp this will brick your device unless you flash the original recovery first. Provided you got the kdz or LG bridge you should be able to just lock put in download mode and use the repair recovery option.I'm not responsible if you brick your device. Good luck
Frosthaxx said:
fastboot flash oem lock.
Note however if you used twrp this will brick your device unless you flash the original recovery first. Provided you got the kdz or LG bridge you should be able to just lock put in download mode and use the repair recovery option.I'm not responsible if you brick your device. Good luck
Click to expand...
Click to collapse
I had used LG Bridge to reflash my phone so I believe that I have original recovery on the phone. How can I verify?
When I enter fastboot flash oem lock I get < waiting for device> on my terminal screen and thats it?
Once you have the phone wiped completely back to default (including recovery) with the LG tools. Enable developer mode, and then enable USB debugging. While it is plugged into your PC navigate to the folder where you have the ADB applications in CMD or add the location to your Environment variables. The latter will allow you to launch ADB/fastboot commands from any location in CMD. I definitely suggest this. With your phone connected run "adb devices" to make sure that it sees your device. Then run "adb reboot-bootloader" to reboot into the bootloader. While on that screen run the command "fastboot flashing lock_critical". It should prompt OKAY then give the time it took and also that all of the user data was deleted. Then finish up by typing "fastboot reboot". That will put the phone back into a normal mode. Boom, you are done.
Help
When I use the fastboot oem lock, at the moment when I power on the phone in the screen appears the text "Your device has failed a routine safety check and will not boot.
This may be a temporary problem.If this message occurs rerepeatedly, visit this link on another device and refer to the Red case: g.co/ABH
I have two days looking for the solution, and I didn't found anything

Stuck in Fastboot Reboot Loop. Fastboot Reason: reboot mode set to fastboot

Last week i received a notification the 8.1 Oreo update was available for my Moto g4 Plus.
Downloaded the package and hit the install button. My moto restarted in order to perform the installation.
However, since i had TWRP installed and thus bootloader unlocked, the phone restarted in recovery mode.
Downloaded a TWRP 8.1 rom and installed it without a problem.
Unfotunately everytime I restart my Moto it starts up in fastboot mode.
Bootloader log shows: Fastboot Reason: reboot mode set to fastboot
From bootloader I can start the Android OS, but i wan't to get rid of this reboot mode
I tried tools like "Android Multi Tool" and "Free ReiBoot for Android" but this reboot mode can not be cleared.
Anyone encountered this problem and how did you fix it.
Thanks in advance
Try this:
Reboot your device to the bootloader.
Connect your device to your computer and open an ADB terminal on your computer.
In the ADB terminal, type 'fastboot devices' without quotes. Press Enter - your device should respond with its serial number.
If so, then type 'fastboot oem fb_mode_clear' without quotes. Press Enter, then reboot your device.
That fb_mode_clear command seems to clear a flag that keeps your device booting into fastboot (usually for OTA updates).
I have Tried that option as i found it as one of the possible solutions for this issue.
the clear_fb unfortunately does not remove the fastboot mode on my moto.
mbodewes said:
I have Tried that option as i found it as one of the possible solutions for this issue.
the clear_fb unfortunately does not remove the fastboot mode on my moto.
Click to expand...
Click to collapse
Alright, though this is for solving TWRP bootloops, might be useful for you https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
echo92 said:
Alright, though this is for solving TWRP bootloops, might be useful for you https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
Click to expand...
Click to collapse
echo92. Thanks. Works like a charm. Issue fixed.

No fastboot option on Oneplus 8 Pro - can't unlock bootloader

I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Docomoco said:
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Click to expand...
Click to collapse
Sure. You are allready in that mode. Just type fastboot devices and check..
I did that but no response.
The cursor jumps to the next line but there is no response from the phone.
If I type adb devices the phone is listed but the fastboot command doesn't return anything.
Docomoco said:
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Click to expand...
Click to collapse
Restart to bootloader, then fastboot should work. If your phone is still on, and you can access adb, you should also be able to type adb reboot bootloader
Thanks.
So apparently the command "fastboot devices" returns nothing.
However I was able to unlock the bootloader just by entering "adb reboot bootloader" then
"fastboot oem unlock".
What confused me was that there is no "fastboot" option on the phone itself as there was on my Oneplus 5t.
Docomoco said:
Thanks.
So apparently the command "fastboot devices" returns nothing.
However I was able to unlock the bootloader just by entering "adb reboot bootloader" then
"fastboot oem unlock".
What confused me was that there is no "fastboot" option on the phone itself as there was on my Oneplus 5t.
Click to expand...
Click to collapse
The option in the power menu is called bootloader (fastboot only will work there) the hint was in the adb command I gave you, adb reboot BOOTLOADER. Not sure why they changed what the menu was called but I'm glad you got it sorted. To give you a short summary, adb will only work when your phone is powered on and booted into android, or if you have recovery mode open and on the adb section, and fastboot only works in the bootloader hope that could help!
Edit: fastboot devices should work but only in bootloader mode, not when your phone is started normally
Docomoco said:
I have a brand new Oneplus 8 Pro from China with global ROM installed.
I wanted to unlock the bootloader however there is no fastboot option in the boot menu.
There is Start, Restart Bootloader, Recovery and Turn Off.
The Fastboot option is missing.
I can connect the phone to my PC, adb recognizes the phone, but Fastboot is missing.
Any ideas?
Click to expand...
Click to collapse
You have to insert a SIM card, boot of the device and make a phone call to get it to register your device. Wait a few minutes and then restart your phone. Go into settings under about phone and enable developer options. Back out and go into developer options and you will see OEM unlock. You need to turn that on and USB debugging. Both of them must be turned on. Now you can boot into fastboot and unlock your bootloader. It will wipe the device so if you have any data you want to save you better do it now.
hey i am having this issue, i am able to adb reboot bootloader but when i try to oem unlock or anything else, it is just waiting for device and not finding it....
SourPower said:
hey i am having this issue, i am able to adb reboot bootloader but when i try to oem unlock or anything else, it is just waiting for device and not finding it....
Click to expand...
Click to collapse
That's a driver issue.
Are you using Windows 7? If so use 10
If not then sort out your driver's and it'll be fine.
Theres a bug in 7 where the driver for ADB cannot be collaborated with fastboot drivers.
dladz said:
That's a driver issue.
Are you using Windows 7? If so use 10
If not then sort out your driver's and it'll be fine.
Theres a bug in 7 where the driver for ADB cannot be collaborated with fastboot drivers.
Click to expand...
Click to collapse
thanks for the reply, i am on windows 10 and i dont know what is causing the issue when the phone goes in fastboot, but i went on my wife's laptop and got it working within a few minutes after installing adb...
Having similar problem here:
win10x64, drivers installed, USB debugging is enabled.
ADB sees the devices, reboots it correctly with "adb reboot bootloader"
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
trying to communicate with smartphone via terminal "fastboot" command doesn't do much:"fastboot devices" doesn't return anything at all, "fastboot oem unlock" just shows <waiting for device>
tried to reinstall drivers
tema_ka said:
Having similar problem here:
win10x64, drivers installed, USB debugging is enabled.
ADB sees the devices, reboots it correctly with "adb reboot bootloader"
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
trying to communicate with smartphone via terminal "fastboot" command doesn't do much:"fastboot devices" doesn't return anything at all, "fastboot oem unlock" just shows <waiting for device>
tried to reinstall drivers
Click to expand...
Click to collapse
If you type fastboot reboot what happens? If nothing then either you're device doesn't have usb debugging on, could be the cable/usb slot (some people have had issues with this)
Or its the driver installed for fastboot.
Show hidden devices in device manager you may have multiple devices, remove them all and start over.
Your also need to have used ADB and have trusted the device (prompt will appear on your phone the first time you connect it successfully whilst in your phones system, not fastboot)
for windows 10:
firstly download the google adb driver:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
then do the following:
1. adb devices [you should see your device ] > adb reboot bootloader
2. device manager > update driver > chose from list [android device]
3. still in device manager got the newly populated Android device and then update driver > choose adb interface
3. fastboot oem unlock
etc.
hope this helps
i have similar problem
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
i reached till fastboot. fastboot oem unlock is not working because SECURE BOOT - Yes.
any help will be highly appreciated
shweta007 said:
i have similar problem
then bootloader menu's shown:
START // RESTART BOOTLOADER // RECOVERY MODE // SHOW BARCODE // POWER OFF
Fastboot mode
Product_name - kona
Variant - SM8 UFS
BOOTLOADER VERSION - (nothing appears here)
BASEBAND VERSION - (nothing appears here)
Serial number - (appears 8-symbol sn)
SECURE BOOT - YES
DEVICE STATE - LOCKED
i reached till fastboot. fastboot oem unlock is not working because SECURE BOOT - Yes.
any help will be highly appreciated
Click to expand...
Click to collapse
Secure Boot means your Bootloader is locked.
Setup fastboot correctly, open a cmd window, navigate to fastboot.exe and enter fastboot oem unlock, follow instructions on phone screen

Semi-bricked??

Weird: I was just using it normally, it switched off and now it stays stuck on the Google logo; when entering recovery mode, I get TWRP"s splash screen and it stays there, so I cannot even recover.
Suggestions please??
Note 1: I'm pretty bad with this kind of stuff, need step-by-step instructions.
Note 2: rom is AOSP 7.1.2 but I guess is irrelevant, as even TWRP does not load.
Thanks in advance!!
Can you fastboot boot the TWRP recovery?
Hmmm dont know exactly what that means sorry; I mean I havent tried connecting it to the laptop and using thr ADB toolkit, but I can reset via Power+VolDown to the bootloader menu (? the android layind down and giving the option to StartSystem/ SwitchOff/ Restart/ RecoveryMode), and choosing RecoveyMode it tries to launch TWRP (it even shows the logo) but stays there on the splashscreen, doesn't quite manage to give me the TWRP menus
Someone?
AndDiSa said:
Can you fastboot boot the TWRP recovery?
Click to expand...
Click to collapse
let's see... I set in recovery mode, connect to the PC (does not recognise it), and with "fastboot boot twrp.img" it just sends/writes the file, the tab shows the Google logo with open lock, and then tries to launch Twrp, but as before, it just get stuck in the splashscreen "TeamWin Recovery Project 3.3.1.0" , so just the same.
Command "fastboot flash boot twrp.img" the same
Command "fastboot flash recovery twrp.img" the same
Command "adb devices" returns the list empty
Command "adb reboot recovery" returns "error: no devices / emulators found"
Command "fastboot oem unlock" returns "(bootloader) bootloader is already unlocked"
I tried running a tool called FirstAid (https://forum.xda-developers.com/devdb/project/dl/?id=16684) but does nothing for me
I'm lost, please help
Video and photos of the issue (device, not adb)
video: https://photos.app.goo.gl/GrFrmQhbyQeHVFZN7
Well, looking at your video it seems that there is no bootable ROM installed and also the recovery (for what ever reason) has some issues to start.
The fact, that you are able to boot into bootloader shows that at least it's not completely bricked ... but there's still the chance that the flash memory has some issues.
I would connect the device via usb with a PC and try to do a
fastboot boot <twrp-3.3.1-grouper.img>
to whether in that case the recovery is booting.
If this is successful, the next step would be re-flashing the recovery into the recovery partition and booing into recovery mode from the bootloader.
If this is successful, too, wiping and flashing a new ROM would be the last step.

Reboot to Recovery Loop but no Recovery Installed - How to get back to System reboot?

I tried flashing a recovery program (TWRP) in fastboot mode. The powershell said it was successful, but now the phone cannot get past the bootloader unlocked screen. It started to System twice, and I made sure to remove the security PIN and enable ADB debugging on this computer automatically. However, "fastboot devices" and "abd devices" commands do not return the device ID, but the phone does turn on when I attached the USB cable that's connected to my computer. I think it's trying to restart into recovery mode, but the recovery program (TWRP) did not install correctly. How can I get it to reboot to system again?
CurlyTemple said:
I tried flashing a recovery program (TWRP) in fastboot mode. The powershell said it was successful, but now the phone cannot get past the bootloader unlocked screen. It started to System twice, and I made sure to remove the security PIN and enable ADB debugging on this computer automatically. However, "fastboot devices" and "abd devices" commands do not return the device ID, but the phone does turn on when I attached the USB cable that's connected to my computer. I think it's trying to restart into recovery mode, but the recovery program (TWRP) did not install correctly. How can I get it to reboot to system again?
Click to expand...
Click to collapse
When I try to give a fastboot command, the powershell just returns
<waiting for device>
and then nothing happens.

Categories

Resources