Android 3.0 Honeycomb Preview Image v04 - 2/7/2011

Search This thread

rdubbs007

Senior Member
Jun 24, 2010
53
15
I am having problems getting v02 going, I DLded the torrent, extracted it with WINRar, Used WINImage to burn it to the SD card, and when I insert the SD card into the nook it simply hangs in the boot screen with "ANDROID _" in the bottom lefthand corner if held in landscape mode, the _ is a blinking cursor line. It goes no further, it just sits there...
 

jtbnet

Senior Member
Oct 28, 2009
568
59
Cochituate
I keep getting the same error. Is there anyway to get SU working. It's not much fun Testing things when I can't access Root.

Bump hoping someone has built a 'working' su ? I get the same error using the latest su I use from Froyo Superuser 2.3.1 version;

root@android:/system/xbin # chmod 4755 su*
chmod 4755 su*
root@android:/system/xbin # ls -l su*
ls -l su*
-rwsr-xr-x root root 68340 2011-02-03 19:51 su
-rwsr-xr-x root root 26264 2010-08-10 06:52 su-new
-rwsr-xr-x root root 68340 2011-01-31 11:22 su-org
root@android:/system/xbin # ./su-new
./su-new
reloc_library[1315]: 2886 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
255|root@android:/system/xbin # ./su-org
./su-org
root@android:/system/xbin # exit
exit
root@android:/system/xbin #
 

dehidding

Member
Dec 29, 2010
22
6
Chicago
I am having problems getting v02 going, I DLded the torrent, extracted it with WINRar, Used WINImage to burn it to the SD card, and when I insert the SD card into the nook it simply hangs in the boot screen with "ANDROID _" in the bottom lefthand corner if held in landscape mode, the _ is a blinking cursor line. It goes no further, it just sits there...

you need a slower kernel. Read the thread on replacing the HC kernel, it's easy.

Sent from my GTablet-TnT-Lite using Tapatalk
 

straby187

Senior Member
Dec 13, 2009
55
2
What's the possibility of this on emmc to see what it really feels like on nook

Sent from my HD2 using XDA App
 

joe91584

Member
Jan 19, 2011
38
2
Delanco
deeper-blue Thanks for the nice rom.

as for the emmc I can't wait to see some one with 3.0 write up good directions on how to do this.

Without overclocking this nook I really think it's great.

Can't wait to see what the next build has for us.
 

ChrisJ951

Senior Member
Jan 25, 2011
494
307
I am having problems getting v02 going, I DLded the torrent, extracted it with WINRar, Used WINImage to burn it to the SD card, and when I insert the SD card into the nook it simply hangs in the boot screen with "ANDROID _" in the bottom lefthand corner if held in landscape mode, the _ is a blinking cursor line. It goes no further, it just sits there...

I had this problem too (despite what people tell you i don't believe its an OC issue). For me it was an issue of the SD card being partially corrupt. Re DDing (or windows equivalent of writing the image) the image fixed it for me.
 

slugbug2010

Senior Member
Oct 12, 2010
1,764
150
Austin, Tx
Just curious about a few things -

I have version 2 set up pretty well. I seem to get more FCs on this than the one day I ran v1 (no OCing, on stock kernel). I know this is an alpha so I'm ok with that. I've read a few suggestions on how to optimize what we do have. I've read that setting the auto-rotate to off that it will help with FCs but when I do that and it stays in landscape mode, the bottom 1/4 of my screen cuts off. I've read the other thread where the dev/poster has used DB's img and added market, no camera, etc and he adjusted the dpi to 150. Can we do that with this version and would that help with the landscape mode showing the whole screen? I was able to get the red square turned off in Developer Settings (shows up a lot less anyway - it's not a big deal either way)..

By using the browser and going to mobile or tablet versions of many apps (facebook, google voice, etc) I have managed to make this very user friendly and think with a little digging around I can get this thing of beauty just about right :) (plus I have the sd card with decad3nces stable rom to go to if and when I need it )

Any others suggestion about tweaking what we have now, with this version, the make the best use of the HC img that DB has developed?
 

willp2

Senior Member
Nov 8, 2004
95
4
Been working on this all day now. I've tried the various versions of the image in this thread and the other gingerbread version. I've tried different kernels and blowing away and re-flashing the SD card over and over again and always I end up back at the android with a flashing curser

Any more ideas would be appreciated

Thanks
 

jtbnet

Senior Member
Oct 28, 2009
568
59
Cochituate
Missing Superuser su from ASOP build

root@android:/system/xbin # chmod 4755 su*
chmod 4755 su*
root@android:/system/xbin # ls -l su*
ls -l su*
-rwsr-xr-x root root 68340 2011-02-03 19:51 su
-rwsr-xr-x root root 26264 2010-08-10 06:52 su-new
-rwsr-xr-x root root 68340 2011-01-31 11:22 su-org
root@android:/system/xbin # ./su-new
./su-new
reloc_library[1315]: 2886 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
255|root@android:/system/xbin # ./su-org
./su-org
root@android:/system/xbin # exit
exit
root@android:/system/xbin #


So I've found the missing unresolved _mktemp error is a known problem when not building the special extras superuser su as explained by proceedure here;

http://howto.ccroms.net/android_project/build/mod/root

Does anyone have the latest ASOP already setup and thus can perhaps quickly make the change in the link to build the static executable to solve the unresolved _mktemp error so we can root these installs and get further in testing?
 

Divine_Madcat

Retired Forum Moderator
Sep 9, 2005
2,936
2,608
USA
root@android:/system/xbin # chmod 4755 su*
chmod 4755 su*
root@android:/system/xbin # ls -l su*
ls -l su*
-rwsr-xr-x root root 68340 2011-02-03 19:51 su
-rwsr-xr-x root root 26264 2010-08-10 06:52 su-new
-rwsr-xr-x root root 68340 2011-01-31 11:22 su-org
root@android:/system/xbin # ./su-new
./su-new
reloc_library[1315]: 2886 cannot locate '_mktemp'...
CANNOT LINK EXECUTABLE
255|root@android:/system/xbin # ./su-org
./su-org
root@android:/system/xbin # exit
exit
root@android:/system/xbin #


So I've found the missing unresolved _mktemp error is a known problem when not building the special extras superuser su as explained by proceedure here;

http://howto.ccroms.net/android_project/build/mod/root

Does anyone have the latest ASOP already setup and thus can perhaps quickly make the change in the link to build the static executable to solve the unresolved _mktemp error so we can root these installs and get further in testing?

3.0 isn't even on AOSP yet...
 

NuroSlam

Senior Member
Feb 27, 2010
108
42
Hell aka Phoenix
pushed modified su to /data/local. cat to /system/xbin chmod 6755 su, now have root. DO NOT UPDATE su via SuperUser

app_45@android:/data/local $ ls
opendir failed. Permssion denied
255|app_45@android:/data/local $ su
su: access granted, courtesy of www.magicdroidapps.com
app_45@android:/data/local # ls
su
tmp
app_45@android:/data/local
 
Last edited:
  • Like
Reactions: wvcachi

rdubbs007

Senior Member
Jun 24, 2010
53
15
Been working on this all day now. I've tried the various versions of the image in this thread and the other gingerbread version. I've tried different kernels and blowing away and re-flashing the SD card over and over again and always I end up back at the android with a flashing curser

Any more ideas would be appreciated

Thanks

Same here, I wrote and rewrote and rewrote the image to the sd card so I know that it is not partially corrupt. I am using a PNY 8GB class 4 and it is being a stubborn little *****, won't get past the damned Android screen. And I ran out after work yesterday to buy the nook just for this! Blah.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 284
    First of all I have to thank the CM people, especially mbm, nemith, fattire and cvpcs for their work on gingerbread which helped me a lot in understanding where to look and what to patch.

    The whole thing is based on the honeycomb preview emulator images, some of the B&N modules+driver, pieces from the upcoming CM7 and manual patching ARM assembler in libraries, writing ugly scripts to hack around various issues, a lot of time and many brain cells.


    Use this on your own risk. I'm not responsible for any damages. This is not meant as a primetime ready rom. This is a preview after all.


    The unzipped image is around 3.5gb and fits on 4GB SD cards.

    MD5 (nookhoney04.img.zip) = 27396e63396a59a25f5d6fdbe0341276
    http://www.rbrune.de/nookhoney04.img.zip.torrent
    http://www.rbrune.de/nookhoney04.img.zip



    Changelog

    v04 - 02/07/2011
    • increased touchscreen sensitivity and made touchscreen more usable close to the borders (kernel change)
    • fixed heap size issue to get much more programs running (e.g. nook app, kindle app, etc.)


    v03 - 02/05/2011
    • fixed screen turning animations and previews in taskswitcher
    • sd card access and secure storage support
    • turned off the debug screen flashes and vibrator
    • added display timings
    • sd card image now usable on 4gb cards
    • changed to a self compiled kernel to make these things work
    • reduced compressed image size


    v02 - 02/02/2011
    • sound support
    • patched in some graphics improvements. Can play non-hd videos from m.youtube.com
    • sdcard storage


    v01 - 02/01/2011
    • initial release


    Status

    What works:
    • Graphics acceleration
    • Accelerometer
    • Wireless!
    • Touchscreen
    • Buttons
    • Sleep/Wakeup
    • Sound

    Known issues:
    • The accelerometer behaves funky. Will try to fix this.
    • The Gallery app crashes when opening an image. Not my fault, it's broken in the emulator from google too.

    Doesn't work:
    • DSP e.g. no hardware video decoding (and will possibly never work before the AOSP release)


    FAQ

    Q: Why?
    A: I thought it would be fun. It was and still is. And now developers have an actual device to test their apps on instead of relying on the slow emulator.

    Q: How?
    A: I'm planning to write a blog post. Mostly learning how Android works, debugging, patching, reusing binaries from different sources, finding easy ways to reach a goal, try and error, a lot of brain power.

    Q: During boot I get stuck at the Android screen with the blinking cursor.
    A: It seems to be a timing issue with mounting the partitions. Sometimes rebooting helps to get it booting. If not a different SD card might to the trick.

    Q: Why is there no Market app installed?
    A: There's no legal way to distribute the google apps with a ROM.

    Q: Angry Birds, Nook reader, Kindle app?
    A: Yes.

    Q: I want to port Honeycomb to device xyz... send me the instructions how to do that now!
    A: I like the 'I' in that sentence - but there are no instructions, no source, no nothing. Learn and read about Android, Android porting, making custom roms, embedded systems, ARM assembly, driver programming, programming in general, the Linux Kernel and much more - and when you're comfortable and have experience with all of that come back and do your port.

    Q: Can you port Honeycomb to device xyz?
    A: I don't have xyz. And even if device xyz would magically appear at my front door doesn't necessarily mean I'll have the time and motivation to port anything to it.

    Q: I want to use a different kernel what changes did you make in the kernel?
    A: https://github.com/rbrune/nook_kernel

    Q: Where can I donate?
    A: I don't want any money. If you want to put your money to good use donate to a humanitarian organization and/or the EFF.

    --
    Rafael Brune
    12
    A Children's Book

    So Many Zeroes!

    Blue had his V2, all shiny and GNU, and wanted to send it, but stopped to review.
    "What would this ware weigh, if zipped up today? Should it not be much larger than the SDK?"
    And yet it was bigger (nearly one-half a gigger!), but Blue still released it with vim and with vigor.
    "A drive is a drive, at any old size! But a drive is alive when its zero'ed to thrive!"
    So Blue packered his tracks with a /dev/zero-whacker. And then that blue cracker, he launched his bittracker...
    And he ripped, and he zipped (but he didn't encrypt), until it was scripted, and that's when he shipped it!
    It was plain to see-- that his brand-new V3-- was shiny and tiny and better. Whoopie!
    In fact the whole thing was down to 180. A number of megs that was far, far less weighty.
    And now when the Rommers all rom their romses, and now when the Singers all sing their songses,
    their image of Blue will be bigger and taller,
    and installers they image will be *many* megs smaller.
    9
    There are a LOT of devices in CM7's stable. In order for them to launch even an RC, each has to be working or near-working, which takes a lot of effort.

    Also, from what I understand, Gingerbread has a few critical bugs that the CM team is attempting to fix before committing to a formal release. It's a choice not to put it out now, not a lack of skill or talent.

    That's right. There could have been a release in early Jan but while the demo video would have been neato, the build itself would have been WAY too early. And then it would have been a month of "IS IT READY? IS IT READY NOW? Why isn't there sound? Where's the accelerometer? Why is the keyboard so screwy?" etc etc.

    CM has a rule not to release until it's 100% hardware compliant-- that's how CM got a reputation for being so great. That said, the nook CM team has been working with blue in the last few days, so what you're seeing in his release today has several parts from cm7 in it (as he noted in the original post). CM7 also does have sound working, ext4 support, and other hardware and build-process fixes that were impossible to migrate in blue's timeframe (or did not apply w/o the source). Those will be in cm7 (it's two bugs away from full hardware support), and when the source is released for honeycomb, I've no doubt the work will be leveraged into that quickly. Which is good because as you can see, HC and NC fit together very well.

    In other words, this has been time well spent, and you're seeing some of the fruits of that project today.
    8
    Looks like you're gonna make the front page of engadget and the other sites again ;)

    Heres a Mirror to v04:
    http://android.stolenrobot.com/NookColor/Honeycomb/nookhoney04.img.zip

    Here are some basic instructions on how to flash it:

    Windows Instructions
    Download Win32DiskImager.exe
    Download the file in the first post and extract the img from the zip
    Run Win32DiskImager and make sure you pick the drive letter corresponding to your MicroSD card
    Click the Folder icon and locate the img file you extracted earlier
    Click on Write and then wait...

    Once its done remove the SD card from your computer
    Power off your nook color and insert the MicroSD you just prepared
    Power On your Nook Color and wait for it to load

    Welcome to Honeycomb!