Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

installing CM from 2.3.4


  • Please log in to reply
36 replies to this topic

#1 ddog

ddog
  • Members
  • 1 posts
  • Country:
    us - United States
  • Device Model:
    droid 2
  • CM Version:
    not yet
  • Recovery Image:
    TWRP

Posted 14 May 2012 - 04:09 AM

Do i have to bring the operating system back to factory then root or is there an easier way?

#2 bassmadrigal

bassmadrigal
  • Administrators
  • 12912 posts
  • Country:
    us - United States
  • Location:
    Newport News, VA
  • Device Model:
    Nexus 4
  • CM Version:
    10.2 Nightlies
  • Recovery Image:
    TWRP

Posted 14 May 2012 - 05:40 AM

From what I can read about your phone, it seems it is impossible to root it while running 2.3.4, and everyone who has tried to downgrade their phone bricked it. If that is correct, you are stuck with the stock firmware and can't put any custom ROM on there.

#3 Supercutetom

Supercutetom

    Pants not needed.

  • Donators
  • 6 posts
  • Country:
    us - United States
  • Location:
    VA
  • Device Model:
    Galaxy S3
  • CM Version:
    Cyanogenmod 10.2.1
  • Recovery Image:
    TWRP

Posted 15 May 2012 - 04:21 AM

Here is what I can do to help. Go to the Rootzwiki D2&D2G page located here:

http://rootzwiki.com...droid-2-global/

The first few posts are some work being done for the many people in the same boat as you. Its not a solution, yet, but its the best you're going to get, unfortunately. There are some talented people working on it so I'm sure a solution will be found at some point...

#4 rfmodeler

rfmodeler
  • Members
  • 8 posts
  • Country:
    us - United States
  • Device Model:
    DROID2
  • CM Version:
    none yet
  • Recovery Image:
    ClockworkMod

Posted 27 May 2012 - 01:52 AM

What about installing from rooted 2.3.4? Do I need to roll back to 2.3.3 or can I install as is? I used Voodoo root keeper to keep root after updating to 2.3.4 OTA.

#5 bassmadrigal

bassmadrigal
  • Administrators
  • 12912 posts
  • Country:
    us - United States
  • Location:
    Newport News, VA
  • Device Model:
    Nexus 4
  • CM Version:
    10.2 Nightlies
  • Recovery Image:
    TWRP

Posted 27 May 2012 - 01:59 AM

 rfmodeler, on 27 May 2012 - 01:52 AM, said:

What about installing from rooted 2.3.4? Do I need to roll back to 2.3.3 or can I install as is? I used Voodoo root keeper to keep root after updating to 2.3.4 OTA.

 bassmadrigal, on 14 May 2012 - 05:40 AM, said:

From what I can read about your phone, it seems it is impossible to root it while running 2.3.4, and everyone who has tried to downgrade their phone bricked it. If that is correct, you are stuck with the stock firmware and can't put any custom ROM on there.

Sounds like you are stuck on 2.3.4.

#6 rfmodeler

rfmodeler
  • Members
  • 8 posts
  • Country:
    us - United States
  • Device Model:
    DROID2
  • CM Version:
    none yet
  • Recovery Image:
    ClockworkMod

Posted 27 May 2012 - 11:59 PM

 bassmadrigal, on 27 May 2012 - 01:59 AM, said:

Sounds like you are stuck on 2.3.4.

I am rooted and can get into recovery. I'm just wondering if CM7.2.0-RC1 RC2 or RC3 will have any issues if I attempt this from stock rooted 2.3.4? Has anyone tried this? I'm afraid to go for it because this phone is my daily driver. I'll be getting a new phone in just over a month, but until then I would like to rely on someones experience other than my own.

Are you saying this definitely won't work?

Edited by rfmodeler, 28 May 2012 - 12:01 AM.


#7 bassmadrigal

bassmadrigal
  • Administrators
  • 12912 posts
  • Country:
    us - United States
  • Location:
    Newport News, VA
  • Device Model:
    Nexus 4
  • CM Version:
    10.2 Nightlies
  • Recovery Image:
    TWRP

Posted 28 May 2012 - 02:19 AM

I honestly don't know. Hopefully someone else can come in with some experience.

#8 asoduk

asoduk
  • Members
  • 2 posts
  • Twitter:asoduk
  • Country:
    us - United States
  • Device Model:
    Motorola Droid 2
  • CM Version:
    Stock
  • Recovery Image:
    TWRP

Posted 03 July 2012 - 06:15 PM

Did anyone ever figure out rooting 2.3.4?

#9 tgwoh

tgwoh
  • Members
  • 1 posts
  • Country:
    us - United States
  • Device Model:
    Droid 2
  • CM Version:
    Cyanogenmod 9 Unnofficial Beta
  • Recovery Image:
    ClockworkMod

Posted 17 July 2012 - 05:48 AM

 asoduk, on 03 July 2012 - 06:15 PM, said:

Did anyone ever figure out rooting 2.3.4?

A root method for 2.3.4 OTA has been discovered and I have personally used it.

Here is a link to the RootzWiki forum for anyone interested:
http://rootzwiki.com...nd-droid2-r2d2/

I was never able to successfully flash Cyanogenmod 7.2 stable (or any release candidate), even before flashing it back to stock and accepting the 2.3.4 OTA (BIG mistake)
I was, however, able to get the unofficial port of Cyanogenmod 9 Beta to work after rooting 2.3.4 and following the wiki guide for all of the remaining steps.

Edited by tgwoh, 17 July 2012 - 05:52 AM.


#10 EricPSU

EricPSU
  • Members
  • 1 posts
  • Country:
    us - United States
  • Device Model:
    DROID 2
  • CM Version:
    N/A
  • Recovery Image:
    Cyanogen

Posted 21 July 2012 - 02:29 AM

I successfully rooted my DROID2 2.3.4 using the steps outlined in here.  But when I flash Cyanogenmod 7.2 I get the following error log.  Does anyone have any ideas?  Thanks!

Starting recovery on Sat Jul 21 01:35:57 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 4 (480 x 854)
ClockworkMod Recovery v5.0.2.0
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null)
  1 /recovery emmc /dev/block/mmcblk1p16 (null)
  2 /misc emmc /dev/block/mmcblk1p18 (null)
  3 /system auto /dev/block/mmcblk1p21 (null)
  4 /cache ext3 /dev/block/mmcblk1p22 (null)
  5 /preinstall ext3 /dev/block/mmcblk1p23 (null)
  6 /data ext3 /dev/block/mmcblk1p24 (null)
  7 /pds ext3 /dev/block/mmcblk1p7 (null)
  8 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.factorytest=0
ro.usb_mode=normal
ro.serialno=015D884E12024026
ro.bootmode=reboot
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=D237
ro.hardware=mapphone_cdma
ro.revision=0
ro.sys.atvc_allow_netmon_usb=0
ro.sys.atvc_allow_netmon_ih=0
ro.sys.atvc_allow_res_core=0
ro.sys.atvc_allow_res_panic=0
ro.sys.atvc_allow_all_adb=1
ro.sys.atvc_allow_all_core=0
ro.sys.atvc_allow_efem=0
ro.sys.atvc_allow_bp_log=0
ro.sys.atvc_allow_ap_mot_log=0
ro.sys.atvc_allow_gki_log=0
persist.radio.cdma.min=8142496312
persist.sys.country=US
persist.radio.vzw.cdma.mdn=8149343694
persist.sys.timezone=America/Detroit
persist.sys.localevar=
persist.sys.mot.encrypt.mmc=0
persist.sys.language=en
ro.FOREGROUND_APP_MEM=2464
ro.VISIBLE_APP_MEM=3712
ro.SECONDARY_SERVER_MEM=7392
ro.BACKUP_APP_MEM=7392
ro.HOME_APP_MEM=7392
ro.HIDDEN_APP_MEM=8608
ro.CONTENT_PROVIDER_MEM=9856
ro.EMPTY_APP_MEM=9856
ro.blan.interface=usb0
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=1
ro.PERCEPTIBLE_APP_ADJ=2
ro.HEAVY_WEIGHT_APP_ADJ=3
ro.SECONDARY_SERVER_ADJ=4
ro.BACKUP_APP_ADJ=5
ro.HOME_APP_ADJ=6
ro.HIDDEN_APP_MIN_ADJ=7
ro.EMPTY_APP_ADJ=15
ro.PERCEPTIBLE_APP_MEM=4096
ro.HEAVY_WEIGHT_APP_MEM=4096
net.tcp.buffersize.default=65536,131072,262144,65536,131072,262144
net.change=net.tcp.buffersize.gprs
net.tcp.buffersize.wifi=4095,87380,110208,4096,16384,110208
net.tcp.buffersize.umts=4094,87380,110208,4096,16384,110208
net.tcp.buffersize.edge=4093,26280,35040,4096,16384,35040
net.tcp.buffersize.gprs=4092,8760,11680,4096,8760,11680
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
8f1786ad7a50da1e8248eeb04ffcd683
8f1786ad7a50da1e8248eeb04ffcd683
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.8");
ui_print("July 20, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
format("/cache");
format("/data");
format("/sd-ext");
assert(install_zip("/sdcard/cm-7.2.0-droid2.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.8
July 20, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk1p24 on /data failed: Device or resource busy
mount: mounting /dev/block/mmcblk1p22 on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk1p22: 11/48768 files (0.0% non-contiguous), 11821/194560 blocks
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: 256-byte inodes not usable on older systems
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
e2fsck 1.41.6 (30-May-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/block/mmcblk1p24: 11/436320 files (0.0% non-contiguous), 64029/1742848 blocks
Formatting /sd-ext...
-- Installing: /sdcard/cm-7.2.0-droid2.zip
Finding update package...
I:Update location: /sdcard/cm-7.2.0-droid2.zip
Opening update package...
Installing update...
Checking Kernel Version...  about to run program [/tmp/check_kernel] with 1 args
run_program: child exited with status 1
script aborted: assert failed: run_program("/tmp/check_kernel") == 0
If install aborts here make
sure you are on the OTA and
not the original GB Leak!

assert failed: run_program("/tmp/check_
kernel") == 0
E:Error in /sdcard/cm-7.2.0-droid2.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/cm-7.2.0-droid2.zip")

#11 GregMoens

GregMoens
  • Members
  • 45 posts
  • Country:
    us - United States
  • Device Model:
    Galaxy Nexus (Verizon)
  • CM Version:
    MMuzzy
  • Recovery Image:
    ClockworkMod

Posted 23 July 2012 - 01:08 AM

Look like you're failing the check_kernel script.  This was put in place to prevent someone with a Froyo based kernel from flashing a CM version that required the Gingerbread kernel.  If you open up the cm-7.2.0-droid2.zip file and look at /system/etc/check_kernel, you'll see that the required kernel version is 2.6.32.9-gca08d89, which matches my Droid2 exactly.  I'm assuming your version does not match.  That 2.3.4 update must have bumped the kernel version.  This new kernel may or may not work with CM7.2.

Couple options I can think of.  You could change the required version in the check_kernel script.  Or you can blank out that entire file and replace it with:

#!/sbin/sh

exit 0

You could also edit the main update script found under /META-INF/com/google/android/updater-script and delete this line:

assert(run_program("/tmp/check_kernel") == 0);

Just make any of those changes, repackage the zip file, and try flashing that.  You could very well get stuck in a bootloop due to the new kernel being incompatible and you may have to SBF back to rooted 2.3.4 and live with that for now.  Good luck!

#12 Supercutetom

Supercutetom

    Pants not needed.

  • Donators
  • 6 posts
  • Country:
    us - United States
  • Location:
    VA
  • Device Model:
    Galaxy S3
  • CM Version:
    Cyanogenmod 10.2.1
  • Recovery Image:
    TWRP

Posted 09 August 2012 - 04:19 PM

If you or anyone wants to have CM7 you can use this. It should work because it worked for me!

https://www.dropbox....temare-.621.zip

#13 DaFox

DaFox
  • Members
  • 1 posts
  • Country:
    ca - Canada
  • Device Model:
    DROID2
  • CM Version:
    Stock 2.3.4
  • Recovery Image:
    ClockworkMod

Posted 13 August 2012 - 09:05 PM

What exactly does this change that makes it work Supercutetom?

And is it based on Stable?

Edited by DaFox, 13 August 2012 - 09:10 PM.


#14 TechNoid665

TechNoid665
  • Members
  • 4 posts
  • Country:
    us - United States
  • Device Model:
    Droid 2 A955
  • CM Version:
    CM
  • Recovery Image:
    Cyanogen

Posted 16 August 2012 - 04:51 PM

Hello all,

I have been unable to try out CM7.2 at all with my 2.3.4 / 621 Droid2, and I've tried over and over using different methods to load RC1, RC2 and the official CM 7.2 6/16/12 release, all failing with
Checking Kernel Version... If install aborts here make sure you are on the OTA and not the original GB Leak!  (Status7)  Installation aborted

I am pleased to announce that I was able to load Supercutetom's Spitemare build ( droid2-cm7-gb-20120611-spitemare-.621 ).  Thanks Tom!  
As a sidenote, this is my first successful load ever of a non-stock ROM :D

But I too ask the question what is it based on?

EDIT:
Well I got courageous and tried to install CM7.2 official release over top of Tom's Spitemare, and it failed with the same error indicated above, and now it appears I am bricked.  Now onto SBF and reroot....fun fun fun!

EDIT2:
Well I am back to playing with the Spitemare build.  This build feels like Froyo, not GB.
Anybody else running this?

Edited by TechNoid665, 16 August 2012 - 07:12 PM.


#15 plithwo

plithwo
  • Members
  • 1 posts
  • Country:
    iq - Iraq
  • Location:
    USA
  • Device Model:
    Droid2
  • CM Version:
    SuperCuteTom 7.2
  • Recovery Image:
    ClockworkMod

Posted 16 August 2012 - 06:47 PM

Supercutetom: THANK YOU SO MUCH!!!! Can you give us a MD5 for that to verify (it worked great on mine, but ya know). I downloaded the CM7.2 you posted. It works like a dream and IT'S AWESOME! I'd love to know how you did it but honestly I'm not sure I even care.

Technoid665: Yeah, I'd just use Supercutetom's.

The whole process was a severe pain in the butt. Trying to remember it may make me sick, but I'll try:

Now, the actual instructions:

Quote


1. Follow instructions on CMWiki to back up everything that you want to keep.

2. Ignore instructions on cyanogenmod wiki to downgrade your phone. If your phone is at 2.3.4, you can still install cyanogenmod using Tom's Spitemare... but don't downgrade your phone. Don't. For the love of God, don't do it. It WILL brick your phone, I swear. I spent most of Tuesday unbricking my phone after I ignored the advice and tried to do it anyway. Link to the CMWiki: http://wiki.cyanogen...ll_Update_Guide

{However, if you DO decide to downgrade your droid 2 2.3.4, i think I unbricked mine by sending it the sbf from the rootzwiki unrooting instructions below with RSD Lite. What a relief that was!}


2. maybe optional, not sure: Follow the instructions on cyanogenmodwiki to root your phone. Skip the downgrade step. Also use the instructions at rootzwiki generated by phifc (google "root droid 2 2.3.4 rootzwiki", should be the second result, then go back to the first page of that thread). I don't know if it will post my link, but I'll try: http://rootzwiki.com...2d2/page__st__0

3. Follow the directions at the cyanogenmod wiki for installing droid 2 to install clockworkmod. (I can't remember if I used the instructions on cyanogenmod wiki to root it or not (I think I did), but after rooting, install clockworkmod per the cyanogenmod wiki.)

4. Download Supercutetom's Spitemare (3 posts up from mine).

5. Use the cyanogenmod wiki's instructions in the Flashing Cyanogenmod section of the instructions for the droid 2. IMPORTANT: In step 1, use supercutetom's Spitemare instead.

6. (optional) I recommend downloading the google apps from the wiki as well).

7. Finish the install as instructed on Cyanogenmod wiki.

8. Enjoy!


Many, many thanks to supercutetom. You have made our phones awesome.

EDIT: Back up your SMS

Edited by plithwo, 16 August 2012 - 06:52 PM.


#16 TechNoid665

TechNoid665
  • Members
  • 4 posts
  • Country:
    us - United States
  • Device Model:
    Droid 2 A955
  • CM Version:
    CM
  • Recovery Image:
    Cyanogen

Posted 17 August 2012 - 01:18 PM

Well not having heard back from Supercutetom about what his version was based on, then discovering on a forum what the exact mod it is I needed to do (remove the kernel check), I took the official release of CM7.2, modded it accordingly, and was able to finally successfully flash it to my D2.  

If anyone would like me to provide the modded zip file for your convenience, chime in and I will post a link.

#17 cranked247

cranked247
  • Members
  • 1 posts
  • Country:
    us - United States
  • Device Model:
    A955
  • CM Version:
    cm7
  • Recovery Image:
    ClockworkMod

Posted 23 August 2012 - 11:38 PM

TechNoid please post that link as what you have made is exactly what I've been looking for. Thank you

#18 joeblow789

joeblow789
  • Members
  • 21 posts
  • Country:
    us - United States
  • Device Model:
    D2
  • CM Version:
    7.2
  • Recovery Image:
    ClockworkMod

Posted 26 August 2012 - 05:43 PM

Supercutetom's ROM is a tweaked version of Nis/Spitemare's 6-11-2012 unofficial CM7.  I believe Tom & TechNoid just removed the kernel check like Greg mentioned, but not positive.  Nis' build is based on CM7 stable (actually nightly, but it is "stable") as of June 11th, plus:
  • Focus sound muting
  • Torch toggle on lock screen
  • Pattern lock ring style
  • Custom calendar reminders
  • MIUI bar
  • Center clock
  • Swatch Internet time
  • Alt-lock
  • Source based libsensors
  • Optional charge light (must manually add the following to /system/build.prop:)
    ro.mot.charge_light=1
Nis also has a 7-19-2012 build that includes init changes to fix sticky settings problems, but it will need the kernel check removed to flash over 2.3.4 / .621.

Unfortunately, I think Nis has moved on from D2 deving.  It's possible someone else will pick up the torch on Rootz, though.

Edited by joeblow789, 17 December 2012 - 09:23 PM.


#19 zoof

zoof
  • Members
  • 3 posts
  • Country:
    us - United States
  • Device Model:
    Droid 2
  • CM Version:
    7.2
  • Recovery Image:
    Cyanogen

Posted 29 August 2012 - 01:33 PM

View Postjoeblow789, on 26 August 2012 - 05:43 PM, said:

Supercutetom's ROM is a tweaked version of Nis/Spitemare's 7-19-2012 unofficial CM7.  I believe Tom & TechNoid just removed the kernel check like Greg mentioned, but not positive.  Nis' build is based on CM7 stable as of July 19th, plus:
  • Focus sound muting
  • Torch toggle on lock screen
  • Pattern lock ring style
  • Custom calendar reminders
  • MIUI bar
  • Center clock
  • Swatch Internet time
  • Alt-lock
  • Source based libsensors
  • Optional charge light (must manually add the following to /system/build.prop:)
    ro.mot.charge_light=1
  • init changes for sticky settings
Unfortunately, I think Nis has moved on from D2 deving.  It's possible someone else will pick up the torch on Rootz, though.
Any one have any luck installing google apps.  I've tried different versions from the CM website but they never show up.

#20 zoof

zoof
  • Members
  • 3 posts
  • Country:
    us - United States
  • Device Model:
    Droid 2
  • CM Version:
    7.2
  • Recovery Image:
    Cyanogen

Posted 29 August 2012 - 03:05 PM

Nevermind -- I reflashed everything and it seemed to work this time... Weird.