Related
A question for any intellectual Android/Nook-addicts out there...
Basically, I've rooted my Nook HD+ (Numberous times now) and have experience rooting android devices in the past and have had no problems. I used the CWM method - installed universal root on factory stock (And afterwards, 2.1.0 stock just to see if it fixed the problem... it didn't) and extras (Tried not installing extras twice also, didn't make a difference)
Basically, I've learnt the hard way that eight resets on boot and the device hard-resets to factory stock. The first Root Bootup is fine (The bootup after removing the CWM sdc) and, after turning it off and on again, so is the second bootup... But the third one is where the problem occurs. I power on as normal, and the standard 'Nook' screen appears as it begins to boot...
It then proceeds to resetting itself eight times - never getting past the 'Nook' screen that appears at the start of every bootup, therefore causing a hard factory reset.
I've tried using the CWM recover method to the OS I used before rooting the nook originally, and there doesn't seem to be any problems if the device isn't rooted. I've also just let it update itself from factory version to current version - and it works fine with that also.
Perhaps this is common and I'm just a plain idiot. I honestly can't find any answers - so if it is common, sorry for wasting your time!
Thanks for your time!
- P
Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Do you have some apps being automatically installed by Play Store? Sometime people have their settings set so that happens. Then a root app gets installed and makes some changes to /system and causes a reset. Go to Play Store and tell it not to automatically install or upgrade apps.`
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:
P Complex said:
No apps that automatically download that i can see. But you're likely onto something - I do install all the apps manually (No matter how menial) (Going through the list, hitting install for each of them) before manually logging into each one afterwards. I do use a few root apps - no ad-versions to avoid those annoying popups, Ultrabox, Superuser, Pimp my Android and Root Browser to name most, if not all of them.
I'm going to have to do things the awkward way now, installing each app, setting them to the setting I want for them, and seeing what happens. I have a mild suspicion it's a setting on Pimp my Android...
I'll let you know if I sort it. Thanks for the suggestion :cyclops:
Click to expand...
Click to collapse
Why are you installing superuser? It is already installed with the universal root. That may be it too.
Edit: And some of the apps I put on there are old on purpose. Like Root Browser. I have it set so that the free version is ad free. If you update it, the ad free goes away.
Sent from my Nook HD+ running CM10.1 on emmc.
I am VERY sorry it's taken me so long to reply! Even though I've only just joined, I should have done it long before now.
I found the problem - it was 'Pimp my Android' app. I was experiencing something called 'boot loop' - so much for my research skills for such a common problem. I fiddled about with my usual settings - and found some that cause it to get stuck like that, even when they're set not to activate on startup!
Tis' all working now. Everything else seems to be just peachy! You were right, thanks for your help
I am a serial rom flasher. Often flashing a new rom every day or 3. Often times more than once in a day if I am testing new ones or playing with dual booting, etc. With the last few roms I have flashed (AOSP and CM based) I have had issues with TiBu not being able to uninstall apps in /system. Odd, because I have been using this to do so on every other rom since I got the phone (dozens) so it is a recent issue. Nothing else has changed as far as recovery goes and all that, no issues with how the roms run, applying mods, etc, but every time I would uninstall and reboot, the app would be there again. As I prefer inverted Gapps, and typically they work best if the old one is uninstalled, this would not do. I thought maybe it was the type of Superuser access I had or Busybox, as those are often culprits in TiBu issues. Not the case here. Long story short, it's all about the SELinux permissions.
Fix:
http://forum.xda-developers.com/showthread.php?t=2524485
Install that, grant root access, change to Permissive and BAM. Problem solved.
Hope this helps others!
Hopefully this gets added to CM because it gets really annoying after a while. Thanks for finding a fix for this!
Sent from my Nexus 5 using Tapatalk
My pleasure. Can't believe it's not been talked about more...
I'm sorry if this has been covered. I did a search for otter2 in SuperSU forum as well as a google site: search. I have an otter2 on CM 11-20141028-NIGHTLY-otter2. I get the message that the SU binary needs to be updated. When I allowed it, the update ran ok but I could not get it to boot back into anything but TWRP Recovery. Even when I selected regular boot it always booted to recovery. I tried every boot option and it always booted to recovery. The only way to get regular boot back was to reflash the ROM. I realize that this device may not be fully supported but a message said to report this to this forum. Even though there are some oddities like apps not being listed in the SuperSU Pro list, I do get the window to allow SU and it works fine with the file manager and some things work in the Xposed framework so I know the permissions are enabled. I had to give up my Nexus 7 tablet to my SO because she kept insisting I buy her a new one too, so I am pretty happy to have a real android tablet because in the KF2 ROM a lot of things like chromecast would never work right even though it was available in the Amazon app store. Thanks a lot. EDIT: I tried to use the TWRP/CM setting to update. I just noticed on my Nexus 7 that I didn't try update in the regular manner. I will try that way. Sorry.
compwrench said:
I'm sorry if this has been covered. I did a search for otter2 in SuperSU forum as well as a google site: search. I have an otter2 on CM 11-20141028-NIGHTLY-otter2. I get the message that the SU binary needs to be updated. When I allowed it, the update ran ok but I could not get it to boot back into anything but TWRP Recovery. Even when I selected regular boot it always booted to recovery. I tried every boot option and it always booted to recovery. The only way to get regular boot back was to reflash the ROM. I realize that this device may not be fully supported but a message said to report this to this forum. Even though there are some oddities like apps not being listed in the SuperSU Pro list, I do get the window to allow SU and it works fine with the file manager and some things work in the Xposed framework so I know the permissions are enabled. I had to give up my Nexus 7 tablet to my SO because she kept insisting I buy her a new one too, so I am pretty happy to have a real android tablet because in the KF2 ROM a lot of things like chromecast would never work right even though it was available in the Amazon app store. Thanks a lot. EDIT: I tried to use the TWRP/CM setting to update. I just noticed on my Nexus 7 that I didn't try update in the regular manner. I will try that way. Sorry.
Click to expand...
Click to collapse
No idea what an otter2 is. Binary update issues go to this thread: http://forum.xda-developers.com/apps/supersu/support-update-failures-t2907365. Be sure to read the first few posts so you know what logs to provide.
***** TotalX *****
I've built a mofo-flashable system image for the Verizon Moto X 2014 containing root, WiFi tethering, Busybox, SQLite3, Xposed, a symlinked hosts file for adblocking, a custom bootanimation, and the stock Google Dialer that has caller ID and allows you to search for business phone numbers. I also added the stock Google Messenger app. I'm currently working on getting CF.lumen to work, and AirAudio is fully functional with this image. I really didn't do much, most of the hard work was thanks to @JulesJam, @Slack3r, @slogar25, @btdownloads7, and @mikeoswego. Shout out to all of them for their hard work.
Download here:
TotalX-1.3.rar
TotalX-1.2.rar
TotalX-1.1.rar (do not recommend flashing, very buggy and drains battery)
TotalX.rar
Instructions:
Download the Xposed installer if you don't already have it, and install it to your phone but don't do anything with it. Also install AdAway 3.0.
If this is your first time flashing an image with Xposed, go into your file manager and delete /data/dalvik-cache/arm and /data/dalvik-cache/profiles. If you don't already have root, just do this step after flashing and reboot.
Wipe cache prior to flashing:
Code:
adb reboot bootloader
fastboot erase cache
Next, extract TotalX.rar to your mofo directory, flash the image with mofo, and wipe cache when its done:
Code:
mofo flash TotalX-1.1.img
fastboot erase cache
It might take a while to boot up, but at least you can enjoy the crazy new bootanimation. When it finally boots, open up AdAway and go to preferences, scroll down to "Target hosts file" and select /data/data/hosts. This sets it so that AdAway modifies the hosts file in /data/data, which is where the /system/etc/hosts file is pointing to.
If you'd like extra heavy-hitting adblocking, add XXXXXXXXXX to your hosts sources (EDIT: Don't do this, it screws up MMS). Then hit download and apply on the main screen and reboot once its done.
Install any Xposed modules you want and reboot. And here's a great module you can't get through the Xposed app: Pandora Patcher
That's it! You should be all set after that with no ads and the power of Xposed. If you have any trouble flashing, don't be afraid to post here and I'll try to help out. And if you'd like to buy me a beer, feel free to shoot [email protected] some cash on Google Wallet
Changelog:
Version 1.3:
- AirAudio is now fully functional!
Version 1.2:
- Removed build.prop edits due to HDR bug and battery drain
Version 1.1:
- Switched to @mikeoswego's base to fix busybox due to Xposed installation removing busybox for some reason
- Google Messenger app added
- build.prop edits by @trimax84
- New bootanimation taken from @motomotomotoG's collection (Geometry Dark), if you'd like any of the others from that page let me know and I'll make you an image!
- Fixed bootanimation memory leak using fix by @arter97
Version 1.0:
- Original, based on @btdownloads7's image, added Xposed, hosts symlink, 5.1 bootanimation, and Google Dialer.
Click to expand...
Click to collapse
Known Bugs:
- Upon flashing, you may experience Google Play Services constantly crashing. Still not sure what causes this. To fix it, uninstall updates for the Google Play Store and Google Play Services, reboot, and then reinstall the update. No more crashing after that.
- If you followed my instructions earlier to add http://adblock.mahakala.is/ to your hosts sources in AdAway, you will most likely be unable to send MMS. To fix this, revert your hosts file and remove this source, then reboot, reapply, and reboot again.
- Version 1.1 was very buggy due to the build.prop edits. The edits create a bug where the camera app crashes when taking pictures in HDR mode. It also seemed to drain battery at a ridiculous pace and created huge slowdowns. I fixed this in later versions and will not be editing the build.prop in future versions.
Click to expand...
Click to collapse
You are the man. I'm downloading now and will flash as soon as I can. [emoji106]
Install went as expected. I was coming from another version of this img with adaway and xposed and bb, sqlite. I cleared cache before and after install, on boot everything went good, not too long. At first everything was smooth, I was letting it settle before playing with the new dialer, then I started getting mass unresponsive apps, mostly google. I did a reboot and haven't had a repeat of the issue yet. Adaway updates fine, xposed modules load fine, and busybox is good. Google dialer is operational if a little slow feeling to me, oh and the boot animation is gorgeous as well. Great work putting this one together, to all who input.
contesauce said:
Install went as expected. I was coming from another version of this img with adaway and xposed and bb, sqlite. I cleared cache before and after install, on boot everything went good, not too long. At first everything was smooth, I was letting it settle before playing with the new dialer, then I started getting mass unresponsive apps, mostly google. I did a reboot and haven't had a repeat of the issue yet. Adaway updates fine, xposed modules load fine, and busybox is good. Google dialer is operational if a little slow feeling to me, oh and the boot animation is gorgeous as well. Great work putting this one together, to all who input.
Click to expand...
Click to collapse
hmmm.. that sound a little scary might hold off until its confirmed that this was a one off issue. But thanks for the upload!
To be fair it happened to someone else on one of the other threads with a dif image. Seems to be a one off after a reboot. Understand your trepidation though.
It actually just happened to me too. Rebooted and hasn't happened again. But yeah, it also happened to me with one of the previous builds as well, so I think it might just be a one-off problem. Will report if it happens again.
It does that with every new flash. Not sure why, but a reboot fixes that sucker.
Thanks for this! Any chance of getting this image without Xposed?
TokedUp said:
Thanks for this! Any chance of getting this image without Xposed?
Click to expand...
Click to collapse
I can do that, do you want everything except Xposed?
ClydeDroid said:
I can do that, do you want everything except Xposed?
Click to expand...
Click to collapse
YES! I had a very bad experience with Xposed once and i'll never use it again. Thanks. There's no rush though. Im on vacation so I wont be able to flash anything or donate to you until I get back home. I really appreciate it man and I promise I'll buy u some beer as soon as i get back.
Is this based off the image that has the HDR fix?
TokedUp said:
YES! I had a very bad experience with Xposed once and i'll never use it again. Thanks. There's no rush though. Im on vacation so I wont be able to flash anything or donate to you until I get back home. I really appreciate it man and I promise I'll buy u some beer as soon as i get back.
Click to expand...
Click to collapse
Alternatively you could flash this image and not use Xposed i.e. don't install the APK. Libs are't doing anything important.
Mayze23 said:
Is this based off the image that has the HDR fix?
Click to expand...
Click to collapse
Yep!
ClydeDroid said:
Yep!
Click to expand...
Click to collapse
Installed! Thanks for the Birthday Present -
As a suggestion you could modify the Build.prop to add a custom Rom Name under settings and custom details etc. That way you can really feel ownership of your changes.
Also if you really wanted you could delete Verizon Apps under the /system/app partition to remove bloatware but I understand that may be a bit tedious and undesirable. Otherwise really good build, worked well - no issues.
Haxxa said:
Also if you really wanted you could delete Verizon Apps under the /system/app partition
Click to expand...
Click to collapse
Or you could just freeze them with TiBU. If you are not going to be able to use the space for anything else, no sense in deleting them. Also some Verizon customers actually use NFL Mobile, Verizon Navigator, MyVerizon, etc.
I've had the gapps issue as well, basically neutered the phone until I forced a restart. A reboot had fixed it temporarily but it came back again a couple of times. I eventually uninstalled updates for both Play Store (gapps) and Google Play Services and re-downloaded the updates. Have been fine for a while now.
My bluetooth has also been wonky. Used to connect to my car without issue but now I seemingly have to manually connect, or even reboot the phone to get it to connect. Wasn't having these issues on previous images...
Now that I've bltched, I really appreciate the work...and the changes are worth the few headaches! Thanks!
ClydeDroid said:
Yep!
Click to expand...
Click to collapse
Do you have any interest in adding CF Lumen to your image? When I download it, it has to install a driver and that must be something that is installed on /system b/c it never gets installed. However, I don't know if drivers are something that is too complicated to bake into an image.
http://forum.xda-developers.com/showthread.php?t=2711912
There is an unrooted mode but it doesn't work near as well as the rooted mode. With the rooted mode you can get the whites to be a very nice cool-toned white w/o any yellow/pink tinge.
JulesJam said:
Do you have any interest in adding CF Lumen to your image? When I download it, it has to install a driver and that must be something that is installed on /system b/c it never gets installed. However, I don't know if drivers are something that is too complicated to bake into an image.
http://forum.xda-developers.com/showthread.php?t=2711912
There is an unrooted mode but it doesn't work near as well as the rooted mode. With the rooted mode you can get the whites to be a very nice cool-toned white w/o any yellow/pink tinge.
Click to expand...
Click to collapse
Sure, I'll give it a shot!
tjohnstone3 said:
I've had the gapps issue as well, basically neutered the phone until I forced a restart. A reboot had fixed it temporarily but it came back again a couple of times. I eventually uninstalled updates for both Play Store (gapps) and Google Play Services and re-downloaded the updates. Have been fine for a while now.
My bluetooth has also been wonky. Used to connect to my car without issue but now I seemingly have to manually connect, or even reboot the phone to get it to connect. Wasn't having these issues on previous images...
Now that I've bltched, I really appreciate the work...and the changes are worth the few headaches! Thanks!
Click to expand...
Click to collapse
That's really strange. I've only experience the gapps freaking out once, but this is worrying. I might do some research to try to figure out what the problem could be.
ClydeDroid said:
That's really strange. I've only experience the gapps freaking out once, but this is worrying. I might do some research to try to figure out what the problem could be.
Click to expand...
Click to collapse
It's been 5 hours since I did the uninstall updates and reinstall them and I haven't had any issues since. So hopefully it's a thing of the past.
Though I haven't retested the bluetooth since this morning.
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Kov8 said:
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Click to expand...
Click to collapse
Hi Kov8.
I was running CM 11.1 for ovation and experienced the same thing. My solution was to install a newer version.
To save your data, set up an SD card (be sure you have enough extra room for your data) with the TWRP 3.0.1-0 version here:
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
Load TWRP and look for the File Manager. I think it's under "Advanced." You can use that to copy or move your data to the SD card.
After that, consider upgrading to AOSP or LNOS. I can install AOSP without much difficulty, but LNOS doesn't go well. More on that in a later post.
If you need more detailed information, look at this post and download the pdf at the end of the first post:
https://forum.xda-developers.com/nook-hd/general/install-cyanogenmod-12-1-barnes-noble-t3211119
Kov8 said:
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Click to expand...
Click to collapse
Yes. I've been reading that all the recent ROMs do that.
The solution is to do a standard shutdown followed by a hard shutdown (by holding the power button for 8 seconds).
I suspect that going straight for the hard shutdown caused some file system errors that made installing new ROMs very difficult.
I'm OK now, though.
Thanks for the detailed reply! I will try.
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Kov8 said:
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Click to expand...
Click to collapse
That's funny. I just downloaded two copies from that link.
For version 3.2.1-0, it sounds like you're looking at the version from the team win website. I haven't tested that one thoroughly, but I have tried out their version 3.1.1-0. It works pretty well. It gave me some minor error messages here and there, but if I just repeated what resulted in the error, it generally went through on the second attempt without an error.
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Kov8 said:
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Click to expand...
Click to collapse
Mind telling how you managed to update twrp from 3.0 1 to the latest? I successfully installed 3.0.1 to my nook hd+, then flashed 3.2.1 img to recovery, now the device stuck at boot.
I simply downloaded to img file from their website (for ovation, my device), placed on the micro-sd, and installed it from TWRP itself. As simple as that.
Are you sure that you got the correct version for your device?
I also always verify the integrity of roms after writing them to a card. I've seen bad cards.