CWM for RAZR i

Search This thread

turl1

Senior Member
May 2, 2011
507
997
Well, after figuring out the image format for boot and recovery, I built a CWM image for the RAZR i. I had to fix and hack around quite a bit of code to have it building (arm is hardcoded on several places :( ), and it's completely untested as I don't own the device, so try at your own risk :)

Download: https://dl.dropbox.com/u/553461/recovery-razri.img

If it works I'll talk with koush and see how we can get all this broken code fixed to support x86 devices :)


After a session of remote debugging with @mattlgroff's phone, here's the first usable razr i recovery image! :)

Download https://dl.dropbox.com/u/553461/recovery-razri-try4.img

There's still a couple of bugs to kill on it (like keys being a little.. slow to generate events) but it's usable and mattlgroff was able to nandroid his phone with it.


After more debugging with @mattlgroff's phone today, touch works now, and I have implemented a workaround for the screen refresh issue.

Download: https://dl.dropbox.com/u/553461/recovery-razri-tryAtouch.img

You can use both touch and buttons on it. Power button selects the highlighted option, camera button goes back, vol+/- highlight the next/previous option. The recovery should be "4.2-ready".

I appreciate all the donations I have received lately. As you probably noticed already, I have recently been working on the RAZR i but I don't own the phone. If I receive enough donations to be able to afford it, I plan to purchase one to port CM to and do my own testing :)
 
Last edited:

ReeSilva

Senior Member
Dec 30, 2010
144
33
Well, after figuring out the image format for boot and recovery, I built a CWM image for the RAZR i. I had to fix and hack around quite a bit of code to have it building (arm is hardcoded on several places :( ), and it's completely untested as I don't own the device, so try at your own risk :)

Download: https://dl.dropbox.com/u/553461/recovery-razri.img

If it works I'll talk with koush and see how we can get all this broken code fixed to support x86 devices :)

Just to know, if I test it and doesn't works what can occurs to my device? I'll have a way to back to stock recovery?
 

mattlgroff

Inactive Recognized Developer
Dec 5, 2011
2,289
2,445
San Diego

Attachments

  • adbTest.jpg
    adbTest.jpg
    30.7 KB · Views: 3,605
Last edited:

mattlgroff

Inactive Recognized Developer
Dec 5, 2011
2,289
2,445
San Diego
Can you try on another OS just to be sure? Windows and its silly need to install drivers for all the things can cause an issue or two :p

Yeah silly Winblows.

Code:
matt@matt-desktop:~$ adb devices
List of devices attached 
TA23700S5B	device

matt@matt-desktop:~$ adb wait-for-device reboot recovery
matt@matt-desktop:~$ adb wait-for-device devices
^C
matt@matt-desktop:~$ adb devices
List of devices attached 
TA23700S5B	recovery

matt@matt-desktop:~$ adb shell
~ # ls
boot                 etc                  sd-ext
cache                init                 sdcard
data                 init.rc              sys
datadata             proc                 system
default.prop         res                  tmp
dev                  root                 ueventd.goldfish.rc
emmc                 sbin                 ueventd.rc

~ # cat default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=cm_smi-userdebug 4.1.2 JZO54K eng.root.20121105.023150 test-keys
ro.build.version.incremental=eng.root.20121105.023150
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Mon Nov  5 02:32:23 UTC 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=root
ro.build.host=laptop
ro.build.tags=test-keys
ro.product.model=cm_smi
ro.product.brand=generic_x86
ro.product.name=cm_smi
ro.product.device=smi
ro.product.board=smi
ro.product.cpu.abi=x86
ro.product.manufacturer=Motorola
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=smi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cm_smi-userdebug 4.1.2 JZO54K eng.root.20121105.023150 test-keys
ro.build.fingerprint=generic_x86/cm_smi/smi:4.1.2/JZO54K/eng.root.20121105.023150:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=smi
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10-20121105-UNOFFICIAL-smi
ro.modversion=10-20121105-UNOFFICIAL-smi
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.carrier=unknown
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
~ #

Code:
matt@matt-desktop:~$ adb reboot recovery
matt@matt-desktop:~$ adb logcat
- waiting for device -
^C
matt@matt-desktop:~$ adb logcat
/sbin/sh: exec: line 1: logcat: not found
matt@matt-desktop:~$ adb shell
~ # logcat
/sbin/sh: logcat: not found
~ # cd system
/system # ls
bin
/system # cd bin
/system/bin # ls
/system/bin #
^^^
Looks like there isn't a way for me to log errors.. at least from what I see.
 
Last edited:

turl1

Senior Member
May 2, 2011
507
997
Well, judging by the output it looks like it's crashing over and over. I'll see if I can get CWM running on a virtual machine and debug further that way.
 

mattlgroff

Inactive Recognized Developer
Dec 5, 2011
2,289
2,445
San Diego
Man, that command that u send early doesn't work. There is another command to back to stock recovery?

Code:
fastboot flash recovery recovery.img

Code:
fastboot flash recovery recovery_signed

Code:
fastboot flash recovery razr_i_recovery.img

I don't know what your filename is for your stock recovery, but I will show example below.

Code:
fastboot flash recovery example
 
  • Like
Reactions: baxxter106

ReeSilva

Senior Member
Dec 30, 2010
144
33
Well, just in case, there's my log.

Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
/tmp # cat recovery.log
Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
Starting recovery on Tue Nov 6 04:25:17 2012
Starting recovery on Tue Nov 6 04:25:22 2012
Starting recovery on Tue Nov 6 04:25:27 2012
Starting recovery on Tue Nov 6 04:25:32 2012
/tmp # cat recovery.log
Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
Starting recovery on Tue Nov 6 04:25:17 2012
Starting recovery on Tue Nov 6 04:25:22 2012
Starting recovery on Tue Nov 6 04:25:27 2012
Starting recovery on Tue Nov 6 04:25:32 2012
/tmp # cat recovery.log
Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
Starting recovery on Tue Nov 6 04:25:17 2012
Starting recovery on Tue Nov 6 04:25:22 2012
Starting recovery on Tue Nov 6 04:25:27 2012
Starting recovery on Tue Nov 6 04:25:32 2012
Starting recovery on Tue Nov 6 04:25:37 2012
/tmp # cat recovery.log
Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
Starting recovery on Tue Nov 6 04:25:17 2012
Starting recovery on Tue Nov 6 04:25:22 2012
Starting recovery on Tue Nov 6 04:25:27 2012
Starting recovery on Tue Nov 6 04:25:32 2012
Starting recovery on Tue Nov 6 04:25:37 2012
Starting recovery on Tue Nov 6 04:25:42 2012

---------- Post added at 02:29 AM ---------- Previous post was at 02:27 AM ----------

Code:
fastboot flash recovery recovery.img

Code:
fastboot flash recovery recovery_signed

Code:
fastboot flash recovery razr_i_recovery.img

I don't know what your filename is for your stock recovery, but I will show example below.

Code:
fastboot flash recovery example

Can u send to me the stock recovery img?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 60
    Well, after figuring out the image format for boot and recovery, I built a CWM image for the RAZR i. I had to fix and hack around quite a bit of code to have it building (arm is hardcoded on several places :( ), and it's completely untested as I don't own the device, so try at your own risk :)

    Download: https://dl.dropbox.com/u/553461/recovery-razri.img

    If it works I'll talk with koush and see how we can get all this broken code fixed to support x86 devices :)


    After a session of remote debugging with @mattlgroff's phone, here's the first usable razr i recovery image! :)

    Download https://dl.dropbox.com/u/553461/recovery-razri-try4.img

    There's still a couple of bugs to kill on it (like keys being a little.. slow to generate events) but it's usable and mattlgroff was able to nandroid his phone with it.


    After more debugging with @mattlgroff's phone today, touch works now, and I have implemented a workaround for the screen refresh issue.

    Download: https://dl.dropbox.com/u/553461/recovery-razri-tryAtouch.img

    You can use both touch and buttons on it. Power button selects the highlighted option, camera button goes back, vol+/- highlight the next/previous option. The recovery should be "4.2-ready".

    I appreciate all the donations I have received lately. As you probably noticed already, I have recently been working on the RAZR i but I don't own the phone. If I receive enough donations to be able to afford it, I plan to purchase one to port CM to and do my own testing :)
    8
    B-R-A-V-O !!!

    Yessss, it works fine. Now I can do a backup Nandroid !!! It's perfect !
    ;)

    Here is a small tutorial for newbies...
    1. Download Android SDK and install it on your PC (http://developer.android.com/sdk/index.html)
    2. Download the recovery file from the firts post of this thread (http://xdaforums.com/showthread.php?t=1974097)
    3. Plug your USB cable into your RAZRi and into your computer
    4. Reboot your RAZRi with (volume -) and (power) buttons simultaneously pressed to go to "Fastboot Mode"
    5. Go to directory "C:\Program Files\Android\android-sdk\platform-tools" and launch "fastboot.exe" in a command prompt with the following command : "fastboot.exe flash recovery name_of_the_recovery_file.img"
    6. Done !!! Reboot your RAZRi in "Fastboot Mode" and choice "Recovery"... Now you can do a nandroid backup ! (it is slow, slooooooow, veryyyyyy slooooooow... about 30 minutes to make a full backup).
    7. FYI, backup files are stored on your internal phone memory into a directory "clockworkmod/backups"
    8. Please click on the "Thanks" button if this tutorial was helpfull for you ! And if you don't know Dropbox yet, fell free to test it via this link to get 3GB for free : DROPBOX

    LeBobo
    5
    I have updated the first post with a new link, the recovery should be "4.2 ready" now :)

    As always, thanks to @mattlgroff for letting me remote-test on his phone!
    5
    here is a turl1 recovery but with a black background all credit goes to turl1
    as i only changed the background

    download here
    5
    :(

    How skilled are you debugging? Do you know how to use gdb? Can you use gdb and find out what's wrong?

    If you cannot debug it yourself, the best I can offer you guys is try to debug it myself via SSH to someone's box running ubuntu or some other distro with adb and a razr i connected to it in recovery mode (with the nonworking image of course).

    Feel free to SSH in or Team Viewer in to my lappy and RAZR i. :)