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
Related
Hey
Today I was on Team Win Recovery Project v2.21 and I wanted to flash a new mod in however half way, I accidentally click on reboot now.
I already - Factory reset my device
- Wiped Dalvik Cache Directories
then tried to flash in one of my rom i was flashing in but I got an error then clear dalvik cache directories again. After I tried to reflash my rom but it failed again.After this I accidentally reboot my device and now it is stuck on a screen with "Reboot.." as the title. I can not restart the my nexus 7, touch any keys given (home and back). When I press/hold power, it comes up with a look.
I am wondering if there any way to fix this problem
Maybe try this...
http://forum.xda-developers.com/showthread.php?t=1781250
Or use this program...
http://forum.xda-developers.com/showthread.php?t=1766475
Lockable said:
Hey
Today I was on Team Win Recovery Project v2.21 and I wanted to flash a new mod in however half way, I accidentally click on reboot now.
I already - Factory reset my device
- Wiped Dalvik Cache Directories
then tried to flash in one of my rom i was flashing in but I got an error then clear dalvik cache directories again. After I tried to reflash my rom but it failed again.After this I accidentally reboot my device and now it is stuck on a screen with "Reboot.." as the title. I can not restart the my nexus 7, touch any keys given (home and back). When I press/hold power, it comes up with a look.
I am wondering if there any way to fix this problem
Click to expand...
Click to collapse
Reboot into bootloader (hold power to turn off, as soon as it does hold vol down)
Install the android sdk if you haven't. Download a recovery image from clockworkmod.com, put the image in your /platform-tools folder. Open a command Window there
Fastboot flash recovery xxxx.img
Fastboot boot xxxx.img
Dl a rom
Put it in your platofrm-tools folder
Adb push romxxx.zip /sdcard/Download
Flash the ROM in recovery
Reboot
Sent from my Google Nexus 7 using Tapatalk 2
When I turn on my tablet now, it automatically open up ClockworkMod Recovery. I am able to properly install a rom (wipe all data then install rom from sd) but when i reboot my device it goes back into clockwordmod recovery. Any idea how to bypass automatically booting straight into recovery mood and booting into flashboot?
EDIT
i am unable to push new roms in
mis-post, my bad.
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.
So I wiped cache and so on now the thing is hanging at the Motorola screen and that's it.
I tried to get a sbf but all who should be compatible are down so that I pretty much am freaked.
Is there a way to get at least now a clean rom on it maybe something new 4.4.2 without SDCard or is that also a nogo?
----
So if your phone won'T boot and you just have a white light or nothing at all. You probably have less battery power to sbf flash something.
I used the Jumper cable method from Sorensiim.
That worked like a charm.
If you are looking for sbf files. Here are some.
----
So now I rooted that thing and tried to install bootmenu. Iused the adb method with ./install.sh permission denied after the copy procedure was complete ((data/bootmenu chmod etc.). I tried 2ndinit with the problem that the program hangs after the download. So what is it now that freakin thing wants me to do?
----
Got Bootmenu installed now the Defy has a Bootloop. For a short time before it loops the white led blinks. No volume up or volume down work.
----
Hanging at M logo on re-boot
Having rooted the phone . . .
1. Switch on and await blue LED
2. Press volume down to enter Android Boot Menu (v 1.1.8-jordan)
3. Recovery
4. Custom Recovery > Cyanogen Defy Recovery (v5.0.3.1-jordan)
5. Wipe Data / Factory Reset
6. Wipe Cache Partition
7. Advanced > Wipe Dalvik Cache
8. Install zip from SD card
9. Toggle signature verification to Disabled
10. Toggle script asserts to Disabled
11. Choose zip from SD card
12. Apply zip from SD card
13. Reboot
14. Hangs at M logo
Tried with and without step 10.
The zip files tried are the only two ‘nightlies’ on the XDA website, as I have been unable to find the last ‘stable’ version.
Can anyone help please?
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
LS997 (September 2016 security patch), got to the end of root and couldn't reboot into TWRP recovery. The device is recognized in ADB while in fastboot but when I'm at the secure startup it's unrecognized, like USB debugging is disabled.
https://forum.xda-developers.com/v20/how-to/guide-root-twrp-lg-v20-using-dirtysanta-t3722278
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Phoenix591 said:
If you've hit secure startup the phone has likely booted into regular Android far enough to replace twrp with stock recovery. Reboot into fastboot and reflash twrp (you can use the newest twrp if you want). Once done flashing unplug from PC and pull the battery. Reinsert the battery then boot into twrp via the factory reset/volume button method: hold volume down, press power until the screen turns on then (still holding vol - ) tap power repeatedly until a prompt to factory reset appears. Approving it twice boots twrp if it's installed, otherwise stock recovery will do the reset.
Once in twrp go to wipe, then format data (type yes to confirm), then go to reboot, then recovery. Once twrp restarts flash your choice of magisk/supersu.
Once one of those two is installed it makes it so twrp won't be replaced.
Click to expand...
Click to collapse
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
strapdad said:
Did this, got to the set-up screen (languages, accessibility) and an error ¨com.android.phone has stopped¨ spammed the screen. I tap ¨stop app¨ and the pop-up comes back immediately.
I tried to fix it by factory resetting (in the settings, NOT using the volume down/power button menu OR TWRP) and now I´m stuck in TWRP. Every time I try to reboot to System, it boots to TWRP now.
Click to expand...
Click to collapse
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Phoenix591 said:
Power down, then boot to twrp using the volume buttons. Use the wipe menu there to do the reset.
Click to expand...
Click to collapse
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
strapdad said:
Wiped it, still get the com.android.phone errors.
Unfortunate, makes doing anything impossible with so many error popups.
Click to expand...
Click to collapse
Reflash your variant's official KDZ using [PARTITION DL] with patched LGUP leaving [aboot], [abootbak], [recovery], [recoverybak] partitions unchecked.
- Once the flash finishes & phone reboots, do a battery pull so phone doesn't fully boot (wiping recovery & encrypting data)
- Insert battery again
- While pressing volume down button - reinsert usb cable so it boots into fastboot mode.
- Follow dirtysanta guide for your variant from running step3.bat onwoards (which flashes TWRP back into your otherwise stock phone).
LS997, no official KDZ. Use VS995, but dump everything with LGUP (bar userdata) before hand