[Q] Bad ROM install, alternative methods to fix? [SOLVED]
My brother has been having problems with his Google Play store (force closing, etc) as well as some other Google services. He wasn't even able to actually load Play Store and browse, so to fix his problem I decided the best route would be to start clean and do a factory reset. This worked well, for about 2-3 hours until he told me he wanted me to put the Google Edition 4.3 JB ROM on his phone. (He's a hipster, trololol)
So I looked up the thread of the AOSP Google Edition 4.3
JB for his GT-I9505. Having flashed my Galaxy S3 many times with UltimaROM and various other ROMs, I figured his S4 wouldn't be much different to any of the other Galaxy devices we've had in the past. So I download TWRP, and also rooted his phone via Motochopper. Once I installed TWRP I hit wipe and wiped the data and dalvik cache. Then I installed the ROM. Few moments later and we reboot the phone.
Phone decides to go into a boot loop, so I go back into TWRP and wipe again like I would with my Galaxy S3, but still getting a boot loop.
I really should have made a back-up of his original stock ROM (I made a boo-boo, I know
) but I figured he had nothing to lose. The problem now is that I can't flash any other ROMs because normally I would just transfer the .zip's onto the phone and then install from there. He doesn't have an SD card either, and mines doesn't work anymore (water damage...).
So my question is, what other ways can I transfer .zip's onto his phone so we can flash another ROM and not let his phone be a huge expensive paper weight.
I know about ADB and I downloaded the ADT Bundle from Google's site, but I have no idea how to execute adb or fastboot. They open cmd but then immediately shutdown again after a flash of a wall of text.
I'm able to access recovery & download modes fine. I've tried "mount" but when it mounts the S4, Windows doesn't pick up on it like it would if I were to do MTP otherwise I'd be able to transfer files no problem.