SBF to root and to unroot

[AlBundy]

In case it helps, I started with 2.1 Stock did the manual (full) 2.2 stock install. A few days later I installed the 2.1 SPRecovery sbf, and then flashed JRummy's 2.2 Rooted file. I just checked and currently have bootloader version 2C.7C.

Another thing I noticed is that the date modified of the nandroid backups do not correspond to the actual time it was made (e.g., a nandroid backup which was actually made around 4 pm has a date modified time stamp of 8:37 pm on the same date).

 

[TizzMahNizz]

trouble i think

flashed my system with the latest recovery only sprecovery sbf file..it wont work. i reboot into recovery mode and it is the default recovery. What should I do? i did a full back up of my apps..have wiped my data a few times trying to load a few roms...If i could get a couple suggestions it would help..i gotta leave but I'll be back later tonite any help would be amazing

 

[christim]

flashed my system with the latest recovery only sprecovery sbf file..it wont work. i reboot into recovery mode and it is the default recovery. What should I do? i did a full back up of my apps..have wiped my data a few times trying to load a few roms...If i could get a couple suggestions it would help..i gotta leave but I'll be back later tonite any help would be amazing

Back a couple of posts should be your solution. flash the 2.01 stock sbf, then flash the sprecovery file. then install the rom of your choice. Then, please let us know how you made out.

 

[MotoCache1]

I have a 2C.7C phone in my hands now. Let's see if I can replicate this issue.

 

[MotoCache1]

OK. I have good news. The issue is the either the 2C.7C boot loader that the 2.2 OTA puts on, something in the 2.2 OTA build, or the two working in combination. I was able to duplicate the problem. Whatever it is appears to be smart and keeps a copy of the correct boot loader. If it notices that you've changed it, it changes it back for you. How helpful. This does not happen if you have the 2C.6C bootloader.

OK, so now that I have "isolated the fault domain" so to speak, I'm going to see what it takes to fix it. I have a commitment tonight so if the resolution comes tonight it will be late. Be sure to check back tomorrow for an update.

The good news is it's not my SBF.

 

[skylordusa1]

OK. I have good news. The issue is the 2C.7C boot loader that the 2.2 OTA puts on. I was able to duplicate the problem. The 2C.7C boot loader appears to be smart and keeps a copy of the correct boot loader. If it notices that you've changed it, it changes it back for you. How helpful. This does not happen if you have the 2C.6C bootloader.

OK, so now that I have "isolated the fault domain" so to speak, I'm going to see what it takes to fix it. I have a commitment tonight so if the resolution comes tonight it will be late. Be sure to check back tomorrow for an update.

The good news is it's not my SBF.

Oh man good job man. I have faith that you will figure this out for us cause you rock. I am going to be refreshing my screen every 3 minutes until tomorrow hahahahahah just kidding. Great work man way to stay on it. Also thanks again for all the help you have provided so far.

 

[Tallica]

OK. I have good news. The issue is the 2C.7C boot loader that the 2.2 OTA puts on. I was able to duplicate the problem. The 2C.7C boot loader appears to be smart and keeps a copy of the correct boot loader. If it notices that you've changed it, it changes it back for you. How helpful. This does not happen if you have the 2C.6C bootloader.

OK, so now that I have "isolated the fault domain" so to speak, I'm going to see what it takes to fix it. I have a commitment tonight so if the resolution comes tonight it will be late. Be sure to check back tomorrow for an update.

The good news is it's not my SBF.

Knew it was only a matter of time for you to isolate the problem, and i'm sure it's only a matter of time before you have a fix.

Great job Moto!

Sent from a long time ago, in a galaxy far, far away

 

[MotoCache1]

I really should have left for my evening commitment by now but there's no way I could do anything else if I didn't at least try a couple more things.

The good news is I was able to fix it and make the phone let me put on whatever recovery I want, and not have it disappear -- without having to try to downgrade the bootloader to 2C.6C (because who knows if the phone will even allow that).

I have to split for now -- but everything is OK. It's funny -- I don't think anybody knows about this because I don't think anybody has been trying to flash things onto the 2.2 OTA yet. Now that I know I can fix it, I want to break it again by reapplying the OTA and turning that evil feature back on. I think I know where it is going to stash the backup copy of the recovery image. If so, I can make it do my bidding. Would be a nice feature to have it automatically replace SPRecovery if it got corrupted eh?

OK, gotta split for now. More later.

 

[AlBundy]

So..question... I had stock 2.2 and flashed the 2.1 SPRecovery onto it, and then flashed in 2.2 root. After that I got an nandroid 31 error (corrupt SD), when trying to make a nandroid backup. Fixed by formatting the SD in the Droid.

I've been flashing in various overclock kernals today, and I can make a nandroid backup right after flashing, but after I boot into the system and then go into SPRecovery to flash in another kernal, it failed most of the time (not being able to mount the SD). If I tried making a nandroid backup at that time, I'd get a error 31. I could then boot into the system, transfer the nandroid folder to my PC, reformat the SD and recopy the files back onto the SD, and everything worked normally (install a new kernal in SD Recovery).

Anyone else seeing this? Could it be caused by having the 2.1 SPRecovery on top of the 2.2 OS? Any suggestions to fix?

 

[skylordusa1]

I really should have left for my evening commitment by now but there's no way I could do anything else if I didn't at least try a couple more things.

The good news is I was able to fix it and make the phone let me put on whatever recovery I want, and not have it disappear -- without having to try to downgrade the bootloader to 2C.6C (because who knows if the phone will even allow that).

I have to split for now -- but everything is OK. It's funny -- I don't think anybody knows about this because I don't think anybody has been trying to flash things onto the 2.2 OTA yet. Now that I know I can fix it, I want to break it again by reapplying the OTA and turning that evil feature back on. I think I know where it is going to stash the backup copy of the recovery image. If so, I can make it do my bidding. Would be a nice feature to have it automatically replace SPRecovery if it got corrupted eh?

OK, gotta split for now. More later.

hahahhahahahhahha I knew you would fix it. I had faith ahhahahahhah. You da man.

 

[Tanknspank]

Motocache, if you can make it backup a recovery to that spot, I will love you forever. Would solve so many threads

 

[furbearingmammal]

Motocache, if you can make it backup a recovery to that spot, I will love you forever. Would solve so many threads

Tanknspank, are you thinking issues with ROM Manager, or am I the only one with that thought?

Also, Motocache, what he said +1 and +2. You are earning undying grattitude over here.

 

[Tallica]

Motocache, if you can make it backup a recovery to that spot, I will love you forever. Would solve so many threads

Tanknspank, are you thinking issues with ROM Manager, or am I the only one with that thought?

Also, Motocache, what he said +1 and +2. You are earning undying grattitude over here.

Custom Recovery wins!!

 

[zakany]

The good news is I was able to fix it and make the phone let me put on whatever recovery I want...

I'll be looking for that fix. Using an OTA stock 2.2 (FRG01B) and your naked SPRecovery (MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b), when I try to reboot into recovery (after the first time, which is successful) I get the triangle-exclamation icon, but nothing else. No text selections or anything.

 

[MotoCache1]

The good news is I was able to fix it and make the phone let me put on whatever recovery I want...

I'll be looking for that fix. Using an OTA stock 2.2 (FRG01B) and your naked SPRecovery (MC1_A855_1282081087_Recovery-Only_SPRecovery_0.99.3b), when I try to reboot into recovery (after the first time, which is successful) I get the triangle-exclamation icon, but nothing else. No text selections or anything.

Yep, that's the "stock recovery". If you want to actually see the menu you have to hold up on the volume key and then press the camera button (while holding up on the volume key).

Stock recovery is useless for anything but data wipes and installing signed update.zip files, so you probably don't have much reason to go look at it.