Database Users

[HOWTO] Update to 4.0.3 OTA ICS from any version with Root access (For I9020T/I9020A)

Okay First of all download the following files
a)http://android.clients.google.com/packages/ota/google_crespo/VQ8PQk_V.zip (4.0.3 OTA)
b)http://android.clients.google.com/p...a25375426.signed-soju-ota-189904.1ada2537.zip (2.3.6 Official I9020T Build)
c)http://bit.ly/su2361ef (SU flashable)
d)http://forum.xda-developers.com/showthread.php?t=988686 (Grab recovery form this thread)
e)http://developer.android.com/sdk/index.html (Grab the android SDK installer)
f)http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429 (Radio file only required for I9020A)
Okay so when done with all that proceed as follows
1) Backup your current apps using Titanium Backup (Optional/Recommended)
2) Backup(Nandroid) your rom using backup option in CWM (Optional/Recommended)
3) Do a full wipe, wipe sdcard, system, data, cache Transfer a,b,c,f to your phone.
4) Flash the 2.3.6 Official I9020T Build you had downloaded using the install zip option in CWM (IMP-DO NOT REBOOT RIGHT NOW)
5) Flash the flashable SU file you had downloaded and then reboot.
6) Once your phone is on, continue to set up your account or skip it as you wish. (Optional)
7) Open up market, download the latest SU app, Voodoo OTARootKeeper, Titanium Backup and any other app you use that requires root.
8) Open the updated SU app, hit menu button and click preferences, go all the way down, click on su binary(tap to check for updates) , and make sure it updates to v3.0.3
9) After that is done, open and allow root permissions to all your root apps. (This is important)
9.5) Run Voodoo OTARootKeeper and click on protect root, make sure all options get checked.
10) Turn off phone, keep volume up and power pressed to boot into fastboot.
11) Select recovery with volume buttons and use power to launch.
12) Once you see a android bot image and an arrow image, keep volume up pressed and press power once, then you'll see some options appear.
13) Select apply update option and find the official 4.0.3 OTA file you had downloaded and flash. Reboot.
14) Once you have booted into ICS, go to Voodoo OTARootKeeper and select resture Root, all options should now be ticked, if not something went wrong.
15) Voila, you have root. Now to get back CWM recovery you can follow this -
i) Place the recovery img file in the android sdk platform-tools folder
ii) Switch to the directory where you unzipped the Android SDK & go to "tools"
iii) Then type "fastboot flash recovery yourfilename.img" & hit enter
iv) That should do it.
v) Optionally you may do it form Rom Manager too, if it works.
16) (ONLY FOR I9020A) Reboot phone, turn it off, boot into fastboot, select recovery, CWM should launch, flash the radio file you had downloaded to get radio working on I9020A (ONLY FOR I9020A)
Root only works for the apps that were installed while on 2.3.6
http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip , use this root file, flash it in cwm, everything works, permissions etc.
This might work for other variants, tested on I9020A and I9020T, I take no responsibility for anything that might go wrong with your device. I take no credit for any links or procedures provided in this guide, I just tested and compiled.
Thanks and best of luck.

..........

Good guide but first two links are broken.

bajansurfer said:
Good guide but first two links are broken.
Click to expand...
Click to collapse
Thanks, fixed.

Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?

poging22 said:
Do I really need to flash official 2.3.6 before ICS? what if I wipe and format then install 4.0 immediately?
Click to expand...
Click to collapse
Might not work, though you can try, if it fails, do it my way, also its impossible to get any kind of root that way.

Link for the ATT Radio doesnt seem to be working

Great work!
wipe SD card?
Is this necessary?

I don't think it's necessary to wipe the SD card, I followed the procedure in http://forum.xda-developers.com/showthread.php?t=1396913 and although it said my SD card would be wiped, everything was still there after I was done!

Anyone on a i9023 tried this?

Hmm...does "any version" includes M200(Korean Nexus S)?
Sent from my Nexus S using Tapatalk

http://attachments.xda-developers.com/attachment.php?attachmentid=687157&d=1313224429
I think he meant that for the 9020A radio

Link fixed, sorry for that, SD wiping might not be necessary, but I suggest as it makes it cleaner. Might work for I9023 and M200, I have no clue, maybe some experienced developer can answer that better.

Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.

Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?

little hiccup at step 12. im getting the android bot with exclamation mark but i press volume up with power and nothing happens. menu doesnt show up....
Edit: NVM... i pressed it 3 or 4 times and it finally worked

Michie23 said:
Hi mine keeps hanging in the boot animation and can't get into recovery, what else can i do? Is my phone bricked?
Click to expand...
Click to collapse
You should post it in questions, I cannot answer this.

fromthestars said:
Not to crap on a great tutorial, This is exactly what I would be looking for if I were not already set up and running. Last night was a dizzying whirlwind of flashing, high heart rates and finally becoming familiar with fastboot and flashing things like that.....lol
But in the end I simply found a cwm flashable zip without radio or bootloader and installed through cwm like any other rom. As far as root all I did was flash a zip file found on the forums and I was good to go.
Click to expand...
Click to collapse
Many ways of doing it, I just am suggesting one, the flashable zip for ics isn't available as yet, what did you flash?

i9020 keeps getting status 7 aborted and my padlock is still unlocked on t-mobile 2.3.6

Has any tried this on an i9023? Thank u
Sent from my Nexus S using xda premium

[GUIDE]Fix unknown serial ROOT stock ics w/o binary incr/cfw flash guide !

hi guys this is my first post i'd expect you all to go easy on me if i make any mistakes,but i have tested it on my international s2 and this method works fine ! this will give you root access and allow you to install all sorts tweaks and custom roms without triggering the binary count !! yep that's right !!
WHAT THIS GUIDE IS GOOD FOR :
*Clean install of ICS.
*Gaining root access with custom kernel flash or increase binary count. NO YELLOW TRIANGLE !
*FIX FOR UNKNOWN SERIAL NUMBER.
*Sorta detailed guide for installing cm9 or any other custom rom.
here's what you need :
*odin 1.85 [link attached]
*check fus downloader . [link attached]
*official stock samsung i9100 ics firmware for your country/region[ in my case it was i9100xwlp7_tml_blabla] get it using check fus downloader.
*cwm.zip [attached]
*your kernel of choice that supports both sammy and aosp/aokp [my preferred is siyah 3.3.2 if you need cwm manager ]
*cwm flashable rom/addon zip.
l
*20 minutes at max.
before you proceed here's a how-to to download stock ics firmware using check fus downloader.
launch the application.on the standard tab on the right side select android from the drop down menu.select gt-i9100 from the devices list and finally the region where you live.then on the left side click check firmware. it will take a few moment and finally a download button will appear in the bottom. press it and wait patiently as it finishes downloading.usually takes about 20-25 mins depending on your connection.
once downloading is finished or if you already have it downloaded,read on:
1. boot into download mode to flash stock firmware if you are not running official samsung ics. if you're running stock firmware then skip step 1. this also fixes the cm9 no serial number issue.
2.flash with odin the official firmware.
3.wait for the phone to boot up automatically.set up and connect the phone again to your PC.
4.after getting detected switch phone to mass storage mode.copy the attached cwm.zip to your external SD card. Also copy your desired cfw like cm9 rc1 in my case and gapps if needed.
5.now disconnect and turn your phone off.reboot into default android recovery using vol up+home+power button combo. let go off the power button once you see the Samsung gt i9100 boot logo.
6.once you successfully manage to get into android 3e recovery, select apply update from external storage and flash the cwm.zip.immidietly your phone will reboot into cwm recovery. this will give you temporary recovery access to flash your phone. if you reboot from this step you will loose your cwm and you will have to repeat the step 3-4 to get it back.
7.once into cwm,choose wipe data/factory reset.
8.then wipe cache partition.
9.go to mounts and storage and format system and data and cache. [this is necessary for a fresh cfw install, it will also ensure your cfw will function correctly.]
10.go to advanced and wipe dalvik cache,wipe battery stats to ensure your battery gauge is reading correctly and there are no previous kernel remnants.
10.then press power button to come back to main menu and select install zip from sd card.
11.choose your rom from sd card and wait till it finishes flashing.
12.reboot your phone once done.
if your rom comes with gapps then your flashing process ends here.if not or if you want flash modem or a different kernel then read on.replace gapps mentioned below with your desired package and the rest of the process are the same.
13.set up your rom.
14.press and hold the power button and select recovery from the reboot sub menu.
15.once back into cwm flash gapps/kernel/modem/add on package.
16.once finished go to advanced and select fix permissions. [necessary in case of gapps,other wise not needed]
17.reboot and you're done
Enjoy your newly rooted and flashed phone with no binary increase ! :highfive:
just to make sure there is no binary count increase,turn off your phone.press vol down+power+menu and get into download mode.you will see it reads binary as official samsung.
Hope this guide helps.please follow the steps i mentioned. i will not be held responsible for any damage caused to your phone but i believe there won't be any as I tried and tested it myself on my i9100 after a faulty flashable zip messed my phone up.please press the like button if i could help you.
please leave a comment if you need further help. I will not be attending pms at the moment.thanks ! :angel:
disclaimer : i did not make the cwm package nor any of the packages i mentioned above.credit goes to the respective devs.thanks to chainfire,codeworkx and teamhacksung for their wonderful contribution.
zip files include work of other respective devs.please donate and give thanks to them for their work.
press thanks for this guide if this helped you

Think i have seen a post pretty much like this before but there isnt many posts about rooting and installing cwm for ics s2 other than cf root. Very handy for the newbies
Sent from my GT-I9100 using xda premium

Old News!!!
http://forum.xda-developers.com/showthread.php?t=1501719
please search before posting

tsinc said:
http://forum.xda-developers.com/showthread.php?t=1501719
please search before posting
Click to expand...
Click to collapse
my post not only guides to root,but also guide to flash rom. please read first before you post a link

it might also help you with this LINK. I dont get on very well with 4.0 but been told it works

c'mon folks please press the like button i am not asking for donation here

Do you have permission from gokhanmoral to redistribute his kernel?
Also LuffarJoh's Check Fus Downloader.

I am afraid i did not ask the devs personally but i did mention it in the disclaimer that the attached zips are not my work. I will take it down if needed and provide urls.
Sent from my GT-I9100 using xda premium

Nice...
Sent from my GT-I9100 using xda premium

i have i9100m and i9100g both have same problem wich is come after update GB to ICS
let me check this method i tried all method non oh them work for me

JB on A500/A501 [Working][New Links][No ICS Bootloader]

I had trouble finding a guide on how to get JB working on my a501 so I'm xposting this to xda. The link to the superuserfix was dead, but my install worked without it. I take no credit for this. Written by "dime" over at Tegra Owners.
I wanted to write a consolidated tutorial for people on the latest/unrooted 3.2.1 OTA and how to flash it to rooted Jelly Bean ROM. If you follow step 1, it actually installs an old version of Touch Recovery for you, so you do not need to bother with Acer Recovery Installer. All links are derived from the FAQ stickied thread.
1. First you need to obtain root. Follow this guide to install a rooted 3.2.1 image.
All data will be lost. The 10 step guide is included as a PDF in the download:
http://forum.xda-developers.com/showthread.php?t=1307539
Confirm you have the Superuser app installed once completed.
2. Download the following 4 zip archives, put them on your A500 external SD card, and do not extract them.
Touch Recovery: MOD EDIT: LINK REMOVED
Both latest JB ROM and GApps: MOD EDIT: LINK REMOVED.
Superuser Fix: http://www.mediafire.com/?xyznxalycnw9znw
3. Reboot your A500, and hold VOL- button until you boot into recovery.
VOL- is closest to the power button, what some would consider to be VOL+ on a phone.
Once in recovery, use VOL+/- to navigate the menu and power button to select.
4. Now that you are in recovery:
Go into the Wipe menu, and do a Data Wipe.
Go into the Install Zip from SD Card menu, and install/upgrade to the latest version of Touch Recovery.
Reboot the A500, and once again go into Recovery (hold VOL-).
Go into the Install Zip from SD Card menu, and install the JB ROM.
Go into the Wipe menu, and do a Data Wipe. (yes a 2nd data wipe)
Go into the Install Zip from SD Card menu, and install GApps.
Go into the Install Zip from SD Card menu, and install Superuser Fix.
(skip Superuser Fix if there comes a time when superuser is working by default)
Reboot the device (Don't hold VOL- this time).
5. You should now be in rooted JB.
Backup your apps with Titanium Backup or MyBackup Root.
Hope this helps.

Hi and thank you for this tutorial.
Can you please fix the links of the xda threads? None of them is working

behemot24 said:
Hi and thank you for this tutorial.
Can you please fix the links of the xda threads? None of them is working
Click to expand...
Click to collapse
found new link

Mizun0h said:
found new link
Click to expand...
Click to collapse
Which JB rom are you using, how is it working? Thanks.

A 501
Do it realy works an a A 501?
Anybody already tried?

thanks
thanks for the tutorial !

Mizun0h said:
found new link
Click to expand...
Click to collapse
new new links

emmerich1234 said:
Do it realy works an a A 501?
Anybody already tried?
Click to expand...
Click to collapse
worked on a501. I went from stock gb, straight to JB.

Many thanks, great post
MANY, MANY THANKS for such a great post, it really has helped me to get out of a 'sticky situation' I now have a fully functioning and latest version of JB on my PB G100 (Now Acer A500 )
You are A STAR :highfive:

Mizun0h said:
I had trouble finding a guide on how to get JB working on my a501 so I'm xposting this to xda. The link to the superuserfix was dead, but my install worked without it. I take no credit for this. Written by "dime" over at Tegra Owners.
I wanted to write a consolidated tutorial for people on the latest/unrooted 3.2.1 OTA and how to flash it to rooted Jelly Bean ROM. If you follow step 1, it actually installs an old version of Touch Recovery for you, so you do not need to bother with Acer Recovery Installer. All links are derived from the FAQ stickied thread.
1. First you need to obtain root. Follow this guide to install a rooted 3.2.1 image.
All data will be lost. The 10 step guide is included as a PDF in the download:
http://forum.xda-developers.com/showthread.php?t=1307539
Confirm you have the Superuser app installed once completed.
2. Download the following 4 zip archives, put them on your A500 external SD card, and do not extract them.
Touch Recovery: MOD EDIT LINKS REMOVED
Superuser Fix: http://www.mediafire.com/?xyznxalycnw9znw
3. Reboot your A500, and hold VOL- button until you boot into recovery.
VOL- is closest to the power button, what some would consider to be VOL+ on a phone.
Once in recovery, use VOL+/- to navigate the menu and power button to select.
4. Now that you are in recovery:
Go into the Wipe menu, and do a Data Wipe.
Go into the Install Zip from SD Card menu, and install/upgrade to the latest version of Touch Recovery.
Reboot the A500, and once again go into Recovery (hold VOL-).
Go into the Install Zip from SD Card menu, and install the JB ROM.
Go into the Wipe menu, and do a Data Wipe. (yes a 2nd data wipe)
Go into the Install Zip from SD Card menu, and install GApps.
Go into the Install Zip from SD Card menu, and install Superuser Fix.
(skip Superuser Fix if there comes a time when superuser is working by default)
Reboot the device (Don't hold VOL- this time).
5. You should now be in rooted JB.
Backup your apps with Titanium Backup or MyBackup Root.
Hope this helps.
Click to expand...
Click to collapse
Hi there....I'm just wondering how this works!!!!!
If I understand your guide correctly then,
U run timmydeans v4 rooted HC bootloader
check s/user
Flash 1.7.3 ics recovery, the ROM, gapps and s/user fix
Then enter recovery wipe/flash etc....
So, not only did u manage to flash a recovery, u r also running JB - all without the unlocked boot loader?????
I have to give this a go....if this really does work you have made my day, lol
Sent from my A500 using Tapatalk 2
EDIT: k I've just read 60 odd pages from the JB ROM thread - and answered my own question...seems this tegra-owners ROM runs with or without the patched boot loader....interesting!
EDIT: ok i tried this anyway even tho i was running the patched bootloader....may explain my issues!!
had troubles right from the get go - The tdv4 EUU wouldnt recognise my tab in apx mode, after mucking about I got the "Pass"
rebooted into cwm - nup - stock recovery??? weird....
found a boot.p file so renamed that and installed acer recover installer to flash cwm 1.7
from there flashed cwm 1.7.3 and the rest of the guide!!!!
could not install super user fix zip kept telling me there was an error and had aborted installation...s/user seems to be working ok
so after 7 hours I have thors JB with the 3,01 BL
perhaps it could be made clearer that this guide is for tabs runnin gingerbread or HC, altho it will work on the v8 BL the question would be why you would want to....however for those who havent updated its not as complicated as trying to get ones head around patched bootloaders, nvFlashing etc.
JUST A WARNING not all ICS/JB roms can be flashed like this MOST WILL REQUIRE the patched bootloader....
ALWAYS BACKUP and ALWAYS CHECK THE DEV's OP for whatever rom u intend to fllash, and if u dont understand something
please ask stating what rom/BL config you're on and what you're trying to flash to!!! Its alot easier than trying to talk/msg your way out of a brick

Mizun0h said:
worked on a501. I went from stock gb, straight to JB.
Click to expand...
Click to collapse
After the update did you have any issues with cellular data or is that still intact too?
Thanks!

lft4ded said:
After the update did you have any issues with cellular data or is that still intact too?
Thanks!
Click to expand...
Click to collapse
I dont use a sim card. but on my a501 it asked me to please insert sim during first boot and always has a signal bar in the bottom right the indicates no reception. So most likely yes. Hope that helps.

lft4ded said:
After the update did you have any issues with cellular data or is that still intact too?
Thanks!
Click to expand...
Click to collapse
For me cellular data has worked flawlessly. It has been definitely the best rom for my a501!

Thread Closed
Thread is currently closed and links removed for the following reason;
Thor202ro rom kernel violates GPL. Otherwise know as not releasing kernel source. Most people here in the forums are well aware of the fact that non-GPL compliant kernels are not allowed to have links directly posted to them. This in the XDA rules.
The reason GPL is in place, is so that things like "carrier IQ' don't happen again. This is why kernel source should be open-source. Without it, the kernel could be transmitting personal data, and nobody would know it.
Additionally, the website in question, is a revenue generating website, and thus this also violates XDA rules by having links posted to revenue generating websites (ad-fly) to download Thors software. So this is a touchy spot.
Most people know where the site is anyhow.
And no, I am not going to re-hash the history.
Any issues regarding this, then please contact XDA Senior Moderators.
MD

Download KitKat CM11 4.4.2 for Nook HD+ Here

Time to get the Nook HD+ rolling on Kitkat! XDA forum member succulent (aka Iamafanof) has given me permission to post a link to his blog with all the necessary info that you need, plus the all important links to download his CM11 4.4.2 roms.
I had previously been running his CM 10.2 builds with sgt7 and they were great. Now, been running his CM11 builds since 12/16 and they are very functional and run extremely well.
It is highly recommended that you read over his blog to get the info you need to properly flash it. It's likely that your current recovery, be it CWM or TWRP will be unable to flash 4.4. You can try and if it fails, download the zip recoveries for either CWM 6.0.4.5.x or TWRP 2.6.3.0 on succulent's website listed below. Succulent recommends CWM but I've had great success with both of them. If you have a problem flashing the recovery zip, extract the image file from the zip and flash either through ADB or the PS app flashify from within your OS. EDIT: You do need to update your recovery to one of the above-mentioned recoveries.
Note: succulent's 4.4 builds are scripted to automatically install CWM 6.0.4.5b when installing the rom. But, the catch-22 is that you need to already have CWM 6.0.4.5.x or TWRP 2.6.3.0 to install 4.4 roms. EDIT 01/14/14: Currently, succulent's builds are now scripted to automatically install TWRP 2.6.3.0 instead of CWM 6.0.4.5b.
New TWRP 2.6.3.0 and CWM 6.0.4.5.x recoveries: http://goo.im/devs/succulent/ovation/recovery If you choose CWM, 6.0.4.5b is preferred as it supports both internal and ext sdcard.
Needless to say, make a nandoid backup before proceeding and if you're not comfortable doing this...DON'T!
Link to succulent's blogsite with download links: http://iamafanof.wordpress.com/2013/12/20/cm11-0-kitkat-android-4-4-2-for-nook-hd-xx-20dec2013/
Note: There are two different builds, one for internal (eMMc) and one for sdcard, be sure to download and install the correct one. I am using the eMMc build,so I don't have any knowledge of how the sdcard build is working.
Additional link to succulent's rom builds on Goo: http://goo.im/devs/succulent/ovation/cyanogenmod/internal
On the Goo site, he also has his CM 10.2 builds that might be of interest to some of you. Note: His CM10.2 rom builds automatically install TWRP 2.6.3.0.
You must use KitKat 4.4 gapps. A gapps link is provided on succulent's blog site. Either use those gapps or the PA zero day gapps linked below. If you are going to use ART, it's recommended that you do use the PA zero day gapps for best compatibility. If you don't know what ART runtime is, google it!
All credit for the rom builds, as well as the new recovery images goes to succulent (aka Iamafanof). I am just spreading the news so we can all finally have KitKat on our devices.
EDIT: Just a reminder regarding the newer recoveries, CWM 6.0.4.5.x and TWRP 2.6.3.0, they are in flashable zip form on succulent's blogsite linked above. If you run into a problem flashing the zip, one of the simplest ways to get the job done is with Flashify. Just unzip the recovery zip to get the image file. Put the image file on your device and flash it with Flashify. Play Store link: https://play.google.com/store/apps/details?id=com.cgollner.flashify
Regarding ART runtime: Since it's still "experimental", YMMV with the results you get. Google may decide ART isn't feasible and dump it going forward.
Note: Not all gapps packages are ART compatible, at this time it is probably best to use the Paranoid Android zero day gapps. Link for PA gapps: http://forum.xda-developers.com/showthread.php?t=2397942 Be sure to choose the current 4.4 gapps.
With ART runtime, it is generally better to initiate it on a fresh rom install and before you install all of your user apps. Btw, it's normal for it to take a long time to initialize on the first reboot. , I found that it generally takes a while to "settle in" and should become more fluid/speedier over time.
Always be sure to have a nandroid backup so you can easily go back to dalvik if ART isn't your thing.
One last thing about ART, Xposed Framework does not yet support it. It will appear to work but it does not. Matter of fact, with Xposed installed on your device, it will revert ART runtime back to Dalvik. Since I love using Xposed, this has kept me from using ART except to test it.
EDIT: Hey guys, just posting as new stuff comes up. Here's another possible alternative for those that may have a problem with either of the internal recoveries. XDA member sandsofmyst has put together a bootable TWRP 2.6.3.0 sdcard installer. If you use it, please post your results here and don't forget to give sandsofmyst a thanks click.
http://forum.xda-developers.com/showthread.php?p=48549135#post48549135
Enjoy!
Mike T

I'm in my kitkat glory right now. happy, happy, joy, joy.
Makes sure to update CWM BEFORE flashing CM11. Trust me, I lost 30 minutes trying to ungoober my Nook HD+.

supergroverthm said:
I'm in my kitkat glory right now. happy, happy, joy, joy.
Makes sure to update CWM BEFORE flashing CM11. Trust me, I lost 30 minutes trying to ungoober my Nook HD+.
Click to expand...
Click to collapse
Good tip and we always learn by trying. :laugh: I already had TWRP 2.6.3.0 from a previous rom, so my install of 4.4 was quick and painless. LOL
If you haven't already, hook this baby up with Xposed module by rovo89. Some really cool extra features without bogging things down with stuff you don't want or need.
Mike T

Oohh, I'm very very interested in this. Kept saying about memory optimizations for lower end device, have you noticed much performance differences? Pretty stable? Bluetooth, hdmi and everything work?
Sent from my HTC One using Tapatalk

Wow. Just wow
So now that you built it, can we expect it to become an official release soonish?
Thanks a lot for your work!

Hi, I just bought two nook hd+ one for me and one for my parents as a christmas present.
Beautiful devices, the only problem is that it does not provide italian as interface language,also all the appdownloaded from the play store are in english and I can't find a way to change that. My parents reallyneed the italian language sadly they don'tspeak a word of english....
So now I'm here wondering if this cyanogenmods have the italian language.
Saluti
Luca

superanima said:
Hi, I just bought two nook hd+ one for me and one for my parents as a christmas present.
Beautiful devices, the only problem is that it does not provide italian as interface language,also all the appdownloaded from the play store are in english and I can't find a way to change that. My parents reallyneed the italian language sadly they don'tspeak a word of english....
So now I'm here wondering if this cyanogenmods have the italian language.
Saluti
Luca
Click to expand...
Click to collapse
Well, I looked in the Language+input section under settings and Italiano (Italia) and Italiano (Svizzera) are in there. I was able to switch to them and then...not be able to read anything so I'm assuming it's right. haha. Going into the Play Store all of the app names are still english but their descriptions changed so, it seems like it mostly works. I believe language support is an app-to-app basis though, so if the app developer didn't include Italian tranlations then it's going to be in English or whatever native language the App is in. I'm not totally sure how the language support works. Maybe someone else with more info can fill in my blanks.
On to this ROM as a whole, I've been playing with it, coming from CarbonRom 10.2 and haven't noticed much difference but I dig it none-the-less. I've tested Bluetooth headphones and my HDMI adapter and both work just fine. If anyone is wanting me to test anything let me know.

Have you enabled ART?
Sent from my GT-N7105 using XDA Premium 4 mobile app

aedgington said:
Have you enabled ART?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Going into Settings>Dev Options and changing the runtime to ART and then rebooting...it doesn't get stuck in a bootloop, but going back into the Dev options shows that the Runtime option is still Dalvik and not ART so... I don't think that is there yet.

Wow, I have 342mb RAM Aavailable with GAPPS installed according to cool tool!
I've enabled ART and its showing on dev options. What's the deal with this new method? Is it better, faster, etc?

felacio said:
Going into Settings>Dev Options and changing the runtime to ART and then rebooting...it doesn't get stuck in a bootloop, but going back into the Dev options shows that the Runtime option is still Dalvik and not ART so... I don't think that is there yet.
Click to expand...
Click to collapse
Awesome, thanks for checking. I think that may be where we'll see some performance increase, but if it's not implemented yet, there's no rush for me to install

aedgington said:
Awesome, thanks for checking. I think that may be where we'll see some performance increase, but if it's not implemented yet, there's no rush for me to install
Click to expand...
Click to collapse
Mine is showing ART in dev option after reboot...

supergroverthm said:
Mine is showing ART in dev option after reboot...
Click to expand...
Click to collapse
Have you noticed any difference between ART and Dalvik?

aedgington;4872557[LEFT said:
[/LEFT]0]Have you noticed any difference between ART and Dalvik?
Click to expand...
Click to collapse
Only that more RAM is available. Now showing 390mb RAM available.

Flashing CWM
Sorry for the bit of a newb question, but how are you getting the CWM update in there? My prior ROM flashing, I had just used the bootable SD card image that verygreen had setup. I don't know how to update the version of CWM on that image currently.
When I put CWM on my phone, I had used fastboot to install it, but I can't get fastboot to recognize my nook for some reason (adb works fine). Did you use this method (from cwm site)?:
EDIT: This doesn't work... flash_image seems to be scanning for some partition that's not available:
"error scanning partitions: No such file or directory"
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img

Nook HD Kitkat
chili81 said:
Sorry for the bit of a newb question, but how are you getting the CWM update in there? My prior ROM flashing, I had just used the bootable SD card image that verygreen had setup. I don't know how to update the version of CWM on that image currently.
When I put CWM on my phone, I had used fastboot to install it, but I can't get fastboot to recognize my nook for some reason (adb works fine). Did you use this method (from cwm site)?:
Code:
adb push c:\flash_image /sdcard/
adb push c:\recovery.img /sdcard/
adb shell
su
mount -o remount, rw /system
cp /sdcard/flash_image /system/bin
cd /system/bin
chmod 777 flash_image
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I placed the files on my internal SDCard/Download and TWRP could see them and I installed.
Went here to get the zip file http://www.mediafire.com/download/c32pw4qf1l9a0mu/flash_recovery_TWRP_2.6.3.0_internal.zip
After installing the new TWRP and reboot I reset the old ROM then installed the new ROM and GAPPS.
norm883

That did the trick, thanks... I was thinking the older CWM would have same problem updating to newer CWM as it would KitKat.

Flashed TWRP 2.6.3, rebooted then tried to install 4.4 and got a mount/data1 error.
I'll guess I'll try with the new CWM.
Does anyone know if the new CWM can read and restore TWRP back-ups?
EDIT: rebooted then booted back into TWRP 2.6.3.
So far so good, flashing GAPPS now.
All good.

Decided to put some extra notes here for those that only read the last page. Also put this in the OP.
Just a reminder regarding the newer recoveries, CWM 6.0.4.5 and TWRP 2.6.3.0, they are in flashable zip form on succulent's blogsite linked above. You should be reading his blog info anyway, so just scroll untill you see the links for those recoveries. If you run into a problem flashing the zip, one of the simplest ways to get the job done is with Flashify. Just unzip the recovery zip to get the image file. Put the image file on your device and flash it with Flashify right from within you current OS, ie; CM10.2 etc.
Regarding ART runtime: Since it's still "experimental", YMMV with the results you get. Also, Google may decide ART isn't feasible and dump it going forward.
A couple of things to note, not all gapps packages are ART compatible, the gapps I linked from 1209 do work, I'm not sure about the ones linked on succulent's blogsite from 1208. I believe the PA zero day gapps are also ART compatible.
With ART runtime, it is generally better to initiate it on a fresh rom install and before you install all of your user apps. Btw, it's normal for it to take a long time to initialize on the first reboot. I found that it generally takes a while to "settle in" and should become more fluid/speedier overtime.
Always be sure to have a nandroid backup so you can easily go back to dalvik if ART isn't your thing.
One last thing about ART, Xposed Framework does not yet support it. It will appear to work but it does not. Matter of fact, with Xposed installed on your device, it will revert ART runtime back to Dalvik. Since I love using Xposed, this has kept me from using ART except to test it.
Mike T

FirePsych said:
Flashed TWRP 2.6.3, rebooted then tried to install 4.4 and got a mount/data1 error.
I'll guess I'll try with the new CWM.
Does anyone know if the new CWM can read and restore TWRP back-ups?
EDIT: rebooted then booted back into TWRP 2.6.3.
So far so good, flashing GAPPS now.
All good.
Click to expand...
Click to collapse
CWM and TWRP backups are not compatible, probably never will be unless some third party dev figures something out.
Mike T

[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")

[GUIDE] [SOLVED] HOW TO FLASH CM11 ON BRAVO (Previously "Cm11 Issue, Status 0 Error")
So, I tried to flash CM11 for the MB520 Bravo, found in this post:
http://forum.xda-developers.com/showthread.php?t=2515036
So I copy the ROM .zip to the SD card in my Bravo, and I reboot into CWM Recovery version 5.0.3.9, with the name "CyanogenDefy Recovery v5.0.3.9-jordan" on the top of the screen. This version of recovery came from josuearisty's one click tool for rooting and putting a recovery on the MB520 Bravo, which can be found here:
http://forum.xda-developers.com/showthread.php?t=1559109
I factory reset/clear cache like I know I am supposed to when flashing a custom ROM, but when I select the "Install zip from sd card" option and select the CM11 MB520 Nightly to flash, it gives me this:
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-11-20140407-NIGHTLY-mb520.zip
(Status 0)
Installation aborted.
So then as I read on further in the CM11 install page, it says this: "For CM10,10.1,10.2 < 07.11.13 users: To install KitKat, need update recovery. Do not forget reboot, after install recovery. http://defy.bytekiste.de/cm11-nightl...e-recovery.zip". The thread is for the DEFY+ according to the title, but since I see there's also a Bravo download link, I assume that this means that I should install this updated recovery as well, since I am running the stock rooted 2.2.1, which is in fact "less than" 10.x or 4.x. I select the same "Install zip from sd card" option, and the same Status 0 is presented to me.
Then I go and try putting on CM10.x first, because then according to the thread's instructions I won't have to install this updated recovery if I am running that currently. I find a link for CM10.2 for the Bravo here:
http://forum.xda-developers.com/showthread.php?t=1779324
I download it, do the same install method, and I STILL GET A STATUS 0 saying it is unable to flash the zip!
Now I've done some research, and I THINK the status 0 means the zip is not compatible with my phone. I could see that with the updated-recovery.zip, but I don't see why that is showing up for the ROM's themselves because they are in fact made for the mb520.
Can someone please tell me what I am doing wrong, and if possible post a set of step-by-step instructions as to how I can go installing CM11 on my MB520 Bravo? Thanks.

*BUMP*
UPDATE: I seemed to get around the Status 0 issue in CM10.2 so far. First, I went from 2.2.1 to CM9 4.0.4. Then, I went from CM9 to CM10.1 in quarx2k's "archive" folder on his website. This updated my recovery to TWRP 2.6.0.0. From this new TWRP, I was able to flash the latest 10.2 nightly CM rom. I will keep this posted on how things go, in case anyone out there is actually following this

*BUMP AGAIN, PROBLEM SOLVED*
I got CM11 finally running on the Bravo. Here's the steps I took to get it on there. Some of these steps may be unnecessary, but I'm just going to list EXACTLY what I did in case all of these steps really are necessary:
1) I started out with stock 2.2.1. I rooted it, and used josuearisty's tool for one click root and recovery just to put recovery on it.
2) I flashed a build of CM9 from quarx2k's website. Here is a direct link to download it. Flashing this ROM also updated my cwm recovery. HOWEVER, this new version of recovery had scrolling issues with the volume rocker, so I just rebooted and pressed the vol. down button at the blue flashing LED light to boot into the boot menu. From there, I select to go to recovery, but instead of selecting "Custom Recovery" I select "Stable Recovery". This takes me back to the older recovery I got with the one click tool.
3) I flashed one of quarx2k's builds of CM10.1, which you can get for yourself here. Doing this updated my recovery again. It went from CWM 5 to TWRP 2 (I believe it was 2.6.0.0).
4) I flashed a CM10.2 build for the bravo from quarx2k, which I got from here. This updated my recovery YET AGAIN, to TWRP 2.6.3.0.
5) From here, I was able to flash the update-recvery.zip that is mentioned in the CM11 topic. I don't think this was necessary, because when I then booted into recovery again after flashing the update-recovery.zip, the version number for TWRP still read 2.6.3.0, the exact same as last time. But I just did it anyway to be safe. Here is a direct download link to the update-recovery ZIP mentioned on quarx's CM11 thread.
6) FINALLY, I flash the CM11 nightly zip from quarx2k's website. I get an error, but this time it's not a status 0 error, this tells me that the ZIP is not compatible with my device.
7) I give myself a facepalm, and take 3 deep breaths. "All hope is lost..." I think to myself.
7.5) A GOOGLE SEARCH TELLS ME THAT ALL HOPE IS NOT LOST!!! (that's supposed to signal you to keep reading)
8) Turns out, there is a way to disable the device compatibility check. So what I did was copy the CM11 zip to my pc, and unzip all of its contents. I go to META-INF\com\google\android\, and add a .txt ending to the "updater-script" file, which allows me to open it with Notepad++. It is possible to edit this with plain old Notepad in Windows, but it doesn't format the code very neatly like Notepad++ does. If you open the file in Notepad and Notepad++ and compare them you will see what I mean. Anyway, the line of code that reads...
assert(getprop("ro.product.device") == "mb520" || getprop("ro.build.product") == "mb520" || abort("This package is for \"mb520\" devices; this is a \"" + getprop("ro.product.device") + "\"."); (ignore that winking face in the line of code, that is supposed to be a "; )" but without the space between them.)
... was the one I deleted from the updater-script file. This should be the first line of code. I save, exit Notepad++, and remove the .txt ending from the updater-script so that it returns to an unknown filetype. Now, I take the META-INF, system, and file_contexts files that came from the original CM11 ROM zip and I create a NEW ZIP with all of the NEW files and folders.
9) I reboot to TWRP with the ROM zip copied to my phone's SD card, and I flash the new, fixed ROM zip. "Installation completed."
10) My Bravo is rebooted, it boots up, and i get a "Welcome!" bubble in my brand-new homescreen in KitKat
11) I nearly cried. Seriously.
So looking back I think it was really the recovery that was the issue for the Status 0 problem, and the only real way to update the recovery and solve the Status 0 problem is by flashing all these ROMs in the order I mentioned, but that's as far as I know, there may be a better and quicker way to do this that I just don't know about.
So basically this thread turned into a how-to. I wanted to post the instructions here because on the CM11-for-the-Defy-and-Bravo topic did NOT have any instructions whatsoever for flashing the Bravo CM11 build on the Bravo. If anyone has questions about what I wrote, then you can certainly post them below and I'll respond to them as soon as I can, and I'll answer them to the best of my abilities.

Thanks for the Guide
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?

Gastnow said:
I just wanted to thank you for this well-written, step-by-step guide. I haven't tried it since I'm a beginner and need some more reading to do. I'm glad you overcame those issues, though.
Anyway, I wanted to ask you how smooth it ran and if it was worth it. Also I'm starting with Android 2.1, would that make a difference?
Click to expand...
Click to collapse
I think you should upgrade to 2.2.1 to make sure the one-click tool works with it because I do not know if the one click root and recovery works with 2.1. Upgrade to 2.2.1 just to be safe.
Sent from my SAMSUNG-SGH-I847

Thanks for the guide
Appreciate the work. What gapps are you using.

Doesn't have much support
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.

ilikepcs said:
Appreciate the work. What gapps are you using.
Click to expand...
Click to collapse
ilikepcs said:
I tried it. A lot slower then CM7.2 and very difficult to get my most important apps working (and I don't use many).
I would not recommend it for a daily (as mentioned on the Defy link). But, has potential if a developer takes up the task.
Click to expand...
Click to collapse
The gapps for this KitKat ROM can be found here. This came from the 4.4 thread:
QUARX2K'S KITKAT GAPPS
I used this as a daily driver for a little bit, until an update (I believe was from April 10th) with the Android 3.0 kernel broke the Camera. Whenever you would try to open the camera it would say "Can't connect to Camera". I'm not sure if this issue was fixed since then, and I know the versions before this had the 2.x kernel which was fine with the camera. I lent my Bravo to a family member because their phone broke, so I can't really do anything with the phone because it is not in my possession.
Anyway, check back at this thread and the link that it gives to the Bravo version of 4.4 to keep up with the latest version. This thread does not give a change log for the BRAVO version, but I assume that it's basically the same as the main version that the majority of the thread is talking about:
ANDROID KITKAT FOR DEFY AND DEFY PLUS (ALSO FOR THE MOTOROLA BRAVO)

Help please
The procedure to install cm11 after October 1 is the same? Or did it change? @jasonmerc
Quarx on their website does not mention cm10 and cm10.1
Sent from my mb520 using XDA Free mobile app

@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus

oldschool63 said:
@jasonmerc
You are not using CM11 anymore? Do you know if the camera problem has been solved (I assume that with the 2.6.x kernel the original motorola camera drivers were used which most likely do not work with a 3.x kernel)? What was your general experience (especially regarding performance) with CM11 on the Bravo?
Thanks,
Markus
Click to expand...
Click to collapse
Its been forever since I've used my Bravo let alone CM11. From what I can remember the new CM11 was EXTREMELY FAST compared to other ROMs. The only issue was the camera.
Sent from my LG-D415 using XDA Free mobile app

can you create a backup of it because some of the downloads don't work i got cm 9 4.0.4 im 12 and i ran into
a problem on cm 10.1 i cannot download it or flash it thx