Root Am I screwed?

[BATMAN123]

Yeah, I put in the battery back in and hold the power button and up on the d-pad for about 10 seconds.

 

[johnlgalt]

Nah, Try it this way.

Pull battery.
Make sure phone is not connected to a charger.
Put battery back in
press and hold up on D-Pad
press power button
wait 2 seconds
let go

 

[johnlgalt]

Loading the bootloader is very fast, not like recovery of the OS....

 

[BATMAN123]

So I'm holding it too long?

 

[johnlgalt]

maybe - I'm wondering if holding the power button that long and / or the D-Pad that long is causing it to reboot again or something else....

 

[BATMAN123]

I just noticed that under device information Everything is N/A or a bunch of zeros. I know that's not normal.

 

[johnlgalt]

definitely not.

However, if you were not in the bootloader, you should not even be seeing anything there at all.

So, looks like it is hosed for good now lol. Good thing you're already having it replaced.

 

[BATMAN123]

So.... I really screwed it up?

 

[johnlgalt]

Here is what I see:

And I timed it - when powering on it was literally less than 2 seconds before the bootloader screen was up.

Finally, no, I don't think you screwed it up - something happened, but you're like the third poster I have seen talking about blank screens in the last day....

 

[BATMAN123]

ok, I removed battery and tried to go into bootloader again and I see that.

That's really weird about everyone getting blank screens.

 

[johnlgalt]

OK, then you should be able to do it - did you download the right file?

Try downloading a different file (use the 2.0 stock to really pi...er, make them scratch their heads lol...)

 

[BATMAN123]

I'm using VZW_A855_ESD56_QSC6085BP_C_01.3E.01P_SW_UPDATE_03.sbf But I will try a different file

 

[johnlgalt]

If it is failing that fast, then your download may have been corrupt. I was thinking that it was not making it into the bootloader since we could not visually confirm it - but if you're seeing what I am seeing in the RSDLite program, then it is definitely making it into the bootloader.

Therefore, your phone is in bootloader (check) and RSDLite is working (check) - so it has to be the file.

 

[BATMAN123]

I downloaded a new file and the start button is not lighting up. This is rather annoying.

 

[BATMAN123]

And now the phone is no longer showing up in RSDLite.... I quit.

 

[breadnatty08]

And now the phone is no longer showing up in RSDLite.... I quit.

Yep, bedtime for you

 

[BATMAN123]

Ok, So I am trying again and I have downloaded a couple of different .sbf's and they all fail almost instantly.

 

[BATMAN123]

Ok, I decided to try using the 2.2 .sbf file. and it worked. I tried the 2.1 and 2.0.1 and neither of them worked, even though I tried multiple different files of each. And 2.2 .sbf works first time!!

 

[johnlgalt]

2.2 SBF? didn't know there was such an animal....

/me runs off to look

 

[BATMAN123]

FRG01B .SBF to Unroot to 2.2 instead of 2.0.1 - Droid Forum - Verizon Droid & the Motorola Droid Forum

Right here

 

[johnlgalt]

hmmm - that SBF is actually a 2.1 SBF that you push onto your phone.

 

[BATMAN123]

Is it? Well, whatever it is, it seems to be working. It has been on 99% for a while now though


Edit: Ok, it said failed lashing process, then RSDLite stopped responding. But my phone rebooted because I can see the notification light blinking.

 

[johnlgalt]

The phone should have rebooted already right?

If so, then at this point you can close out RSDLite and ignore the warning about it 'failing'.

 

[BATMAN123]

So I'm good??

 

[johnlgalt]

No, I am wrong - the actual file linked *is* the 2.2 SBF - for FRG01B.

This has an added benefit in that you start out with a clean ROM, and have to activate and reinstall all your apps - which is what I am trying to get folks who use the update method to do anyway lol.