[Verizon] [HELP] Everything's Broken!!

[andoird213]

Hi all,

So yesterday I compiled my own 4.2 build for toro. No problems there. When all was said and done, there weren't any real working Gapps packages (at that time, anyway) so I decided to take my chances and flash the leaked 4.2 one (which was reported not working) and see what happened. I was expecting it not to work, which is why I backed up in TiBu and in TWRP. All else fails, restore, right? So went ahead and did it, and as expected, force close galore on the Gapps till it went in to a bootloop. So disappointed, but still ok. So I go to boot in to recovery and restore my backup, and guess what isn't there... TWRP! Now stock recovery has somehow been installed. Ok...this sucks. BUT there's ADB! Adb pull my TiBu folder and my TWRP Backup and then restore to stock, install TWRP, push files, and all is dandy. So boot in to fastboot mode, and I get this lovely little thing! "Fastboot Command Read Error -2147483647" No commands work, adb or fastboot. So I have no custom recovery, no bootable ROM, and no adb or fastboot. Now I've gotten myself out of similar situations, but I only when I have a combination of two of the above not all 3. I see no doors, no options. They say Nexi are unbrickable...here's to that! Please someone help!!

 

[colchiro]

Install Wug's and return back to stock?

 

[andoird213]

Install Wug's and return back to stock?

That requires fast boot/adb to be working which it isn't

 

[iowabowtech]

That's a spooky conundrum. Is your phone recognized while plugged into the PC and in the bootloader? If so, what is the device called in that situation (in device manager)? Only thing I'm coming up with is to try and remove the bootloader interface drivers and attempt to reinstall them?

 

[iowabowtech]

Forgot to ask...have you attempted to access download mode? (power off, then volume down + power). Maybe you could use Odin to reflash stock? I'm no Odin expert so not much help here if that's the route of travel.

 

[andoird213]

That's a spooky conundrum. Is your phone recognized while plugged into the PC and in the bootloader? If so, what is the device called in that situation (in device manager)? Only thing I'm coming up with is to try and remove the bootloader interface drivers and attempt to reinstall them?

I'm actually on Linux (although I did try in a VBox)

 

[andoird213]

Forgot to ask...have you attempted to access download mode? (power off, then volume down + power). Maybe you could use Odin to reflash stock? I'm no Odin expert so not much help here if that's the route of travel.

Someone over at Rootz suggested that too...I'm really looking for some way to pull my backups first...to my PC first though...

 

[iowabowtech]

Someone over at Rootz suggested that too...I'm really looking for some way to pull my backups first...to my PC first though...

I can't see that happening without a booting phone or a custom recovery where you could adb pull.

Here's a crazy thought that most likely won't bear fruit...just thinking from the standpoint of any possibilities you DO still have at your disposal under the current scenario, how about going into the stock recovery, then press and hold volume up + power (I think that's right if memory serves) to access stock recovery options and see if there's an option to factory reset. Or wipe data/cache however it's listed. I don't know why that would help but I'm just grasping at the few straws remaining.

 

[andoird213]

I can't see that happening without a booting phone or a custom recovery where you could adb pull.

Here's a crazy thought that most likely won't bear fruit...just thinking from the standpoint of any possibilities you DO still have at your disposal under the current scenario, how about going into the stock recovery, then press and hold volume up + power (I think that's right if memory serves) to access stock recovery options and see if there's an option to factory reset. Or wipe data/cache however it's listed. I don't know why that would help but I'm just grasping at the few straws remaining.

No that won't work...and I tried anyway but the results were as predicted...and what I just released about ODIN...if my device isn't being read properly for fastboot or adb, won't it not be read properly for ODIN either?

 

[iowabowtech]

and what I just released about ODIN...if my device isn't being read properly for fastboot or adb, won't it not be read properly for ODIN either?

I think it still COULD be recognized in Odin mode. Because if I'm not mistaken, Odin mode utilizes the Samsung USB driver instead of the bootloader interface driver when using fastboot. So basically we are talking the same driver you already use when you could boot up normally and hooked into the PC. Only now you'll be in Odin mode and hooked into the PC. I can't say that with 100% confidence but I believe that to be the case which makes me think there's a chance. Fingers crossed.

 

[andoird213]

I think it still COULD be recognized in Odin mode. Because if I'm not mistaken, Odin mode utilizes the Samsung USB driver instead of the bootloader interface driver when using fastboot. So basically we are talking the same driver you already use when you could boot up normally and hooked into the PC. Only now you'll be in Odin mode and hooked into the PC. I can't say that with 100% confidence but I believe that to be the case which makes me think there's a chance. Fingers crossed.

Hmm...I guess I'll have to check it out