yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] krelvinaz:
I suspect that you will have to roll back to "get" the OTA... since it will expect the stock GB... however, a dev will roll it into an RUU you can then flash.

Worse case, you S-OFF and get it after that.
[HTC Rezound] refuse2bstopped:
So what would be a good "roll back" or "stock" rom to install?
[HTC Rezound] mjones73:
The stock GB RUU is probably the only one that will work.
[HTC Rezound] dg4prez:
you won't be able to OTA, but you will be able to grab the ruu that will inevitably be posted an hour or so after the ota drops. i wouldn't be at all surprised if we have the ruu as a leak before the ota, anyway.

a few days after that, i suspect that many of our devs will have updated versions of their roms available. they're all itching to get at the ota.

at some point after the ota is released htc will release the source, at which point the kernel devs can get to work making us some decent ics kernels.

as far as aosp based roms, that will depend on devs like protekk (not sure if anyone else is working on this) finding ways to interface with the sense-based RIL apks. i'm pretty sure this will require some sort of go-between layer, but i'm not certain. protekk seems very confident he can make it work due to some difference in the ICS RIL stuff vs. the GB RIL stuff. i don't know enough about it to say why, however. either way, this will probably be the last thing we see - it's gonna take him some time to crack.
[HTC Rezound] Thadrow:
The one x already has an early cm9 build, thry wasted no time lmao
[HTC Rezound] Shiznit14:
That is because the One X is a gsm device, much easier to get AOSP working. Our problem is due to the rezound being an LTE device.
[Samsung Galaxy SL i9003] muhsino:
Hi guys, I have a huge amount of dust in my camera and a small black area which can appears for no reason (it exists on stock rom, custom rom, now on cm9). Black area can disapper and appears in different places and in different shapes (now it is near camera swapping button)

Anyway I want to know is there is a way to get rid of the dust ? Where they enter my phone ? Are there anyone have same problem ?
[Samsung Galaxy SL i9003] rohan.:
You need to open ur phone and clean it by a clorh!

But do it only if u have hardware skills!

Proceed with CAUTION.

Sent from my GT-I9003 CM9
[Samsung Galaxy SL i9003] akashsgpgi:
dude the same thing happened to me

gave it to the service centre 3 times and they cleaned it,sealed some something,..

but it has never recovered , the remains dust free for about 1-2 weeks after they clean it at the service centre and then the dust reappears

so i have stopped using the camera, also i dont require camera at all,as i have it on my other devices

well i did not have any black spots, for me everthing was hazy and foggy
[Samsung Galaxy SL i9003] muhsino:
Thank you for helping. Yesterday I asked to service centre how much they want. It was about 8-9 dollars. So tomorrow it will be fixed. Again, thank you
[Samsung Galaxy SL i9003] kbar1:
I've been through the same. Two times the service center just cleaned the lens and gave it back. The dust used to collect again in two weeks. Then I specifically told them to replace the part (most of the back body you see after you remove the back cover). Now, seems to be fine. I think certain units have a manufacturing defect.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] peoples_flip:
Hello XDA,

I'm currently using ICS Stunner v1.4.19 with the LP6 modem and I personally feel I was getting better battery life with LP5.

My question is can anyone provide a link for the LP5 modem so I can downgrade?

Any links or suggestions would be most appreciated. Do you think I should stay on LP6 or downgrade? If so please leave a link.

Thanking you in advance.

Sent from my GT-N7000 running ICS Stunner v1.4.19
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] bioweb:
I predict geo.samuel is going to post all instructions you need below my post.

Edit: omg, I'm psychic :D

I personally have no issues with the LP6 radio, battery life is great and it's very stable.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] geo.samuel:
Hi

I am attaching both the modems here just flash whichever you want through CWR after clearing cache and dalvik cache.

Personally for me I get Better speeds in data and strong signal strength with LP6

But you can try both for few days and settle for the best.

Moreover Please try to use the search button !! Its there for a purpose!!

Edit

Bio you beat me !! LOL :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] peoples_flip:
Thank you very much.

Sent from my GT-N7000 running ICS Stunner v1.4.19
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] LordManhattan:
Remember that if CWM won't downgrade something (kernel or modem), then change the filename to "update.zip", move it to the root of your SDcard and choose "install update.zip" in CWM.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] peoples_flip:
Question:

I'm currently on the LP6 kernel... if I flash the LP5 modem do I have t reflash the kernel to something else too?

Sent from my GT-N7000 running ICS Stunner v1.4.19
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] geo.samuel:
No bruh just go ahead and give em a swing!! These are just modems!!

SHOT FROM A LOADED GT - N7000!
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] peoples_flip:
Would be it possible to have someone post the LP5 kernel? If I'm going to flash the LP5 modem I figured I should be running the appropriate kernel.

Unless I don't have to?....

Sent from my GT-N7000 running ICS Stunner v1.4.19
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] chasmodo:
You absolutely don't have to. Kernel and modem are independent.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] peoples_flip:
If possible could the LP5 kernel be posted here as well? I downgraded my modem but the battery is still bad... perhaps downgrading the kernel to LP5 would help.

BTW I have betterbatterystats installed and I have no excessive wake locks holding the deep sleep down.

Many thanks

Sent from my GT-N7000 running ICS Stunner v1.4.19
[Motorola Droid RAZR] djerk:
please help,after ota update failed on my razr 912 rooted,i have been searchimg all the forums and there is great info but i'm having trouble putting it all together,running the droid razr utility i get,path not found,i can't find rsd lite either,thought i was all prepared when ota's come out,rom manager,voodoo,titianium,please i need a super hero to help me:confused:
[HTC One S] FunkyELF:
Hi,

I'm wondering if I'll be able to use the Sixaxis Controller app with the One S. Anyone know if this works?

It says it requires root access and even then it depends on the kernel. Is there a stock rom out there that has root?

Mine is supposed to be delivered today.

Thanks,

~Eric
[HTC One S] nerfman100:
Don't know about One S rooting, but try the compatibility test before buying.

I sent this from my Motorola Atrix on MOTOBLUR™.
[HTC One S] FunkyELF:
I already bought it. Works like a charm on my G2 with CM7
[HTC One S] briandresstoyota:
I actually tried this recently. Bumping this older post to see if anyone has any experience with this on the boards, dying for help.

Ok, so step 1, installed compatibility checker, test confirmed compatibility

step 2, installed pair tool on pc and set master address of ps3 controller to local bt address on htc one s

step 3 ran sixaxis app, start, searching for devices...

pres ps button on controller, no worky, lol.

No flashing pair lights or anything. Only flashes all four lights when connected to usb to pc.

running cm10 nightly with stock cm10 kernel
[HTC Amaze 4G] elfrisi:
Well, two days ago I decided to put ICS on my Amaze. Previous to ICS I was Rooted with S-ON, and Unlocked.

I followed the instructions on the Development section to install ICS on my unlocked, S-ON Amaze. However after I installed CWM, and flashed Superuser, Titanium Backup, or any other root app says I don't have root privileges.

From what I understood, once SU was flashed, the device would be rooted.

I used the All In One Kit to put the CWM Recovery, and flash the SU. I did HTC Steps to unlock the phone (which the AIO Kit helped also)

I tried looking for a solution or something before posting, but I couldn't find one in the 80+ pages of the ICS thread in the Development section.

Thanks in advance!
[HTC Amaze 4G] jcparks:
I initially had an issue flashing Superuser-3.0.7-efghi-signed.zip (found here http://xdaforums.com/showpost.php?p=20992340&postcount=4) because I didn't toggle the signature setting in recovery. Perhaps it didn't flash correctly? Make sure it said it was successful at flashing the zip.
[HTC Amaze 4G] Double0EK:
Flash it again.

Wait....I sent this with Tapatalk?
[HTC Amaze 4G] hasoon2000:
I realized that my tool didn't set the SU permissions. I have to fix that. Just flash the SU zip file and it'll be fine.
[HTC Amaze 4G] elfrisi:
Got it working! Thankss!! :)
[HTC Amaze 4G] the show stopper:
is there anyway to root your phone with ics on it ? my phone was unrooted b4 i put ics on it.
[HTC Amaze 4G] jcparks:
You sure can. Detailed instructions posted in development section. Basically you need to unlock bootloader through HTC, flash a custom recovery, load up the superuser zip, then flash it in your custom recovery. More details are given in other posts already.
[HTC Amaze 4G] kered424:
Just going to throw this out there. I flashed superuser after installing ICS to get root. It works for most applications, but one app that it doesn't work with is LuckyPatcher (to get rid of those stupid ads in my other apps). For LuckyPatcher to work, I had to install superSU (can be found from the play store). It seems to be my default root app now.
[HTC Amaze 4G] glacierguy:
Did u install busybox after flashing su by chainz?

Sent from my iced out HTC Ruby
[HTC Amaze 4G] kered424:
Yep, LuckyPatcher didn't like it. Installing SuperSU took care of it, and it works fine with all of my other apps.
[Nook Color General] bowguy:
After I burned your modified Verygreen image file I used EaseUS Partition Master to set the partition to whatever size you need. I then copied the CM9 zip and the gapps zip into the boot directory as well as your modified CMW files. Worked great.
[Nook Color General] jicama:
A couple of things I've found recently:

1. To make ADB over USB work with the NC on Linux, I needed to run

mkdir -p ~/.android && echo 0x2080 > ~/.android/adb_usb.ini && adb kill-server && adb devices

(Found at nookdevs)

2. To modify a stock image so you can flash it from CWM and still have CWM on the emmc, you need to modify one file in the zip: META-INF/com/google/android/updater-script

First change line 1 to

assert(getprop("ro.product.device") == "zoom2" || getprop("ro.build.product") == "zoom2" || getprop("ro.product.overall.name") == "NOOKcolor" || getprop("ro.product.device") == "encore" || getprop("ro.build.product") == "encore") ;

Then from the bottom of the file, delete the lines

package_extract_file("kernel-recovery", "/boot/uRecImg");

and

package_extract_file("ramdisk-recovery.img", "/boot/uRecRam");

I found the first edit here; the second I figured out for myself after I missed it the first time and needed to re-install CWM.

Hope this is useful to someone.
[Nook Color General] RevTom:
Thanks for your many posts all over the forum.

I am a noob, and you've helped. I had a question about your post here.

I see you did this in April. Do newer builds of CM9 automatically fix the naming problem with the nightlies?

As far as I know, I downloaded a January version, and then added a nightly, and I think the nightly installed correctly.

Thanks!

I just keep hacking away...
[Nook Color General] leapinlar:
Depends on where you get your nightly. If you get it at sphsolutions, it is named properly (update-) and will install with the January edition of the image. If you get it at techerrata, they are named cm- and will not install unless you rename to update- or use my new image.
[Nook Color General] 2kst:
I was able to bring a new nook color out of a boot loop using your CWM (5.5.0.4)! Thanks so much for taking the time do document / post this information and the clear/concise way it is done.

Thanks again.
[Nook Color General] cvhovey:
I have no idea what happened. One day my NC was fine. Next time I tried to use it, it varies from bootloop to a dead screen. On rare occasions it will boot, but I get various gapps throwing me f/c right and left.

Let's see, I'm on an older CM7 nightly from a couple months back ... I believe nightly cm_encore_full-253m.zip.

Anyway, I've tried various things from formatting system, cache, etc ... but all fail. I've tried the New Bootable CWM Recovery SD (A10) as well as the CWM update (A8), but not solving anything. Though the CWM update appears to install, it changes nothing as when I get back into recovery, I'm still on the old 3.2.0.1. I've tried to install 7.2 and though it appears to go through the install process okay (i.e. no errors), when I'm infrequently able to reboot nothing has changed.

I've tried the 8 interrupted boots to no avail ... possibly because the boot process fluctuates from going to recovery or bootlooping or black screen or succeeding ... so the 8 step process just doesn't work.

Its though something (system, emmc, or ???) has corrupted and locked me into where I was without allowing anything new to install or change?

Any other suggestions on what I can do to wipe, go back to factory 1.0.1 stock, and start over? The restore procedures that I have seen require formatting system, cache, etc. but as far as I can tell, noting is actually formatting anything.

I'm usually able to back my way out of any problems, but since I don't know how this issue happened when my NC was fully charged and off ... turning into a battery dead NC for unknown reasons, not sure what next since I'm not making any headway.
[Nook Color General] leapinlar:
It really does sound like nothing is taking. You should have been able to go to the new CWM on emmc. But you are still on the old CWM and your formats fail. So, I suspect that one or more of your partitions got corrupted somehow and everything is read only. I do not know a lot about how to fix those. But others here are very adept at that. DizzyDen for one. You might search xda nook color for info on repairing partitions. I know adb is often used for that. Sorry if I'm not much help, but maybe someday when I learn a little more on how to fix them I can help someone.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color General] cvhovey:
Thx ... I'll continue searching and try to find something to fix the partitions.
[Nook Color General] icemanwbs:
One question. What is meant by the term " hard shut down "? I take it that refers to shutting system down using power button ? How else would one accomplish this shut down of the NC ? Uggg I'm such a NOOB ! :o
[Nook Color General] leapinlar:
Hard powering off means holding the power key for like 15 seconds until the device goes completely off, not just to sleep. A short touch does not turn it off, it just puts it to sleep. If you are in a ROM, the proper way to turn the power completely off is to hold the power button until a menu pops up and you select 'power off'. If you are in CWM you should go to the menu item that says 'reboot' and it will. You want to shut your devices down properly so they finish any tasks they have running before shutting down. It's just like on your PC, you don't unplug the power cord on the PC when it's running, you tell it to shut down with the start menu. Hard powering off is just like pulling the plug on a PC. Sometimes it is necessary if things are locked up, but it is not the preferred way to do it.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color General] icemanwbs:
Ahh OK. Gotcha ! Love your guide, been using it since I got my NC :)

I'm pretty good at android flashing with phone ( Samsung fascinate running ICS 4.0.4 ! )

One more thing, do I need to do anything special now that I have flashed the CWM 5.0.0.4 recovery ?

Thanks a million. People like you make XDA a treat !! :thumbup:
[Nook Color General] leapinlar:
No, just leave it there in case you need it in the future. Any time you tell your nook to go to recovery, it will be there waiting.

Sent from my Nook Color running ICS and Tapatalk
[Nook Color General] corvair64:
Okay, I'm REALLY a noob at this...

I have tried my hardest to follow the threads about loading CM7 onto my mSD card in order to allow dual-booting stock (via emmc) and CM 7.2 stable via mSD (an 8GB Samsung class 6), but I feel I really f'd things up.

How I got to here:

1. I tried following this thread:

http://xdaforums.com/showthread.php?t=1000957

Got to where it should have run the cm-7.2.0-encore.zip, but wouldn't find it.

2. Tried renaming to update-cm-7.2.0-encore.zip, as well as udpatei-cm-7.2.0-encore.zip.

3. Started reading more (didn't do that at first because it seemed complete enough).

4. Found your posts towards the end saying things have changed and to go to your tips page, so I did.

5. Read that I should use CWM 5.5.0.4-bootable_SD.img instead WITH SDCard-BootFiles-Rev3.

6. Ran Win32DiskImager with CWM 5.5.0.4...img to image the mSD.

7. copied the Rev3 files into the mSD as well as the cm-7.2.0.encore.zip.

8. inserted the mSD into the NookColor.

9. Booted into CWM.

10. selected the cm-7.2.0-encore.zip and said I'm sure.

11. It installed, i rebooted.

12. It looks like it installed onto the emmc as all my old settings are still there (wireless networks, etc.).

13. Immediately started force closing some process apps.

Now what? I feel I'm in a bad place and need to get back to having a stock 1.4.2 NC on the emmc and CM7 (stable) on SD. Maybe I missed a step (as great as the effort has been to get all this automated and setup, I feel it's still not straight forward enough for me :( ). Any and all help is appreciated.

P.S. Also, Is see CM9 mentioned, but no links as to where to get it for the NC (No encore build either). Is this still beta? If so, I'll stick with CM7 for now.

Thanks again in advance.
[Nook Color General] leapinlar:
Ok, your first mistake was copying the rev 3 boot files to the CWM SD. You should have copied them to the verygreen SD. That way it upgrades the older version to my newest version so it reads the newly named files correctly. And if you wanted CM 7.2 on SD you should have copied that zip there too. (You probably wiped out your verygreen SD to make the CWM SD and that caused your confusion.)

The second mistake was when you used my CWM SD to flash the CM 7.2. It put it on emmc replacing your stock. And if you do that you should have done a factory reset first as the apps as installed on stock do not work well on CM7. That's why you are getting the force closings.

If you want to keep CM7 on emmc, just boot to my CWM card and do a factory reset. That clears out the apps as installed by stock. That also means you will have to install all your apps again. Also you should install gapps. Go to goo.im/gapps and select the latest gingerbread version, download it and flash with my CWM card.

If you are happy with CM7 on emmc, you should flash CWM to your emmc so you don't need my card anymore (see the last paragraph in my item B1 for instructions 'get the flashable version here') Then you can reformat the CWM card to use as a data card for your emmc installed CM 7.2.

If you truly want to return to stock on emmc and CM7.2 on SD, let me know and I will walk you through it. It is a lot more work.

Also CM9 is available but is still in development. If you want that I can direct you to that too.
[Nook Color General] icemanwbs:
New question. In settings/battery use.....it shows " PHONE IDLE " 40%....and "CELL STANDBY" 30%.....since obviously we don't need these, how do I get rid of them ??? Lol; :o
[Nook Color General] leapinlar:
You don't need to. Those are false readings. Just leave them there.
[Nook Color General] icemanwbs:
Help. I flashed cm9 onto SD card. ( from cm7 ). Said was successful, then when I went to re boot, on boot menu, I chose" SD Card Normal" and now its just stuck there. :(

OK....I got it to boot into cm9...! :D. Now screen becomes unresponsive while in use and I have to keep re booting.
[Nook Color General] leapinlar:
Sometimes it is necessary to wipe things when going from CM7 to CM9. That is difficult to do with the SD install. I recommend you go to my item B5 in my tips thread and install the alternate CWM that has been modified to work with SD installs. You can do a factory reset with that and it cleans up the SD. Also wipe system with it. It will not effect emmc. You may want to backup with Titanium Backup first to save your installed apps. Then reinstall the rom and restore your apps with Tibu.
[Nook Color General] leapinlar:
I guess I am stumped. I still would bet it is the burning of the card. To me there is not much more to try. You could read about burning in Windows by reading A9 on the OP. Or you could try formatting the card first with SDFormatter before reburning. You can get free Windows and Linux versions of that on the web. Use the full format with overwrite. There may be something from your earlier burning attempts carrying over.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook Color General] MrPib:
FYI 10.1-RC1 is up. Downloading it now.
[Nook Color General] michaelg1030:
What's the best speaker booster for CM10.1?

Nook tweaks was awesome for CM7, but its not compatible with 10.1.

Thanks.
[Nook Color General] stolenmoment:
DSPManager works on some apps, SpeakerBoost works on others; I don't know why this should be...
[Nook Color General] AgentCherryColla:
Volume Plus. You can get the beta pro version for free on the XDA thread.

Sent from my ~Ballin'~ Nook Color
[Nook Color General] SoraRX:
Okay, so I have this old nook color that I used a boot sd on and got to load CM10 nightly. After a lot of fiddling with it, I unplugged it accidentally and when I rebooted I saw that Cyanoboot hung at "Booting from alternate..." Looking at this thread, I'm led to believe that it is an error with the 2nd partition of the emmc(After booting into stock and doing a reset and getting no result). And I know that there are instructions on this very page but, I just got into this scene, like what? About a few hours ago? So I'd love a reply/advice on how I could go about repairing this issue on this nook with it's broken volume keys... If it's possible in the first place without being able to navigate the menu of cyanoboot.
[Nook Color General] leapinlar:
It is not a partition 2 repair issue. I believe it is a file on partition 2 that tells cyanoboot to boot to the alternate by default. But there is no way of getting there without booting to either CM on SD or rooted stock. There is a file there named device.alt or something like that that needs to be deleted.

Another way is to put the SD in your PC and copy uImage and uRamDisk to uAltImg and uAltRam respectively. Then when it boots, it might boot to CM10.

Sent from my Nook HD+ running CM10.1 on emmc.
[Nook Color General] SoraRX:
I see. Thank you for taking the time to fix a newbie's problem.
[Nook Color General] ralhamami:
Trouble with SD Capacity

First of all, great work on this. I've read all the tips thoroughly, but I guess I am just missing something. I installed everything on my device, and it's working fine, however when I try to use the gallery, it says "No external storage detected" or something of that sort. Do you have any advice you could throw my way? Sorry, if it's a silly question. I just can't seem to get past this one. Thanks in advance.
[Nook Color General] leapinlar:
What version of CM are you running? And do you have a microSD plugged into the slot?
[Nook Color General] gravitysandwich:
Can someone give me a a link to a thread on how to dual boot cm7.2 (mirages) and stock, I'm currently on cm7.2 and I want some of the stock experience:D There's a lot of old threads so if someone can give me updated instructions I would be thankful.