[reidoreilly]

skynet11, on 08 January 2013 - 04:24 AM, said:

When he first flashed CWM, he hadn't had a ROM on his SD card that he could flash, thus his recovery screen is all he could boot to.

yeah, I understand that, but ive done the same thing too. I don't know how capable cwm is for adb, but when I did it I was able to flash twrp through fastboot, then go into recovery and push a rom through the adb sideload command. I don't know if you can push a rom through fastboot or not, but using the sideload push command through twrp was easiest for me. I was just wondering why he couldn't do the same

Edited by reidoreilly, 08 January 2013 - 11:46 PM.

[slvrdrgn123]

His problem was that the computer wasn't reconizing the phone through adb for him to push the rom to.

[prestie]

Try flashing an insecure boot image from fastboot then try pushing a rom through adb. Since the DNA is still s-on, you have to flash an insecure boot image before you flash any rom or you end up stuck in your recovery.

Edited by prestie, 11 January 2013 - 09:32 AM.

[DroidModderX]

My phone is stuck in recovery and I am not able to boot into fastboot. I think it is because my battery is dead. If i plug the phone up it goes straight to recovery. Will it charge in recovery if i leave it there? I think if i can get to fastboot i can flash an insecure boot.img and it will load its just a matter of getting there from cwm recover. Any suggestions

[skynet11]

Yes, it'll charge while in recovery, but I don't think that's your problem. Does your PC recognize your phone when connected?

[DroidModderX]

yes. If i type "adb devices" it list the device as "FA2B9S500933 recovery"

[DroidModderX]

Skynet11 any thoughts?

Nevermind I let it charge a while then i was able to boot to fastboot and flash an insecure boot.img Thanks anyhow bro!