• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Virgin Mobile/Sprint] Stuck in fastboot or recovery mode

E

etechgeek24

Newbie
I rebooted my F3 today and it brought me into fastboot mode for some reason...

It showed
Fastboot mode started
udc_start()

Connecting it to my PC (which has fastboot/adb on it) adds:
-- reset --
-- portchange --
-- reset --
-- portchange --
fastboot: processing commands

onto the phone screen, and shows up on the pc's fastboot devices as:
0123456789ABCDEF fastboot

Rebooting brings it back to the fastboot mode, and doing fastboot continue shows this repeatedly on the phone:

Error No.2: Failure sending read command to the Card(RCA:2)

followed by:

Error No.2: Failure setting read block count for Card (RCA:)
ERROR: Cannot read boot image header

Please help! I am rooted and have access to the factory recovery but not a custom one like CWM...
 
I would love to know what you did to receive fastboot mode. I've been trying to get access to fastboot mode for a while now.

Did you do anything to cause it to appear? Did you make any changes or install anything recently or drop it in water?

It looks like your boot.img is corrupt. To get out of fastboot mode you will have to flash a boot.img or system.img file. I'm assuming you would need a new boot.img.

Inside the Psycho Billy cm flavored rom there's a boot.img file. Use that to reflash your boot img

To do that, copy the boot.img file to where your adb & fastboot is located that you used to connect via fastboot.

in the terminal type the following minus the ' $ ':
$ fastboot flash boot boot.img

That should flash the boot.img to your phone.

If your using linux you may have to use sudo and add a ' ./ ' before the fastboot command.

Before you flash the boot.img, I would appreciate it if you could make a copy of your current boot.img with adb shell, and pull it from your phone using adb pull.

If you need more information let me know.

This may not work. I'm just assuming this is how it would need to be fixed.

You may need to return it to VM.
 
The most recent major change I made related to flashing was flashing the unbrick ROM (from the sticky on the All Things Root board) when I had this problem: http://androidforums.com/lg-optimus...ly-process-com-android-phone-has-stopped.html

I'm all good with grabbing the image, although I don't know how to use ADB since I can only use FastBoot mode and Android System Recovery <3E>. The device doesn't appear for either of them. I use Linux, so drivers shouldn't matter...
 
That was my fault. I assumed you could use adb.Just flash the boot.img with fastboot if you can.

If you can get into the <3E> recovery, you should be able to get into download mode. Why not just run the unbrick method again?
 
Run this command in the terminal where fastboot would be on your computer:

$ fastboot oem unlock

You should get a prompt asking if you want to unlock the bootloader. Select yes
This will wipe your data. If you can unlock the bootloader you would be able to do something none of us could do.
 
No. It has nothing to do with cwm.

After talking to PlayfullGod, we're both pretty sure it's a corrupted aboot image. (bootloader) and not the boot image. Run the Unbrick method again. I'm assuming you can get into download mode since you said you can get into the stock <3e> recovery.

If you can't then you'll need to have an aboot image provided to you.
 
LG-F180
Also known as LG Optimus G E973, LG Optimus G E971, LG Optimus G E975
how to fix any solution
fastboot mode started
udc_start()
-- reset --
--portchange --
 
So, I was trying to put ubuntu on this ms659, and to do so required access to fastboot mode. I couldn't get to the bootloader, due to it seeming to be locked, despite being able to get TWRP and custom roms on the phone. In a blind noob attempt to get what I had working, I attempted to use flashify to flash the ubuntu core image as a boot image, and it dropped me into this mode. The only zip I had with a boot img in it was a cm that I haven't been able to flash, and when I used fastboot to push that boot.img to the phone, it dropped me at a LG screen that seems frozen. From there I can still get to download mode, so re-flashing a kdz is no problem, but I was unable to repair it manually with fastboot.

Apparently, the ubuntu-device-flash checks the device, and only flashes it with an image made for that device, so I think I'll have to either learn to port it, or find a nexus.
 
fyi, all of the boot images you find on here have been loki'd or bumped. Modified to bypass the locked bootloader. If it has a .lok extention, it's been loki'd. if it's got a .img extention, it's been bumped. Also, there is a old thread on here on the virgin mobile side where someone put together a package to enable fastboot mode. Basically all that was required was to remove the boot image.

I'm pretty sure you could of recovered your device using fastboot but you needed the correct files. You would need a good system.img, boot.lok, and aboot.img.

That's a good start, and i'm glad someone's attempting to get ubuntu on this phone. :)
 
You must log in or register to reply here.
Back
Top Bottom