Hi all, I need some help.
I tried to install the official CyanogenMod 13 Snapshot (2016-04-18) for my ZUK Z1. First everything went fine but after the first reboot the device ended up in a boot loop. For several hours I tried to fix this for no avail, flashing different versions of CM13, formatting the device and setting everything up again until I gave up and flashed the original CyanogenOS 12.1 from here. Now the device works again however when I want to encrypt my device through the security settings the following happens:
First I see the green Android robot, then the animated CyanogenOS logo and after a few seconds the device has booted again but no encryption was performed. I also made sure to flash the original recovery back onto my device. The only thing that has changed to before is that the bootloader is now unlocked. Could this be a problem? How can I now encrypt my device?
Thanks for any help!
Well, I locked the bootloader and it's still not working
Related
Hello guys, i'm having a problem ;f
I was on cm12 nightly when i decided to reboot my device after few days of running, strange thing happend and i ended up in bootloop.
I've downloaded 4.4.2/4.4.4/5.0.1 stock images and tried to flash it guided by the instructions in this thread, however i still get a bootloop, even after clean installation, even after wiping cache and doing a factory reset.. I've managed to boot up my device twice since yesterday, after getting stock image to work i pushed cm12 and gapps on my phone and flashed them.
At the first try, i got bootloop again, so i decided to go through the whole process again, many attempts later i've managed to boot up my device again, and again i decided to flash cm12 and gapps, this time my device booted up properly so i wanted to gain root access, in order to do so I flashed UPDATE-SuperSU.zip file and as a result end up in bootloop again.. I have no idea wtf is wrong with my nexus. I am still trying to flash factory image, and i always end up with bootloop.. I'm out of ideas here, HALP! ;(
@update:
I have uninstalled all drivers, and mount my device to another usb port, then with NRT i installed google's drivers, by using nrt i have flashed 5.0.1 factory image, rebooted into recovery and wiped/factory reset, after that i rebooted my device and still no luck - hanging on floating dots for 15 minutes..
Before all of this I tried formatting my cache to FAT and to sdf4 and it didn't help, I literally tried every single instruction i could've found ;/
What's wired is that when i encountered bootloop yesterday and wiped/factory reset i booted fine, after restart it went into bootloop again, so i thought i would wipe/factory reset again i'll be good to go, but.. it didn't help this time oO
things i've already performed:
1. fastboot oem lock/unlock
2. wipe data/cache/factory reset
3. flash factory images of 4.4.2/4.4.4/5.0.2 through NRT/manually
4. converting partition to fat and next to sdf4
5. reinstalling drivers
6. different ports and usb cords
6. i even tried switching motherboard from my old n4 and i still stuck at bootloop *LOL!?*
7. after 6 i thought it may be related to usb port so i switched usb port from my old n4 and it did help but.. until next reboot ;/
from time to time, after flashing it boots up just to make my hopes and then it gets the bootloop after restart ;/
@update2:
It seems it's hardware related issue. I have tearn down my nexus device and left only motherboard with fron/back cameras and audio jack, daughterboard, i even disattached the speaker along with antena. At this point i flashed factory 5.0.1 and it works, i'm in the moment when i plug peace after peace and turn on the device to check if it still works. I'll update when i find out what was the cause of the problem.
@update3
Stupid as it sounds the issue was caused by the vibrator module, while it was disattached, the device was booting up without any problem.
Hi all,
I was pretty happy with the Cyanogen OS, but when issues started with only OS and not with hardware for more than 3-4 times,
I am not happy now, My latest issue...
One fine day I saw a Message on My Yu Yureka Plus with regional language Hindi which was looking like an advertisement on my Device, I just ignored for 1st time and 2nd time, but it was something written like encryption unsuccessful,
it prompted me to reset the phone and I did it.
After resetting the device, it just showed reboot system now and that's it, only Yu logo and restart.
Tried to flash the device but system not detecting the device.
Taken to Service center and they said that Mobile is rooted and not able to flash the device.
So now I can see the Cyanogen recovery and the charging % ....
Tried to upadate the device with official COS12.1 (YOG4PAS3JM), but failed.
My device is not rooted yet.
Anything that I can do regarding this?
Rajesh.TR
Hello,
I'm currently experiencing a bootloop on my phone, it gets to the resurrection remix logo screen during boot then restarts. I've tried booting into recovery and download mode. When I try to boot into recovery it loads the factory reset screen as usual but when I say yes to the reset in order to launch TWRP it just goes to the LG logo, then remix and restarts all over. I got into download mode one time since this started but since then I've made countless attempts to boot into it again and can't.
What I was doing right before this happened is, I recently completely wiped my phone, flashed stock firmware, wiped, then installed resurrection remix. Everything was going perfect, it started no problem, I went through and cleaned up some apps I didn't want etc normal setup steps then I used the power menu to boot into recovery instead of just using the hardware keys and the bootloop started.
Besides the not booting, the other major issue here is that it never stays connected to the pc via adb long enough to do any actions or flash a single file. By the time the pc sees it and adb sees it, I have roughly 2 seconds before it restarts again.
I really really really need any help I can get please ASAP as this is my mom's phone and she needs it for work in 4 hours. This issue started about four hours ago and I've been trying to fix it ever since. I feel like I have looked everywhere on here and through google but probably missed the solution. Before you ask, I'm 28 not a teenager and work in IT as a career for the last 12 years so don't get the wrong impression. She asked me to work on it because I had set it up a few months back with a lollipop version of resurrection remix and magisk, but in the last month or so she was having really poor performance and issues with settings crashing and a few other apps.
I hope you don't need any more info from me, if you do however I'll be here trying to fix it until she goes to work at least. I really could use the help and would greatly appreciate it.
Thank You
I flashed the ROM Ressurection Remix onto my phone to get a newer Android version since the model is quite old. Everything worked perfectly for over two years. Then while browsing, my phone crashed and got into a bootloop and restarts after showing the Samsung Logo. After manually removing the battery and putting it back repeatedly it boots up somehow. I couldn't reproduce what was happening back then.
After that it crashes in irregular intervals for no apparent reason and every time I could get it to boot properly by turning off and on for a long period of time.
Now I got the same problem and I wanted to get rid of the bootloop, so I decided to flash it with a new version of Ressurection Remix. I updated TWRP via Odin and had much trouble to get into recovery mode since my phone was crashing at the Samsung logo. As I got into recovery I made a factory reset and flashed the new rom. But as soon as my phone started to reboot after the flashing, it crashes again and the loop starts once again. Again, I searched for another Rom and used LineageOS but the problem persists.
Now I'm out of options, I can't even get into recovery mode by now.
Could anybody help me out?
Kolon22 said:
I flashed the ROM Ressurection Remix onto my phone to get a newer Android version since the model is quite old. Everything worked perfectly for over two years. Then while browsing, my phone crashed and got into a bootloop and restarts after showing the Samsung Logo. After manually removing the battery and putting it back repeatedly it boots up somehow. I couldn't reproduce what was happening back then.
After that it crashes in irregular intervals for no apparent reason and every time I could get it to boot properly by turning off and on for a long period of time.
Now I got the same problem and I wanted to get rid of the bootloop, so I decided to flash it with a new version of Ressurection Remix. I updated TWRP via Odin and had much trouble to get into recovery mode since my phone was crashing at the Samsung logo. As I got into recovery I made a factory reset and flashed the new rom. But as soon as my phone started to reboot after the flashing, it crashes again and the loop starts once again. Again, I searched for another Rom and used LineageOS but the problem persists.
Now I'm out of options, I can't even get into recovery mode by now.
Could anybody help me out?
Click to expand...
Click to collapse
Hey. I have same problem. I can just boot the Phone with bootloader. Anyone have an idea about this?
Hi guys,
Trying to fix a friends x704f wifi only, but no luck.
It had Lineage 18.1 on it, and for whatever reason he did not like that, and went on to reflash stock with Lenovo's Rescue and Smart assistant which showed it a success rescue, but now Tablet boots to EULA, arrives to choose wifi and it crashes and reboots constantly, with no wifi icon being shown.
Lenovo rescue installed TB_X704_S000060_220916_ROW, so I factory reset it a few times from recovery, went through rescue again, installs same ROM, success, yet again it crashes at network selection, of if you do not touch anything, it crashes itself after about 20 seconds after being booted and if i hold the Power button and select shutdown, briefly the standard desktop shows with icons and than it crashes, so guessing ROM is there, it just can't boot.
Tried with QPST and latest ROM, but on eMMC xml selection I get error Document error on element program and name/value true.
Guessing baseband or some other thing should of been backed up before flashing stock again? if it helps, OEM lock is OFF, secure boot is ON what I can see from fastboot.
Thanks.
There must be something wrong with the persist partition, flash the persist.img again.