• Login:

Welcome to the Acer Tablet forum.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed.

+ Reply to Thread
Page 1 of 2 1 2 LastLast
Results 1 to 10 of 12
  1. #1
    Iconia Operative
    Member #
    8381
    Join Date
    Mar 2012
    Posts
    168
    Liked
    5 times

    custom rolled CWM won't boot

    I wanted to take a crack at testing a fix for USB mounting in CWM on the Acer but the recovery.img that I built wouldn't boot (stuck at acer logo). Here are details, that I did from memory. Perhaps I missing something obvious:

    Code:
    $ curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo && chmod +x ~/bin/repo
    $ mkdir ~/DROUD && cd ~/DROID
    
    $ repo init -u git://github.com/CyanogenMod/android.git -b ics
    $ repo sync
    
    $ . build/envsetup.sh
    
    # I didn't see anything picasso* ie. picasso_e so I picked:
    $ lunch full-eng
    Code:
    $ make recovery
    This takes a little bit and succeeds:
    <snip>
    Install: out/target/product/generic/system/lib/libdl.so
    Install: out/target/product/generic/system/lib/libc.so
    Notice file: bionic/libstdc++/NOTICE -- out/target/product/generic/obj/NOTICE_FILES/src//system/lib/libstdc++.so.txt
    Install: out/target/product/generic/system/lib/libstdc++.so
    Notice file: bionic/libm/NOTICE -- out/target/product/generic/obj/NOTICE_FILES/src//system/lib/libm.so.txt
    Install: out/target/product/generic/system/lib/libm.so
    Install: out/target/product/generic/system/bin/recovery
    At this point my plan is to take the new recovery and repackage it.

    Code:
    $ cd ~/work
    $ unpack-bootimg.pl cwmrecovery.img
    
    $ cp ~/DROID/out/target/product/generic/system/bin/recovery ./cwmrecovery.img-ramdisk/sbin/
    
    $ mkbootfs ./cwmrecovery.img-ramdisk | gzip > cwmrecovery.img-ramdisk.cpio.MOD.gz
    
    $ mkbootimg --kernel cwmrecovery.img-kernel.gz --ramdisk cwmrecovery.img-ramdisk.cpio.MOD.gz -o recovery.MOD.img
    
    $ adb reboot-bootloader
    
    $ fastboot flash recovery recovery.MOD.img
    So now when I try to boot recovery it hangs at logo, last line printed is Booting recovery kernel image.

  2. # ADS
    Ads


  3. #2
    Developer

    Member #
    743
    Join Date
    Jun 2011
    Posts
    48
    Liked
    3 times
    Maybe i'm missing something, but it looks like your repacking it with the same kernel that was unpacked from the one you built. Try plugging in the a zimage from hbwealch's recovery.

    Sent from my SPH-D710 using Tapatalk
    A500 running FlexReaper R10
    A200 temporary development device
    Epic 4G Touch running ICS Blend

  4. #3
    Iconia Operative
    Member #
    8381
    Join Date
    Mar 2012
    Posts
    168
    Liked
    5 times
    No I didn't build cwmrecovery.img that is your recovery image provided by Acer Recovery free edition. I unpacked that because i knew it had hbwelches kernel + CWM 5 ramdisk. All i think I have done is roll a new sbin/recovery.

  5. #4
    Developer

    Member #
    7978
    Join Date
    Feb 2012
    Location
    Topeka, Kansas, United States
    Posts
    198
    Liked
    130 times
    the init. files in the ramdisk are specific take a look at those...

  6. #5
    Iconia Operative
    Member #
    8381
    Join Date
    Mar 2012
    Posts
    168
    Liked
    5 times
    Now it could be that this approach too generic? Even though I am repacking the compiled sbin/recovery w/a good kernel and ramdisk there may be some device specific things sbin/recovery needed during compile? Any compile example I have seen for CWM people have device specific make files and in those cases cases it generates a full recovery.img.


    Quote Originally Posted by hbwelch View Post
    the init. files in the ramdisk are specific take a look at those...
    I can flash cwmrecovery.img as is and boot fine. Should I still expect that something would need to change if I simply pack in a freshly compiled sbin/recovery binary?
    Last edited by acertabuser; 04-05-2012 at 08:58 PM.

  7. #6
    Iconia Operative
    Member #
    8381
    Join Date
    Mar 2012
    Posts
    168
    Liked
    5 times
    I can't test this yet, but I'm wondering if the unpackaged kernel (produced by unpack-booimg.pl) actually needs to be gunzip'd so that it is a regular zImage before doing the repack.

  8. #7
    Developer

    Member #
    7978
    Join Date
    Feb 2012
    Location
    Topeka, Kansas, United States
    Posts
    198
    Liked
    130 times
    Quote Originally Posted by acertabuser View Post
    I can't test this yet, but I'm wondering if the unpackaged kernel (produced by unpack-booimg.pl) actually needs to be gunzip'd so that it is a regular zImage before doing the repack.
    it is a zimage just renamed...

  9. #8
    Iconia Operative
    Member #
    8381
    Join Date
    Mar 2012
    Posts
    168
    Liked
    5 times
    Ok. I was able to use my created cwmrecovery.img-ramdisk.cpio.MOD.gz ramdisk + emulator kernel in emulator just fine. I did another mkbootimg test and I had same lockup using your zImage. Maybe their is something wrong with my mkbootimg command? such as I need to make use of the --cmdline switch to specify init= and some such.

  10. #9
    Developer

    Member #
    7978
    Join Date
    Feb 2012
    Location
    Topeka, Kansas, United States
    Posts
    198
    Liked
    130 times
    My Brain Hurts: Porting Clockwork Recovery to New Devices

    this is how I got recovery going on the 200... now granted I had spent a lot of time digging around to over come problems that I ran into but this is how it got done...

    hw

  11. #10
    Iconia Operative
    Member #
    8381
    Join Date
    Mar 2012
    Posts
    168
    Liked
    5 times
    Here was the command that worked:

    Code:
    mkbootimg --kernel cwmrecovery.img-zImage --ramdisk cwmrecovery.img-ramdisk.gz --base 0x10000000 --pagesize 2048 -o recovery_new.img
    Your link mentioned mkvendor.sh and when messing around with that I discovered a new unpackbootimg binary which unpacked things with more information:

    Code:
    tuxuser@droid:~/Downloads/DROID/tmp$ ls
    cwmrecovery.img-base  cwmrecovery.img-cmdline  cwmrecovery.img-pagesize  cwmrecovery.img-ramdisk.gz  cwmrecovery.img-zImage
    
    $ cat cwmrecovery.img-base
    10000000
    
    $ cat cwmrecovery.img-cmdline
    
    $ cat cwmrecovery.img-pagesize
    00000800


 

Ads

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts

Search tags for this page

a200 kernel recovery image
,

acer a200 boot image

,

acer a200 wont boot

,
acer iconia won't boot from usb cd
,

acer iconia wont boot

,

binary /sbin/recovery cwm

,

board ums lunfile

,

booting recovery kernel image iconia

,

booting recovery kernel image iconia a200

,

cwm won't boot

,

cwm wont start

,
iconia a 500 stuck on booting primary kernel image
,
iconia can't boot custom kernel
,
iconia can't use custom kernel
,
unpack and mod recovery.img
Click on a term to search our site for related topics.