Related
I hope this helps everyone! I followed the directions for Auto-Nooter particularly the part where it tells you to De-Register your device with B&N. After auto-nootering there did not seem to be a way to relaunch the app that allows you to sync with B&N. Here is how I get re-registered:
Open NookColor Tools
Tap All Settings
Find the options listed "Wireless"
There is 3 options for Wireless, choose the second one in the list.
This will open up the Barnes and Noble starting wizard.
Press Continue with setup, and it will ask you to login to B&N or Create a new account.
Main Target said:
I hope this helps everyone! I followed the directions for Auto-Nooter particularly the part where it tells you to De-Register your device with B&N. After auto-nootering there did not seem to be a way to relaunch the app that allows you to sync with B&N. Here is how I get re-registered:
Open NookColor Tools
Tap All Settings
Find the options listed "Wireless"
There is 3 options for Wireless, choose the second one in the list.
This will open up the Barnes and Noble starting wizard.
Press Continue with setup, and it will ask you to login to B&N or Create a new account.
Click to expand...
Click to collapse
I stumbled upon this today too, can vouch that it does work.
Does anyone know why there are multiple "Wireless" entries listed after autonootering in the NookColor Tools?? BTW, there are multiples of some others too.....Thks
If you try each one, they open up different wifi settings menus, one for the quick access from the notification bar, one for the actually settings menu wifi access, and one for the wizard at the beginning.
Does this fix the auto restore that keeps happening ?
If you reregister the device, will it prevent the nook color from auto restoring the software as it randomly seems to do ?
nmhusa said:
If you reregister the device, will it prevent the nook color from auto restoring the software as it randomly seems to do ?
Click to expand...
Click to collapse
????? Care to elaborate? I dont have this problem.
After rooting my nook, I've registered it to my B&N account like normal, but none of my past purchases show up. It just shows 2 books, the 2 nook manuals. Do I need to refresh the list or something?
Congratulations self, you're blind. Just noticed the refresh icon on the Library screen.
Main Target said:
I followed the directions for Auto-Nooter particularly the part where it tells you to De-Register your device with B&N.
Click to expand...
Click to collapse
I'm a little confused, I do not see any mention of de-registering my nook in the auto-nooter instructions.
How to Use:
Before you begin:
* To update to 1.0.1 you must do a complete wipe.
* You must update to 1.0.1 to use AutoNooter 2.12.25 Instructions Here.
1 You must already have a registered NOOKcolor
2 You must have a Gmail/Youtube linked Account. IF you used a Gmail account for B&N Registration you should use that one for this process.
3 You must either have dd (Linux) or WinImage (Windows) software.
4 You must have an external microSDCard reader or this will not work. Do NOT use the NC.
5 You must have enough intelligence to follow instructions.
Let's get started:
1 Download Auto-Nooter from here: auto-nooter-2-12-25.img.zip
2 Linux: Unzip and use dd if=auto-nooter-2-12-25.img of=/dev/sdcard
2 Windows: Unzip and use WinImage to "Restore Virtual Hard Disk Image" to your SDcard.
2 Windows Alternative: https://launchpad.net/win32-image-writer/+download
3 Unplug your NOOKcolor from computer. (If Plugged in.)
4 Insert AutoNooter SDcard into your NOOKcolor.
5 Plug the USB cable into your computer and your NOOKcolor. (This will boot up the NOOKcolor.)
6 Your NookColor will reboot when it's done.
That was the hard part, now to the simple stuff.
7 Upon boot unlock your screen.
8 At the Android Welcome Screen skip Sign In.
9 Enable Location Services when given the option.
10 Connect to Wifi and launch Youtube from "Extras".
11 Click the Menu button (The one RIGHT of the Up Arrow).
12 Select "My Channel" and Login using your Gmail Account.
13 Exit Youtube and Launch Gmail from "Extras".
14 Sync your Gmail Account and Exit. (If it fails to sync that is fine.)
15 Open up Market and Accept Terms and Service.
If you made it this far your nook should be successfully Rooted. Go Download an App to make sure.
16 Enable Non-Market Installs by running the NookColor Tools App.
17 If your Youtube fails to launch Uninstall and Reinstall Youtube from /data/app
18 Go to Settings > Device Info > SdCard > UnMount > Format
Complete Wipe:
1 8 Failed Boots > Wipes /system
2 Factory Reset > Wipes /data
You must do both of these to completely wipe clean your NOOKcolor.
Click to expand...
Click to collapse
From this thread.
Are you referring to a different set of instructions?
thanks!
idburns said:
I'm a little confused, I do not see any mention of de-registering my nook in the auto-nooter instructions.
From this thread.
Are you referring to a different set of instructions?
thanks!
Click to expand...
Click to collapse
Quick question. I have a NC autorooted and its working great. I'd like to give to my GF so I need to remove my gmail/BN account information and setup one for her. Do I need to de-register with B&N and wipe the NC to be able to reregister it with her gmail/youtube/BN account info?
Thanks.
suzook said:
????? Care to elaborate? I dont have this problem.
Click to expand...
Click to collapse
I have this problem as well. Almost immediately after updating and booting into the pre-rooted 1.1 V2, the Nook reboots and loads the regular 1.0.1 software. None of my previously installed apps show up, but I still have Market (non-working), Rom Manager, and Root. Luckily, I made a recent backup and can get my stuff back, but it's on the 1.0.1 software. I still haven't figured out how to keep 1.1 V2 installed, and I'm not sure if my 950MHz UV/OC kernal 'stuck' either. Someone suggested 'Freezing' Device Manager in Rom Manager, so I'm going to give that a shot.
craigeryjohn said:
I have this problem as well. Almost immediately after updating and booting into the pre-rooted 1.1 V2, the Nook reboots and loads the regular 1.0.1 software. None of my previously installed apps show up, but I still have Market (non-working), Rom Manager, and Root. Luckily, I made a recent backup and can get my stuff back, but it's on the 1.0.1 software. I still haven't figured out how to keep 1.1 V2 installed, and I'm not sure if my 950MHz UV/OC kernal 'stuck' either. Someone suggested 'Freezing' Device Manager in Rom Manager, so I'm going to give that a shot.
Click to expand...
Click to collapse
I have the same problem. Its SO annoying. Constantly back and forth with the resets. I was the one who suggested "freezing" device manager but this is not an acceptable solution. I want to be able to use the B&N store also =/
I've actually decided to give up on this update for now. I'm staying on the 1.0.1 rooted software. Every time I upgrade to 1.1v2 it auto defaults to an older version. "Freezing" device manager did not help.
[UPDATE] So I gave it one more shot. This time I removed all the permissions of any file in system/app that seemed B&N related. Rebooted. Then I used Rom Manager to update to 1.1V2. So far no issues, and I can use the Library feature. I'm still afraid to click the "lend book" and I think I will completely remove it as soon as I figure out how (there doesn't seem to be a matching apk in system/app).
craigeryjohn said:
I've actually decided to give up on this update for now. I'm staying on the 1.0.1 rooted software. Every time I upgrade to 1.1v2 it auto defaults to an older version. "Freezing" device manager did not help.
[UPDATE] So I gave it one more shot. This time I removed all the permissions of any file in system/app that seemed B&N related. Rebooted. Then I used Rom Manager to update to 1.1V2. So far no issues, and I can use the Library feature. I'm still afraid to click the "lend book" and I think I will completely remove it as soon as I figure out how (there doesn't seem to be a matching apk in system/app).
Click to expand...
Click to collapse
How did this work out for you? Did you try the Shop button?
Everything works that i need. The Shop icon says application not installed but i can use the library, reader, and accidentally hit the lend book feature without the dreaded reboot.
Sent from my LogicPD Zoom2 using Tapatalk
FYI, I found out the random resets are caused by Titanium Backup. When you restore system settings with it, I think the AndroidID gets changed and then it resets. I restored from stock, installed Titanium Backup, restored ONLY the apps NOT data and I'm set.
I can goto the shop or use Lend Me with no issues.
swordfury said:
Quick question. I have a NC autorooted and its working great. I'd like to give to my GF so I need to remove my gmail/BN account information and setup one for her. Do I need to de-register with B&N and wipe the NC to be able to reregister it with her gmail/youtube/BN account info?
Thanks.
Click to expand...
Click to collapse
I have the same question - this ever get answered? (I couldn't come up w/ the right search string :/
spyz88 said:
FYI, I found out the random resets are caused by Titanium Backup. When you restore system settings with it, I think the AndroidID gets changed and then it resets. I restored from stock, installed Titanium Backup, restored ONLY the apps NOT data and I'm set.
I can goto the shop or use Lend Me with no issues.
Click to expand...
Click to collapse
Somehow I do not think this is the issue... Since this is happening to me and I do not even have Titanium Backup. Everytime I turn on Wifi it reregisters my Nook... So frustrating.
I am thinking of purchasing a used NC @ v1.1
Do I simply create or new B&N account? Or is there a de-register -> re-register process? Or is this something that the seller needs to do?
TIA
Ok guys my dilemna is pretty straightforward:
First of all the reason for decompiling, I hate apps that don't rotate... I use my Streak in landscape 99% of the time like it was meant to be used... so I had an app that I wanted to convert, Remote Web Desktop...
So the whole thing goes perfect, BUT when I want to install over the existing app it says app not installed, BUT if I uninstall the existing app and replace it with mine then I'm all good.
So I'm sure it has to do with signing, but I don't know how to do anything about that. I'm using Sign+ v1.2.2 to sign my apps if that makes a difference. And the only thing I'm changing is the AndroidManifest.xml to enable rotation to sensor instead of portrait or landscape.
Any help would be appreciated
Editing apks obviously invalidates their signatures.
normal apps (installed in data) only allows correctly signed apks. The cert must also match when updating.
system apps (ie installed in system\app) do not, their signatures are genrally not checked, except if when updating if applicable
It's exactly as you described, if you want to modify an app you must resign it and cannot update it automatically anymore because it's cert is different.
The only way to update in the future is to bug the dev to add in your change for all users or to update manually every time for both reasons.
Thank you TheManii, that's exactly the type of answer I was looking for to make sure I wasn't doing something wrong or had left out a step.
So you are saying that when an update comes along, I won't be able to install it, I will have to manually uninstall my version as I did before and install the new version?
Yes, one of the first things the app updater checks if the app is signed with the same cert as the previous version, along with the internal version number
Thanks again, I guess it's a step I will have to bear and I'll write to the devs of the apps I have modded...
S-on and rooted.
Noticed this with Aurora about a week ago. Thought it was just a problem with that app. Now I discover the same problem trying to update VLC.
"Unknown sources" box IS checked.
Any ideas?
_________________
Try to give us a little more information.
When you say sideloading, do you mean installing from an apk on your phone, or pushing one with adb?
At what point in the process do you get an error or stoppage, and describe what that stoppage or error is.
zourn said:
Try to give us a little more information.
When you say sideloading, do you mean installing from an apk on your phone, or pushing one with adb?
At what point in the process do you get an error or stoppage, and describe what that stoppage or error is.
Click to expand...
Click to collapse
Sure.
I was trying to update from an apk that I had downloaded to the phone. (Same behavior for apks for two different apps, Aurora and VLC.)
The install process starts, but can't get past the "Cancel / Install" dialog screen unless I select Cancel. When I try to select Install, it behaves as if the button is not recognized.
dm5530 said:
Sure.
I was trying to update from an apk that I had downloaded to the phone. (Same behavior for apks for two different apps, Aurora and VLC.)
The install process starts, but can't get past the "Cancel / Install" dialog screen unless I select Cancel. When I try to select Install, it behaves as if the button is not recognized.
Click to expand...
Click to collapse
Yeah, that sounds like an overlay issue. Do you have HALO or a screen filter running on your phone? Or anything that draws on top of everything else? If so, try disabling it, then installing the apk. If that works, you can enable whatever it was again without any issues (until you need to install another apk from sd).
dm5530 said:
Sure.
I was trying to update from an apk that I had downloaded to the phone. (Same behavior for apks for two different apps, Aurora and VLC.)
The install process starts, but can't get past the "Cancel / Install" dialog screen unless I select Cancel. When I try to select Install, it behaves as if the button is not recognized.
Click to expand...
Click to collapse
I had this issue, I think it was on TRON, with ribbons enabled.
#BlameAnt
zourn said:
Yeah, that sounds like an overlay issue. Do you have HALO or a screen filter running on your phone? Or anything that draws on top of everything else? If so, try disabling it, then installing the apk. If that works, you can enable whatever it was again without any issues (until you need to install another apk from sd).
Click to expand...
Click to collapse
I uninstalled a bunch of apps. I tried after a handful at a time and finally had eliminated the culprit. Thanks.
I'm not sure which app is the culprit, but I'll try to sort that out.
Thanks for the feedback.
_________________
so I picked up a used pixel from craigslist. seems ok. but I starting thinking... how can I be certain this phone is not booby trapped. it would be awful to have a trojaned device and not really know it.
I searched quite a bit about about malware that can survive factory reset. so it seems that simply resetting is not so great.
then I thought adb sideload an official google factory image to both slot a and slot b would purge any demons. but then again, I cannot find any documentation that make it clear what get overwritten and and what doesn't. (eg do the bootloader or recovery partition remain intact... seems like a great place to hide malware on a booby trapped phone). similarly, it is unclear what /system paritition blocks get replace.. all of them? some of them? can a clever trojan/rat survive an ota?
and then there is the full factory image install via fastboot. the problem is that I cannot enable oem unlocking b/c Verizon locked bootloader. booooooo
final thing. and the trigger that really had me thinking about this. after setting up the phone and connecting to the network, I saw a notification that subtley asked to install a Google screen reader. no idea why. and no google searches return anything useful. was this device hacked already??!
specifically the notification said:
"install app for screen share" and "tap to install from the play store"
so, any security minded android users out there who can help me understand if I need to trash this phone?
Infrequent pop-ups when using a web browser or when running an app can be normal. However, if you are getting pop-ups even when you’re not opening a browser or when using a totally different app, there could be malware in your phone. Malicious pop-ups are often brought about by a bad app that you may have installed in the past. In some cases, legit looking apps may update to a sinister version after some time and cause pop-ups to be displayed.
Run the phone in safe mode and observe it. Safe mode is great tool in detecting a problem app. On this mode, all third party apps will be suspended so if the problem is absent when your Android is running on safe mode, that means there’s a malicious app in the system. While in this mode, you should be able to use preinstalled apps normally as well as use basic networking services without a problem.
My recommendation to have a malware-free phone:
Do a factory reset
Before re-installing any app install an anti-virus app
So will sideloading an official factory OTA image using adb from recovery, completely remove any malware? (I read about malware that can survive a factory reset.)
Also, has anyone else ever seen a notification asking to install a screen reader? This appeared after a factory reset, immediately after connecting to the wifi network. No apps installed.
A factory reset really only deals with the Data and the Cache partitions. System partition isn't affected. This is true regardless device is rooted or not So if malware got installed in System partition it survives a factory reset. A factory reset will also not remove any ROM upgrades or OTA's.
Hopefully by now you have a better understanding of what a factory reset is.
May be the browser - what typically is installed as system app / system-privileged app - is the culprit: Use another browser and see what happens.
I think I understand how the factory reset works. For this discussion, I am do used on Google Pixel line, no modifications, and no root, and only app from the official Play Store.
The adb sideload of a Google factory OTA is the part I don't fully understand.
For example, doe the OTA merely replace files? Or does to do a bitwise blocklevel swap? Does it modify anything in the bootloader, or recovery partitions?
I cannot find clear documentation on this.
The notification requests to install Screen Reader do not come from Chrome or any browser. They appear to come from the system. (Android 10).
So what I am trying to figure out is whether some malicious actor/app installed a persistent malware into the system partition, or the bootloader, or the recovery. Such that a factory reset cannot remove it (like with xHelper malware)
Like for example, can a malware get into the system partition, and a manual adb OTA sideload , or even manual fastboot factory image install, fail to remove the malware from the system partition? That would be. a nightmare for security.
Finally, I cannot find any documentation from Google that Pixel (3) on Android 10 will automatically try to install a screen reader as a native operation.
Basically, is this used, never rooted phone, permanently Trojan-ed junk now?
@thehighhat
Sorry to say this: I'll no longer waste my time with this ...
oops: duplicated post deleted
jwoegerbauer said:
...
My recommendation to have a malware-free phone:
Do a factory reset
Before re-installing any app install an anti-virus app
Click to expand...
Click to collapse
OK. Not sure why you're done with this - if you have insight, sharing it is good for everyone.
anti-virus (13 different ones) all show no malware. shows it is clean.
there are well known malware that can survive a factory reset.
the notification to install "screen reader" occurred immediately after a newly wiped phone connected to internet, even before any of the default apps (chrome, settings, etc.) opened
still looking for answers from someone who knows:
has anyone ever seen a system notification asking to install a "screen reader"?
does anyone know if
Code:
adb sideload official.google.ota.img
on a pixel modifies the boot partition or the recovery partition?
does anyone know if that manual ota install will guarantees the system partition contains only unmodified valid files/blocks?
thehighhat said:
OK. Not sure why you're done with this - if you have insight, sharing it is good for everyone.
anti-virus (13 different ones) all show no malware. shows it is clean.
there are well known malware that can survive a factory reset.
the notification to install "screen reader" occurred immediately after a newly wiped phone connected to internet, even before any of the default apps (chrome, settings, etc.) opened
still looking for answers from someone who knows:
has anyone ever seen a system notification asking to install a "screen reader"?
does anyone know if
Code:
adb sideload official.google.ota.img
on a pixel modifies the boot partition or the recovery partition?
does anyone know if that manual ota install will guarantees the system partition contains only unmodified valid files/blocks?
Click to expand...
Click to collapse
If you fastboot flash an official google system.img partition. From Google. With the correct hash value to insure correct download. It should flash the entire partition. Same goes for any other partition. If you have a certified unmodified image and flash it, the entire partition should be flashed, not just part of it.
With OTA updates. You only get patches. At least that's how the normal process goes. You got the smaller sized ota update and it only modifies the specific files that are being patched for that particular OTA update.
So with normal OTA only pieces of the partitions get updated. Sometimes they all are not touched with every update.
Delgoth said:
If you fastboot flash an official google system.img partition. From Google. With the correct hash value to insure correct download. It should flash the entire partition. Same goes for any other partition. If you have a certified unmodified image and flash it, the entire partition should be flashed, not just part of it.
With OTA updates. You only get patches. At least that's how the normal process goes. You got the smaller sized ota update and it only modifies the specific files that are being patched for that particular OTA update.
So with normal OTA only pieces of the partitions get updated. Sometimes they all are not touched with every update.
Click to expand...
Click to collapse
Thank you. This is exactly what I was looking for
So it sounds like file level replacement instead of block level.
Does the ota verify the other files on the system partition that it does not intend to modify?
thehighhat said:
Thank you. This is exactly what I was looking for
So it sounds like file level replacement instead of block level.
Does the ota verify the other files on the system partition that it does not intend to modify?
Click to expand...
Click to collapse
It does in the sense that it verifies before and after the process begins/ends, the correct size of the partition. This is true in the sense of Ssmsung devices and how the typical standard recovery image works.
But it is the update zip that does most if not all of the size/digest verifications after the files have been patched. Because there is no real way for the rom to know how big the updated build(s) is going to be before the update arrives.
Generally I've seen it verify all the hash values are the same as last time it updated when it begins. And the update zip specifies the ending size.
This might not be the right place to ask this question but I have been lurking here for a bit and am hoping someone can help me out.
A quick bit of background. I just recently started using Android Tablets. So far all I do with them is to read ebooks, browse the web in an emergency, and, wirelessly access my Xfinity live TV and Peacock streaming service. I have 3 Onn tablets (7", 8" and 10") one of which is Android 10 and the other two are Android 11.
I have absolutely no interest in anything Google and have disabled pretty much all the pre-installed apps based on guides I found here. The only pre-installed apps I use are Files-by-google and Gboard. I use the Nova7 launcher. I do have a google account and access to the google play store but only use it in the extremely rare case I want a purchased app, otherwise I download APK's from sites like APKMirror and APKPure to my PC, validate them using MetaDefend and VirusTotal and then load to the device via usb.
I also have no interest in any cloud based storage.
In general I have all goggle apps disabled. In the rare case I do use the play store I have to first enable Google Play Services and Google Play Store and then once the specific app is installed I re-disable Google Play Services and Store. Also I only go online to use the Xfinity and Peacock apps, everything else I do offline.
So everything worked as I wanted it until at some point I allowed an Android 11 "security patch" to install on one of my Android 11 devices. Immediately I could no longer install any APK file on that device (see attached). Note that previously I could install apps with the Nova7 launcher, the Files app, the Files-by-google app and Firefox, all of which are enabled to install unknown apps. Now all of these methods result in the same error message (see attached). Still no problem installing on the Android 10 device or the other Android 11 device that I've kept from updating.
So does anyone know how I can get back to being able to install APK's? I've followed the standard recommendations of restarting the device, making sure install unknown apps is enabled and reset app preferences and the only thing that I see to do at this point is a factory reset. A factory reset would cause me a whole lot of pain to set things back up to how they were before and I'm not even sure that a factory reset is guaranteed to fix this.
Can anyone help me?
A factory reset won't undo the update.
If that is the cause and there's no work around you would need to reflash to the version without the update. System upgrades/updates tend to break things...
blackhawk said:
A factory reset won't undo the update.
Click to expand...
Click to collapse
That's what I was afraid of.
At this point for $59 I can throw out the old one and buy another but that brings up the question of how to disable system updates.
Would rooting the device solve the problem?
So far I've been able to do everything I wanted to do using adb shell pm disable-user --user 0 <package_to_disable>.
But given I'm going to throw the device out if I can't fix this, it seems like the perfect candidate to risk trying to root.
Mumblefratz said:
That's what I was afraid of.
At this point for $59 I can throw out the old one and buy another but that brings up the question of how to disable system updates.
Click to expand...
Click to collapse
It looks something like this. I use Package Disabler to kill this parasite, it's the first apk I disabled... with extreme prejudice
A ADB edit will work too.
blackhawk said:
It looks something like this. I use Package Disabler to kill this parasite, it's the first apk I disabled... with extreme prejudice
A ADB edit will work too.
Click to expand...
Click to collapse
The Package Disabler app that you showed in your screenshot looked like a better way to go that what I've been doing which is to use Application Inspector along with ADB but I've had some problems trying to install it.
For one thing they change a couple of things in MI settings and I don't have that category of setting. The bottom line is that I still haven't been able to get PD to work although the set-device-owner command did seem to work and resulted with the following:
C:\ADB>adb shell dumpsys device_policy
Current Device Policy Manager state:
Device Owner:
admin=ComponentInfo{com.pdp.deviceowner/com.pdp.deviceowner.receivers.AdminReceiver}
name=
package=com.pdp.deviceowner
isOrganizationOwnedDevice=true
User ID: 0
Enabled Device Admins (User 0, provisioningState: 3):
com.pdp.deviceowner/.receivers.AdminReceiver:
uid=10156
followed by a whole bunch of other stuff.
At this point it seems best to forget about Package Disabler and just continue with Application Inspector and ADB but I'm worried that the device owner change I made is going to screw me up sooner or later.
My question is do I have to do (yet another) factory reset and reinstall all my stuff or is there an easier way for me to undo this owner setting?
PS. I suddenly got a notification "this device belongs to your organization" This must have something to do with the owner thing.
Mumblefratz said:
The Package Disabler app that you showed in your screenshot looked like a better way to go that what I've been doing which is to use Application Inspector along with ADB but I've had some problems trying to install it.
For one thing they change a couple of things in MI settings and I don't have that category of setting. The bottom line is that I still haven't been able to get PD to work although the set-device-owner command did seem to work and resulted with the following:
C:\ADB>adb shell dumpsys device_policy
Current Device Policy Manager state:
Device Owner:
admin=ComponentInfo{com.pdp.deviceowner/com.pdp.deviceowner.receivers.AdminReceiver}
name=
package=com.pdp.deviceowner
isOrganizationOwnedDevice=true
User ID: 0
Enabled Device Admins (User 0, provisioningState: 3):
com.pdp.deviceowner/.receivers.AdminReceiver:
uid=10156
followed by a whole bunch of other stuff.
At this point it seems best to forget about Package Disabler and just continue with Application Inspector and ADB but I'm worried that the device owner change I made is going to screw me up sooner or later.
My question is do I have to do (yet another) factory reset and reinstall all my stuff or is there an easier way for me to undo this owner setting?
PS. I suddenly got a notification "this device belongs to your organization" This must have something to do with the owner thing.
Click to expand...
Click to collapse
Not sure as I never used that approach. I use whatever comes in handy...