1. Check out our companion app, Forums for Android! Download from Google Play

Root ERROR: Nandroid exited with status 28

Discussion in 'Android Devices' started by brettlewis, Mar 23, 2010.

  1. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    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!
     

    Advertisement

  2. UBRocked

    UBRocked VZW Nexus Please!!!
    333

    Jan 31, 2010
    4,335
    1,563
    333
    Ohio
    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!
     
  3. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    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.
     
  4. dmodert66

    dmodert66 Well-Known Member
    163

    Oct 24, 2009
    1,553
    221
    163
    Project Manager
    Southern California
    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!
     
  5. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    well, everything works up till installing a nanadroid backup.
    There might be some change made, however, I installed the SBF file of the original ROM first, so I don't see how it could be blocked.
     
  6. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    well, I did a little test. I made a nandroid backup of my phone, and then tried to restore from that backup. still got that error...

    I might try a different sprecovery version, a slightly older one?
     
  7. Fadelight

    Fadelight Well-Known Member
    148

    Oct 29, 2009
    1,395
    95
    148
    Security
    Mulberry, FL
    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.
     
  8. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    that would be error 25

    Ill try removing all the other files though

    edit: my current structure is
    sdcard/nandroid/BDS-20100321-0257/(filename)
     
  9. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    no luck

    Its the only backup in my folder now. still error 28

    I really think the issue has to do with something else beside the ROM
     
  10. Fadelight

    Fadelight Well-Known Member
    148

    Oct 29, 2009
    1,395
    95
    148
    Security
    Mulberry, FL
    The only other reason I have seen for errors is if you rename the folder. And I can't figure out why that happens either.

    Out of curiosity... which version of SPR are you using?
     
  11. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    i believe its 99.3b

    I got if from DMUpdater... so im assuming it works for the masses...

    edit: Yes, it is 0.99.3b.img
     
  12. Fadelight

    Fadelight Well-Known Member
    148

    Oct 29, 2009
    1,395
    95
    148
    Security
    Mulberry, FL
    Idunno man. I would say the next logical step would be to email the dev and tell him what the code is and ask him what is going on.
     
  13. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    im giving in... :(

    I have spent over way to many hours trying to figure it out. Ill wait till this happens to someone else maybe. Till then I guess ill take the 2.1 ota...:cool:
     
  14. VeryApe

    VeryApe Well-Known Member
    36

    Nov 24, 2009
    118
    3
    36
    Systems Administrator
    Lancaster, PA
    I think it was mentioned before, but I would download a new nandroid backup and try that. My guess is it was a corrupt download. Try one version lower and see if that works.
     
  15. OMJ

    OMJ Bazinga
    213

    Nov 27, 2009
    3,290
    825
    213
    Finance
    Pennsylvania
    Have you tried using an update.zip?

    You could also try redownloading and manually flashing Sprecovery. Its pretty easy to do.
    SirPsychoS Recov. 0.99.3b, Koush's ClockworkMod Recov. 1.4.1

    If none of that works then I would try UBRs suggestion of trying rom manager. If another recovery doesnt work there is something up with your phone
     
  16. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    Ive done it all...

    this phone seems to have a few screw loose. Its not as nice as my other one. very slow, restarts, tons of FC...
     
  17. OMJ

    OMJ Bazinga
    213

    Nov 27, 2009
    3,290
    825
    213
    Finance
    Pennsylvania
    take it back
     
  18. UBRocked

    UBRocked VZW Nexus Please!!!
    333

    Jan 31, 2010
    4,335
    1,563
    333
    Ohio
  19. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    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.
     
  20. UBRocked

    UBRocked VZW Nexus Please!!!
    333

    Jan 31, 2010
    4,335
    1,563
    333
    Ohio
    Wait...I'm trying to understand this...You installed the SBF file on your new phone?
     
  21. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    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:
     
  22. UBRocked

    UBRocked VZW Nexus Please!!!
    333

    Jan 31, 2010
    4,335
    1,563
    333
    Ohio
    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:
     
  23. peenapple390

    peenapple390 Well-Known Member
    16

    Dec 10, 2009
    74
    3
    16
    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!!
     
  24. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    horray! Im not the only one!!!!!! :d
     
  25. brettlewis

    brettlewis Well-Known Member
    Thread Starter
    68

    Nov 3, 2009
    867
    49
    68
    Arizona
    Working on my new phone... Guess it was a hardware issue. :)
     

Share This Page

Loading...