Android Logo and Exclamation mark on boot

[BHuber09]

Okay that a really weird then. Were you rooted or romed?

Sent from my Galaxy Nexus using Tapatalk 2

[Ads]

[blahberrys]

Okay that a really weird then. Were you rooted or romed?

Sent from my Galaxy Nexus using Tapatalk 2

Rooted and running liberty 3 I believe. Also update: Tried to sbf 'Android 2.3.4 System Version 4.5.621' Am I just completelyed screwed now?


Edit: Plugged into charge now just goes to 'recovery' again.

[Nemo aeternamn]

Try sbfing to 605?

Did anything happen the day this started our the days preceding this

Sent from my Galaxy Nexus using Droid X Forums

[BHuber09]

Try sbfing to 605?

Did anything happen the day this started our the days preceding this

Sent from my Galaxy Nexus using Droid X Forums

That was a did you go to 621 then try and go back to 605 question?


But my suggestion would be to sbf it again. But to 621 since that's what you're on

Sent from my Galaxy Nexus using Tapatalk 2

[blahberrys]

That was a did you go to 621 then try and go back to 605 question?


But my suggestion would be to sbf it again. But to 621 since that's what you're on

Sent from my Galaxy Nexus using Tapatalk 2

I've tried to sbf 3 times..

[newmanx4]

How are you performing the SBF? RSD Lite?

Sent from my Liquid X

[blahberrys]

How are you performing the SBF? RSD Lite?<br>
<br>
Sent from my Liquid X

Yes, why?

[newmanx4]

After the SBF in RSD you have to do a factory reset for the phone to boot. At the screen with the triangle and ! you press both volume keys simultaneously to open stock recovery. If your keys don't work then unfortunately you might be dead in the water.

And since you've done a .621 SBF that is now the ONLY one you can use.

Sent from my Liquid X

[Goose306]

You can also try the .604 SBF, isn't stuck using .621, is only stuck with .621 if done via RSD Lite and/or cares about their baseband (far as we know this is a WIFI-only device)

Also, if you insist on using RSD Lite, its a super-finicky sucker.

Make sure you get the Moto Helper utilities to get the right drivers.

Make sure you are using the OEM cable (or similar cable of equitable high quality - I have only had success SBF'ing with OEM or Mediabridge cables, both are very high quality USB cables, and OEM is the only one that is really guaranteed to work 100% of the time - assuming the cable isn't damaged.)

Make sure you are using a USB port plugged directly to the motherboard (not a hub, not an unpowered port, not on a monitor... etc)

Make sure it is USB 2.0 port (not 1.1, not 3.0)

What version of RSD Lite are you on? I have been using v5.6.4 lately (the latest I believe) and it is stable with the .621 SBF.

What is your Windows version? Some have different requirements for .621.

Finally the Linux method (natively using sbf_flash in Linux or one of the 1KDS isos) seems to have less compatibility issues (read: can skip over most of that junk I wrote above, besides the high-quality USB part and 2.0 and non-hub part) You can try booting off the .604 1KDS disc and give it a burn/flash see what comes out the other end. There is no harm in doing that, just make sure its done in Linux natively or on the 1KDS live disc (so it doesn't screw with the radio, assuming this is an activated device). Make sure you do the factory reset as listed by NewmanX above as well.

[blahberrys]

You can also try the .604 SBF, isn't stuck using .621, is only stuck with .621 if done via RSD Lite and/or cares about their baseband (far as we know this is a WIFI-only device)

Also, if you insist on using RSD Lite, its a super-finicky sucker.

Make sure you get the Moto Helper utilities to get the right drivers.

Make sure you are using the OEM cable (or similar cable of equitable high quality - I have only had success SBF'ing with OEM or Mediabridge cables, both are very high quality USB cables, and OEM is the only one that is really guaranteed to work 100% of the time - assuming the cable isn't damaged.)

Make sure you are using a USB port plugged directly to the motherboard (not a hub, not an unpowered port, not on a monitor... etc)

Make sure it is USB 2.0 port (not 1.1, not 3.0)

What version of RSD Lite are you on? I have been using v5.6.4 lately (the latest I believe) and it is stable with the .621 SBF.

What is your Windows version? Some have different requirements for .621.

Finally the Linux method (natively using sbf_flash in Linux or one of the 1KDS isos) seems to have less compatibility issues (read: can skip over most of that junk I wrote above, besides the high-quality USB part and 2.0 and non-hub part) You can try booting off the .604 1KDS disc and give it a burn/flash see what comes out the other end. There is no harm in doing that, just make sure its done in Linux natively or on the 1KDS live disc (so it doesn't screw with the radio, assuming this is an activated device). Make sure you do the factory reset as listed by NewmanX above as well.

I honestly don't know what most of this means. But is there a different method then SBFing with RSD lite?