09-22-2015 02:20 PM
6,009 ... 2021222324 ...
tools
  1. Raul720's Avatar
    Im on bumblebee 2.4 which has the dalvik cache mod. Will it be safe if just wipe everything then install the backside rom and gapps? How would I get the dalvik cache mod on the backside rom? Or does it already have it?
    Yes, wipe everything. Not sure about your second question.
    08-02-2011 09:17 PM
  2. drezliok's Avatar
    As stated in the OP I'm using CWM 3.0.2.8 with the only problem being AnyKernel doesn't update the modules.
    I can't find that cwm version. Could someone drop a link?
    08-02-2011 09:23 PM
  3. Raul720's Avatar
    I can't find that cwm version. Could someone drop a link?
    Try this one: http://forums.androidcentral.com/opt...-2-8-beta.html
    drezliok likes this.
    08-02-2011 09:27 PM
  4. larryc's Avatar
    I'm still having some odd Market problems with the latest build. I have found a few apps that say "Not Compatible" and won't let me download, yet if I restore back to stock, they show as fine in the market.
    Two examples:
    https://market.android.com/details?i...guide.i95guide
    https://market.android.com/details?id=inrix.android.ui

    Not sure if this is specifically an IHO problem or perhaps it's just something due to 2.2 vs 2.3. Hopefully some more educated minds can chime in.
    08-02-2011 09:54 PM
  5. ravenroost's Avatar
    That's what I have now, it gets the job done, I just know alot of people will use rom manager just to flash a recovery, and its a bad idea
    Could you please explain your comment? Are you saying "using rom manager is a bad idea" or are you saying that "using it only to flash recovery is a bad idea?"

    I currently have cwm recovery 3.2.0.1 flashed through rom manager. It has been a mess. I have backed up roms only to find when I attempt to restore I get MD5 mismatch errors. Also, I cannot get it to install the latest version of IHO (July 30) but July 22 sets up fine. I am not smart enough to know what I may be doing wrong on my end.
    08-02-2011 10:22 PM
  6. Raul720's Avatar
    Could you please explain your comment? Are you saying "using rom manager is a bad idea" or are you saying that "using it only to flash recovery is a bad idea?"

    I currently have cwm recovery 3.2.0.1 flashed through rom manager. It has been a mess. I have backed up roms only to find when I attempt to restore I get MD5 mismatch errors. Also, I cannot get it to install the latest version of IHO (July 30) but July 22 sets up fine. I am not smart enough to know what I may be doing wrong on my end.
    You should install a different recovery.
    ravenroost likes this.
    08-02-2011 10:31 PM
  7. mustafu's Avatar
    Could you please explain your comment? Are you saying "using rom manager is a bad idea" or are you saying that "using it only to flash recovery is a bad idea?"

    I currently have cwm recovery 3.2.0.1 flashed through rom manager. It has been a mess. I have backed up roms only to find when I attempt to restore I get MD5 mismatch errors. Also, I cannot get it to install the latest version of IHO (July 30) but July 22 sets up fine. I am not smart enough to know what I may be doing wrong on my end.
    I have had zero problems with this same setup since day one. Can't help but feel like I'm in the minority here with all the CWM and rom manager bashing that goes on here.

    Sent from my LG-VM670 using Tapatalk
    08-02-2011 10:33 PM
  8. Raul720's Avatar
    I have had zero problems with this same setup since day one. Can't help but feel like I'm in the minority here with all the CWM and rom manager bashing that goes on here.

    Sent from my LG-VM670 using Tapatalk
    The only problem i had with that recovery was that my sd-ext partition wouldn't be recognized so it wouldn't back it up.
    08-02-2011 10:35 PM
  9. Whyzor's Avatar
    Could you please explain your comment? Are you saying "using rom manager is a bad idea" or are you saying that "using it only to flash recovery is a bad idea?"

    I currently have cwm recovery 3.2.0.1 flashed through rom manager. It has been a mess. I have backed up roms only to find when I attempt to restore I get MD5 mismatch errors. Also, I cannot get it to install the latest version of IHO (July 30) but July 22 sets up fine. I am not smart enough to know what I may be doing wrong on my end.
    Maybe these problems should be reported to ROM Manager so the dev can work on them, instead of using an older version that is difficult to locate & install for beginners. (I haven' thad any problems with 3.2.0.1 flashed through ROM Manager)
    ravenroost likes this.
    08-02-2011 10:37 PM
  10. Jk16w's Avatar
    I ain't sure if this is a bug or it has been fixed, but on BACKside ROM I cannot turn off the phone with the USB/Charger connected. Does anybody know why this does this? thanks for any help
    08-02-2011 10:38 PM
  11. Raul720's Avatar
    I ain't sure if this is a bug or it has been fixed, but on BACKside ROM I cannot turn off the phone with the USB/Charger connected. Does anybody know why this does this? thanks for any help
    Because that is a "feature" of cm7
    08-02-2011 10:40 PM
  12. ravenroost's Avatar
    You should install a different recovery.
    What is the easiest way to do that? I have read a lot and tried to change the recovery but when it rebooted it was still the same one.
    08-02-2011 10:41 PM
  13. ravenroost's Avatar
    The only problem i had with that recovery was that my sd-ext partition wouldn't be recognized so it wouldn't back it up.
    I have the same problem.
    08-02-2011 10:43 PM
  14. Raul720's Avatar
    What is the easiest way to do that? I have read a lot and tried to change the recovery but when it rebooted it was still the same one.
    Download this recovery

    http://forums.androidcentral.com/opt...-2-8-beta.html


    unzip it and place it on your sd card. Then use the commands provided in that thread. If you don't use adb you can just use terminal emulator. You might also need flash_image. Make sure you also place that on the root of your sd card
    08-02-2011 10:58 PM
  15. ravenroost's Avatar
    Download this recovery

    http://forums.androidcentral.com/opt...-2-8-beta.html


    unzip it and place it on your sd card. Then use the commands provided in that thread. If you don't use adb you can just use terminal emulator. You might also need flash_image. Make sure you also place that on the root of your sd card
    In terminal emulator do I just copy the commands? I tried before but it didn't seem to work.
    08-02-2011 11:02 PM
  16. Raul720's Avatar
    In terminal emulator do I just copy the commands? I tried before but it didn't seem to work.
    It will probably be better if you input them yourself. I know its going to take long but will probably ensure a better result.
    08-02-2011 11:05 PM
  17. ravenroost's Avatar
    It will probably be better if you input them yourself. I know its going to take long but will probably ensure a better result.
    Let me see if this is correct:

    On termnal emulator, when I open it up it says:

    $ export PATH=/data/local/bin.$PATH
    $

    Then should I type the commands?
    mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system ENTER
    cat /sdcard/flash_image > /system/bin/flash_image ENTER
    chmod 755 /system/bin/flash_image ENTER
    .... and so forth?
    Am I missing any steps?


    [HL]Note:[/HL] If this is going off topic too much, should I start another thread or go pm route?
    08-02-2011 11:13 PM
  18. Whyzor's Avatar
    MD5 error fix for when restoring ROMs:

    Clockwork-mod Recovery MD5 mismatch! error FIX - xda-developers

    Let us know if it works for you, or which file was missing (or did the backup name have special/space characters?) I just checked my backup dir and all the files are there.

    EDIT: Try the quick & easy steps first:

    adb shell
    # cd /sdcard/clockworkmod/backup/2010-06-29.20.22.53
    # rm nandroid.md5
    # md5sum *img > nandroid.md5
    08-02-2011 11:14 PM
  19. blarf's Avatar
    Maybe these problems should be reported to ROM Manager so the dev can work on them, instead of using an older version that is difficult to locate & install for beginners. (I haven' thad any problems with 3.2.0.1 flashed through ROM Manager)
    Later versions of CWM should work /fine/. Assuming they're the ones with the various bugs fixed. Xionia OTOH is known to have problems not doing complete wipes with certain versions and is, AFAIK, no longer maintained. I mention that I use an old version of CWM because that's what I'm doing and I seem to have fewer problems. If there's a newer version (like 3.2.0.1) that works reliably for a bunch of people that's great and is probably a better place to start.

    I ain't sure if this is a bug or it has been fixed, but on BACKside ROM I cannot turn off the phone with the USB/Charger connected. Does anybody know why this does this? thanks for any help
    I believe that's a function of the recovery image, could be CM7. I know the stock firmware doesn't do this, but I'm 99% sure that even aospCMod did this.
    08-02-2011 11:16 PM
  20. Raul720's Avatar
    Let me see if this is correct:

    On termnal emulator, when I open it up it says:

    $ export PATH=/data/local/bin.$PATH
    $

    Then should I type the commands?
    mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system ENTER
    cat /sdcard/flash_image > /system/bin/flash_image ENTER
    chmod 755 /system/bin/flash_image ENTER
    .... and so forth?
    Am I missing any steps?


    [HL]Note:[/HL] If this is going off topic too much, should I start another thread or go pm route?
    type "su" first and then the rest


    su
    mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
    cat /sdcard/flash_image > /system/bin/flash_image
    chmod 755 /system/bin/flash_image
    mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
    mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
    flash_image recovery /sdcard/recovery.img
    08-02-2011 11:17 PM
  21. ravenroost's Avatar
    type "su" first and then the rest
    OK I will try it and let you know how it went.
    08-02-2011 11:20 PM
  22. cr42ydude's Avatar
    What is the easiest way to do that? I have read a lot and tried to change the recovery but when it rebooted it was still the same one.
    the eaiest way is to flash a recovery... [Tool] Flashable Zip Recoveries - xda-developers
    just flash from the recovery u have now .. no need to wipe.
    ravenroost likes this.
    08-02-2011 11:22 PM
  23. drezliok's Avatar
    Download this recovery

    http://forums.androidcentral.com/opt...-2-8-beta.html


    unzip it and place it on your sd card. Then use the commands provided in that thread. If you don't use adb you can just use terminal emulator. You might also need flash_image. Make sure you also place that on the root of your sd card
    I installed it but I am getting a status 7 error when ever I try to flash a rom.

    BLarf mentioned that the latest CWM from the app should be fine so I am reinstalling that one.
    08-03-2011 12:03 AM
  24. blarf's Avatar
    Actually I was using the aosp version of CWM.

    aospCWMod-OV-20110427.img looks like it's available here:

    aospCWMod-OV-20110427.img

    MD5 checksum = 541a89ec68425a5fa3952fb83e4a284f

    Because 'aosp' never publicly released his source I have NO IDEA how this differs from the other CWM posted.
    08-03-2011 12:14 AM
  25. pbailey212's Avatar
    Could you please explain your comment? Are you saying "using rom manager is a bad idea" or are you saying that "using it only to flash recovery is a bad idea?"

    I currently have cwm recovery 3.2.0.1 flashed through rom manager. It has been a mess. I have backed up roms only to find when I attempt to restore I get MD5 mismatch errors. Also, I cannot get it to install the latest version of IHO (July 30) but July 22 sets up fine. I am not smart enough to know what I may be doing wrong on my end.
    The cwm recovery it flashes on your phone is worthless
    08-03-2011 12:27 AM
6,009 ... 2021222324 ...
LINK TO POST COPIED TO CLIPBOARD