Help Broken Bootloader Not Connecting Properly?

[Thedarkness523]

Hi everyone,
So recently I got one of the cheap RCA Voyager II tablets and I decided it might be fun to root it. I used KingRoot for my device however this did not work well... The tablet got stuck in a bootloop and Kingroot was at about 43% so i tried using the RESET button on the back and that just made it worse. The tablet is now stuck at a black screen in Bootloader mode and when I try to connect it to the PC, Its found but then disconnects after 3-7 seconds. I cannot seem to get into recovery and I have files to fix it. Fastboot sits at "<waiting for device>" and ADB cant see anything. Is this a driver issue? Or have I just fried a tablet?
Please help!

 

[Bg260]

Do you have ADB/Fastboot installed on your computer? Make sure to install it system wide when prompted.
Also what operating system do you have on your PC?

 

[Thedarkness523]

Yes i have ADB and Fastboot, all with admin access and Windows 7 Ent.

 

[lvt]

Did you enable the USB debugging option on your device?

 

[Thedarkness523]

I cant. Its stuck in bootloader mode.

 

[lvt]

If you didn't enable USB debugging prior to the rooting, there is chance that your PC won't see your device.

 

[Thedarkness523]

I did before rooting it.

 

[lvt]

I did before rooting it.

Good to know, so maybe you should check your computer's USB drivers. Some phones need a specific drivers rather than windows's generic drivers.

 

[Thedarkness523]

I have. I tried 1 OS, Linux. It was a bare install with ADB and Fastboot. That didnt find any devices. I know the cable is good because my phone worked fine with it. The this, Windows. Both dont work.

 

[iowabowtech]

I have. I tried 1 OS, Linux. It was a bare install with ADB and Fastboot. That didnt find any devices. I know the cable is good because my phone worked fine with it. The this, Windows. Both dont work.

If it wasn't found with linux, you're not likely to have a good working solution. You say you have the files to fix in the OP so I'll assume you have a "revert to stock" file that works on that device, likely requiring the stock recovery to apply? If so, the only option is to find a button combination that would boot you into the stock recovery which may not be possible depending on what the Kingroot did to your tab. Most likely it overwrote the primary bootloader which is why you're now in your current position.

If you have any information to offset that, then perhaps there's a chance. Honestly, it doesn't sound good. Cheap, lesser supported devices are difficult to revive because proprietary tools and/or files often don't exist.