Related
New member; just registered today. I'm really pleased to be here.
I've been learning how to install CyanogenMod CM-12.1 with help from many xda threads, but especially these two:
http://forum.xda-developers.com/nook-hd/development/unofficial-cm12-1-nook-hd-hd-2015-04-08-t3078260
http://forum.xda-developers.com/showpost.php?p=42406126
Many thanks leapinlar, e.mote, Hashcode, verygreen, and amaces.
I successfully installed amaces's CM-12.1 20150628 build on my three Nook HD+, and then successfully moved on to 20150706 build for each of them. Some details are mentioned below.
But I've not been successful with my Nook HD tablet. I started with the 20150706 build which seemed to go well. CM-12.1 booted nicely and the setup wizard led me through initial settings for a while, but hung in one of its "Just a sec" moments after I declined to allow using GPS for location.
I wondered if I was being punished for declining, but I did the same with the HD+ tablets without consequence.
I eventually shut down and restored to the stock HD OS, which appears to be working fine.
I've tried a few more times, but each time CWM fails the wipe maneuver at "formatting data", and reboots to the stock OS.
I guess I'll have to learn how to use ADB to find and fix this problem, but if anyone has a suggestion to try before that I'm very anxious to hear it.
Thank you for reading my first post.
Some details:
My installation method, successful only for the HD+, is adapted from leapinlar's Installing CM11 for Dummies (Updated 7-13-14). I used the provided .rar file contents to build the external bootable microSD card with the CM-12.1 zips from amaces. But instead of flashing the provided CWM resident recovery zip I substituted a TWRP zip that I fabricated around amaces's TWRP 2.8.7 images. I was obsessively careful to use the model-specific images and zips in each case.
With build 20150628 on the HD+ I saw the Netflix green screen problem, and a serious screen instability when trying to manually enter a URL in a browser (keyboard and auto-suggest overlays). Disable HW overlays stopped this of course.
I then moved on to 20150706 build on each HD+. The only issues I now see are slight screen instability with overlays and restart about 15 seconds after power-down, which happens almost every time.
P. S. I really like the Nook HD and HD+ tablets. They are perfect for my use as annunciator panel displays for my horticultural controls (hobby), and so plentiful on eBay.
PeteInSequim said:
But I've not been successful with my Nook HD tablet. I started with the 20150706 build which seemed to go well. CM-12.1 booted nicely and the setup wizard led me through initial settings for a while, but hung in one of its "Just a sec" moments after I declined to allow using GPS for location.
I've tried a few more times, but each time CWM fails the wipe maneuver at "formatting data", and reboots to the stock OS.
Click to expand...
Click to collapse
A Factory Reset solved the CWM problem and I was able to get a good install of CM-12.1 UNOFFICIAL build 20150706. I exercised a few things including the Android browser, and entered a URL manually from the overlay keyboard with no screen instability. Really looked good.
Sadly though, after shutdown it won't complete a restart. Just hangs with the cyanoboot universal bootloader banner in view.
Can anyone suggest what might be wrong?
FIRST EDIT: I should add that I am able to restart and boot into the resident TWRP recovery utility that I flashed during the installation. Just can't boot into CM-12.1.
SECOND EDIT: Rebooting from TWRP seems to have blazed the trail for a normal boot from power-up, which has worked 4 times out of 4 tries. Maybe its fixed now.
Still have the unexpected reboot after shutdown, though it doesn't happen every time. It seems to shut down and stay there if I've exercised it a bit with some apps. I did install Netflix and watched a few minutes of something, then shut down and it stayed off.
Things are definitely improving.
Have you tried the latest builds of 12.1 yet? It went beta just a few days ago! Also, twrp now has an official release for both HD and HD plus. As for the occasion of it getting to the cyanoboot banner, then restarting, and completing an of, it happens at times for me as well, but usually when I am changing a lot at a time. Once I get everything set to my liking, it pretty much never gets turned off at all.
ieatabiscuit said:
Have you tried the latest builds of 12.1 yet? It went beta just a few days ago! Also, twrp now has an official release for both HD and HD plus. As for the occasion of it getting to the cyanoboot banner, then restarting, and completing an of, it happens at times for me as well, but usually when I am changing a lot at a time. Once I get everything set to my liking, it pretty much never gets turned off at all.
Click to expand...
Click to collapse
Thanks for the reply. The only builds I've been able to find are the UNOFFICIALS from amaces, for which I am most grateful. CM-12.1 nightly download pages for ovation and hummingbird always come up blank. Where should I look for those beta releases you mentioned?
But yes, I've moved on to amaces's build 20150716, which when installed by CWM 6.0.4.6 from a booted microSD card to a wiped target has shown no problems, except of course for the reboot after shutdown.
But when installed with resident TWRP over an earlier build the "Unfortunately Google Play services has stopped" problem appeared. I got it fixed on one of the Ovations but not on a second one.
I noticed build 20150717 this morning which I might try on an additional Nook (I have 7 of them scattered around here).
I wonder what's counting out the approximately 10 seconds between shutdown and reboot?
It sounds like you might want to try a different gapps file then. The unofficial amaces builds are the ones I meant, the latest ones are great. For gapps try googling "tk gapps pico" its a bare minimal gapps that let's you install the rest that you use from play store. It works for me, so maybe it will help you. Also, a full gapps file runs the ovation and hummingbird pretty hard on RAM, that could possibly cause an out-of-memory error and make the kernel panicked, which leads directly to a reboot. That pico gapps can help by freeing up ram for more useful things than having everything Google has to offer running all at once.
Hello everyone
I have a unique issue with the G2 that I have not really seen before. I rooted my G2 and flashed CM 12 onto it with TWRP. This was about 6-8 months ago. Then, I saw the 12.1 update so I tried to flash it and it failed. I kept trying different nightly builds and none of them worked. Then one day, I could not boot into TWRP at all. The TWRP version has not changed since the day I put it on 2.6.0 and I have not changed anything else. Can anyone please help me to solve this issue because my CM build is starting to show issues and I really need to update it.
Can someone please help me with this???
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
9000RPM said:
After more than 10 months after release, BLU has promised on delivering the marshmallow update. I just saw the notification today at around 4:00PM CMT.
Currently updating!
Click to expand...
Click to collapse
Screen Shots Please....
I just updated last night. Everything running smoothly. I had the phone rooted previously but the one click root app got removed in the update process. If anyone has success rooting after the upgrade, I'd love to know about it.
I upgraded this morning and I've been having lots of issues with my installed apps, like Facebook, Messenger, Whatsapp and more, and of course I lost Root which was previously accomplished by KingRoot which doesn't work anymore.
Also I noticed that during the update process, particularly while flashing the firmware, it was flashed using my TWRP recovery and afterwards it got removed.
I'm sure that if I start fresh by performing a factory reset, all will be fluid and in working order, minus TWRP and Root of course, at least for the time being.
All in all, the update to Mashmellow seems to be awesome, some new features.
Cheers!
I'm having issues with the update. It downloads just fine and when I go ahead and try to install...it just spins around on "unzipping" and then proceeds to restart..or turn off for that matter. The phone turned off...I didn't do anything to it just let it sit there for a while and then I saw the charge icon show up (the one you see when the phone is off and charging) at which point I started the phone up. The phone did not update and I can basically repeat the process. There is 4.30 GB of space free and no SD card. What do I do?
EDIT:
So I tried again, kept at it and it eventually worked. Updated just fine but now there are doubles of all folders in the phone. When I plug it into my computer, all the folders (Music, Download etc etc) are showing up twice with the same contents in the each of them...
What...is...going...on?
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
disChapo said:
Was pretty laggy at first. Decided back up my files and do a factory reset. Works much better now.
Click to expand...
Click to collapse
Yeah, mine is working flawlessly after a factory reset! Much improvement compared to Lollypop!
Anyone found a Root for Marshmellow yet?
Unless Blu changed something other than the interface I'd guess TWRP won't be working on MM anytime soon. It's a problem seen in the Gionee phone and I would expect the same to happen to the Blu. As for root and a custom recovery (although not a great one) you could try following these instructions: https://forum.hovatek.com/thread-15270.html
I've played a bit with the Gionee Marshmallow firmware on my Vivo XL during the past month or so, and one thing that really bugs me is that it seems to be shipping with a kernel that is way older than it should be on an MM release. And the OTA service that is known for leaking info also seemed to still be present in the updated firmware.
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me. And, if you guys manage to get root, check if AdupOTA is still lurking in there.
batoussai said:
Can someone who's got the Blu update check if these two things are the same for the Blu release please? Enter device info in the settings menu and check the Kernel version for me.
Click to expand...
Click to collapse
Kernel Version: 3.18.19
Build Number: MRA58k
Custom build version: BLU_V0030UU_V07_GENERICM14-11-2016
Does anybody with TWPR/root upgraded to official 6.0 successfully? What's exact procedure/steps?
I have my Blu Vivo XL with TWRP now, in last (small) OTA update a few months ago, I tried flashing back to original recovery and rom, but still failed OTA.
I was looking into multi-boot on my xt1060. Not important, just a project. Looking around, I saw a pretty cool project here on XDA called DualBootPatcher and started digging around into whether or not it would work for our device. Maybe not even the xt1060, but any variant of the device. Turns out, as of January 8th 2016, our device (all) is supported by DualBootPatcher: https://github.com/hankching/DualBootPatcher-1/wiki/[Devices]-Motorola and https://forum.xda-developers.com/android/development/list-support-devices-dualbootpatcher-t3278937
Anyone used it? I have an unlocked bootloader and I'm running 5.1, however my device has never been OTA'd past 4.4.2. I think it'd be pretty nifty to dual boot into a non-stock ROM for testing or just to give it a try before you fully commit. I'm also kind of impatient and make weekly backups, so I plan on giving it a shot tonight and will report back how it goes.
Tried
I did try this app on Kitkat 4.4.4. I installed Xperience 7.1 and Gapps Nano, I installed it on data partition, but the phone won't turn on, it only vibrates 5 times.
What I did to restore is installing the utilities.zip from TWRP and changing back to my primary rom.
Sidd24 said:
I did try this app on Kitkat 4.4.4. I installed Xperience 7.1 and Gapps Nano, I installed it on data partition, but the phone won't turn on, it only vibrates 5 times.
What I did to restore is installing the utilities.zip from TWRP and changing back to my primary rom.
Click to expand...
Click to collapse
Same result. Damn. I might keep digging into it if I can find the time.
I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL
MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.