DroidForums.net is the original Verizon Android Forum! Registered Users do not see these ads. Please Register - It's Free!
Results 1 to 4 of 4

Thread: Beware of Potential Brick when using ROM Manager!

  1. Junior Droid
    drfsupercenter's Avatar
    Member #
    155322
    Join Date
    Dec 2010
    Posts
    29
    Phone
    Motorola Droid 2
    #1

    Beware of Potential Brick when using ROM Manager!

    This is something I noticed earlier today when I more or less bricked my phone!!!

    The newest version of ROM Manager wants you to update to a new ClockworkMod Recovery, it's version 5.something. However, the Bootstrap app in the marketplace is not updated past 2.5.0.8. Why is this a problem? Well, it appears that this new version of CWM makes the backups as data.ext3.tar and so on. 2.5.0.8 will ONLY work if the file is called data.img.

    Now, I would have assumed that since using ROM Manager to make the backup pulled up this 5.x CWM that when using ROM Manager to restore the backup, it would do the same. But nope. Instead it resorted to the bootstrapped 2.5.0.8 and guess what happened. It wiped /system and then realized since there was no system.img, it couldn't restore anything, and left my phone unbootable. I ended up having to use the 2.3.20 SBF, then re-upgrade it to Gingerbread, install ROM Manager, and SPECIFICALLY BOOT INTO RECOVERY MODE FROM ROM MANAGER to ensure that it's the proper version.

    Not sure if anyone has figured out a fix for this, but I thought I'd let you guys know so it doesn't happen to you. Another solution is to rename each of the files to *.img, however you also need to use a text editor (and one that preserves UNIX line-breaks) to change nandroid.md5 to also have the .img in the name, or it will say the sums don't match.

    Hope this helps, and if anybody has figured out a way to update the bootstrapped version on the phone, I would love to hear about it.
  2.  
     
     
     
  3. Master Droid
    alienware777's Avatar
    Member #
    10139
    Join Date
    Nov 2009
    Posts
    616
    Liked
    6 times
    Phone
    Droid
    #2
    Its common knowledge that you really shouldn't use Rom Manager for much more that downloading Clockwork because of bugs like this.

    Sent from my Droid using Tapatalk
  4. Junior Droid
    drfsupercenter's Avatar
    Member #
    155322
    Join Date
    Dec 2010
    Posts
    29
    Phone
    Motorola Droid 2
    #3
    Ah, well I've always used it for scheduled backups. I have my phone back up the ROM every day at 5am. But if I can't restore it without the phone being able to boot so that I can use the *proper* ClockworkMod, then what else can I do?
  5. Droid Ninja
    Redflea's Avatar
    Member #
    5967
    Join Date
    Nov 2009
    Posts
    1,954
    Liked
    8 times
    Phone
    Motorola Droid 2
    #4
    ....................
    CM7

Links

Posting Permissions

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

Similar Threads

  1. Help with potential brick.....
    By Matte242 in forum Droid X Tech Support
    Replies: 7
    Last Post: 07-27-2011, 05:13 AM
  2. Help with potential brick...
    By Matte242 in forum Droid X Tech Support
    Replies: 4
    Last Post: 07-25-2011, 08:25 AM
  3. Beware
    By bdsullivan76 in forum LG Ally
    Replies: 2
    Last Post: 05-24-2011, 09:01 PM
  4. beware
    By snappingfish in forum New Member Introductions & Site Assistance
    Replies: 10
    Last Post: 04-20-2010, 11:12 AM
  5. Help with potential brick.....
    By in forum Droid X2 Tech Support
    Replies: 0
    Last Post: 12-31-1969, 06:00 PM

Search tags for this page

data.ext3.tar
,
droid x2 rom manager
,

how to use rom manager

,
how to use rom manager android
,
rom manager
,
rom manager brick
,
rom manager brick phone
,
rom manager bricked my phone
,
rom manager how to use
,
using rom manager
Click on a term to search our site for related topics.

Tags for this Thread

Find us on Google+