[ALL][CWM][APK]Hard-Keys editor app! (Volume keys to whatever you want!) - Nook Color Android Development

Hey everybody!
***New APK editor added! Set the keys to whatever you want, see below!***
****I will not be held responsible if your Nook Color starts eating babies!!****
****Or if it breaks either!!****
****Added a revert, for those who may have issues returning the keylayout to stock (like 1.1 users who can't run the keylayout app)****
****As an added request, if anyone knows how to reload the keylayouts sans reboot, please let me know, as that is really the only thing missing from this little thing. I would love to be able to quickly reload these as needed.****
So after creating the flashable zip file for the keylayouts, and receiving some feedback that implied it would be nice to have more options, I decided to brush up on the coding skills and write a nice little app that can re-write the keylayout files without having to flash anything. This is actually my first android app, so please provide me with any feedback you may have, the more the better. The way I see it, the more I know, the better things I can make.
The keylayout app currently supports mapping the volume keys to these items:
Volume Up
Volume Down
Menu
Back
Search
D-pad Center
and can additionally support wake on press, if desired. Once written, you will need to reboot your device for the keylayout to be effective, but it's still easier than manual edits or multiple flashes.
***Note that using the app requires su access, and also at this point requires that you first flash one of my v5 keylayout zip files***
***I have received notice that the application does not run on stock rooted 1.1.0 I will be looking into this and posting an update, and most likely a revert to stock zip in case anyone needs it.***
Thanks go to whoever first suggested this, I'll be damned if I can't remember who I got this from, but thank you, whoever you are, I'll be sure to give you props when I figure out who you are.
History over, now for the details:
To install: Simply flash either zip file in CWM after flashing your CM7 or Honeycomb build to your eMMC. Once you do this, you can install and use the apk file to make changes to the keylayouts to your heart's content.
The CWM zips have been confirmed to work on most all versions of android for the nook, and in theory, the APK should work as well, however YMMV. If it works, or if it doesn't, please please post your version or build info, and let us all know what works and what doesn't.
Feedback and/or critiques accepted, may be subject to rebuttal. Hope this helps someone else, and thanks to everyone on this forum for all the hard work you do!
FYI: For those who still want an easy way to change the volume when these keys are no longer volume keys, try replacing the longpress home app with Recent Plus, by local forum contributor timoskrempel, which I first found HERE and works very well as a replacement.
Version History
-----------------------
apkv0.1b - Initial version of the keylayout app. Feedback appreciated.
v5: added files that apparently weren't as useless as I assumed. Also created inverted keys zip, use INV zip to switch the buttons.
v4: removed useless files from update zip, cause I'm being a bit too perfectionist.
V3: added files to improve compatibility (HC v4 tested, should work on Froyo, maybe stock)
V2: removed wake on press (thanks jasoraso)
V1: First Version

I definitely prefer hard keys, even with the modifications in CM7. I'll give your zip a try next time I flash a rom (I've already changed my qwerty.kl on this rom).
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...

jasoraso said:
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
Click to expand...
Click to collapse
An excellent point. Editing my zip and attaching v2. thanks to you!

success! just flashed this along with nightly#4 and it works like a charm.

I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.

digitalslacker said:
I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.

EpicFail236 said:
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
Click to expand...
Click to collapse
thanks, i'll check it out.

What would be really cool and I'm not sure it's possible and I know it's not in the scope of this thread; but a way to change functionality of the buttons per app. So for example when in Pandora (or music app of choice) buttons behave as volume buttons, but under other various apps like gallery it could be home+back button set.
Seems like you'd have to have an app running as a service and monitor the currently running focused app (not in sleep mode) and depending on what has focus do a live update to the qwerty.kl file to change buttons to expected functionality, not sure if a reboot is required after an update to the kl file though?

How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..

spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..
Click to expand...
Click to collapse
change mapping in step 4 from here:
http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
adb pull /system/usr/keylayout/TWL4030_Keypad.kl
adb pull /system/usr/keylayout/omap_twl4030keypad.kl
edit 'TWL4030_Keypad.kl' and 'omap_twl4030keypad.kl' with a unix line ending aware text editor (Notepad++, gedit, vi)
replace 'VOLUME_DOWN' with 'BACK' and replace 'VOLUME_UP' with 'MENU' in each (or vice-versa)
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
exit
adb push TWL4030_Keypad.kl /system/usr/keylayout/TWL4030_Keypad.kl
adb push omap_twl4030keypad.kl /system/usr/keylayout/omap_twl4030keypad.kl
adb shell
cd /system/usr/keylayout
chmod 644 omap_twl4030keypad.kl
chmod 644 TWL4030_Keypad.kl
exit
adb reboot
Click to expand...
Click to collapse

not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...

fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Thanks for the heads up, will review and post v5 sometime today.

my status bar always shows with HoneyComb, so I always have the back menu buttons. are there apps where this is not the case?

Anyone try this on froyo yet?

fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Yeah, I totally deleted an extra file, added to v5 and it should now work with this eMMC build. oops.
spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Click to expand...
Click to collapse
I will have to put together a stock zip and put it up sometime in the near future. Your swap keys is not easily done directly, but I have posted a new flashable zip that will swap the keys, flash INV-v5 to have the volup function as back and voldown to work as menu. This one I haven't tested, as I don't actually have my nook with me here now, but in theory it should be OK, as all I did was swap the mappings in the kl files.

After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.

rickpref said:
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
Click to expand...
Click to collapse
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.

EpicFail236 said:
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
Click to expand...
Click to collapse
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?

rickpref said:
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
Click to expand...
Click to collapse
My ADB machine was down and out at the time, so I had to do it via ES file manager and the terminal on the nook itself, but yeah, manual replacement was the way to go. sometimes a bit of command-fu is just easier than the alternative.

digitalslacker said:
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
I use Volume Widget by Futon Redemption. It gives you two little onscreen +/- buttons to adjust the volume.

Related

[ZIP][DEV][ROM] Nookie Froyo 0.6.8 (02/15) CWM flashable!

Nookie Froyo 0.6.8
is a development build of Froyo 2.2.1 for the Nook Color.
ClockworkMod flashable! - info below, please *read carefully* before flashing!
This build is near-AOSP and contains almost no extra software not deemed required for the device to function normally.
It is pre-rooted with SuperUser, busybox, SoftKeys v3.07, and ROM Manager 3.0.0.5 however.
The eventual intention will be a build that other devs and users can easily fork and create their own custom builds, themes, roms, etc.
** THIS IS A DEVELOPMENT BUILD **
Use this at your own risk! Myself, XDA, and NookDevs are *NOT RESPONSIBLE* for anything that happens directly or indirectly related to this software!
We're approaching a daily driver! Most things work now, including mp3 and video playback. Post any bugs you find here!
I'd like to thank all the nook color devs involved in getting to this state, testing, documenting, etc. We've got an amazing group of minds behind this device!
INFO
The microSD card image contains 4 partitions:
/dev/block/mmcblk1p1 : boot (fat32)
/dev/block/mmcblk1p2 : system (ext2)
/dev/block/mmcblk1p3 : data (ext3)
/dev/block/mmcblk1p4 : sdcard (fat32)
Use these partition IDs when following guides that require mounting/remounting filesystems.
What's Working:
MP3 playback
Video playback
Youtube, Pandora and other mp4 streaming apps (apps not included)
Accelerometer!
Wifi (adhoc + infrastructure!)
Graphics acceleration (LWP!)
Sound
Browser
Mostly working
Lockscreen is wrong size - REBOOT to fix
Not included / Not working
gapps ( gmail, youtube, maps, etc ) - can be installed, youtube fixed!
Bluetooth
FM radio
This build was created using the B&N kernel sources for 1.0.0, Omappedia's Froyo source ( currently RLS27.9.0.RC0 ), and binary drivers from TI for wireless, SGX530 acceleration, and DSP codecs.
Download:
This SD image requires a 2GB microSD card! Bigger is OK, smaller is not ok!
Note: if you wish to use a larger microSD card, you can use a partition editor to increase the size of the /sdcard partition (partition 4, fat32) *after* writing the image to your card.
Simply unzip this image and dd the file to your (empty) SD card, just like nooter.
nookie-froyo-SDIMAGE_2GB-0.5.1.gz 76459ec18fd32885257a3c8b7dbb2b76
nookie-froyo-SDIMAGE_2GB-0.5.6.img.gz 74e5310bcc21edf326bdc73a5652c124
nookie-froyo-SDIMAGE_2GB-0.5.8.img.gz 15158e735517c209a8f2ed14683a589c
nookie-froyo-SDIMAGE_2GB-0.5.9.img.gz 7d30f56eeede98ee1e99a0766f69dea3
nookie-froyo-SDIMAGE_2GB-0.6.6.img.gz fc58aa06fcfe1f46939ab72e38292abe
nookie-froyo-SDIMAGE_2GB-0.6.7.img.gz 92ef91dbac7a7baad3999256597b7920
nookie-froyo-SDIMAGE_2GB-0.6.8.img.gz
MD5: 18e7cc8393681ec590f698b7a671e859
If you want to customize your SD card, upgrade an already burned Nookie Froyo SD, live on the edge and burn it into your eMMC, or just want to poke around, download the base filesystem:
nookie-froyo-base-0.5.1.tar.gz 3e95a33e3926bc88011e66a724dccf8f
nookie-froyo-base-0.5.6.tar.gz 4419b21dd8eb56f6a6537345aa1c8ba1
nookie-froyo-base-0.5.8.tar.gz 2c279dbdaa6aad480590d55e48abf8ca
nookie-froyo-base-0.5.9.tar.gz 093a964685f0cbea2ef1aa8f6f0d7581
nookie-froyo-base-0.6.6.tar.gz 2304e337c351c667f27eb9aa4c3791b8
nookie-froyo-base-0.6.7.tar.gz 99b6a9d991951c368cf1f6b3429be958
nookie-froyo-base-0.6.8.tar.gz
MD5 c3c7aea7cdf8a3dde32acc1694f633aa
This archive also contains an uncompressed ramdisk image which you can easily edit, package, and copy to your boot partition.
ClockworkMod Flashable ZIP!
*IMPORTANT*
- please wipe data/factory reset if you're coming from B&N stock firmware or another rom!!
- please see other threads about installing and using CWM recovery - keep this thread to NF issues please
- this has been tested only using CWM 3.0.0.5 downloaded from market, be warned it may not work with IOMonster's kit or other versions. Let us know if you try and it does!
- replaces kernel and ramdisk - if you were using an alternate kernel you'll need to reflash it.
- This will irrevocably erase and replace the software on your eMMC! MAKE BACKUPS BEFORE FLASHING, you have been warned.
If you're upgrading from an older version of Nookie Froyo, you should not have to wipe - however if you do have problems *wipe data* and try again.
*IMPORTANT* - this zip does not require any extra steps such as formatting /boot, changing system permissions, and does not replace or remove CWM. If you are coming from a ROM that required these extra steps and are having issues, *please post your questions there* so the dev can be prompted to correct those issues properly.
If you're coming from a rom that doesn't support CWM properly see the following thread:
http://forum.xda-developers.com/showthread.php?p=11437545
Installing /system will take some time, and the progress bar doesn't update in realtime; you haven't 'locked up', just be patient as it may take a few minutes.
nookie-froyo-flashable-0.6.6.zip 6f61a464483ecf45d6e6e2d199b44d6c
nookie-froyo-flashable-0.6.7.zip 9bd13877addbad725a5bfe1eb13412df
nookie-froyo-flashable-0.6.8.zip
MD5: 03544d6a5a52eebdb468c89a5a2581e9
Please do not PM me for help, that's what this forum and the IRC rooms are for - I simply do not have the time to answer all of your questions, and asking them in a public forum will allow others with the same issue to help or learn from your experience!
CHANGELOG
v 0.5.6
permissions corrected on /system/bin/input for SoftKeys
corrected default cpu governor to conservative
added SuperUser
added busybox 1.17.2
added SoftKeys 3.00 ( thanks bpk! )
AdHoc WIFI support enabled
crypto/cryptofs added in kernel for ASEC support (required for installing some apks such as Angry Birds)
v 0.5.8
uses the /cache partition on eMMC instead of combining with data
replaces u-boot.bin to remove the 'touch the future..' splash (trademark)
increased refresh rate to improve responsiveness and reduce flicker (see tips in the next post)
added sensors lib - accelerometer works!
v 0.5.9
default web browser FC fix - no longer dies on location requests!
v 0.6.6
Youtube, Pandora, and other streaming media should now work.
added codecs for more media formats - including hw accelerated mp3 and video
vold reverted - no more broken SD card message
flashable zip!
updated SoftKeys to 3.07
fixed a /cache issue which sometimes prevented market downloads
v 0.6.7
SD card mount fixed - please post if you continue to have issues
Added back Mms, Phone, Camera, Telephony apks to resolve missing apps in Market - more apps should be available
Modified CWM zip reliability
v 0.6.8
Corrected improper handling of Format SD Card option - no longer formats /boot!
Touchscreen enhancements - no need to toggle screen on boot and better responsiveness around the edges - thanks deeper-blue!
Please see the updated issues/workarounds list in the following post
For more information, sources, and install instructions, please see:
http://nookdevs.com/NookColor:_Nookie_Froyo
Need help? Want to contribute? Join us in IRC! irc.freenode.net
#nookcolor - general chat, questions, ask for help here
#nookie - development
Do not try to Format SD card from Settings -> SD & Phone storage!
- there is currently a bug that causes the system to format the /boot partition instead of /sdcard when this option is used, leaving your NC unbootable. Format your SD card in your PC or another device if you need to! - fixed in 0.6.8!
FIRST BOOT TIPS -
On first boot, Launcher and SoftKeys will fight for control of the home intent - that is, when you boot the first time, your NC will ask you to pick your home activity.
*CHOOSE LAUNCHER* at first (DO NOT select 'always use this action'), and let the system boot and stabilize (3-4 minutes).
Hit Home (the N button). You'll be asked to choose your activity again, this time choose SoftKeys.
Try using one of the SU-required buttons (back or menu), and after a few moments SuperUser will prompt you to accept the action.
SoftKeys 3.06+ now prompt for SU permission at startup, just accept the superuser prompt when it pops, you'll still want to let the system stabilize for a minute or two.
If SoftKeys fails to ask for SU permissions, "Unable to execute as root":
Go to Settings -> Applications -> Manage Applications -> 'All'
Select SoftKeys from the list
'Force close' Softkeys if it's running, then 'Clear defaults'
Hit the N button, choose SoftKeys when prompted to choose your home action, accept the SU prompt when it pops.
Workarounds for some known bugs/issues:
(default in 0.5.8+) Improved Refresh-rate (no flicker! thanks [mbm]!): this should set the refresh rate to 68hz, the supposed default for the Nook Color's LCD panel -
Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
Browser: force closes when opening a website that tries to use location services, due to the missing GPS. Try browsing to a url by typing in the google search box, and if you can get into the browser menu changing your homepage away from google will stop it from FC'ing on open.
Lockscreen wrong size: Simply reboot to correct this.
Touchscreen is slow/unresponsive:
Turn your screen off and then back on.
Disable Haptic Feedback in Settings -> Sounds.
Also, see this page for a possible calibration fix: http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
(fixed in 0.5.6 w/included SoftKeys 3.00) No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
(fixed in 0.5.6) SoftKeys - in 0.5.1 softkeys' buttons do not work due to a permissions issue. To fix, do:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb shell chmod 0755 /system/bin/input
Please post issues/workarounds/bugs in this thread, I'll try to keep this list updated.
To answer from the other thread...
Timeframe-- well, this isn't me doing this. But I think the devs just want to take the edges off, so be patient... I'm just the messenger on the news that it's been done. This is other people's accomplishment.
In fact, froyo was done weeks ago, though not entirely from open-source/freely distributed components like this (as far as I know).
To answer some questions--
BT not working, FM not working, accellerometer not working. Softkeys should work... dont' see why not anyway. It's stock froyo. No gapps, no Superuser.apk, no nothing over and above AOSP. Overclocking not in but should be possible... video playback hasn't been tried (it's early still!).... battery life who knows I haven't even had a chance to let it run down... I posted because the news was "out" anyway. I also can't compare to stock because I've never run stock, believe it or not. But it's based on the same kernel 2.6.29. It boots off a SD partitioned for system, data, cache, and sdcard. Only thing (I think) it touches on the internal storage is resetting that boot counter, otherwise you'd only get 7 boots at a time. Doesn't need much space. 2GB should be enough. That's what phones have anyway. Guess it depends what you want to do with it. Performance is decent, not steller compared to my g2 at least. Will benefit from OC.
devis said:
@fattire
Questions on everyone's (well, mine at least) mind... please answer as much as you can, and a big big thank you!!!
1. Is BT working?
2. Is FM working?
3. Can we still use SoftKeys for hardware key emulation?
4. Can we overclock the processor?
5. How's the video playback?
6. How's the battery life compared to stock?
7. Since you're booting from SD, does that mean the internal memory of the NC remains untouched, should we need to boot stock?
and
8. How does the device feel overall?
Click to expand...
Click to collapse
Nice stuff guys keep up the stellar work
Sent from my LogicPD Zoom2 using XDA App
So awesome, looking forward to the progression of this!
I got my SD to boot tonight!
It defiantly isn't for the faint of heart but it seems to work well enough as a good base to start on. Pretty snappy to boot.
I would like to emphasize that this is VERY rough around the edges and if you aren't planning on hacking with the kernel, or code, or attempting to make your own rom then this is NOT for you.
http://i.imgur.com/WRyNV.jpg
http://i.imgur.com/H4ahM.jpg
Defiantly awesome work (and pure AOSP + TI drivers) which means no propritary B&N bits
Thanks for releasing such and early build to the public. It's not often you see that.
(I won't even consider playing with this build)
As a humble Analysts I grovel at the feet of your magnificent tech prowess.
(thanks)
Does this include a working JIT or is that one of the things in progress?
That seems to be one of the more compelling things from froyo (at least for a device with more internal storage than a nexus one). I would expect (well, hope anyway) that the froyo JIT would have a noticeable impact on the speed...
Mods, can we please stickie this?
Very awesome... Will try it out later today!
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Novarider said:
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Click to expand...
Click to collapse
Read: http://nookdevs.com/NookColor:_Nookie_Froyo#After_you_have_burned_the_uSD_card
To get back to stock, just remove the uSD card and reboot.
Click to expand...
Click to collapse
It has all the info you want, and is mentioned in the first post.
cicada said:
Workarounds for some known bugs:
No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
Click to expand...
Click to collapse
You also have the option of converting the volume buttons to back/menu as well. It is documented in this thread, but the filenames have changed in this build. You will need to modify the following files..
/system/usr/keylayout/qwerty.kl
/system/usr/keylayout/twl4030-keypad.kl
I am not a developer.
I am not likely to become one at this stage of the game...
I am, however, either brave or stupid because I am downloading the image and will see if it will boot on my NC.
I do this because:
A) I want to SEE froyo running on my NC, and
2) If I have any problems, feedback might help the devs
I love seeing all the progress that has been made on these things.
Is flash supported in the browser with this initial froyo build?
jay084 said:
Is flash supported in the browser with this initial froyo build?
Click to expand...
Click to collapse
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Just rebooted back to my regular rooted NC system after pulling the sdcard and can only say-
Marvelous.
Yes, it is slow, no keyboard and all of the other things that were spoken of in the initial posts, but IT WORKS.
I don't have time to do much else with it right at the moment, but I will mess with it more later.
BertoJG said:
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Click to expand...
Click to collapse
Could you post the flash plugin you used? I would really appreciate it. Could you also comment on the quality of flash videos online. I'd like to watch espn3 on the nook...in bed...lol
OK, so I booted the rom, and followed the instructions at nookdevs...
Installing superuser.apk and pushing su seemed to work just fine!!!
Softkeys installed and got superuser permissions and works as well.
Installed astro file manager, and that works fine too...
At that point, I wanted to mount the usb storage and move over a bunch of APK files... mounted the nook and could only see the mlo, img file etc... no problem creating an apk folder and putting files in there, but then I can't see that folder when I look for it in astro....
Any info on simply copying files via USB using this build?
Also, thanks to all the devs for the awesome work... looking forward to playing around with this more!!!

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Dees_Troy said:
[RECOVERY] TeamWin Recovery Project (twrp) 2.0.0RC0 [2011-12-17]
Team Win Recovery Project 2.0, or twrp2 for short, is a custom recovery built with ease of use and customization in mind.
Special thanks to xboarder56 for helping test the port and a couple of other testers that I forget the names of at the moment.
Click to expand...
Click to collapse
NICE, thanks to the both of you! Goin' on tonight fo sho.
Very nice job guys! I just might have to update my signature now.
Is there any future in external sdcard support?
Looks good I guess I'll have to update from the old version, thanks.
Awesome work guys.... this kicks total butt!
Nice! It's come a long way since I used it on my 3D. Alot faster compressed backup, thanks
Sent from my HTC Amaze 4G using xda premium
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
milo356 said:
Has anyone had luck installing this on amaze????
Sent from my HTC Amaze 4G using xda premium
Click to expand...
Click to collapse
I have. I can do it in different ways. flash_image recovery recoveryname.img command from the phone itself if you have the flash_image binary installed or by fastboot flash recovery recoveryname.img with the phone in bootloader mode.
Not complicated at all.
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Sikety said:
Works great, so much better than using the volume up/down keys and power keys. Two weird things that I want to see if anyone else is having issues with (want to know if it is worth reporting on the github)
1. After accessing recovery I get the "Tell HTC" This phone has just recovered from a abnormal reset message. Didn't get that with clockwork, not sure if it is a bug or not.
2. Cant mount ext SD card. Saw that the EVO 3D had the same issue but they had fixed it. I assume this is a problem with the Amaze since it is the same with clockwork mod?
Click to expand...
Click to collapse
Use this one if you want to backup and restore to and from external sdcard.
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
gregma said:
pardon the question, I've looked all over TeamWin's web site... Is there a way to boot the Amaze into twerp directly?
Click to expand...
Click to collapse
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Binary100100 said:
I don't understand your question.
You want to reboot into recovery?
adb reboot recovery
or use the 22 different other ways to reboot into recovery.
Click to expand...
Click to collapse
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
gregma said:
I'm talking about rebooting into recovery when I'm not anywhere near a computer. Such as on my HD2, I would hold the power button down until in MAGLDR, then choose to boot into Recovery. Is there something similar on the Amaze?
Greg
Click to expand...
Click to collapse
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Binary100100 said:
Which rom are you using?
There are a couple of roms that have the Advanced Power Menu that has a reboot option. When selected it gives you other options such as recovery and bootloader.
There are also a few apps (do a search for Reboot Recovery) on the Market.
I have always used the option from ROM Manager.
You can also use terminal emulator and use the command "reboot recovery" and that should do it too.
You can also power off the device, hold volume down while pressing power to get to hboot mode then select recovery.
Click to expand...
Click to collapse
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
---------- Post added at 01:55 PM ---------- Previous post was at 01:22 PM ----------
gregma said:
Stock ROM right now, I'm getting things set to start flashing new ROM's. Aha! I did see the "recovery" in hboot. Now once I figure out how I lost the ability to get into hboot by holding the volume down button I'll be good to go!
Greg
Click to expand...
Click to collapse
I LOVE answering my own darned post.... Didn't realize you had to battery power cycle the device to get it back into hboot. I'm good to go now!
Greg
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
2sh0rt said:
ok i got it loaded up fine on my phone but i cannot figure out how to flash. i click the install button and it takes me to my directories but i dont see any files in the directories... there is no files listed in the root of either sd card as well. what am i doing wrong?
Click to expand...
Click to collapse
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Binary100100 said:
Move the zip file to the other sdcard. Remember that you have two.
Here's a free tip!
Make two empty zip files.
Name one internal.zip
Name the other external.zip
Place the internal.zip in the internal sdcard and the external.zip in the external sdcard.
Reboot into recovery and if you see internal.zip file. Guess what sdcard you're looking at? Same goes for external.
Click to expand...
Click to collapse
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
2sh0rt said:
Dude, i know this... i came from the vibrant. Im saying that NEITHER card shows ANY files... only directories... no zips on the root of /sdcard or /sdcard/ext-sd... nada, zip, zilch
Click to expand...
Click to collapse
I came from the vibrant as well however I wasn't so active there.
I don't understand why you don't see any zip files then. Strange.
Me either... think i'll just try and reload it and see what happens. Thought maybe i was clicking the wrong thing or not clicking something.
---------- Post added at 07:47 PM ---------- Previous post was at 07:43 PM ----------
and its not just that i dont see any zip files. i dont see ANY files at all! every directory i click is empty! even on the system partition! not a single file shows up. only directories and when i click them there is nothing except /.. and /.

CyanoBoot-- encore gets some love too! (u-boot WIP) alpha

Hey guys.
So in the last couple months I ported the encore u-boot menu/console/configuration stuff over to acclaim (Nook Tablet). The acclaim really needed the menu plus had a ton of "2nd bootloader" issues that needed to be addressed to fix the locked bootloader bug. On nemith's suggestion, the u-boot really isn't just for cm7/9 (it can be used with any OS), so I called the newer bootloader, "CyanoBoot". Kind of a working title until I think of something better.
In the process of the acclaim port, the UI menuing interface was rewritten and some small features were added.
Anyhoo... Last night on a whim I decided to port the improvements back to encore's u-boot. So there's a version now for encore as well so that NC can enjoy the UI benefits.
It's similar to the acclaim version, minus fastboot (which we don't need, since encore doesn't use dedicated boot and recovery partitions) and minus a 'clear bootcount' setting since, well, development is up to speed w/NC that such a feature seems not necessary.
That said, here's the new stuff:
new exciting splash
Indicator in top left. "E" means u-boot is loading from emmc. "S" means it's loading from Sdcard.
Additionally you can now see the system's "boot count" - the number after the indicator described above. If this count goes up, your boot count is not being cleared as it should be.
Instruction to "hold down "n" for menu"
boot menu is way easier to use, clearer, and uncluttered.
all the old stuff is there (Nook Color Tweaks' boot settings), combo keys, etc.
If you feel bold and are willing to risk everything, give it a try and let me know if you run into issues. Think of this as an alpha. If people like it, I'll push it to the repo as the default.
To install: It's just "u-boot.bin", and it goes in the first partition of your SD or EMMC. Make sure you have a good backup in case things screw up.
NOTICE: CYANOBOOT (WORKING TITLE) IS HIGHLY EXPERIMENTAL AND IS NOT INTENDED TO BE USED BY NON-DEVELOPERS AND/OR THOSE UNWILLING TO ACCEPT FULL RESPONSIBILITY FOR ANY UNTOWARD CONSEQUENCES OF USING (OR ATTEMPTING TO USE) THE SOFTWARE. ALL SUCH ACTIVITY MUST OCCUR *ENTIRELY AT YOUR OWN RISK* AND YOU ACCEPT ALL CONSEQUENCES FOR DOING SO. THE USE OR ATTEMPTED USE MAY HAVE UNINTENDED RESULTS, INCLUDING BUT NOT LIMITED TO LOSS OF DATA, DAMAGE TO HARDWARE, AND/OR EXPLOSIVE DIARRHEA. CYANOBOOT IS NOT ENDORSED, AFFILIATED, SPONSORED, NOR ASSOCIATED WITH THE "DAS U-BOOT" PROJECT, GOOGLE, BARNES AND NOBLE LLC, TEXAS INSTRUMENTS, DENX., NOR ANY OF THEIR PARTNERS, OWNERS, EMPLOYERS, AFFILIATES, CLIENTS, SUBCONTRACTORS, OFFICERS, DIRECTORS, ADMINSTRATORS, INFORMATION PROVIDERS, ETC. EXCEPT INSOFAR AS THEY HAVE PROVIDED AND LICENSED SOURCE CODE TO BE FURTHER MODIFIED AND DISTRIBUTED. SEE THE RELEVANT GNU PUBLIC LICENSE FOR LICENSING DETAILS AND OTHER DISCLAIMERS. THIS SOFTWARE IS OBVIOUSLY INTENDED FOR USE ONLY BY THOSE WHO ARE AUTHORIZED TO DO SO.
Aside from thanks mentioned in the acclaim thread, I want to add thanks to hacdan and racks for testing for me on emmc and sd.
Seriously though, as opposed to the acclaim version that was in development for weeks, this has been tested for like an hour. On the other hand I actually have a device to try it.
Update March 28, 2012
So thanks to some hard work from tonsofquestions, we've got a new version with some very cool improvements!!!
New Stuff
* The UI now dims out any option in the menu that isn't available
* some nice code refactoring that I was too lazy to do
* the "altboot" button combo (up and down volume keys) will now choose regular boot if altboot is set as default (and vice versa)
* You can now enable a previously "hidden" menu option (plus a second configuration menu) by doing the following commands:
adb shell echo "0" > /rom/u-boot.altboot
adb shell echo "0" > /rom/u-boot.device
This unlocks a "built-in" default menu, effectively doing the same thing as the Tablet Tweaks build options, only right from u-boot itself!
Please test from various configurations (emmc/sdcard/normalboot/altboot/etc/etc)... I haven't tested this one as thoroughly.. or really thoroughly at all. And thanks to tonsofquestions for the contribution!
updates:
9/20/12: Two minor fixes...
9/19/12: Moved to a new repository at nookiedevs.
3/28/12: New features from tonsofquestions. See update notice above.
3/16/12: Clear the "Push n for menu" message on screen once boot has been determined.
cyanoboot-12-9-20.tar.gz
(source)
Another post.
Dumb question, I don't see a u-boot.bin using Root Explorer looking in root. Shouldn't there be one there that I am replacing with this new one? Or just copy it in there and reboot?
911jason said:
Dumb question, I don't see a u-boot.bin using Root Explorer looking in root. Shouldn't there be one there that I am replacing with this new one? Or just copy it in there and reboot?
Click to expand...
Click to collapse
It would go in /boot-- or partition 1. On emmc it looks like: /dev/block/mmcblk0p1 on SD it's /dev/block/mmcblk1p1.
There should indeed be one there already. Along with uImage, uRamdisk, etc...
it's not usually mounted by default. One way to access it is to use these commands from your computer:
$ adb shell mkdir /data/mnt
$ adb shell mount -t vfat /dev/block/mmcblk0p1 /data/mnt
$ adb shell cp /data/mnt/u-boot.bin /data/mnt/u-boot.bin.old
$ adb push u-boot.bin /data/mnt/
$ adb reboot
$ is the prompt, of course. Here's what they do:
1. make a "mount point" (a directory) at /data/mnt so that you can
2. mount the vfat boot partition (p1) at that mount point. Then,
3. backup your old u-boot.bin in case this one is deeply flawed
3. push your local copy of u-boot.bin (CyanoBoot) on top of the old one, and
4. reboot and hope it doesn't crash.
Good luck, and my apologies in advance if/when this screws up. Remember, you are assuming all risk here
(you can also do it by loading clockworkmod, mounting boot to /boot and then backing up and/or pushing u-boot.bin to /boot)
911jason said:
Dumb question, I don't see a u-boot.bin using Root Explorer looking in root. Shouldn't there be one there that I am replacing with this new one? Or just copy it in there and reboot?
Click to expand...
Click to collapse
its in the boot partition
Works like a charm! Very nice!
thanks fattire, this in my opinion is much nicer then the other menu we have available to us. hope to see you polish this off
ehh, the possibilities of running 4 OS's with this makes me smile
Dropped it into one of Eyeballer's nightly opengl zips (http://forum.xda-developers.com/showthread.php?t=1526115) and it works great! Thanks fattire!
Excellent work, Thanks
Been following your development on the NT even though I don't have one. I was hoping this would be ported sooner or later.
Can someone please drop this into a normal ZIP file and put it somewhere where it can be downloaded?
Thanks....
I think the whole purpose of it being compressed in the gz format is to prevent people thinking it was an installable zip file... but I could be wrong...
To use this file google search for win-gz... a simple free gzip windows utility.
If fattire gives the ok... I will upload a rar file containing the bin file.
Additionally:
@ fattire... is it ok if I include this in my file for customizing ROM's in this post instead of the cyanogen u-boot.bin?
DizzyDen said:
I think the whole purpose of it being compressed in the gz format is to prevent people thinking it was an installable zip file... but I could be wrong...
To use this file google search for win-gz... a simple free gzip windows utility.
If fattire gives the ok... I will upload a rar file containing the bin file.
Additionally:
@ fattire... is it ok if I include this in my file for customizing ROM's in this post instead of the cyanogen u-boot.bin?
Click to expand...
Click to collapse
Sure and sure. Be sure to include the GPL notice.
CyanoBoot in RAR
Thanks to fattire for all the hard work put in for our devices... and with his ok... here is the CyanoBoot in RAR format for those that have difficulties with gz files.
I will keep this updated and named to coincide with development.
DizzyDen said:
I think the whole purpose of it being compressed in the gz format is to prevent people thinking it was an installable zip file... but I could be wrong...
To use this file google search for win-gz... a simple free gzip windows utility.
If fattire gives the ok... I will upload a rar file containing the bin file.
Click to expand...
Click to collapse
Thx Dizzy....I'll find the win-gz and use that.
---------- Post added at 02:21 PM ---------- Previous post was at 02:09 PM ----------
Works great on an SD card using CM7
Thanks Fattire!
Good to go in my opinion, great work as always fattire.. my nook and tp would be collecting dust if it wasn't for your hard work
Just since we're chiming in here, yeah looks ready to me too. I've been testing several types of software this last week, some of which require flashing and rebooting for what seems to be all day. No joke, I have probably rebooted 60+ times since I downloaded this yesterday. Multiple installations, multiple configurations. No dual-emmc, but everything else has worked great.
It has been kind of bittersweet to lose the little green box though, even to such an obvious upgrade. Despite all the crap I've tried on this thing, once that logo showed up, I knew it was gonna be okay, ya know?
I have had a totally different relationship with technology since the very first time I laid eyes on it.
Good of time as any to thank the commenters on this thread in particular.
Heh. I know what you mean re that green logo (from drakknar, btw). For me it was a HUGE battle to get a multi-colored logo to appear in the first place ...This commit and this one took many, many cycles of booting and rebooting... and trying to figure out how to get the pallette to work, etc. Before it, the u-boot could only do black and white logos (does anyone remember the "Loading..." text?) and it looked pretty awful. But nemith made a good case that for the next revision, the newer u-boot might be rebranded since it's not the start up for only CM... Still, I kept the "cyano" part in the name as a tribute...
Thanks for testing, and I'm glad y'all are having success. Maybe tomorrow I'll push to the repo.
mateorod said:
It has been kind of bittersweet to lose the little green box though, even to such an obvious upgrade. Despite all the crap I've tried on this thing, once that logo showed up, I knew it was gonna be okay, ya know?
I have had a totally different relationship with technology since the very first time I laid eyes on it.
Click to expand...
Click to collapse
Just curious: Tell me about your relationship with technology and how it's changed? I feel like the NC in the last year has really helped me to learn a LOT.
OFF-TOPIC (spoiler alert).
I got a replacement nook for the one my wife got me at Christmas last October. I was absolutely flabbergasted that they has changed the storage so that it couldn't hold the books and music I had sideloaded on the original. I looked to see what I could do, and followed directions to repartition the emmc.Flashing the ROM was an afterthought.
I didn't know before finding the info that the reader had external storage. I didn't know what an sdcard was. I had to sign up for Gmail. My last computer died because of the Love Bug.
Yes.
The only reason I registered here was because I couldn't understand why every time I tried to install the Google Music Manager .exe, it wouldn't work.
Today I decompiled a services file and edited it, so I could share it with others. I spent this evening testing a package distro system. I posted in the forum and some of the words are in color!
My wife bought me an e-reader, you know? These things you've made have had a big impact and it can't only happening to me.
Thanks fattire! Have it on my SD and it works great!
I'm not sure if this is a bug or just a user common sense issue, but if you select an Alternate boot from the menu without actually having an alternate image, the Nook freezes on "Loading AltBoot from"... requiring a hard reset.
Obviously, if you don't have an Alternate boot, you wouldn't be selecting it. But I wasn't sure if there could be a potential improvement, like if Cyanoboot doesn't detect an uAltImg, it wouldn't give it as an option?

[DEV][BETA][PREVIEW] TWRP 2.2 Recovery for NT

Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
ORIGINAL POST (from May):
This is a work in progress.
TWRP (Team Win Recovery Project) 2.1 by TeamWin is an alternative recovery (instead of ClockworkMod) that is a good companion for Goo Manager. See this video for more info.
This is an experimental, mostly untested build of TWRP2 for entertainment purposes only. USE OR ATTEMPT TO USE ENTIRELY AT YOUR OWN RISK. It is intended for those who are willing to risk any and all damage, loss, and STD infection to their hardware, data, person, and associates resulting from this software. Do not attempt to use unless you understand and accept these risks.
Please note this is using the still-being-developed 3.x kernel.
I am including the raw .imgs which can be fastbooted or used on an SD (rename recovery.img.sdcard to recovery.img and put on SD in place of the existing version). Which I don't recommend doing of course, given the disclaimer above. Remember I don't have an NT so I haven't run this... ever.
Finally, this has not at all been put through any kind of paces. That's for you, assuming all the risks, to do. And report it back here for everyone's benefit.
Thanks to dees_troy, eyeballer and demetris_I & frustro for testing this. I'm busy the next few days, so I'm volunteering demetris_I, who has it running, to answer anyone's questions per his availability
twrp-2.1-nt-2012-05-17E-fullofbugs.tar.gz
History
6/12/12 - updated first post.. No binaries yet.. Can someone make one?
5/17 -
Updated 3.0 kernel to support new 512GB NTs (untested)
Updated twrp codebase to latest
Newer cm9 stuff as well
5/17B&C
Use cmdline from u-boot.bin to determine max ram size.
fix device showing up as "B" to "NookTablet"
5/17D&E
I can't remember. But it's betterer.
Has anyone successfully flashed this yet? And can anyone offer up the steps in a more-in-depth way?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Well... there's always update.zip
I haven't tried it, but I'm guessing if you've installed fastboot to your computer, this should work:
1. boot into cyanoboot and choose Fastboot from the menu.
2. On your computer, navigate to where recovery.img is and enter into the terminal
fastboot flash recovery recovery.img
Or... maybe someone could whip up a quick update-twrp2-nt-2012-5-14.zip maybe?
I guess that someone might as well be me. This is intended for use with an existing cwm recovery. This will flash to emmc...maybe.
update-twrp-2.1-nt-2012-05-14-fullofbugs-emmc.zip
MD5: 337269fa77017150325d398216a6dd3c
Thoroughly and completely untested. I really don't know if it will even install, and if it does, if it will work. See all disclaimers above, plus make up some additional ones yourself.
Edit: See below about a possible issue with possible difficulties accessing the external SD card. Internal /emmc seems to work consistently. Looking into it, but if you want to help debug this, that would be much appreciated. Just knowing what works or doesn't work and log samples (dmesg via adb) would be great.
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
It will replace cwm.
Rom doesnt matter , they reside in different partitions.
Cyanoboot is all you want if anything goes wrong or/and CWM/TWRP from sd card so you can dd the recovery.
SilentStormer said:
Will this completely replace CWM as the recovery? Or will it run alongside. Anything else I should be aware if before I try to flash (do it on a fresh rom install, will I be able to restore from a backup if something goes wrong etc etc...)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Should replace it completely. I say should because if you do this with the update.zip, you will be the first one to try it.
Oh, Mister_Argent is trying it on IRC...
The Zip seems to work! Android boots fine, and it's entirely possible to get into TWRP via Cyanoboot. This might just be me, but the terminal seems to lock up...
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
Oh hey argent, so the zip works? And is it worth my time to change from CWM to TWRP?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
So we can still flash stuff through emmc?
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Indirect gave me this command to flash recovery via terminal emulator and it worked out nicely
dd if=/recovery.img of=/dev/block/mmcblk0p3
Click to expand...
Click to collapse
where "/recovery.img" is the file path/file name of the recovery image
Recovery looks nice. I'll do some more playing with it later when I have time.
fattire said:
There may be issues with selecting the external SD card... not sure what the deal is. I believe demetris_I checked this out previously, but you can use the internal (/emmc) one though until this is worked out/confirmed one way or the other.
Note: if anyone is good at verifying/debugging, post any relavent dmesg stuff + what your theory is on the issue
Click to expand...
Click to collapse
No issues with external sd it just take some seconds to mount, is not instant but it will mount.
8gb NT. Successfully flashed internally; will test, log and provide feedback on any issues.
The zip file name is overly long and CWM doesn't like it. Renaming to something shorter solves the issue.
In my experience with other android devices, it is normally recommended you wipe 'dalvik cache' whenever changing / updating kernel. Perhaps this step will avoid some issues for people.
Edit: Flashing gapps update via Goo Manager results in failure of rom to load after Cyanoboot screen. I did not choose to wipe dalvik / cache in Goo Manager. Also unable to access Cyanoboot via N. Screen appears but does not seem to respond and automatically boots emmc (blank screen).
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
demetris_I said:
Re-download Gapps and press the buttons combo to access twrp/cwm and reflash (power+N)
What rom and what gapps you are using?
Make sure they are downloaded ok before flashing.
Click to expand...
Click to collapse
I could not access twrp as already stated, because Cyanoboot did not respond to button press. I've managed to get access to CWM via sdcard and reflashed another gapps. CM9 still will not load.
Next, I plan to wipe everything and flash CM9 anew.
Edit: Still won't boot. Looks like I have a brick to fix.
Edit2: Flashing CWM internally got everything working again. Cyanoboot would previously go automatically to loading from emmc; there was no delay / opportunity to press N to access the menu. Now the delay occurs and I have access. CM9 also loads.
Edit3: Reflashed TWRP internally again. It's not working on 8gb NT. It doesn't break Cyanoboot or prevent CM9 from loading, but any attempt to load TWRP results in a black screen.
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
demetris_I said:
How do you flash twrp?
If you flash the zip can you please try the fastboot way?
fastboot flash recovery twrp.img, thanks
Click to expand...
Click to collapse
I flashed the above emmc zip via cwm internal
I have adb working, however fastboot seems to require a separate driver to work in windows. I've searched the forum and have not found a clear answer.
I'm guessing the 3.0 kernel doesn't have support added for the 8gb nts yet. I guess maybe I could look into that...
Sent from my HTC Vision using XDA
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
SilentStormer said:
So to run this I have to be running the new 3.x kernel? Or can I just flash the zip if I'm on the 2.x Cm9
(16gb Tablet)
Sent from my Team A CM9 Alpha 0.03 Nook Tablet
Click to expand...
Click to collapse
Recovery is separate from the rom. You'll be fine. I have it running on my 16GB.

[Recovery] TWRP Official Builds

Team Win Recovery Project 2.6, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. TeamWin started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of additional features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
HTC Droid Incredible 4G LTE product page on TeamW.in
Older versions can be found here if needed.
Download
Download TWRP 2.6.3.0 Official (Change Log)
MD5: 22c58a87402b4049f8bafa1b07b1a765
Download TWRP 2.6.3.0a Unofficial
MD5: fd9f7b520bec55c980d0ea39616aa271
Includes these commits on top of 2.6.3.0: Never generate empty backup name, Remove unneeded images, check for space after = too, Improvements to Update_Log_File, Fix checking for file_contexts in updater
GooManager Installation:
Automated installation through GooManager will only work if you have the su binary (root access) on your ROM. If you have just performed unlock or S-OFF, you must use the manual installation method for the first recovery installation.
Install the GooManager application from Google Play
Open GooManager, pull up the menu, and select Install OpenRecoveryScript
Confirm the first prompt, then verify the filename in the second prompt (openrecovery-twrp-2.6.3.0-fireball.img) and confirm again
After the recovery has been installed, pull up the menu and choose Reboot Recovery
Manual Installation:
Requirements: you must have fastboot set up: Windows Guide, Mac Guide, Ubuntu Guide
1) Reboot your phone to the bootloader:
Method 1: Disable fast boot under Settings > Power > Fast boot. Shut down the phone. Hold Volume-Down and Power simultaneously until the phone vibrates. Continue holding volume down, but release the power button. When you reach the bootloader, choose the FASTBOOT menu option using the volume keys to move up/down and the power key to select.
Method 2: If you have adb installed, then with your phone fully booted up, type: adb reboot-bootloader
2) Flash the recovery image using fastboot. Open a terminal and navigate to the directory with the downloaded image. Type:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-fireball.img
When the image has finished flashing (usually less than 10 seconds), issue the command
Code:
fastboot reboot-bootloader
3) Use the volume keys to navigate to BOOTLOADER and then select it with the power key. After the phone finishes scanning for PJ____.zip images, choose RECOVERY from the menu. This will start TWRP recovery.
Themes:
TWRP supports themes! Create a folder called theme within the TWRP folder on your internal storage and copy ui.zip into it. You can either search for themes compatible with the 540x960 resolution (check out the EVO 3D forum for instance) or build your own. Known themes listed below:
Holo TWRP Theme by prairiedogn
HTC TWRP Theme by prairiedogn
Blue Dalek Theme by agentc13
Sports Recovery Themes by lnando84
Gray Theme by lnando84
Themes written for earlier versions of TWRP may not have themed elements for new features. Be sure to compare the user interface before and after applying a theme to make sure everything shows up. You can check the log for errors as well (the middle button on the bottom of the TWRP interface), it will say something like: "unable to load button image" if resources are missing.
Additional Information:
The boot image comes from RUU 2.17.605.2
This build includes HTC Dumlock in case it is needed. S-OFF users can safely ignore it. HTCDev Unlock users (who are still S-ON) can try it out if experiencing trouble writing to the /boot partition. It can be found under Advanced in the recovery.
Credits:
Dees_Troy for adding the Inc 4G to TeamWin's officially supported devices for TWRP
con247 for putting in the original effort to build TWRP on the Inc 4G
utkanos and KemoNine for building assistance
TeamWin for TWRP and their great building guide
CyanogenMod for way too many reasons
Release History:
Official 2.6 - In addition to TWRP's official changes, this version also introduces support for AOSP data encryption. Additionally, Aroma installers should not fail anymore.
Official 2.4 - Builds are now maintained by TeamWin: Change Log
Official 2.3.3.0 - Identical to Build 1.2
Build 1.2 - Mount internal and external SD to computer via USB
Beta 1.1 - HTC Dumlock included
Beta 1.0 - Initial Release
Known issues / Workarounds / To Do
The charging status LED currently does not turn on when the phone is charging. This is really a non-issue since there is a charge level and charging indicator within the recovery.
If the phone is powered off while plugged into USB, it will temporarily reboot into recovery then shut down 20-30sec later.
Source
The device tree is at github.com/cyanogenmod/android_device_htc_fireball.
great, glad to see this coming
Do you think this could get goo manager support? Thanks for all that you do.
Sent from my DROID RAZR using Tapatalk 2
Awesome! Thanks updating now
jamminjon82 said:
Do you think this could get goo manager support? Thanks for all that you do.
Click to expand...
Click to collapse
I need successful user reports for all the features. Once I get confirmation that everything works as expected, I'll submit my device tree to TWRP and ask for official builds. Goo manager support would follow from there.
I updated the build to version 1.1. For those who are S-OFF, there's no difference from 1.0. For those who are S-ON and using HTCDev Unlock (from team fireballas), there's now HTC Dumlock included. I'm still not sure if it is even needed...
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Linch89 said:
im running a backup now. i'll try wiping and restoring too
---------- Post added at 02:18 PM ---------- Previous post was at 01:37 PM ----------
Backup, wipe, and restore all work as well as backup compression and backup rename. Under wipe I didn't know about internal and android secure are those required for a full wipe?
Click to expand...
Click to collapse
Relevant posts about androidsecure:
http://forum.xda-developers.com/showthread.php?t=1934739
http://forum.xda-developers.com/showpost.php?p=27172605&postcount=218
Internal wipe clears out your internal sdcard's media partition (pictures, music)... probably don't want to do that.
Good look glad I didn't. Well as far as I can tell this is recovery is a win pun intended
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
The ability to mount the phone's sdcards on the computer while in TWRP was unknown to me. I'm working on the issue. The attached recovery is a first stab at a fix, let me know if it works (my faith is low though since the devices didn't mount in ubuntu for me).
MD5: 6fa24210afa860c38fef3f2a7d4360d1
Edit: the attached recovery did not fix the issue. I'll try to look into this sometime this week (research presentations and job interviews over the next few weeks so time is very scarce right now).
Linch89 said:
im trying to mount my phone to my computer while in recovery and its not working v2.3.3.0 idk if its my computers usb its certainly not my phones micro usb the thing is brand new
Click to expand...
Click to collapse
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Edit: Never Mind, I am running TWRP v2.2.0, this may not have any validity with the OP's version, sorry.
Edit my Edit: OK I just flashed v2.3.3.0 and same goes, I can get in through ADB and I have shell root once in shell. However, the file system looks like it should with "sdcard" and internal and "external-sd" as external. All else seems normal.
DavDoc said:
Mine isn't mounting either, internal nor external card, but I can get it to work through ADB, (work around for the time being)
Click to expand...
Click to collapse
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
DavDoc said:
Interesting side note though, (and this may be expected by some, it was new to me) while in TWRP recovery and running shell though ADB it was listing my actual external SD card as "sdcard" and actual internal SD as "internal_sdcard". I have used CWM on another device and I don't remember it changing the file structure while in recovery. Also I had shell root upon issuing the adb shell command. This is my first device using TWRP, it was just different.
Click to expand...
Click to collapse
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
It doesn't auto mount upon connecting usb, I didn't try mounting it though, through TWRP settings. From what I can tell, both versions work the same, they just have different names for the file structure, and only for the external and internal sdcards - didn't really investigate any other files.
Edit: To answer your first question, no it didn't work in either version. Don't know who's v2.2.0 it is, but it is the recovery that was added into the supercid.auto script.
mdmower said:
I worked on the sd card mounting issue last night, but still have not figured it out. I will try to get some assistance from the TWRP folks if I find time tonight. Just to make sure, the feature worked when you used TWRP 2.2 by con247?
In fact, I may be misinterpreting how the feature works. Is the computer supposed to auto-mount your SD card when plugged in via USB, or do you have to activate the feature from within TWRP somewhere?
I just tested and this is what I see:
Code:
drwxrwxrwx 11 root root 16384 Jan 1 1970 external_sd
drwxrwxrwx 11 root root 32768 Jan 1 1970 sdcard
EDIT: Both in TWRP and in 'adb shell' the locations are correct.
Click to expand...
Click to collapse
i think they mean usb mounting is gone it is suposed to be under mount option
jose51197 said:
i think they mean usb mounting is gone it is suposed to be under mount option
Click to expand...
Click to collapse
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
mdmower said:
Right, so if I just understood this a couple of days ago I could have had a fix pretty quick. I naively thought the phone was supposed to auto-mount to the computer, which would make no sense because the drives would then be inaccessible to TWRP's routines. Anyways, build 1.2 enables the feature and both internal and external SD cards can be accessed.
Click to expand...
Click to collapse
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Its back thanks I wish I can thank you twice and don't want to complain but only thing missing is the backup android.secure option under backup
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
Does your .android_secure folder actually have anything in it? Mine is empty on Viper 2.1.1. I just moved an app to SD and the folder is still empty. The reason I ask is because the and-sec folder is correctly mounted and linked to /sdcard/.android_secure when in TWRP.
I've never seen anything in android secure ever on any phone
Linch89 said:
I've never seen anything in android secure ever on any phone
Click to expand...
Click to collapse
On my OG DInc running AOSP that folder would indeed store sdcard apps... strange its different now....
I moved all apps my apps to sd card and I checked android_secure under sdcard and sdcard2 in root explorer and nothings in there. I can't delete the folder though so it must be of some importance

Categories

Resources