Hi,
I am not deep into mobile world. I bought a Lenovo Zuk Z1. Suddenly my phone stopped booting. When I boot, this menu comes: 0. Board Test, 1. Current Test, 2. SD Update, 3. Erase Userdata, 4. Restore QCN, 5. Save Parameter, 6. Reboot. I have tried all these but the phone doesn't start normally. I have done factory reset but no use. Please help. How can I get my phone to normal usage?
probably the system is down try installing latest twrp on the phone and after that install the latest nightly lineage os also dont forget to install gapps it should work good if there are problems install cm13
It seems to be that your volume down key is stuck. Press it for sometimes then press and hold power key until phone reboot
Related
I noticed many average users out there, bricked their devices so here's a guide for you to unbrick it:
Bootloop is a state when your phone is not able to boot properly and it is stuck on the Bootanimation It is the commonest thing that Android users face with their phone or tablet device and this can be fixed easily by performing certain steps by booting the device into stock or custom recovery mode. Here is our detailed guide that will help you fix bootloop on your device.
1-How to Recover When your Android Device is Caught in a Bootloop:
The reasons for getting a bootloop on your Android device might be anything.Here are some major reasons why your Android device is caught in a bootloop.
-After installing an official or custom ROM
-Flashing a wrong ROM or Kernel
-Running an incompatible app or game
-Wrong Permissions fix for an app or file
Installing a custom mod or theme
Most often we face a bootloop just after flashing a stock or custom ROM over an old one. This might be a major factor behind the bootloop issue on your device. Suppose you have flashed a new version of firmware over the old version. Your old data still remains on the device and the new firmware will use the Dalvik Cache from the old ROM that might not be compatible with the new system files and it will result in a bootloop. It mostly happen just when your device tries to reboot after you have flashed a stock or custom ROM. If this is the case, here is the solution.
Method I-If your device is on stock firmware, that also means it does not have a custom recovery like CWM or TWRP not installed on it, do the following steps:
Pull out the the battery of your phone, wait for about 30 seconds and reinsert it to its place.
Boot your device into ASR (Android System Recovery) mode. The method involves a hardware key combination and varies from one phone to another. For Samsung phones, for example, the key combination is Volume Up+ Home + Power keys. The tablets which generally have no Home button, you can enter the Recovery mode by pressing and holding the Volume Up + Power keys simultaneously.
In the Android System Recovery, scroll down to “wipe cache partition”. option using the volume rockers and select it using the power key.
When you have wiped the data/factory, go back to the main menu and reboot the device by “reboot system now” option.
If the device is still stuck on Bootanimation pull out the battery again and repeat the above steps. This time also “wipe data/factory reset” and then reboot device
The bootloop problem should be fixed now.
Method II-If you have a rooted device with CWM Recovery installed and your phone is caught into a bootloop after flashing a custom ROM or mod, do as follows:
Pull out the battery, reinsert it after 30 seconds and boot the device into CWM Recovery: Volume Up+ Home + Power keys simultaneously.
Go to “Advanced”
Choose “Wipe dalvik-cache”
Now go to “Mounts & Storage”
Choose “Wipe /cache”
Reboot your phone
The bootloop should be gone now. If it still persists, do this.
Boot the phone again into CWM Recovery
Now go to “Mounts & Storage”
Choose “Wipe /data”
Choose “Wipe /cache”
Then reboot your phone.
Now the phone should reboot normally. Next time when you install a ROM, follow the instructions prescribed by the developer. Be more attentive to the warnings before experimenting with any third party ROM or mod. Always ensure what you are about to install is meant for your device.
Note:
If wiping the data/factory reset, and cache partition does not help you, or you are not able to boot into the Android System or ClockworkMod recovery on your device, you can try installing the official firmware on your device.
In case the two methods described above do not bring your device to normal state, the problem is a little serious but still not out of control. The following method is same as installing the official firmware described above, but it also involves flashing a PIT file along-with the firmware. This file is used to re-partition the corrupt partition on Galaxy devices.
source: DroidView.
Hope this small info help.
Hi, I'm sorry for my English Spanish. I have since today zuk z1, installing "CM13 Coldbird" and entered correctly after performing all the steps, but connect wifi and get ip enters loop mode and does not come out of there, back at the beginning, initial settings and jump around and just 30 seconds later it happens again.
Buy two units and is installed well and gave me problems but restauré factory and it is correct but can not find this solution.
Hi Pichi. Which build did you use?
me too
I have the same problem, but in my case I have no time for do nothing, it turns on and then one second later reboot and reboot and reboot I'm desperate, I have no option to enter to fastboot or recovery because I have no time to press any button, any idea?
Alexdelgadoperez98 said:
I have the same problem, but in my case I have no time for do nothing, it turns on and then one second later reboot and reboot and reboot I'm desperate, I have no option to enter to fastboot or recovery because I have no time to press any button, any idea?
Click to expand...
Click to collapse
To enter recovery when experiencing such problems, you can hold the power button for 5 seconds to turn off / reboot device. After reboot, press and hold the volume up and down button at the same time until you see TWRP screen (2-5 seconds).
Then in TWRP screen, you can wipe system, cache, etc and perform another clean flash.
I experienced such behavior while using build 4/16 before. I recommend installing gapps micro package for such build to avoid reboots. Also, you can try and follow the following steps while installing CM13 build 4/16:
1. Wipe cache, Dalvik cache, data system.
2. Install mm tools
3. Install CM build 4/16
4. Reboot to system. Wait until stabilized (2-5 mins after you see the homescreen)
5. Reboot to TWRP
6. Make full Nandroid backup (just in case) - optional
7. Install gapps micro (if this won't work, try installing gapps Pico or the full gapps suite.
8. Reboot system
After performed wipe cache and firmware update with "Swift&Fast Slim B160 aio" ROM, the phone reboot and stuck at waiting for booting... ==> wait for 3 hours and still show the same as BOOTING.
Performed the factory reset by press Volume Up and Power, the Factory Reset is now stuck at 99%
Please help to the the phone back in working condition.
Resolved yet?
Possible idea
You can probably still load TWRP. Press and hold volume down + power at the same time to load fastboot mode.
ROM Flashing
Obtain a ROM of your choice, and note the location on your computer.
reboot your device into fastboot mode via one of the following options.
1. adb reboot bootloader (requires USB debugging to be turned on).
or...... power off the device then back on with 'vol up' + power button.
Wipe your device.
2. fastboot -w
Update your ROM.
3. fastboot update </path/to/your/RomFile.zip>
Your phone will update and automatically reboot into the new ROM. Try another ROM if Swift & Fast Slim isn't working. Your file could be corrupted.
did u get things fixed?
So I have installed 10.0.1 and it was a mess - wifi didn't work, music (from youtube or games) didn't work, I couldn't receive or make phone calls cause phone crashed + other smaller things. I've decided to remove this sh***y rom and install latest stable Android 9. So I entered TWRP, wiped cache, data system, etc. I have Installed 9.17 and rebooted - no luck. Phone simply boot to recovery (but not twrp anymore). I have installed twrp via fastboot and cmd but after that phone didn't boot to anything...
Right now when I start it by power button or power button + vol down it's getting stuck on *boot loader unlocekd** screen but if I press power + volume up I see error Qualcomm Crash Dump Mode...
Any ideas what to do?
Msm
That helped! Thanks
Please read my problem:
1: I flashed using miflash oreo rom
2: Android 9 update comes to my mobile ,i did it
3. I flashed custom rom (derpfest pie version)
4: I wiped system, data, cache and flashed siberia os using twrp
5: Botloop on android one logo
6: Tried Power+Vol Down : No fastboot
7: Tried Power+Vol Up: No twrp. it show no comand screen
It just restarting continously after androidone logo. Meanwhile I getting VENDOR ERROR after mi flash.Before flashing sberia I was able to do fastboot and twrp. I even tried all three butoon press (VOl + - power). but same behaviour
Let me alive my device please
Thanks
Same happened here.plz help
Swaniya786 said:
Same happened here.plz help
Click to expand...
Click to collapse
I solved it
- exhaust mobile battery by doing bootloop without charging
- when battery is empty, connect usb cable with all drivers installed
- now try to bot in faastboot (power+vol Down)
i am sure after one or two attempt you will gee to fastboot
- now follow below guide:
c.mi.com/thread-2251485-1-0.html
in above URL i got error while restoring twrp backup.To resolve it first make backup of your corrupted rom device.Then using file explorer on PC remove all files.And replace all downloaded one.Delete all backedup files first.(Mind it)\\
Enjoy
If unable to get into fastboot, get battery zero and retry, Dont loose hope.Dont use any special method to zero battery.Simple let it restart