Root Bootloop after Nandroid restore

[peenapple390]

So i'm running into an issue here, whenever i try to do an Advanced Nandroid Restore, it goes through the process and says "done". Then I go to reboot system now, and it repeatedly shows the Motorola Logo and thats it!

What am I doing wrong here?! I'm getting frustrated!

 

[UBRocked]

So i'm running into an issue here, whenever i try to do an Advanced Nandroid Restore, it goes through the process and says "done". Then I go to reboot system now, and it repeatedly shows the Motorola Logo and thats it!

What am I doing wrong here?! I'm getting frustrated!

What rom are you using? You probably need to update to a different kernel. Some kernels just don't work with certain phones.

 

[peenapple390]

i'm trying to go to BB V0.7. How do i update the kernal? I'm sorry that sounds noobish but i've always just went the update.zip way and haven't had a problem. Now i'm reading if i'm not coming from a previous version i need to go the nandroid restore route.

 

[Fabolous]

Hrm, if you're using the BB 0.7 nandroid, it comes with the stock 550 MHz kernel, so there should be no boot looping...

Are you well versed in adb?

If you are, when you're in SPRecovery,

adb shell
format DATA:
format CACHE:
format SYSTEM:

and then try the advanced nandroid restore, select the BB 0.7 folder, and give it another go.

The above commands just make sure the phone is completely wiped and ready for a clean install via nandroid.

 

[peenapple390]

when i got to the format CACHE:, i get
mtd: not erasing bad block at 0x01920000

 

[peenapple390]

then when i do the format SYSTEM: i get
mtd: not erasing bad block at 0x05c60000

 

[Fabolous]

when i got to the format CACHE:, i get
mtd: not erasing bad block at 0x01920000

then when i do the format SYSTEM: i get
mtd: not erasing bad block at 0x05c60000

Umm...bad block? That's frightening. You're doing this in recovery?

This means that there could be something wrong with the file system on your ROM.

Try again?

If no luck, maybe flashing the .SBF might fix it? You'll have to root again, install SPRecovery, yada yada though (so don't do this unless you're out of other options).

 

[peenapple390]

I've done it like 5 times and keep getting the same thing over and over.

Maybe its just a good enough idea to flash the .SBF and start allllll over again.

Quick question though, all apps will still be linked to my Google account right??

Thanks Loso!

 

[Fabolous]

They should be. And if not, you could probably recover an old nandroid that will resync them.

Good luck man. This is the first time I've heard of a filesystem error.

 

[peenapple390]

Thanks! I'm just going ahead and flashing the .SBF file.

Now is there an updated rooting guide that will help me through this all??

Is there anything i have to do or remove from the point between rooting and installing the ROM??

 

[Fabolous]

Nothing different than what you did the first time.

I don't know what caused the filesystem error. The hope is that the .SBF, which restores everything, will fix it.

I don't know how many times I've formatted my NAND, installed ROMs, flashed kernels, whatever, and haven't run into anything like this.

Let us know what happens though.

 

[peenapple390]

Sooo, i got an error throughout the RSDLite Process saying...

Failed flashing process. Failed flashing process. Phone[0000]: Error getting subscriber unit information. Device API Error: 0xE00300009 Command: RQHW (0xE0831009); phone connected

but the funny thing is, it then rebooted my phone and it is back to stock 2.0.1.

I'm thinking that i'm making a visit to Verizon tomorrow and getting this thing replaced...

 

[Fabolous]

Aiyiyi!

Yeah, perhaps the damage is to the actual NAND, and not just the filesystem.

But what will you tell VZW? Is it working fine on the 2.0.1?

 

[peenapple390]

its working OK, but I have a friend that works for VZW (with a rooted Droid) and he'll understand whats wrong haha. I've got a headache now. Is there any other way I can fix it??

Again, thanks for all your help!!

 

[Fabolous]

I'm out of ideas, sorry

I think if it was a software issue, the .sbf would have fixed it.

It's good that you got an inside man at VZW though. Replacing it is probably the best way to go.

 

[peenapple390]

Got it replaced, the replacement should be here by Thursday...

 

[peenapple390]

So, I just rooted my refurbished Droid and went through the Nandroid restore method and had ZERO issues.

I'm convinced that my phone was a one-in-a-million defect.

I'm happy now, its all working!

Thank you so much for taking time to help me, Fabo!