Brick! Help please!

This is a discussion on Brick! Help please! within the Hacking Help forums, part of the Droid Hacking category; I am currently using the .sbf file to unbrick my phone. I'll tell you what happens in around 15 min....

+ Reply to Thread
Page 3 of 4 FirstFirst 1 2 3 4 LastLast
Results 21 to 30 of 37

Thread: Brick! Help please!

  1. Senior Droid
    Benny's Avatar
    Member #
    33559
    Join Date
    Feb 2010
    Posts
    102
    Phone
    Enter Current Phone Model Here
    #21
    I am currently using the .sbf file to unbrick my phone.
    I'll tell you what happens in around 15 min.
  2. dbu
    dbu is offline
    Senior Droid
    dbu's Avatar
    Member #
    34451
    Join Date
    Feb 2010
    Location
    Fort Worth, TX
    Posts
    208
    Phone
    Motorola Droid
    #22
    Not really sure why some of you are having so much trouble. Koush's ROM and Clockwork recovery have been spot on for me and a lot of others. I really suspect you guys that are having trouble are getting mixed up somewhere but I would need more information to help you out. really, though, if you don't even want to mess with clockwork recovery, you can download Koush's ROM, and rename it to update.zip and install via sprecovery. The reason I think clockwork is beneficial is that you can do everything you want from the ROM Manager app, instead of always having to be in recovery. If any of you need help, I will try to check back on this thread today. I would hate for a few bad experiences turning people off of Koush's ROM, it really is quite great, and I have tried every single one out there. I won't leave it until DroidMod puts their new one out.
  3. Rescue Squad
    BayouFlyFisher's Avatar
    Member #
    14195
    Join Date
    Dec 2009
    Location
    Baton Rouge, LA
    Posts
    4,880
    Liked
    77 times
    Phone
    Bionic & Galaxy Nexus
    Premium Member
    #23
    Quote Originally Posted by dbu View Post
    Not really sure why some of you are having so much trouble. Koush's ROM and Clockwork recovery have been spot on for me and a lot of others. I really suspect you guys that are having trouble are getting mixed up somewhere but I would need more information to help you out. really, though, if you don't even want to mess with clockwork recovery, you can download Koush's ROM, and rename it to update.zip and install via sprecovery. The reason I think clockwork is beneficial is that you can do everything you want from the ROM Manager app, instead of always having to be in recovery. If any of you need help, I will try to check back on this thread today. I would hate for a few bad experiences turning people off of Koush's ROM, it really is quite great, and I have tried every single one out there. I won't leave it until DroidMod puts their new one out.
    The problems are coming in when you try to use the clockwork backup that was made at the very beginning of the process. For all of us that had problems, the first bad thing to happen was after doing a restore in clockwork using the backup it created. That resulted in not being able to get past the M during reboot. We had all decided to go back to our previous roms for various reasons. When that backup failed, we had a bit of trouble getting back to sprecovery so we could us one of our nandroid backups. Different folks are having different problems getting back to sprecovery. It was pretty easy for me because I had good clean copies of Flash_Image and 0.99.3b on my sdcard. Others apparently did not have these files and are having to work around that.

    Anyway, I'm back to my nandroid backup of SS2.02 that I made just prior to installing Koush's rom. No biggie and I'm a happy guy.

    The rom worked well on my droid. It was very stable, but it did seem to run hotter than SS2.02. Not dangerously hotter, just warmer (approximately 10 degrees F).
    Baton Rouge, LA
  4. Master Droid
    forkup's Avatar
    Member #
    184
    Join Date
    Oct 2009
    Posts
    317
    #24
    This is a good reminder for everyone to keep good backups of all files you may need in an emergency.

    Btw clockworkmod rocks!
  5. Senior Droid
    Benny's Avatar
    Member #
    33559
    Join Date
    Feb 2010
    Posts
    102
    Phone
    Enter Current Phone Model Here
    #25
    Ok, So I got my phone un-bricked and back to stock. I rooted it and installed sprecovery 0.99.3. Now when I try to do a nandroid restore it says exited with status 25. There are no spaces is the file or folder names, anyone know whats wrong?

    edit: Nevermind I got it working, I'm restoring it now!
    Last edited by Benny; 03-14-2010 at 01:15 PM.
  6. dbu
    dbu is offline
    Senior Droid
    dbu's Avatar
    Member #
    34451
    Join Date
    Feb 2010
    Location
    Fort Worth, TX
    Posts
    208
    Phone
    Motorola Droid
    #26
    Quote Originally Posted by BayouFlyFisher View Post
    Quote Originally Posted by dbu View Post
    Not really sure why some of you are having so much trouble. Koush's ROM and Clockwork recovery have been spot on for me and a lot of others. I really suspect you guys that are having trouble are getting mixed up somewhere but I would need more information to help you out. really, though, if you don't even want to mess with clockwork recovery, you can download Koush's ROM, and rename it to update.zip and install via sprecovery. The reason I think clockwork is beneficial is that you can do everything you want from the ROM Manager app, instead of always having to be in recovery. If any of you need help, I will try to check back on this thread today. I would hate for a few bad experiences turning people off of Koush's ROM, it really is quite great, and I have tried every single one out there. I won't leave it until DroidMod puts their new one out.
    The problems are coming in when you try to use the clockwork backup that was made at the very beginning of the process. For all of us that had problems, the first bad thing to happen was after doing a restore in clockwork using the backup it created. That resulted in not being able to get past the M during reboot. We had all decided to go back to our previous roms for various reasons. When that backup failed, we had a bit of trouble getting back to sprecovery so we could us one of our nandroid backups. Different folks are having different problems getting back to sprecovery. It was pretty easy for me because I had good clean copies of Flash_Image and 0.99.3b on my sdcard. Others apparently did not have these files and are having to work around that.

    Anyway, I'm back to my nandroid backup of SS2.02 that I made just prior to installing Koush's rom. No biggie and I'm a happy guy.

    The rom worked well on my droid. It was very stable, but it did seem to run hotter than SS2.02. Not dangerously hotter, just warmer (approximately 10 degrees F).
    That's just odd that it is happening to some of you. I have backups of all my ROMs in sprecovery, and clockwork recovery and I can bounce between ROMs and recoveries with no issues at all. I really wish there was a way to pinpoint the problem, but unless you can look over someones shoulder you are not going to be able to see all the steps to do something.
  7. Master Droid
    forkup's Avatar
    Member #
    184
    Join Date
    Oct 2009
    Posts
    317
    #27
    Status 25 means either the files are inside /sdcard/nandroid itself or are in /sdcard/nandroid/folder/folder neither of which will work. The files need to be at /sdcard/nandroid/folder
  8. Beta Team
    adrynalyne's Avatar
    Member #
    18036
    Join Date
    Dec 2009
    Posts
    2,900
    Phone
    Droidzilla
    DroidForums.net Developer
    Premium Member
    #28
    Quote Originally Posted by dbu View Post
    Not really sure why some of you are having so much trouble. Koush's ROM and Clockwork recovery have been spot on for me and a lot of others. I really suspect you guys that are having trouble are getting mixed up somewhere but I would need more information to help you out. really, though, if you don't even want to mess with clockwork recovery, you can download Koush's ROM, and rename it to update.zip and install via sprecovery. The reason I think clockwork is beneficial is that you can do everything you want from the ROM Manager app, instead of always having to be in recovery. If any of you need help, I will try to check back on this thread today. I would hate for a few bad experiences turning people off of Koush's ROM, it really is quite great, and I have tried every single one out there. I won't leave it until DroidMod puts their new one out.
    The recovery image pisses me off to no end. I love the features, but half the time he updates it, it breaks previous backups. He updated it yesterday and it broke my previous ESE53 backup. I had to flash to an old version of the recovery image. Then when I went to flash back to CM, it broke CM!

    So annoying.
  9. Master Droid
    kaboyd's Avatar
    Member #
    16497
    Join Date
    Dec 2009
    Location
    Southern Indiana
    Posts
    565
    Phone
    SGN
    #29
    There are a lot of things buggy about Kouch's Rom. My Gmail would not open, the app names were all off center in the app scroller, the Market would not open...etc... The largest problem was with the Rom Manager and the Recovery program. It did not recognize any of my old backups so I could not install anything but Kouch's ROM. and if I tried to revert to stock or run an update.zip, I would get stuck on the Motorola "M" screen. The whole experience was enough to to keep me away from this ROM and recovery system forever... I did finally get back to a functioning Rom and SPrecovery with the help of DMupdater (thanks cupfulloflol, I didn't think of that. it worked flawlessly to install a good copy of 0.99.3b)
  10. dbu
    dbu is offline
    Senior Droid
    dbu's Avatar
    Member #
    34451
    Join Date
    Feb 2010
    Location
    Fort Worth, TX
    Posts
    208
    Phone
    Motorola Droid
    #30
    Quote Originally Posted by kaboyd View Post
    There are a lot of things buggy about Kouch's Rom. My Gmail would not open, the app names were all off center in the app scroller, the Market would not open...etc... The largest problem was with the Rom Manager and the Recovery program. It did not recognize any of my old backups so I could not install anything but Kouch's ROM. and if I tried to revert to stock or run an update.zip, I would get stuck on the Motorola "M" screen. The whole experience was enough to to keep me away from this ROM and recovery system forever... I did finally get back to a functioning Rom and SPrecovery with the help of DMupdater (thanks cupfulloflol, I didn't think of that. it worked flawlessly to install a good copy of 0.99.3b)
    A) The only ROM yo can install with ROM manager is Koush's ROM, it plainly says that old nandroid backups are not compatible with his recovery.
    B) Did you do a complete data/cahe wipe before going to Koush's ROM, especially if you were coming from a 2.01 ROM? A lot of problems can be attributed to that, if that is the case, because none of the issues you were having have been mentioned aside from the app names being off in launcher2 and that is a known bug that can be fixed with a reboot.

Sponsors

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. Brick'ing a Droid
    By hal1 in forum Droid General Discussions
    Replies: 4
    Last Post: 06-11-2010, 03:28 PM
  2. Did i just brick my phone =(
    By phatkat66 in forum Hacking Help
    Replies: 11
    Last Post: 02-20-2010, 03:45 PM
  3. HELP so close to brick its not funny
    By evilsock in forum Hacking Help
    Replies: 10
    Last Post: 02-14-2010, 01:36 PM
  4. Possible Brick! Please Help!
    By MolonLabe in forum Hacking Help
    Replies: 25
    Last Post: 02-11-2010, 10:56 PM
  5. Brick'd? Now what?
    By RayneC in forum Tech Issues, Bug Reports & Suggestions
    Replies: 12
    Last Post: 02-11-2010, 12:37 AM

Search tags for this page

can i unbrick my phone with clockworkmod reecovery

,

dream mtd read all-zero block at 0x00000000

,

flash image read all-zero block android

,

mtd: read all-zero block at

,

mtd: read all-zero block at 0x00180000; skipping

,

mtd: read all-zero block at error reading

,

recovery-0.99.2b.img mtd:read error at

,

recovery-0.99.3b.sbf

,

restore brick droid

Click on a term to search our site for related topics.