[RECOVERY] j_r0dd-mb300-v2.0 (2.7.11)

[xhepera]

Okay, I hate to be a pest, but I'm stumped. I flashed 1.8.1 recovery, did a wipe and reflashed the 1.3 ROM. My phone boots to the Motorola logo screen, briefly goes black (for a few seconds), shows the Motorola logo screen again, then just sits there indefinitely. I have a fresh backup, so I'm not freaked at this point. What might be the problem here though? Anyone have any ideas? Thanks!

[devman1]

I am having the same problem xhepera. Any help would be great!

[j_r0dd]

Okay, I hate to be a pest, but I'm stumped. I flashed 1.8.1 recovery, did a wipe and reflashed the 1.3 ROM. My phone boots to the Motorola logo screen, briefly goes black (for a few seconds), shows the Motorola logo screen again, then just sits there indefinitely. I have a fresh backup, so I'm not freaked at this point. What might be the problem here though? Anyone have any ideas? Thanks!

Did you do a full wipe?

Sent from my SGH-T959 using Tapatalk

[xhepera]

Did you do a full wipe?

Yes. The first time I only did a wipe of the data, cache and Dalvik cache. Subsequent attempts I used the Wipe All option.

[j_r0dd]

Yes. The first time I only did a wipe of the data, cache and Dalvik cache. Subsequent attempts I used the Wipe All option.

Try pulling your sd and see if it boots. If so, just repartition the sd

Sent from my SGH-T959 using Tapatalk

[xhepera]

Try pulling your sd and see if it boots. If so, just repartition the sd

Well, I seem to have somehow or other really hosed it. I pulled the sd and that was a no-go. I copied the backup to the card, put it back in, booted into recovery and did a restore of the nandroid backup. Still a no-go. Is the phone a goner, do you think?

[j_r0dd]

Well, I seem to have somehow or other really hosed it. I pulled the sd and that was a no-go. I copied the backup to the card, put it back in, booted into recovery and did a restore of the nandroid backup. Still a no-go. Is the phone a goner, do you think?

no it's not. If you can get into recovery you can recover for sure. do you have an att backflip?

Sent from my SGH-T959 using Tapatalk

[xhepera]

no it's not. If you can get into recovery you can recover for sure. do you have an att backflip?

Yes, it's an ATT.

[j_r0dd]

Yes, it's an ATT.

Why don't you flash the latest sbf then?

Sent from my SGH-T959 using Tapatalk

[xhepera]

Why don't you flash the latest sbf then?

I'll give that a try. I noticed something, by the way. . .not sure if it's relevant or not, but shouldn't the wipe all remove the partitions and everything else on the sd? Since I use Ubuntu I have to put the sd in a usb reader to copy the 1.3 zip onto it (the usb-ms toggle doesn't seem to work in Ubuntu). The 1.3 zip and the partitions are still in place when I view view the sd. Shouldn't they be gone?

Anyway, I'm off to research flashing the sbf.

[Unicorn9x]

I'll give that a try. I noticed something, by the way. . .not sure if it's relevant or not, but shouldn't the wipe all remove the partitions and everything else on the sd? Since I use Ubuntu I have to put the sd in a usb reader to copy the 1.3 zip onto it (the usb-ms toggle doesn't seem to work in Ubuntu). The 1.3 zip and the partitions are still in place when I view view the sd. Shouldn't they be gone?

Anyway, I'm off to research flashing the sbf.

wipe all just remove the internal memory, to remove the partitions and everything else on the sd u have to use partition sd in recovery

[dy_user]

It looks like people have had a lot of trouble with these last releases of the recovery. I myself have had issues with "sitting at the M". Just a shot in the dark but do you think it has to do with the implementation of an adb shell in recovery?

[j_r0dd]

It looks like people have had a lot of trouble with these last releases of the recovery. I myself have had issues with "sitting at the M". Just a shot in the dark but do you think it has to do with the implementation of an adb shell in recovery?

Not at all. Nobody should have issues with this recovery. the recovery is only loaded when you are booted into it. It would not play a part in the normal boot process. If you are having trouble booting then it might be because something that was flashed. Prime example is the OC kernel.

Sent from my SGH-T959 using Tapatalk

[xhepera]

Thanks for the advice, help and guidance folks. I decided to try one more time before attempting to flash the sbf, and for some reason or other it worked this time. Restoring my Titanium backed up apps right now. Perhaps the fresh flash will alleviate the serial reboots. ;-)

[dy_user]

Not at all. Nobody should have issues with this recovery. the recovery is only loaded when you are booted into it. It would not play a part in the normal boot process. If you are having trouble booting then it might be because something that was flashed. Prime example is the OC kernel.

Sent from my SGH-T959 using Tapatalk

The only reason I would think this is that you are mounting more than the recovery portion when you boot into the recovery and everytime I have tested it with a full wipe mind you i have had the stuck at M problem. If i do the same process with 1.7 I have no problems. When try to do a logcat when i am stuck at the M I get an error that says something like command not found I know it's vague but I don't really want to take the time to recreate the error. Again I love what you are doing and thank you and any contributer whole heartedly. I am not complaining but what i have seen more and more of is blames being put on not doing full wipes when that not could the issue be something else.