yashsingh1/xdaforums huggingface dataset:
[Samsung Mesmerize] gr4ybu5h:
I few days ago I found an explanation here on how to do this:

http://www.howardforums.com/showthread.php/1694111-Installing-Clockwork-and-Voodoo-onto-the-Samsung-Mesmerize

(The same explanation bdemartino gave here today)

1. I used the files from there. How do I tell if I am running voodoo5?

2. If its not the same, I've read that I can install voodoo5 over another voodoo, correct?

3. Is anyone having trouble with 3g, vibrate, etc...on the mez? I saw in the voodoo5 thread that a few people were having trouble with these things. I couldn't tell if they were fascinate, mesmerize or captivate.
[Samsung Mesmerize] bdemartino:
That is the old Voodoo kernel, you will need to go to the link I listed in my post for Voodoo 5, and yes you can simply disable lagfix and flash the new one over the old.

And no problems on the write up, I spent a good amount of time digging up the links and stuff but I'll spend a little more time polishing it and will post it in another thread for Scotsman to stickie.

And to answer your last question, no I'm having no problems with any functions of my phone after upgrading to voodoo 5.
[Samsung Mesmerize] gr4ybu5h:
Thanks for the write up and nice job on it too. It seems, sometimes when people try and tell others how to do something, they don't break it down enough. But you did and made it easy for us noobs. Thanks again.

My clockwork ( or voodoo, not sure) didn't come with a "disable lag-fix" button. I just have to create an empty file called "disable_lagfix". I'm just unclear where to put it. I saw it somewhere before I just have to find it
[Samsung Mesmerize] phidelt82:
There isn't a button, per se. When you go in to recovery, there is a disable lagfix option under voodoo. You can put the file, disable_lagfix, in the voodoo folder on your sdcard to do the same thing.

He does write up a good how-to, though, doesn't he.
[Samsung Mesmerize] bdemartino:
Haha thanks guys, and you're welcome!

I think the reason you don't usually see this much detail from others is because they are more developmentally enabled and therefore "forget" to break down the little steps that are second nature to them but foreign language to a non-developer.
[Samsung Mesmerize] gr4ybu5h:
Thanks. I found it. and disabled it aready. now i just download the file in the write-up and boot into recovery, install zip from sd card and select my file correct?
[Samsung Mesmerize] bdemartino:
I always wipe dalvik cache (in advance settings within Recover) before flashing anything.

So it's;

Disable Lagfix

Reboot (you'll hear the chick reversing the process)

Clear Dalvik

Install voodoo 5.0 from zip

reboot

re-enable lagfix and reboot one last time.

Then you'll need to download the voodoo controller app from the market to control the amp gain and set a few other eq settings.
[Samsung Mesmerize] gr4ybu5h:
Man you guys are fast. Thanks for the quick replies. WOW

Ive done all that except re-enable lag-fix. Noone ever mentions that step. Do I just remove the "disable_lagfix" file from the voodoo file and reboot?
[Samsung Mesmerize] bdemartino:
I just enable/disable it through the voodoo menu in recovery, much easier than pushing files around. In your case i think you should be able to delete the file and reboot, but if not you may just need to go into voodoo and enable it that way (after removing the disable file)
[Samsung Mesmerize] gr4ybu5h:
I guess if I edit a post and dont finish it, the post gets deleted. Oh well, I asked how to reenalbe lag fix but i figured it out. Like I said I had to put the disable lag_fix file in the voodoo folder. I just had to remove it from that folder.

Is there a way to tell (besides the quickness and the extended battery life) how do i tell if its voodoo5? just out of curiousity
[Samsung Mesmerize] bdemartino:
Just a guess here but possibly under About Phone the kernel version might? Mine is listed as 2.6.29

I would also think that when trying to use the Voodoo app it would fail if you didn't have the kernel so that would be a sign too, if that's what you're looking for.
[Samsung Mesmerize] gr4ybu5h:
Well thanks alot. Thats what mine was listed as also. And the voodoo app did work, so I guess I've got it. And I think thats all for now.

Now I think I might wait to see the awesome developers come up with for 2.2. I dont mind the stock 2.1 for now. I just dont want to keep flashing ROM's, if they might be close to getting a version of 2.2 going. I can wait....I think.

Thanks Again
[Samsung Mesmerize] phidelt82:
2.2 is so close, you should be able to smell it. I've had it's froyo-ey goodness all over my phone and even with the issues we're still having, I flash it back every night when I get home to play with it.
[Samsung Mesmerize] bdemartino:
That's what she said....:D
[G Tablet General] mandeep1803:
Hello guys,

I got the G tab as a gift. I hated the UI so now I am using ZPad Clean ROM. PDF I have tried a number of PDF readers I have used and all have given me the same problem. While scrolling, the file is blank. It takes about a second for the text to load. I thought that since my books are around 10-100 MB, it must be a problem with the file. I have tried plain text PDFs which are not even a page long and I have the same problem.

Does anyone know a way around this problem?

Thanks!
[G Tablet General] mandeep1803:
Solution!

Found a perfect reader. Loads even the big PDF files easily!

EZ PDF reader

Download Link:

mediafire . c o m /?5b5681x85bwzb55
[G Tablet General] pyrofool:
I use Adobe pdf reader and it works fine. I'm also pretty sure ezpdf is not free so you should probably remove the link.
[G Tablet General] manikin13:
+1

Its in the marketplace, free, and works like an official version should. :D

Only drawback is using file browser to open the file. No native file browser built into the app.
[EVO 4G Q&A, Help & Troubleshooting] lee61561:
Is there a way to restore the original Sprint startup screen?
[EVO 4G Q&A, Help & Troubleshooting] dmexs:
I don't have (nor did I want) the sound that went with it, but here's the original bootanimation zip. Just place it in appropriate path (/system/customize/resource/bootanimation.zip) and check the permissions. (I can't remember what they're supposed to be but 777 should work.)

A lot of people suggest using adb push commands to change boot animations but root explorer with /system mounted r/w works just as well, just don't forget the permissions!
[EVO 4G Q&A, Help & Troubleshooting] lee61561:
I sorry, but beiong new to this I do not know how to put the file there or set permissions. Thanks in advance!
[EVO 4G Q&A, Help & Troubleshooting] evolishesh:
Do you have Root explorer?
[EVO 4G Q&A, Help & Troubleshooting] lee61561:
No I do not. I have never heard of it.
[EVO 4G Q&A, Help & Troubleshooting] evolishesh:
you can download it from the market
[G2 and Desire Z Q&A, Help & Troubleshooting] xmunkeyboix:
okay so im with att and i got my g2 unlocked.

problem is, is that i have no network. i looked at the settings and its disabled.

i clicked the setting for use 2g only but i still cant get internet.

is there anyway i can get internet besides wifi?

help please
[G2 and Desire Z Q&A, Help & Troubleshooting] ianmcquinn:
No network as in you can't even make calls or just no data? If it's no data, you need to be sure to enter in the correct APN settings. Not sure what they are offhand, but you should be able to find them with a search.

If you mean no network at all, how did you unlock the phone?

Edit: My APN settings (under Settings->Wireless & networks->Mobile networks->Access Point Names):

# Name: ATT WAP

# APN: wap.cingular

# Proxy: wireless.cingular.com

# Port: 80

# Username: Not Set

# Password: Not Set

# Server: Not Set

# MMSC: http://mmsc.cingular.com

# MMS Proxy: wireless.cingular.com

# MMS Port: 80

# MCC: 310

# MNC: 410

# Authentication type: None

# APN type: internet + mms

I think you only need to set the actual APN and the MMS settings to get data working though.
[G2 and Desire Z Q&A, Help & Troubleshooting] xmunkeyboix:
i can make calls and text but i just have no internet data.

i got my phone unlocked from a store near my house.

and when i try to go on my APN settings its just blank. nothing shows up
[G2 and Desire Z Q&A, Help & Troubleshooting] xjaynee:
You would have to add it yourself with the settings the user above has provided. I think it's menu and just add/create

Sent from my HTC Vision
[G2 and Desire Z Q&A, Help & Troubleshooting] xmunkeyboix:
i have some other questions too if you guys dont mind.

should i have just gotten the Desire Z since i have att?

i called att and they said i dropped to 2G from 3G but when i check the phone status it says no Mobile network state is Disconnected. i cant even get the 2g.

is the g2 compatible with att when it comes to the internet data?

like i said, i'm texting and sending/recieving calls perfectly fine.

does anyone have an unlocked g2 with att?
[G2 and Desire Z Q&A, Help & Troubleshooting] steviewevie:
A G2 will work on AT&T for 2G data, i.e. EDGE at best. You will not be able to use 3G. You should really sell that G2 and buy a NAM model (Bell) DZ.

Sent from my HTC Desire Z
[G2 and Desire Z Q&A, Help & Troubleshooting] xmunkeyboix:
the thing is i cant even get the 2g.

is the Desire Z around the same price?
[G2 and Desire Z Q&A, Help & Troubleshooting] ianmcquinn:
Did those APN settings I posted not work properly? Did you enter them all in or only the APN and MMS settings? This should have worked (tried on my phone), but you can try entering everything in if it didn't. Maybe a network issue over at your location?

And the last time I looked, the Desire Z NAM was running around $550 to $600 new.
[Nook Color General] khaytsus:
Hey everyone, I'll up front say I'm more a user than a tweaker, so right now my NC (and my wifes) work awesome. I am currently on CM7, but my wife and many folks need to use the stock ROM and until a clean way to update with autonoot and such comes out, hopefully this is useful.

Clockwork Mod won't install an OTA, but I have a feeling that it'll still download it and try to install it, and I'm afraid it will try to install it over and over as long as the file is there. So moving to CWM to avoid the OTA is out.

Renaming otacerts doesn't work, lots of accounts of that.

But in my experience, OTAs always compare the build prop to see if they need to OTA, so what I'm going to do to my NC and my wifes NC is modify the build prop to the new settings and see if that avoids the OTA.

BTW, I know Nookie Froyo, CM7 etc won't OTA, etc, so now that's out of the way.... :rolleyes:

Due to multiple reports that using Root Explorer has somehow screwed up the system requiring users to manually re-copy their old build.prop back, I suggest you DO NOT use Root Explorer to do this.

First thing is look in /media for the uploader, in case it's already downloaded. Delete it if it's there! If you're paranoid, check when you're done with the following too, just in case it snuck in while you were editing ;)

Get the new build.prop from here:

If you're still on Eclair: http://dl.dropbox.com/u/334233/build.prop-1.3.0-eclair

If you're on Froyo: http://dl.dropbox.com/u/334233/build.prop-1.3.0-froyo

Remount the system r/w

adb shell
su
busybox mount -o remount,rw /dev/block/mmcblk0p5 /system

Push the new build.prop to your system

adb push build.prop-1.3.0-[COLOR="Red"]YOURBUILD[/COLOR] /system/build.prop

Note you need to replace YOURBUILD with the appropriate build, Froyo or Eclair, or whatever you named the build.prop..

Now your NC should have thew new build.prop, so now reboot. When you reboot, you should get a pop-up message with a green N saying you've updated to 1.3, but you should not see any update progress dialogs or any indication there was an actual update. Hopefully this makes it not try to OTA to 1.3.0! Please report back! It worked for 1.0.1 with the 1.1.0, as well as the 1.2.0 update out there, and it should work for 1.3.0.
[Nook Color General] khaytsus:
Below is for old 1.2.0 information, don't use this unless you're sure you need to!

Get the new build.prop from here: http://dl.dropbox.com/u/334233/build.prop-1.2.0

Remount the system r/w

adb shell
su
busybox mount -o remount,rw /dev/block/mmcblk0p5 /system

Push the new build.prop to your system

adb push build.prop-1.2.0 /system/build.prop
[Nook Color General] khaytsus:
Once I get a little feedback on this, I'm going to move it to the NookDevs wiki, just don't want to put nonsense there if that's what it is ;) I've done this to both my NC and my wifes, no problem so far, and hopefully it avoids the OTA.
[Nook Color General] jasoraso:
done - we'll see what happens next ....
[Nook Color General] JF-WS6:
newbie

Hello

I am a newbie at all of this and used the autonooter with 1.01. That's about as deep as i planned going with the nook, enough to read, play some games and surf the web. So my question is for someone like me that really may not have the skill as most of you, what would be the easiest way to prevent an ota update that will unroot my nook? Thanks for any advise
[Nook Color General] khaytsus:
I'll keep revising the instructions in the first post, but that's so far the only theory that hasn't failed yet... So get adb to work and follow the instructions. You can do it over Wifi, so even if USB isn't working out for you due to your OS, the Wifi ADB widget on the Market will work.

How to use ADB itself, you can google.. It's fairly straightforward. Basically you'll just need to adb connect ip : port once you know it, the Wifi ADB widget tells you when it sets up.
[Nook Color General] computercarl:
FYI, I just did all of this from Root Explorer on the device. I snagged yer file from your dl.dropbox link, copy it over via root explorer, and set the rights. When I restarted, the little green n told me I had recently updated.

Maybe we can bypass optional future updates by changing our version to something really high like 1.99?
[Nook Color General] odwalker:
Yes I know I never say anything on here but will now. I have used something like this on before I I do think this will work just fine as the Nook already things it's updated so when it checks it's going to see that it is already updated.

Now as to what BN will do in a week or so who knows. We just need some more support for roms and so on for the nook and we will be good to go.
[Nook Color General] danguyf:
ClockworkMod has no bearing on the OTA; it's not the recovery that attempts to download and install OTAs.
[Nook Color General] ChrisJ951:
Used your download link to install it. Says I updated to 1.1.0. Thanks :D
[Nook Color General] khaytsus:
Um, yeah... Let me explain further I guess?

B&N Components decide it needs an update, downloads it

B&N components see the update is downloaded, sets up the OTA update, reboots

Clockwork Recovery does NOT update

System boots

Repeat step 2 - 5 forever?

That's what I meant by "Clockwork won't install an OTA" and such.
[Nook Color General] khaytsus:
Check your software version? Pretty sure it wouldn't show any updates, mine nor my wifes did. I think you probably already got the OTA.
[Nook Color General] bdcrim:
Copied the new build and rebooted. I received a upgrade notice in the notification bar that said I upgraded to 1.1. I checked the new software version for the nook and it also says 1.1. I know I have not gotten anything ota because I have watched all afternoon. Thanks for this. Only time will tell when the real update hits my nook.
[Nook Color General] khaytsus:
Yes, mine too! interesting! Maybe it fooled it, it just didn't expect it to do that :)
[Nook Color General] bdcrim:
Thanks again.
[Nook Color General] ChrisJ951:
I just checked the about settings and it also says 1.1.0 . If im on 1.1.0 I don't really mind since my device is still rooted and works identically to how it did a day ago. I'm guessing it pulls the about settings pulls the data from the build.prop every reboot
[Nook Color General] skaman77:
Maybe in the doctored file we should update the build to something like 1.1.5 so we have something in "device info" that says the device is build 1.1.5 instead of 1.1.0 which would denote the OTA... that way, if somehow the OTA does install it will change to 1.1.0 and we'll have evidence in the setting menu (unfortunately, of failure of the method).
[Nook Color General] bdcrim:
Good thought. Do you want to flip a coin or draw straws?
[Nook Color General] colorado_al:
As soon as I saw the thread about the 1.1.0 update today, I turned my WiFi off. There was no zip file in my /media folder or on root when I made the changes to the build.prop file. When I rebooted, I received a notice in the bar that my Nook Color software had been updated. WiFi is still off, but I am going to turn it back on and see what happens.
[Nook Color General] vasmi:
i also updated file lines thru root explorer and gave me massage that i had been updated. crossing fingers
[Nook Color General] colorado_al:
You might also want to try this:

http://xdaforums.com/showthread.php?p=10923973#post10923973

Not certain about it, but it appears that the URL that is used to look for updates is:

https://csqaint.barnesandnoble.com/bncloud/serciceG

Put:

127.0.0.1 csqaint.barnesandnoble.com

in your hosts file located at /etc/hosts

and your NC should not be able to find the OTA update (if the OP is correct about where it looks for updates)
[Nook Color General] rholm:
I just changed my build.prop file. I had an uptime of 19 days, 22 hours, and 38 minutes. :(

Hopefully, this will stop the OTA update... which would have been much worse than losing

my uptime.

Thanks!

Cheers,

Rich
[Nook Color General] exactor_mortis:
I've updated build.prop per the instructions. Got the green "n", showing I've updated to 1.1.0, so we'll see.
[Nook Color General] wumpus11:
Well, it seems like a long shot since csqaint.barnesandnoble.com doesn't actually resolve. I suspect from the host name it's for QA and only mapped internally within BN.

Maybe the other URLs in the post you cited will be helpful, though.
[Nook Color General] colorado_al:
Agreed.
[Nook Color General] slugbug2010:
Wait.

What????

I'M offline for half a day and come back to find there is an ota i need to lookout for and avoid??

I just got my bc on Tuesday. Updated to 1.0.1, auotnootered, got everything set up last night the way i want it, haven't even done a backup yet......and now this. Ugh

I am not in my comfort zone here yet (Evo experience is great, but that mostly flashable zip files), i used root explorer for the first time last night.

What does this ota do besides unroot us? If we get it, are we able to re-root??
[Nook Color General] pfcwintergreen:
Perhaps there is some obvious reason why this wouldnt work but i will just throw it out there; wouldnt disabling/deleting all of the com.bn system apps prevent the thing from phoning home and or performing the update? I have all of the bn stock apps frozen via titanium backup...will let you know if i get an update push from bn...although i also edited my build prop so if i avoid te update mhight be hard to draw conclusions?

So far no update but time will tell
[Nook Color General] jadambpharm:
thanks for the idea! for those of you not comfort w adb you can also just edit build.prop as text with root explorer. i guess we'll see if my root randomly breaks, signifying the true 1.1 update being pushed. hopefully not!
[Nook Color General] khaytsus:
Yeah, almost 13 days on mine, but if it avoids the frustration of the OTA possibly tearing up my system that works so awesome right now, it was well worth it ;)

I'm going to move it to the NookDevs wiki today and redirect the first post to that, sounds like the procedure itself works fine for everyone, time will tell if it actually stops the OTA. I'll also add mention of Root Explorer.
[Nook Color General] bdcrim:
I also had the bn apps frozen. The ones that concerned me were the cloud apps. I could not download a book that I purchased with any of those frozen. May need to thaw those for downloads and then refreeze.
[Nook Color General] Mike.Nguyen:
Another success. I too completed the process through Root Explorer. Which might be a whole lot more simpler for those who haven't set up ADB. It's just a few renames, a few permissions, and a move, and it's all set.

I had to exchange my NC today due to some weird WiFi issues, so I sideloaded 1.0.1, rooted, uploaded and installed Root Explorer manually to the NC, and then performed this mod, all without WiFi.

After a quick reboot, it said I was up to 1.1.0. Been on WiFi for the past 6 hours, no issues.

This makes the most sense and seems like it works. OP, I think you're a genius.

Not sure about the whole setting it up to 1.99.0 or whatever as suggested. The system may just notice that you aren't on the current version and update you anyways since you won't have the correct buildIDs or timecodes. Similarly, if you are still at 1.0.0 and it updates you directly to 1.1.0, then it really is a simple matter if the BN system recognizing the wrong timecode and updating you.

If this continues to work out for everyone, then this might be the way to go to avoid future updates. We just have to be able to catch the updates before they start OTA transfers to everyone and rewrite the build.prop
[Nook Color General] nadafinger:
Same here, modified, rebooted, it said it was updated (which it isn't)....so far so good. That being said I have another NC in the family that is not rooted, and there has been no OTA pushed to it yet. (According to the site it will be pushed out within the next week). So we'll wait and see.
[Nook Color General] trjcasper:
Newb here. Hopefully this is relevant. Is the OTA pushed by BN or fetched by NC? It seems some of those who were updated were getting these while the NC was asleep/standby, but I don't recall anybody getting it while the machine was in use.

If the NC needs to sleep, with wifi on to get the update isn't it possible those of us who used the wifi off fix to prevent random rebooting could avoid the update? I apologise for my ignorance in advance.
[Nook Color General] jasonfreeland:
Thanks I tried the adb method and got a not found error (I think busybox isn't working right on my system), but got it working via root explorer. Editing the file manually was nerve wracking, but it worked. Thanks again.
[Nook Color General] capnblackleg:
I have root explorer and the new build.prop but I keep getting a read only error when trying to move it. How can I adjust these permissions?

nevermind, I'm retarded.

It worked! 1.1.0. Thanks OP!

Thanks everyone for a great forum.
[Nook Color General] markiejones:
My guess is that a periodic process on the nook checks the status of some remote resource at B&N, and if it gets a hit, kicks off the OTA process which pulls the info from the remote site, and does its thing.

My guess is based upon being in the software biz, and that's how we do it. Push updates usually happen in an contained environment like an corporate LAN.

Still just a guess.
[Nook Color General] trjcasper:
So if the NC needs to check periodically for updates what promts it? I'm guessing it would be instructed to do this while the machine is idle(sleeping) so as not to disrupt a user with a reboot or limited resources lagging in the middle of what they were working on. Since these appear to be updating while asleep/standby maybe wifi off with screen off would work?
[Nook Color General] Netcruzer:
I updated my build.prop with root explorer.

No need to move/backup manually (IMO), as when you save and exit the text editor it automatically backs up the previous file for you.

I rebooted.. ,got the green N, turned on wifi and received a notification saying 'update available'.

I rebooted it again, to make sure the new update does not install, it didn't. If you update your build.prop exactly as described it will to block the installation of the 1.1 update. However I do want the improvements eventually, so hopefully a 1.1 root is in progress from a dev.
[Nook Color General] leedr:
Ditto for me, except I went the adb route. Everything seems OK, but I just made the change, so we'll see.