Database Develop

Manual Market Fix

Does anyone know how to manually fix the market issue with not being able to see protected apps. I have a friend who is running DamageControl v2.05 and he does not want to have to wipe his device to fix the market because the rom is running perfectly as it is now (other then the above issue).
I am pretty savvy with adb and linux shell. I just don't know where to start to address this. Any insight would be greatly appreciated, thanks!

moved this to q&a as its a question

why doesnt he just update to 2.08? i dont really think you have to wipe in order to update it. last i checked there wasnt any problems with the market.

No, it will not wipe it I have done it many times, it will retain all info & settings
-------------------------------------
Sent from my HERO200

TY all I'll try this!

Thanks to Decad3nce

Since I do not have enough post's to leave a thanks in the Dev forum. I want to thank Decad3nce for the 1.1 update zip. Worked just like a kernel update. All apps continue to work and root was maintained. I will push a real thanks once I get the post number up.

govee said:
Since I do not have enough post's to leave a thanks in the Dev forum. I want to thank Decad3nce for the 1.1 update zip. Worked just like a kernel update. All apps continue to work and root was maintained. I will push a real thanks once I get the post number up.
Click to expand...
Click to collapse
I can't thank the guy enough. He made it infinitely easier to get the B&N update.
I've been waiting for this update as well as it fixes my Wifi sleep reboot issues. I can now actually listen to Pandora with the screen off. OMG!
Buying this device was like buying my G1. I was happy with the package that I received on purchase day, but as my happiness grew tired, new updates and fixes made it more enjoyable everyday. (There was no BT audio or virtual keyboard in Android 1.0)

sounds like it was a piece of cake to set up as well.
hopefully he sticks around as we need all the help we can get around here
thanks again!!

Same here. Flashed his update over my auto nootered 1.0.1 nook. And everything is exactly how it was. No issues with su root permissions or anything. And like first poster i don't have enough post to say thanks in the dev forum. So ill say it here.
Thank you!!!!!!
Sent from my "NookDroid" using XDA App

+1
Sent from my PC36100 using XDA App

Could someone help me with this update? I pretty much understand Decad3nce's instructions, but I don't understand what clockwork is and how to set that part of it up.
I'm Autonootered with 1.0.1 right now and wi-fi is OFF until I figure out what to do.
Thanks!

Worked like a charm on all three nooks in our house! Thank you! such a great community on XDA! Donations coming shortly!

jblues1969 said:
Could someone help me with this update? I pretty much understand Decad3nce's instructions, but I don't understand what clockwork is and how to set that part of it up.
I'm Autonootered with 1.0.1 right now and wi-fi is OFF until I figure out what to do.
Thanks!
Click to expand...
Click to collapse
Download ROM Manager from the Market. Launch it and at the top, there will be an option to install Clockwork. From ROM Manager, you can boot into recover (CWM). Cool?

jblues1969 said:
Could someone help me with this update? I pretty much understand Decad3nce's instructions, but I don't understand what clockwork is and how to set that part of it up.
I'm Autonootered with 1.0.1 right now and wi-fi is OFF until I figure out what to do.
Thanks!
Click to expand...
Click to collapse
This thread shows how to use clockwork recovery http://www.androidtablets.net/forum...m-manager-nandroid-backup-custom-kernels.html

100% Agree on the Thanks! Updated mine in no time and had no issues at all!! Thanks!!
Now I need to make some posts so I can actually thank the people in Devs!

Wow! Nice. I was worried if it will mess up my auto nootered 1.0.1. I am going to all his update zip via CWR.
And that was my 10th post. Yay!

I haven't seen an answer to this question. Hope it's OK to ask here.
I followed instructions to block the 1.1.0 OTA update by editing the build.prop file, and everything still works right on my auotnootered 1.0.1. Do I need to" unmodify" build.prop before using Decad3nce's pre-rooted 1.1.0 ROM?
Also I saw some weird behavior after installing Rom Manager and Titanium Backup: my NookColor Tools app stopped working, so I uninstalled both, and the tools app worked properly again. Is there a workaround for this?
Thanks in advance. Great forum - i'm getting a lot more enjoyment out of my rooted NC and I have all you experts to thank.

govee said:
Since I do not have enough post's to leave a thanks in the Dev forum. I want to thank Decad3nce for the 1.1 update zip. Worked just like a kernel update. All apps continue to work and root was maintained. I will push a real thanks once I get the post number up.
Click to expand...
Click to collapse
I agree 100% with all of the posts that give this thanks. It worked well for me also.

Am I the only one getting an B&N authorization problem. It gives me a message saying that there has been an authorization problem and must reset. Resets back into 1.01. Happens a few minutes after the reboot into 1.1 ROM.
Good thing I have backups, so that's not a problem. I guess I can wait for a new Auto-nooter. Anyone have ideas?

sunsurfer42 said:
Am I the only one getting an B&N authorization problem. It gives me a message saying that there has been an authorization problem and must reset. Resets back into 1.01. Happens a few minutes after the reboot into 1.1 ROM.
Good thing I have backups, so that's not a problem. I guess I can wait for a new Auto-nooter. Anyone have ideas?
Click to expand...
Click to collapse
Are you restoring data using anything, like Titanium Backup?

khaytsus said:
Are you restoring data using anything, like Titanium Backup?
Click to expand...
Click to collapse
No. It happens even if i leave the unit alone.

jsarche said:
I haven't seen an answer to this question. Hope it's OK to ask here.
I followed instructions to block the 1.1.0 OTA update by editing the build.prop file, and everything still works right on my auotnootered 1.0.1. Do I need to" unmodify" build.prop before using Decad3nce's pre-rooted 1.1.0 ROM?
Also I saw some weird behavior after installing Rom Manager and Titanium Backup: my NookColor Tools app stopped working, so I uninstalled both, and the tools app worked properly again. Is there a workaround for this?
Thanks in advance. Great forum - i'm getting a lot more enjoyment out of my rooted NC and I have all you experts to thank.
Click to expand...
Click to collapse
I had mod'd build.prop on my 1.0.1. autonootered and recently installed Decad3nce's ZIP. Minor problems documented and easily resolved in dev thread. Everything working well.
I never saw your issue with Rom Mgr and Titanium Backup.
Also, big THANKS to decad3nce. Great job!

vinal said:
I had mod'd build.prop on my 1.0.1. autonootered and recently installed Decad3nce's ZIP. Minor problems documented and easily resolved in dev thread. Everything working well.
I never saw your issue with Rom Mgr and Titanium Backup.
Also, big THANKS to decad3nce. Great job!
Click to expand...
Click to collapse
Thanks for your comment. I completed the process within about 10 minutes this morning, and everything seems to be working perfectly. No problems or hiccups whatsoever.
Thanks, vinal and another BIG thanks to Decad3nce. Awesome work.

Problem with ADB
I was doing fine with the autonooter 1.01. Used Decadence's 1.10r2 and now can't install SlideIT and can't ADB into the nook.
I have double-checked that USB debugging is enabled.
I have reinstalled the ROM
I have taken off security, thinking that might have impacted it (didn't help)
I have tried using Astro and ES file managers to copy and paste SlideIT from the \sdcard\downloads to \system\apps\ --that didn't work because \system\apps is read only.
Slide it is in my app drawer, but doesn't show up in my list of available keyboards.
Similar problem with SwiftKey. and KeyPurr. With Slide It, I've tried to install the market trial app, and I've also gone the the developers website and downloaded the 15 day trial which (I believe) is the full app only good for 15 days.
Titanium, superuser, and softkeys are working.
Since I can't access the nook with ADB (btw, I'm using Linux), I'm thinking it's a permissions problem in the ROM.
Any suggestions?

I am also a happy customer. Was running 1.0.1 and installed Decad3nce's 1.1.0 R2 and every thing worked great except Wifi reconnecting after sleep.

[Q] CM 7.1 with all the goodies

I'm having a problem installing CM 7.1 and all the speed/memory tweaks. Ive used MANY different roms with alot of tweaks but this one i driving me crazy. Im trying to install CM 7.1 in CWR 2.5.0.7 with the following tweaks...Firerats 1.5.9 auto patcher and KERN 2.6.35.14-10sept-v1 .....the problem is that i can not get it to boot!!!! if i dont install firerats the rom doesnt boot and goes back to CWR...if i do install firerats the screen just hangs on the htc logo...but without the tweaks CM7.1 boots fine
Please help!!

I did the following with success (this is from memory, hopefully I don't miss anything), I'm using firerats 1.5.8. I did not use a single fr patcher.
First, I flashed the firerats REMOVE zip, just to make sure I was really starting over. then flashed the latest CWM unofficial recovery...5.0.2.6.
rebooted to recovery after each step above though, and repeated wipe data/factory reset, wipe cache.
for firerats, had the mdpartmap settings at 125, 20 (just being extra cautious there, I'm seeing some lower numbers bandied about).
Anyway, from the pretty blue recovery screen, I then flashed fr-recovery, (I think it tells you to reboot to recovery again when done, possibly wiping again, anyway, it tells you) then flashed cm 7.1, gapps, kernal, and finally, fr-boot.
Seems I've heard of folks having some difficulty if they don't use a newer recovery, perhaps others can chime in on this.
After some initial settling in and reboots (it was a little hot at first, a few things were a little flakey), everything seems to be running great. I've only had it on here a few days, and I have not tweaked any performance settings, but so far, gps has been rock solid (isn't this ALWAYS a sticky point for some?) and runkeeper has stopped being so crash happy. Need to see how these things behave with age. A clean installation fixes a lot of things for awhile.

Okay, fired up gps status app, and boom, reboot. But like I said, haven't tweaked any performance settings, left everything at defaults. Will tinker eventually.

wow!!! thank you so much for the very fast reply. I am at work at the minute but i am going to try this ASAP!! Thanks again.
I will keep you informed as to how this worked out. Looks like it should work though

Ok thats awesome!! i got it all to work but i can not get android market to work. I just get FC everytime.
Is there a fix for this?

verybigleen said:
Ok thats awesome!! i got it all to work but i can not get android market to work. I just get FC everytime.
Is there a fix for this?
Click to expand...
Click to collapse
Hmm, not sure, did you use the gapps from the OP for CM7.1? Could try redownloading that and flashing it again.
also, what were your firerat settings in the partmap file? Just checking, in case you didn't use mine, which were generous, as I said.
That rather larger second number in the partmap file resolves a lot of market issues, I never have to apply any "market fixes"

My fault. I used 125 2 in the mtd instead of 125 20....worked great!!! now i can use the market...thank you so much!!! just have ooooooonnnneeeeee other small problem.
Now by busybox wont work. Keep saying no root access when obviously i do...and also i can not fix permissions in rom manager..theres always a problem eh.
Hope you can help...you've been great so far!!! got loads more internal space now

Hrm...I have to admit to never using busybox, at least not directly, I usually just install it if asked when I install/update Titanium Backup (after checking the allow unknown sources in applications settings). Are you trying to execute busybox from terminal or something? Apologies if you tried this but if you have Titanium (you should if you don't), then do this:
Go to titanium backup, go to problems then it will install busybox
I just cut and pasted that from ... somewhere.
verybigleen said:
My fault. I used 125 2 in the mtd instead of 125 20....worked great!!! now i can use the market...thank you so much!!! just have ooooooonnnneeeeee other small problem.
Now by busybox wont work. Keep saying no root access when obviously i do...and also i can not fix permissions in rom manager..theres always a problem eh.
Hope you can help...you've been great so far!!! got loads more internal space now
Click to expand...
Click to collapse

So I finally figured it out. I downloaded the cm nightly instead of stable and everything worked great.
Thank you so much for your help!!!
Sent from my HERO200 using XDA App

Just wanted to say. Just installed the new cm nightly and the new jaybobs kernal ....amazing...the new kernal is super fast and every body should use it! Its the Oct 22 build..I'm flying now
Sent from my HERO200 using XDA App

HELP me Pease. market causes reboot of phone

I rooted my OB using wagstuff13 post with a v20i telus canada rom. When I install or update any stock apps :confused from the market the phone downloads and after installation is complete or near it reboot the phone. Is there something that I can do to try to correct this or am I screwed? Please help as I am Android illeterate, any suggestions are very welcome.

My own reply
daroco said:
I rooted my OB using wagstuff13 post with a v20i telus canada rom. When I install or update any stock apps :confused from the market the phone downloads and after installation is complete or near it reboot the phone. Is there something that I can do to try to correct this or am I screwed? Please help as I am Android illeterate, any suggestions are very welcome.
Click to expand...
Click to collapse
So I am replying to my own post as I dont wish to waste anyones time in trying to help me as I seem to have corrected it. What I did was boot into recovery using anreboot and cleared all caches including cache partition. Now I dont know if that was such a great idea, but it does not reboot on its own anymore. If this was windows I would not have any concerns but sadly it is not, and I have trouble grasping linux as I have been spoon fed windows my whole life. Not that particularly like windows, I actually hate it. I have no time to learn a new O/S as I have too much to do as it is.

Try to install GApps with CWM.
GApps from here.

daroco said:
So I am replying to my own post as I dont wish to waste anyones time in trying to help me as I seem to have corrected it. What I did was boot into recovery using anreboot and cleared all caches including cache partition. Now I dont know if that was such a great idea, but it does not reboot on its own anymore. If this was windows I would not have any concerns but sadly it is not, and I have trouble grasping linux as I have been spoon fed windows my whole life. Not that particularly like windows, I actually hate it. I have no time to learn a new O/S as I have too much to do as it is.
Click to expand...
Click to collapse
I would reflash the rom completely again. Follow my tutorial fully and when done, wipe cache, and dalvik cache (which is under advanced). If installing apps still doesnt work, flash GApps using CWM. Hope this helps
Sent from my LG-P970g using xda app-developers app

If nothing works, try installing the Unofficial GAPPS Signed.
By example, CICI Rom have the same issues whit the apps related to google, such earth, viber, etc. And the only way to fix it, its installing the unofficial gapps, i cant post links because im new in xda, but try searching whit words "unofficial gapps" here in P970 forum.
PS: Sorry for my english....

Unable to edit build.prop with rooted phone

Hello everybody,
I'm new to the forum and not that of a newbie concerning Android but since I've updated to Marshmallow on my Nexus 6 I cannot edit the build.prop, even if I'm root.
I already tried a lot of things, since now I used ES File Explorer to edit the file, but now when I want to save it it doesn't work that message appears "Error occurred when trying to save the file. It will not be saved.". So I say ok I'll try using a Build Prop Editor App, it requests root access, I allow it, then fails.
So after many tries I try to completely reinstall the system a second time, thinking maybe there was something I did wrong the first time I installed and rooted, I installed a root checker, it said my phone was correctly rooted, so I try again with ES File Explorer (With root explorer enabled) still the same problem.
Then I find a tutorial on how to get the build.prop via adb shell, which I try, and I have a message saying "Read only File system", so I try to remount but it still the same problem.
Just for the info, the first time I installed Marshmallow and rooted was with a guide on "theandroidsoul" (sory I can't post links since I'm new). And the second time was with the one on ibtimes.
It might not be useful but I tried two different kernels so it might give you some extra info.
Could someone please help me ? I hope I gave you enough information and sorry if I made mistakes, English is not my native language.
Thank you very much for your help.

What version SU did you flash and what kernel are you running? Why would you tell us you ran two kernels but not mention what ones... Lol, were they both stock
With Benzo M2 and supersu 2.46 I edited and saved my buildprop this morning with es file explorer. TWRP 2.8.7.1

scryan said:
What version SU did you flash and what kernel are you running? Why would you tell us you ran two kernels but not mention what ones... Lol, were they both stock
Click to expand...
Click to collapse
Sorry, I'm new and I knew I would forget info...
So I used BETA-SuperSU-v2.49 and yes the kernels I used were stock, the first one was kernel-shamu-mra58k-color-root, and the second one was ElementalX-N6-2.03.
Thank you

Francis_37 said:
Sorry, I'm new and I knew I would forget info...
So I used BETA-SuperSU-v2.49 and yes the kernels I used were stock, the first one was kernel-shamu-mra58k-color-root, and the second one was ElementalX-N6-2.03.
Thank you
Click to expand...
Click to collapse
neither of those are stock, stock is stock... Stock based maybe...
I don't know that all kernels have it sorted yet. I haven't really looked over which ones do, but it seems like it ended up taking a few extra tweaks that everyone is sorting.
Benzino was the first I head people having success with, and I want to say I have heard hells core was working too. If you just want to make it work, my best advice would be to reboot to bootloader, reflash boot.img, immediately boot to recovery (either the volume rockers, or just fastboot reboot recovery should work). then flash Benzino. I can at least tell you is should work there. Dirty flashing kernel may have issue with ramdisk modifications clashing (I don't really know much about this, but its usually recommended not to flash one kernel over another). Once things are settled in a little more, go back to your old favorite kernel?

scryan said:
neither of those are stock, stock is stock... Stock based maybe...
I don't know that all kernels have it sorted yet. I haven't really looked over which ones do, but it seems like it ended up taking a few extra tweaks that everyone is sorting.
Benzino was the first I head people having success with, and I want to say I have heard hells core was working too. If you just want to make it work, my best advice would be to reboot to bootloader, reflash boot.img, immediately boot to recovery (either the volume rockers, or just fastboot reboot recovery should work). then flash Benzino. I can at least tell you is should work there. Dirty flashing kernel may have issue with ramdisk modifications clashing (I don't really know much about this, but its usually recommended not to flash one kernel over another). Once things are settled in a little more, go back to your old favorite kernel?
Click to expand...
Click to collapse
Waou, I just tried Benzino and Super SU 2.46, it worked like a charm in no time, I even didn't have to reflash boot.img ! Should I still do it ?
Anyway, thank you very much scryan, it helped me a lot

Francis_37 said:
Waou, I just tried Benzino and Super SU 2.46, it worked like a charm in no time, I even didn't have to reflash boot.img !Should I still do it ?
Anyway, thank you very much scryan, it helped me a lot
Click to expand...
Click to collapse
Meh.
If there are no problems there are no problems
If things start going wrong... maybe look there first. I don't know too much about what can and can't happen dirty flashing kernels, so I wont say too much... I just know its not normally recommended, but I've seen plenty of people do it and not have major issues anyways. I think its the kind of thing where if one dev did things one way, and another the other... you don't clear them out and the clash.... I'd just be happy with what works

scryan said:
Meh.
If there are no problems there are no problems
If things start going wrong... maybe look there first. I don't know too much about what can and can't happen dirty flashing kernels, so I wont say too much... I just know its not normally recommended, but I've seen plenty of people do it and not have major issues anyways. I think its the kind of thing where if one dev did things one way, and another the other... you don't clear them out and the clash.... I'd just be happy with what works
Click to expand...
Click to collapse
Yes you're right And I am happy with what I have now, thanks to you
I'm glad it's been so quick !