• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ERROR: Nandroid exited with status 28

brettlewis

Android Expert
Nov 3, 2009
862
49
Arizona
This is pissing me off so much.

Just got a replacement phone and have been trying for 24 hours almost non-stop trying to get bugless beast back on it, but every time i try I get that error. I have even tried other roms and keep getting that error.

It has been defined as "28 - The rom is corrupt somehow, simple redownload or pick another mirror site."

I have tried every thing :(

HALP!
 
I'm off to bed...but I'll leave you with this thought: Maybe it is not your ROM that is corrupted...maybe it is your recovery. Why don't you try re-flashing SPRecovery. Or just to test, You could try ROM Manager and see if you can get Koush's Rom to load up. I know the feeling of frustration...but rest assured...it is a "stupid", little problem...it always is. Good Luck, I hope you get it running!
 
Upvote 0
I'm off to bed...but I'll leave you with this thought: Maybe it is not your ROM that is corrupted...maybe it is your recovery. Why don't you try re-flashing SPRecovery. Or just to test, You could try ROM Manager and see if you can get Koush's Rom to load up. I know the feeling of frustration...but rest assured...it is a "stupid", little problem...it always is. Good Luck, I hope you get it running!

yeah seriously. I have done this so many times, I must be missing something. I have loaded up recovery like 20 times though. Maybe Ill try to push recovery from some other source.
 
Upvote 0
I hope this isn't some new problem with newer phones. By the end of this week, I will have convinced 9 people to buy Droids. I have rooted 3 of them so far, and need to root at least 2 more once they come in. The last one I did was around 2 weeks ago, and all went smoothly...

Please keep this thread updated, so I know if I need to deal with anything out of the ordinary! Good luck man!
 
Upvote 0
lol this happens frequently around here. It doesn't have to... enough people have gone through the same thing... but I won't go there.

Anyhow... your error is caused by having one too many folders. ie: your path is /sdcard/nandroid/folder1/folder2/actual backup. It should be /sdcard/nandroid/folder1/actual backup.

seeing the same error when you try a restore directly from a backup is likely caused by having two backups present in the nandroid folder. I don't think it is supposed to respond that way, but it does regardless. Delete all but one single backup and make sure you don't have it inside too many different folders.
 
Upvote 0
Anyhow... your error is caused by having one too many folders. ie: your path is /sdcard/nandroid/folder1/folder2/actual backup. It should be /sdcard/nandroid/folder1/actual backup.

that would be error 25

Ill try removing all the other files though

edit: my current structure is
sdcard/nandroid/BDS-20100321-0257/(filename)
 
Upvote 0
Upvote 0
Hey, I'll chime in again...Can you confirm that you do have root access? Did you try to install the update.zip that gives you root access vs. using DroidMod. I would go step by step through this...just to be sure... http://androidforums.com/all-things-root-droid/45764-guide-s-everything-root-related.html. I'm just throwing shit out there at this point but if it doesn't work...start from the VERY beginning and go step by step.

yeah, after droidmod failed me I did the rootyourdroid.info method, as outlined in that forum post.

I really don't know whats wrong. Im thinking there is a hardware issue with RAM or something, the sbf install failed that step...

just don't know how to tell Verizon that without being told i voided my warranty.
 
Upvote 0
Wait...I'm trying to understand this...You installed the SBF file on your new phone?

I know, sounds silly. but after the third or so attempt of trying to nanadroid restore my phone its pretty much killed itself. Couldn't do anything on it, sbf saved it from a coma, however, it lead me to what appears to be the real problem, while in RSD lite, I get an error when its trying to format the ram, or whatever it wants to do. that stage failed. I tried again, it failed again.

It led me to think there is a hardware issue causing my errors and reboots. It is a "re-certified phone" so im guessing it probably was returned before for the same reason i'm returning it.

I called the 1-800 number, which by the way is like 999999 time easier then talking to a store employee, and explained the problem. They told me all this stuff to do to test it, and I was still having issues. the Verizon guy told me he was going to call me at at 8:45 in the morning (now thats customer service, they call you!) to see if my phone stopped having seizers. Needless to say, all hell broke loose tonight and 3g wont work anymore, and when I open up a data intensive program the phone restarts itself.

Here is a tribute to my previous droid (I have really bad luck I guess)

Droid 1: RIP, your cell antean broke, you could not call :(
Droid 2: RIP, your proximity sensor broke, and was shipped missing the alt key
Droid 3: You were "special", parts of your brain appear to be missing

Maybe droid 4 will survive?

at least i'm getting my monies worth on the warrantys?
:cool:
 
Upvote 0
I know, sounds silly. but after the third or so attempt of trying to nanadroid restore my phone its pretty much killed itself. Couldn't do anything on it, sbf saved it from a coma, however, it lead me to what appears to be the real problem, while in RSD lite, I get an error when its trying to format the ram, or whatever it wants to do. that stage failed. I tried again, it failed again.

It led me to think there is a hardware issue causing my errors and reboots. It is a "re-certified phone" so im guessing it probably was returned before for the same reason i'm returning it.

I called the 1-800 number, which by the way is like 999999 time easier then talking to a store employee, and explained the problem. They told me all this stuff to do to test it, and I was still having issues. the Verizon guy told me he was going to call me at at 8:45 in the morning (now thats customer service, they call you!) to see if my phone stopped having seizers. Needless to say, all hell broke loose tonight and 3g wont work anymore, and when I open up a data intensive program the phone restarts itself.

Here is a tribute to my previous droid (I have really bad luck I guess)

Droid 1: RIP, your cell antean broke, you could not call :(
Droid 2: RIP, your proximity sensor broke, and was shipped missing the alt key
Droid 3: You were "special", parts of your brain appear to be missing

Maybe droid 4 will survive?

at least i'm getting my monies worth on the warrantys?
:cool:

That is a hilarious tribute. :D Glad to know that this was a hardware problem...cause I think you were baffling myself and everyone else that read your thread...Sorry to hear that you are having so many issues. Did someone put a curse on your or something :thinking:
 
Upvote 0
Brett,

Had the same exact issue with Error 28 with my previous Droid and it said "Installation Failed" when I tried to flash the SBF through RSD Lite, got a replacement and it works like a dream now!

It is indeed a more internal issue that cannot be fixed and I could not figure out what was wrong with it for the life of me.

Good luck on #4!!
 
Upvote 0
brett,

had the same exact issue with error 28 with my previous droid and it said "installation failed" when i tried to flash the sbf through rsd lite, got a replacement and it works like a dream now!

It is indeed a more internal issue that cannot be fixed and i could not figure out what was wrong with it for the life of me.

Good luck on #4!!

horray! Im not the only one!!!!!! :d
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones