yashsingh1/xdaforums huggingface dataset:
[Android General] nannycrick:
There's no "visible" signs of life in it but my PC, running Win10 32 bit, "sees" it as a MTK USB device. I here a connection sound from the PC. I does charge but with no visible icon. Can't get boot logo, recovery, or fastboot menu. It was rooted with Kingroot. Tried to flash twrp recovery using Flashify. It bricked. I sent it back to RCA running 4.4.2. When I got it back, it was running 4.4.4. Weird! I rooted it with Kingroot again, and tried to flash twrp again. It bricked. I tried to reflash the scatter backup I had made, but SP Flash Tool & MTK Droid Tools wouldn't flash. I get..."Brom errors 5054 & 4032" from my attempts. I have the MTK USB device both on VCOM port 9. Still no life in this tablet after six months of trying. I opened the back up to check on what chipset I actually had...they're MTK8127 for sure. I can even feel vibration as it's hooked up to my PC. Don't get it. It should have flashed the scatter and rebooted. I'm stumped! There are tons of folks in my boat with me. So far, no way of fixing our bricks!
[Android General] saliltripathi:
help help help

drivers are not working on rca vinking 10,1 pro plz plz pplz:crying: tell me how to install it i tablet is bricked

reply fast
[Android General] Super_Hurf:
HI

Good
[Android General] NepoRood:
Everything you need is in the OP, click here and read carefully...
[Android General] superchill02:
Quick question my tablet when plugged into my pc via microusb always says "unknown / unrecognized device" any solution to this?
[Android General] smartmanvartan:
Completely normal. RCA didn't want you to connect it to a computer cause they suck . there is no driver that lets you connect for adb, mtp, USB Mass.... I have never been able to use the micro USB for anything other than charging.
[Android General] superchill02:
Does that mean I need to buy a normal USB to USB to so this?
[Android General] smartmanvartan:
Yup :)

I made mine with adapters if that helps...
[Android General] superchill02:
Ok thank you so much I'll probably just stop at Walmart or best buy really quick to get one.
[Android General] :
What are the benefits of adding the firmware listed in the OP compared to simply using the firmware the device ships with? Nothing in the OP described any features of the firmware itself.
[Android General] NepoRood:
None really, the main reason it's there is because there are so many different versions of this tablet it's ridiculous. We tried to find all the firmware we could, so, it ended up in the OP.

However, running the Surf firmware is kinda neat, lol (removes the 2 dogs at startup)

Regards,

Nepo
[Android General] :
Thank you for the clarification. Does this mean that I could simply root the tablet and not install this firmware?
[Android General] NepoRood:
Yes it does. Although, if you want a custom recovery or an unlocked bootloader, you'll need a firmware. Otherwise, please note: Follow the directions in the OP for rooting, and do not, under any circumstance, use that supersume app from the play store.
[Android General] mimiddru:
Need help with bricked x.10.x.

I've followed the instructions in the op to the best of my ability but when I try to flash the stock firmware, I get a brom error 4032. I've been reading and re-reading this thread for a few months now and I'm having a hard time following specific instructions for x.10.x. as the firmware looks like it was compiled through trial and error. This all started when I tried the king root/supersume thing way back when. Is there any way I can verify whether or not I've installed the preloader properly? At this point, I got nothing. I was able to boot into recovery mode but now I can't even power up to the original boot loop that started all this. When I look under Device Manager, it's still listed as mtk device so I guess there's still hope?

Thanks
[Android General] NepoRood:
Tough nut to crack, without having original firmware (or at least something close) If I had a working x.10.x, I could probably build something compatible for everyone else. Unfortunately, I do not :(

Best of luck, and hopefully a solution will be found in the future...

Regards,

Nepo
[Android General] mimiddru:
Thanks for getting back to me.

I was under the impression that the zip files I downloaded (namely x.10.x_firmware and 1.10.31) were original firmware that was sort of, pieced together, from files that were sent in by owners of working x.10.xs. Is this not the case? Cuz if it isn't, I should probably lay off before I make things worse, if that's even possible. Also, I thought I read something about flashing x.12.x firmware on an x.10.x tablet but maybe I dreamed it. :confused:
[Android General] NepoRood:
Only full versions of firmware currently available are for the x12x (aka V12) and the x9x (aka V9). and all are on the first page of this thread under the firmware section.

We tried to draw in some other V10 (aka x10x) users with working tablets, but only found one. And since that member hasn't posted anything in a while, it's possibly a lost cause.

And No, you probably shouldn't flash anything from when we were trying to build a working version for V10 users, it's very incomplete and could do more harm than good.

Sorry I can't be of more assistance at this time.

Nepo
[Android General] Ambrosias:
Why?

Why do you hope he doesn't have a x.10.x? I ask this because I am looking to develop for my wife's tablet which is one of those? Anything specific for that build version?
[Android General] smartmanvartan:
Maybe you could help, thru different places on the internet, official firmware was found for the other variations of the tablet. Some of the x.10.x users have bricked tablets that could be fixed with the firmware but a x.10.x hasn't been found yet. Subsequently, custom recovery hasn't been made either because a recovery image can't be pulled with dd command and the recovery kernel is different on the x.10.x.
[Android General] Michael33066:
Stuck in Boot Loop [SOLVED]

I was able to solve this problem the next day. Solution at bottom.

________________________________________________

Original Post:

First, thank you for the instructions in this thread. I used them to successfully root my RCT6303W87DK tablet, and it was working fine. (KingRoot, then replaced it with SuperSU.)

Unfortunately, I couldn't leave well enough alone, and then I did something which put the tablet into a boot loop. :( . . . I unlocked the boot loader (using post #3). Since the link to download TWRP is broken, I downloaded the TWRP recommended by the TWRP Manager app: twrp-2.8.5.1-k200.img

I should have followed the directions in post #4, but instead I used fastboot to flash TWRP: "fastboot flash recovery recovery.img". I don't know whether it was this or unlocking the bootloader that caused the problem.

Now, the tablet boots to the RCA splash screen with the dogs, flashes a white screen for several seconds, black screen, then starts all over. Even just plugging in either power cord causes it to start into the boot loop. The reset button stops the loop. ADB doesn't see the tablet. There's not enough time for the Windows Device Manager to install a driver. Holding down the power button and either volume direction has no effect.

I appreciate any insight you can provide. I'll only have the tablet until tomorrow: 8/7/2016. (I realize it's a long shot.)

________________________________________________

SOLUTION:

After trying all day to find some combination of buttons or ADB to get back into the tablet, I decided to try using the SP Flash tool. It worked!! :D That was the magic formula! I installed the new firmware again (post #3), which was probably still installed from before, and didn't fix the boot loop. Then, I installed the CWM recovery (post #4). And it worked!! It booted up like a champ. I realize now that flashing the wrong TWRP is what caused the boot loop.
[Android General] NepoRood:
There is no "Official" TWRP for this device, if you downloaded using Goo manager (or anything else), you flashed an incompatible recovery. I've only managed TWRP for the V9 versions (x.9.x firmware), if you don't have a V9, you'll need to install the CWM Non-touch recovery
[Android General] darkensx:
ok sorry for the major delay here is the lk.bin i believe its correct
[Android General] Qwzykx:
Hi Nepo,

I've got a brand new, unmodified x10x. If you (or anyone else) need anything from it, I'm more than willing to contribute.
[Android General] NepoRood:
That's cool, thanks for the offer. Take a minute (or 2) to read this

See if you can pull it off, if not no worries, but it'd be great if you could.

Regards,

Nepo
[Android General] Qwzykx:
I've read the instructions carefully and I should be able to pull it off. Just need to get my hands on a male to male USB cable. I've downloaded SPFT for Linux and ROM RCT6303W87DK-ANDROID5.0-V77-V1.12.50-EMMC-user-Kingston-V6.1_20160316. I will let you know when I've made some progress.

Edit: SPFT doesn't see the tablet at all in Linux. Will try in Windows 7 instead.

Edit 2: In Windows 7 right now and successfully installed VCOM driver, but SPFT gives S_COM_PORT_OPEN_FAIL (1013). Trying to solve this.
[Android General] nannycrick:
Hi Smartmanvartan....guess what I got on my work bench now....an rct6303w87dk just factory reset, running 5.0 build v63-v1.12.0. It's got wifi connection issues....wifi not working, or unstable connection. My HTC 626s on our local McD's wifi gets stable connection, but the Viking Pro has nothing. Everything else works. And ideas?
[Android General] smartmanvartan:
Try flashing a newer firmware in the same family or the surf 1001 firmware without the preloader and see if the error persists. May actually be hardware related too... Maybe the antenna was damaged or disconnected... Let me know how it worked out.
[Android General] nannycrick:
Can't flash using SPFT due to driver issue.... being no compatible x64 based Windows 10 driver in the CDC folder of the MTK_SP_Drivers.zip. I already have a W10 x64 VCOM driver installed & working for my MTK based Lenovo Tab2. I have a USB to USB sync cable plugged in from the Viking to the Toshiba W10 x64 laptop, and the micro usb cable to the power supply. Not able to install any driver that works or get usb sync. I also have usb debug enabled. Don't get this one!
[Android General] smartmanvartan:
Nothing USB related works on this tablet other than preloader mode. Tablet has to be off then you plug the male/ male USB cable then plug the power or micro USB cable. When you plug the power in is where the preloader mode activates.
[Android General] nannycrick:
Okay... I'll continue to try flashing that Surf1001 firmware. I hope it will fix the connectivity issues..

This baby's weird!! Grrrrr!

---------- Post added at 07:07 PM ---------- Previous post was at 06:39 PM ----------

I tried that. All I get is nothing...no loading or flash.

Went to Device manager. Got an error on Media Tek AT Port can not run. Check device manufacture for driver support.

Windows 10 doesn't support data transfer via usb to usb. Easy file transfer capability was taken out by Microsoft...which is why it took over six hour to hand transfer files,

via thumb drive, between my old pc and my new laptop. Six years worth of stuff!

Only usb to micro usb will work. Tried a usb otg cable connected to Belkin usb to usb. Nothing!
[Android General] Qwzykx:
I'm following your instructions in order to get to preloader mode but SPFT gives me error 1013 (most often) or 2005 (once in a while). I'm running Windows 7 x64 and VCOM driver is installed (COM7). SPFT runs in admin mode. Do you have an idea of why it's not working?
[Android General] smartmanvartan:
Try flashing the preloader only. But make sure you have the right one. After that you should be able to flash the whole firmware.
[Android General] Qwzykx:
Actually I'm trying to dump the ROM and get scatter file for x10x. I'm following this guide: http://xdaforums.com/showthread.php?t=2540400. I modified the scatter file as required but haven't been able to connect to the tablet. Sometimes I don't get any errors and the VCOM driver stays in the Device Manager window, which might be a good sign, but nothing happens. I've let it run for more than an hour in this state and there was no activity whatsoever.
[Android General] NepoRood:
You have both cables? Full male to male and micro? If so, with device turned off:

connect full cable, hit read back button, then plug in micro (or ac power cord)
[Android General] nannycrick:
Not getting anything. Get a chime when the usb male/usb male is connected to the computer, but nothing when micro usb male to power.

Frustrating!
[Android General] slaeyer:
First off, I want to say thanks to everybody's hard work on this thread.

I jumped the gun last night trying to remove kingroot and replace it with supersu using the supersume app (as I'd read on another thread) and soft-bricked my v12.x tablet. A quick google later and I landed here. I wish I'd started here to begin with, lol.

Thanks to everyone for compiling all this great info, I was able to successfully reflash the stock firmware, unlock my bootloader, install a custom recovery and remove the "recovery-from-boot.p" file.

Now I'm looking to take this further and install a custom rom but after reading 42 pages of forum posts, I see that all work in the past few months has been focused on the v10.x series. An admirable goal I'm sure and I wish you all the best in this regard.

Is there anybody working on a v12.x custom rom? I'd love to have Marshmallow installed so I can use adoptable storage with my 32 GB card.
[Android General] Qwzykx:
I've got male to male, micro and AC cord. Using either AC or micro to get into preloader gives the same result; read back either throws an error or just stays there doing nothing. I noticed, however, than plugging in micro results in having an unknown USB device. The VCOM driver won't install; it only installed on male to male. Don't know if it's relevant or if there's something I can do about it.

Edit: Clarity.
[Android General] nannycrick:
Same here...

I'm also getting the same "non flash" issue. I have the

W10 VCOM x64 driver already working on COM port 9

to support my Lenovo Tab2. I hooked up the cables as

in the directions, but I get nothing! The driver in the OP,

is it old or obsolete?
[Android General] nannycrick:
Well....still no communication between my new laptop & the Viking. Got it rooted & debloated using kingroot. I'll try flashing TWRP using Easy Magic TWRP Installer. It converts your stock recovery to twrp. It worked on the rct6203w46 and a Lenovo A8-5500F 8 inch tablet. Both didn't have working TWRP ports. I'll need to download the Universal USB driver. Hoping it works!
[Android General] smartmanvartan:
Magic won't work without adb. The drivers should work. I use them. Did you disable driver signature verification?
[Android General] nannycrick:
Yes...but I may have to use usbdeview to uninstall, then reinstall that driver. My laptop may be confused cause it's running that W10 VCOM driver for everything that I've plugged in so far. I may try to pickup a mini netbook running W7 to do diagnosis on Androids. It maybe a W10 thang!

Got a bricked Kindle Fire first gen cause the unbrick app I installed is too old to run

in W10. Old development stuff.

Yes... I'm trying to blame it on Microsoft... everyone else does!
[Android General] NepoRood:
Either of you try using just one cable? I know on the Maven Pro, the x.9.x version only needs one cable (the micro) while the x.12.x needs both, like the Viking x.12.x

I'm personally blaming RCA :good:
[Android General] nannycrick:
I've them one at a time, AND in tandem. No luck!
[Android General] darkensx:
on the Viking the micro usb is just a power input nothing more (because the ac cord is absurdly short.).. however it could be possible its disabled via hardware somehow seeing as tracfones have micro/mini usb ports that tend to be disabled and only allow charging
[Android General] Qwzykx:
I've tested all possibilities, nothing so far...

Have you tried replacing Kinguser with SuperSU? I soft bricked my previous x10x by trying to do so.
[Android General] nannycrick:
I think it's a Windows 10 thing. Microsoft took out Win10's ability to connect usb to usb for transfering data. The cable I've been using, the only usb to usb cord I have, is a Belkin Easy Transfer Cable. Maybe the Belkin isn't working because it's for Windows to Windows transfers. I'll try dusting off my Targus 4 port mini. Maybe that will work.
[Android General] NepoRood:
[MENTION=3679990]darkensx[/MENTION] how did you get the driver and SP Flash Tool to work for you?
[Android General] nannycrick:
Yes I did...successfully. Now to continue to try to flash a custom recovery to do more updates & a nandroid backup.

Here's a link to the version I used. Make sure you place the mrw file at the root of the internal memory.

http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

---------- Post added at 04:05 AM ---------- Previous post was at 03:58 AM ----------

Yes please! Let us know what version of Windows you're running, and is it x64 or x86?!
[Android General] NepoRood:
You can install a recovery using WiFi over ADB app from the Play Store. I've attached the x10x CWM recovery we made, in case anyone needs it.

EDIT:

This recovery is for x10x version of RCA firmware, DO NOT USE on any other version! (ie x12x or x9x)
[Android General] nannycrick:
Thanks TONS NepoRood! I'll take any working twrp or cwm I can get! I really hate to run without a full nandroid!
[Android General] nannycrick:
Okay.....bricked it now! Now the kid gloves come off!!! Downloaded all possible firmwares for my 12x....including the stock firmware I found on another xda forum.....

http://xdaforums.com/android/general/root-rct6303w87dk-5-0-lollipop-t3116016/page6

I'm looking for an older laptop with USB 2.0 ports. my BRAND NEW Toshiba Satellite C55 Core i3, has USB 3.0 ports. It doesn't read my older WD Passport 500GB external either!
[Android General] NepoRood:
You used the x10x recovery on a x12x tablet, didn't you? The reason I attached that recovery was because it's not in the OP and there's some x10x owners having trouble getting the drivers to work as well.

If you have any familiarity with Linux, you could try that route, or try to find a usb 3.0 to 2.0 hub...
[Android General] smartmanvartan:
Has anyone with a x.10.x tried the recoveries yet? I'll add them to the OP...
[Android General] NepoRood:
[MENTION=3679990]darkensx[/MENTION] has, we worked on it together. It was flashed with an unlocked bootloader, and AFAIK, it's still working...
[Android General] smartmanvartan:
The bootloader was already unlocked or patched?
[Android General] NepoRood:
Nope, if you have working root, there's no need to unlock the bootloader. It's the same on the Maven Pro (which is where I learned this). It'd been nice to know that a few months ago, yes? All the headache we had trying to get this thing unlocked, lol

EDIT:

Actually, upon reflection, you don't even have to have working root. Flash the recovery (or use ADB over WiFi), boot into recovery and flash SuperSu zip for root. I performed this procedure on 2 semi-bricked Maven's a member sent me and had no issues.
[Android General] smartmanvartan:
That's cool. Then I'll fix up the steps. That means you can do this without a pc. I'll fix up some new steps...
[Android General] Qwzykx:
That's exactly what I did, but SuperSU couldn't update it's binaries and upon reboot I never got past the Viking Pro logo.

I won't have access to my Viking Pro until Friday night, so I can't try anything right now... but if I understand correctly, by using ADB over Wifi I won't require root to flash the recovery image?
[Android General] nannycrick:
Okay.... figured my "brick" issue out.

It was so low that it went completely dead. I also hadn't noticed that "puppy teeth" had chewed into the cord. Changed change cables, and I'm back in business......duh huh!

Noob moment passed.....whew!
[Android General] NepoRood:
My bad for not really being clear on that. The best WiFi over ADB app requires root. There are some that don't, and you may be able to "push" the recovery, but most likely you will need to use the dd command (which requires ADB shell, aka root)

However, flashing the SuperSu zip, should allow you to replace King Root, though I haven't tested this...

Regards,

Nepo
[Android General] nannycrick:
Recovery....the update...

After I screwed up my recovery trying to use "flashing" app, I found one that worked...[root] raster_ flasher from Google Play. Downloaded the stock firmware, unzipped with Es File Explorer, then copied the recovery.img to 0/Raster/recoveries/stock. Closed ES File Explorer, and opened Raster. Went into Recovery from Storage, then followed the path leading to the recovery.img, and flashed. It asks if you want to reboot into recovery....yes. it goes right into my stock recovery! Not sure if's significant, but it worked to restore my recovery!
[Android General] Qwzykx:
Here's what I'm planning to do:

- Kingroot

- Backup stock recovery with FlashFire (just in case)

- Flash CWM with FlashFire (or ADB)

- Make full backup via CWM

- Attempt to flash SuperSU over Kingroot, either via CWM or FlashFire

I think it's the best course of action for now, but I'm no expert. If you have a better suggestion, I'm all ears :)
[Android General] NepoRood:
Sounds like a plan. I have a copy of x10x stock recovery though, if that matters/helps.

I've never had any luck with those "flashing" apps, but that's most likely on me.

Best of Luck,

Nepo
[Android General] Qwzykx:
Your copy of the stock recovery shall indeed be useful in the case that I screw up, but I should be OK. Do you think it would be better to flash CWM via ADB?
[Android General] NepoRood:
I think your best bet would be to root with King, then use adb shell to install recovery. Using dd command...
[Android General] darkensx:
yeah my tablet is still working also got Xposed framework installed as well :good:

btw nepo some posts back i attached the lk.bin in a zip container i think you asked for it if i remember correctly..
[Android General] Qwzykx:
FlashFire won't even get root access from Kingroot, so that option is out. Now trying to find the correct recovery partition... according to dumchar_info it's /dev/block/mmcblk0 but uboot, bootimg and others also use that. Checked some other threads for help but haven't found anything relevant. You got an idea of how I could determine the right recovery partition?
[Android General] NepoRood:
It's: /dev/recovery

---------- Post added at 11:54 AM ---------- Previous post was at 11:53 AM ----------

Yes, I have added it to my x10x folder :good:
[Android General] Qwzykx:
Thank you so much Nepo for all your help! CWM is flashed and I'm backing up my system right now. Once it's done I'll try my luck at flashing SuperSU.

Edit: After reboot, CWM was replaced by stock recovery. Should I have allowed CWM to "fix root" before rebooting? I said "No" just in case it would break something.
[Android General] NepoRood:
worth a shot, but, you should flash the CWM, and flash SuperSu before rebooting. Delete the recovery-from-boot.p file (<-- something like that, lol). It may be necessary to re-flash CWM again, but as long as that file is gone, you'll be ok :good:
[Android General] smartmanvartan:
Always say no to the fix root. It will break root.
[Android General] Qwzykx:
Alright, everything's good; CWM is there to stay and flashing SuperSU zip worked. Kinguser removed.

Is it true only for the Viking Pro or all devices?
[Android General] smartmanvartan:
Not all devices. Why is because the recovery version does not match the Android version SDK so the root is not the same.