yashsingh1/xdaforums huggingface dataset:
[Android General] NepoRood:
Start and Length for Readback

These will be in the following order, file name to save, Start Hex and Length Hex:

preloader_RCT6303W87DK.bin | 0x0 | 0x1c3f0

MBR | 0x0 | 0x200

EBR1 | 0x80000 | 0x200

boot.img | 0x1d80000 | 0x451800

secro.img | 0x3d80000 | 0x21000

logo.bin | 0x4400000 | 0x1aa728

system.img | 0x5d00000 | 0x5ef451a8 (this one will take a bit, lol)

tz.img | 0x5100000 | 0xd9320

lk.bin | 0x1d20000 | 0x3ecc0

EDIT:

That should do for now, the cache.img and userdata.img may have some of your personal stuff in it, if we get the bootloader unlocked for you, all that will be erased anyway by a factory reset. We can grab them then, while they're still stock.

If you run into an error about it not matching correctly, make a note of it and move to the next one on the list, we'll then go back and try to correct the sizes ;)

---------- Post added at 03:20 PM ---------- Previous post was at 03:18 PM ----------

I don't recommend that, run the chance of bricking, just pick one, and flash the stock recovery only, see if that works
[Android General] motolio:
Well, I flash the entire x9x file, and BOOM! Im up and running! Thank everyone for your help.

One last question: is it possible to flash a x12x file in system update mode? or are these hardware specific?
[Android General] PhillMc:
Hardware specific.
[Android General] motolio:
Got it up and running with x9x ! Thank you!!!
[Android General] NepoRood:
Cool, you even get to install the TWRP 3 I built for that version :p
[Android General] PhillMc:
Male to Male USB cable

When I get around to flashing, what is the configuration of the Male to Male USB-A? To use ethernet terminology, should I wire it "straight-through" or "crossed-over"?
[Android General] darkensx:
Straight through (red to red, black to black, green to green, white to white) I've made a ton of Male to Male USB-A Cables by splicing Cables off old dead USB mice they work like a charm.
[Android General] motolio:
I got it to install via the instructions on this forum, but after it installed, It did a continous boot loop into twrp recover. It kept trying to flash something and said error: cannot mount data partition... or something like that. so I Splashed the original recovery back, booted up, and flashed your TWRP zip using Rashr recovery flasher from PlayStore while booted. Then it worked fine! The problem was probably on my end, so I dunno. (I probably should have rebooted after unlockingbootloader, which I did not)? Thank you for making the recovery!!!

BTW, I successfully flashed your recovery a few days ago with a LOCKED bootloader user Rashr, also.

Can I asked why TWRP is upside down on my end? Is there an easy fix?
[Android General] NepoRood:
Yes, you should have rebooted after unlocking the bootloader, that's what caused TWRP to boot loop. And what do you mean by "upside down", it's a tablet, it's supposed to be in "landscape" or "sideways" ;)
[Android General] motolio:
Haha. If it's connected to the keyboard, it's upside down. Same with the CWM recovery (which is actually more of a bother, because then the volume keys to make selections are inverted), which is why I'm using twrp.
[Android General] smartmanvartan:
That's weird.... What about when the system is running? The touch points line up?
[Android General] darkensx:
Uh quick question my tab wants to update to 1.10.31 currently on 1.10.30 what's my risks atm seeing as we have not unlocked bootloader or located firmware yet I'm wondering if I should update or stay on 1.10.30?
[Android General] smartmanvartan:
Golden opportunity!!! Are you rooted? Accept the download but don't install it. Navigate in to the cache folder and you should find the update package. It's a zip. Upload it for us.:). You can install it after but it deletes itself after installation. You will have to reroot after.
[Android General] NepoRood:
^^ What He Said! ^^

And Also: Hell yeah, even after all my work yesterday, lol, Hell Yeah!

---------- Post added at 10:49 AM ---------- Previous post was at 10:45 AM ----------

I never use the keyboard, heck, I don't even know where they are at the moment, lol. However, since TWRP 3.0.2 is out, I may be able to fix that for you, they improved quite a bit of functionality with the latest release a few days back, I'll build one later, and upload it for you to test out.
[Android General] PhillMc:
EXACTLY WHAT THEY SAID! If you can, upload that update -- it'll do more than half the work for them -- they could even (possibly) derive a replacement firmware from it.
[Android General] darkensx:
i'll do you all one better ;) Uploading the zip and....

BOOM! :highfive: The URL the firmware comes from: https://e85c70798a0424993593-a90fdba311566ad7f392b7b310119edc.ssl.cf1.rackcdn.com/1.10.31.zip

Zip: https://drive.google.com/open?id=0B9vvQTsCktPJU3hsVU9pR2VSN0E

---------- Post added at 01:54 PM ---------- Previous post was at 01:48 PM ----------

on a side note the size of the file is slightly more then 32MB seems may only be a partial update so i hope its useful unless rca has some really small full updates but there again we may not need full to do what we trying to atm.
[Android General] smartmanvartan:
I think we can work with this.. The bootloader and boot.img are in there. That's the big ticket items..
[Android General] PhillMc:
Was hoping simply applying this with stock recovery would at least get me booted -- Nope.

-- Install /sdcard/1.10.31.zip ...
Opening update package...
Installing update...
Verifying current system...
"/system/bin/install-recovery.sh" has unexpected contents.

Installation aborted.

Please continue to update your system !

Yay...

---------- Post added at 13:45 ---------- Previous post was at 13:35 ----------

Starting digging through the zip -- found "install-recovery.sh.p" -- doesn't look like a shell script to me -- the first 9 bytes of the file are "BSDIFF403"; possibly a difference file for a patch system.

It's likely you already know this, but I prefer not to assume.

---------- Post added at 13:50 ---------- Previous post was at 13:45 ----------

Ah -- I see; It's Python -- binary difference and patch file. Yeah; you already knew it. lol
[Android General] smartmanvartan:
You know what you should try, just to get it up and running, try flashing the system from a x.12.x firmware. Only the system partition. Should work from what I can see. The only thing is that the system will overwrite the recovery partition with a non functional one for your tablet however the boot.img you already have will work with the x.12.x system. Assuming at the moment, you make it to boot animation. But you have to boot into recovery right after flashing and perform a factory reset before you boot
[Android General] PhillMc:
I do -- stuck in a boot loop at animation. I'll give it a shot in a bit; have a few things that working life requires of me... Lol
[Android General] smartmanvartan:
Actually, if you haven't done it yet..wait.. I'll set you up.
[Android General] PhillMc:
Sure thing. Haven't had time to start yet.
[Android General] motolio:
Touch points? If I touch an app or a link, it's just slightly off, but nothing to noticeable. It'sI is that what you mean?

---------- Post added at 02:31 PM ---------- Previous post was at 02:28 PM ----------

Thanks!
[Android General] smartmanvartan:
Yeah but it would be a rotation. Not a slight alignment offset... I guess it's just up side down... Did you say you had recovery working without unlocking the bootloader?
[Android General] NepoRood:
[MENTION=1306272]hemanolio[/MENTION], I've made an updated TWRP for "Keyboard" users, the screen should be flipped around now (it also has more backup options)

Here's the Link

Get the one that says: viking_V9_twrp3.0.2_kb

Let me know if there are any issues, if there are none, I'll build another V9 for folks that don't use a keyboard :good:
[Android General] motolio:
Thank you so much! Ill try it right now and let you know!

---------- Post added at 04:35 PM ---------- Previous post was at 04:32 PM ----------

Yeah. I did. I was just rooted with Kingroot and flash the zip using Rashr. I even booted into TWRP from my reboot app successfully twice. Then I started messing with the kernel and thats when I bricked. After bricked, I followed all your steps, including the unlocked bootloader steps.
[Android General] smartmanvartan:
But..What zip did you flash????? All the recoveries are images....
[Android General] motolio:
Hey. Visual is no longer upside down, but touch interface IS still upside down. Very disorienting, haha. Good work so far tho! I appreciate it

---------- Post added at 04:44 PM ---------- Previous post was at 04:42 PM ----------

Oops. Thats what I meant. Just used to flashing zips from back in the day. haha. I flashed the img file
[Android General] NepoRood:
Duh, lol, there's a flag for that, sorry I can't test before I send it to you.

New link in about 15-20 min...
[Android General] motolio:
[MENTION=4666511]smartmanvartan[/MENTION]

I wonder if it was due to my x10x bootloader being bypassable? Just a thought. Unless they are all the same
[Android General] smartmanvartan:
You have a x.9.x... Don't you?
[Android General] NepoRood:
Same name, new image!

Link
[Android General] motolio:
Bahaha. Sh*t. Thats what I meant, too. Sorry man. Its been a very long day working on stats!

---------- Post added at 05:16 PM ---------- Previous post was at 05:10 PM ----------

Ok. So now, the touch is not upside down, but is switched from left to right (need flipped vertically). Touching button on left actually touches button on right and vice versa. Also, the initial swipe/warning screen is missing (which I dont mind).

We are almost there. Youre a rockstar right now man!
[Android General] NepoRood:
Alright, well, let's hope: The, Third Time, is the Charm
[Android General] motolio:
Yes yes yes! viking_V9_twrp3.0.2_kb is the charm! It seems all good! Thank you so much!!!!

---------- Post added at 06:09 PM ---------- Previous post was at 06:05 PM ----------

And thanks for giving me the chance to test out your builds, too!
[Android General] NepoRood:
Good deal, and no problem, since, I can't test them (if I could, it'd have been right the first upload, lol)

Please make sure that backup and restore work, pick one of the smaller partitons, like Nvram/Boot/Recovery, back it up, restore, make sure you can still boot after a restore ;)
[Android General] smartmanvartan:
Sorry had a long day but this is a system partition that is prerooted and the build.prop is from your versions. It's actually from the Maven pro but with your boot image it will work just fine until we get some firmware for x.10.x users... Oh yeah.. Don' t forget to make a factory reset. I did remove the recovery flash so yours will stay put...

https://drive.google.com/file/d/0Bz4bOoJ_E5XzVzZRNmlGcFBoTXM/view?usp=docslist_api
[Android General] xdreamer$3:
Sry if this is the wrong place to ask. My Viking Pro is stuck at "Viking Pro" boot screen.

This is what I did. Not a smart move on my end at all. I tried to root the tab with kingroot and installed busybox. It rooted fine. But of course after reboot All I get is the boot screen. In recovery the "root intergrity check" fails.

Model: RCT6303W87

Adroid System Recoveryv RCT6303W87DK-ANDROID5.0-V66-V2.12.20-B

Does anyone knkw where I can dowbload the stock ROM for this device? I downloaded what I thought was the stock ROM but it wont flash in recovery via SD card. I get the "flash aborted"

Thanks guys and sry to bother.
[Android General] smartmanvartan:
On the first page in the firmware section. Everything you need! :)
[Android General] xdreamer$3:
Thank you very much!
[Android General] smartmanvartan:
The one labeled rct6503 is the closest one to yours... But really they all work as long as you stay in the x.12.x
[Android General] smartmanvartan:
On a side note, I have been checking out different xposed mods and found this one called "on-the-go Mode"

[IMG="Screenshot"]https://drive.google.com/file/d/0Bz4bOoJ_E5XzaXlQdzJ4cmNkNmc/view?usp=drivesdk[/IMG]

If your cooler than me and already knew about this, fantastic! If not, basically it activates camera and overlay's it on the screen so you can see in front of you while reading a email or browsing... Kinda cool... :)
[Android General] NepoRood:
[MENTION=3679990]darkensx[/MENTION]

Were you able to pull the firmware from your tablet using the flash tool?
[Android General] PhillMc:
Sweet. I'll jump on it as soon as I get to the office.
[Android General] darkensx:
I will try today I haven't gotten a chance to.
[Android General] PhillMc:
I've gotten around to it. Sadly not getting anywhere -- I keep getting an error dialog; "PMT changed for the ROM; it must be downloaded"

Am I missing something?

---------- Post added at 18:04 ---------- Previous post was at 17:41 ----------

Never mind -- Now there is nothing. :(

Tablet will not turn on, but Windows can still see the device -- no longer called preloader, but rather just USB.

Pretty sure it's hard bricked -- pretty sure it's my fault. I'll just have to buy a new one... Still intend on being around to help test this stuff, though.
[Android General] darkensx:
I have gotten that pmt before not sure what it means might be due to locked bootloader
[Android General] darkensx:
the zip file ??? the 1.10.31 update?? :confused:

---------- Post added at 09:51 PM ---------- Previous post was at 09:35 PM ----------

preloader,system.img,logo.bin,lk.bin & tz.img throw error : Address or bytes not align

but heres the zip of what i could grab : https://drive.google.com/open?id=0B9vvQTsCktPJYzdLUGgySGM2Zzg
[Android General] smartmanvartan:
I'm at the hospital waiting for our first born to come in... In a calm period now.. I assure you it's not bricked. Hang tight and when I get home on Friday or Saturday well figure it out

.. Wish me luck! :)
[Android General] PhillMc:
Still helping out the "tablet-impaired" whilst waiting for your child to be born...

Definitely not rushing you -- good luck and that definitely puts me at ease.
[Android General] NepoRood:
That error means the length hex is wrong, I took the length from my copy of the firmware, only thing I had for a comparison, and I was able to pull all my firmware without getting that error. Unfortunately, it's going to be a guessing game, but the priority right now is the Preloader, that'll help a bunch in fixing [MENTION=7406916]PhillMc[/MENTION]'s tablet.

I have to go to work soon, I'll do some math on it when I get home, and see what I can come up with.

[MENTION=7406916]PhillMc[/MENTION], I've "hard bricked" my tablet several times ;)

[MENTION=4666511]smartmanvartan[/MENTION], Congrats Dude!! PS, they're a handfull, first year will be a doozy :D
[Android General] PhillMc:
Yeah; I had figured I cleared my preloader -- pretty sure I inadvertently cleared it all... lol. Once I had calmed down and had read the assurances that things were fixable and realized since Windows could still see the device and the flash tool was able to read ( and presumably write ) from it, it was fixable.

In the end, all will be good.
[Android General] NepoRood:
I just "bricked" mine again doing experiments, lol

Hey, since you're tab is a little on the "dead" side right now, have you tried flashing just the preloader from the other available firmwares?

If it doesn't work, you're no worse off, but if it does...
[Android General] PhillMc:
Good idea. I'll give it a shot when time allows. :D
[Android General] NepoRood:
That's the Spirit!! :good:

Instead of downloading the whole firmware, I put together a little "package" for you, it has the preloader and scatter for both the V9 and V12, attached below. If it's incompatible, the Flash Tool will throw a BROM error, but, if you get a purple bar and a green check mark, you'd be good to go ;)

To flash just the preloader, use the male to male usb, attach cable, click download, then press and hold Power and Volume Down until it's done (only takes a few seconds)
[Android General] PhillMc:
"Package" downloaded. Going to be out of town for the weekend -- won't be able to test until my return. Probably going to end up with another Viking -- which will give me one to use daily, and one to experiment and test developments here. Either way, you've got an x.10.x guinea pig here.
[Android General] darkensx:
[MENTION=7237874]NepoRood[/MENTION] you said the hex were incorrect? The 1.10.31 zip has a scatter.txt in it I opened it briefly in notepad it mentioned preloader in it among other things and a hex number but the scatter.txt in its current state won't load in SP tools says it's not a valid scatter file :confused: anyway that may assist you in finding the right hex values for what you need.
[Android General] smartmanvartan:
Smartmanvatan 2.0
[Android General] Medfordite:
I am a bit confused...

For the following version:

RCT6303W87DK-ANDROID5.0-V25-V1.10.31

I am stuck in the Viking Pro boot logo. I actually had it move into Android is Upgrading, then reboot back into this mode, so I saw a glimmer of hope.

Anyway, for this version - in the first post, is there a version I should use to get this back up and running at this point?
[Android General] PhillMc:
Hold tight -- they're working on getting x.10.x firmware together -- neither x.9.x nor x.12.x will work for you. I'm in the same boat you are. Would seem x.10.x is newer.

---------- Post added 04-22-2016 at 00:01 ---------- Previous post was 04-21-2016 at 23:59 ----------

Curious: attempting to replace KingRoot with SuperSU?
[Android General] NepoRood:
Funny (to me, anyway) the scatter I made from scratch works better than the one from the OTA. I based it from your "dumchar_info" file that you uploaded, I've asked a friend for help, he's not a RD, but he should be, he knows quite a bit about MediaTek. In the meantime, I'll look over that scatter that you uploaded (I guess it's in the OTA a few pages back...)

---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------

Just hold tight friend, we're working on it. If we can [MENTION=7406916]PhillMc[/MENTION]'s tab going, we'll get you going too :good:
[Android General] PhillMc:
Heh, his should be easier -- he still has a preloader and boot partition; lol
[Android General] darkensx:
ya its the ota you might find more than the scatter file you might like to play with and look at i know there are img files and .p file someone said they were python... anyway.. IN THE NAME OF DROID SCIENCE!! XD
[Android General] PhillMc:
Python Binary Difference and Patch File :)
[Android General] smartmanvartan:
The main issue is the scatter file. The system partition fix I uploaded should work fine but the scatter file is off buy a touch.. It's weird because the x.9.x and the x.12.x scatter files are identical.
[Android General] darkensx:
Rca want to throw a challenge our way by changing somethings apparently lol.. Challenge Accepted! ;)
[Android General] NepoRood:
We have one more partition than they do, called FRP...
[Android General] darkensx:
And what's in it?
[Android General] NepoRood:
I don't know, lol, I noticed when I was making a scatter for your version of the firmware. I'll try to find out, I'm also trying to find out other things that may be helpful for pulling your firmware. But, it's slow going, the wife has me doing other things...
[Android General] darkensx:
Well any ETA on the next uh pull, test...whatever you call it ? also does alco make all our tabs or just x.10.x Seems "Alco" Makes mine for RCA but I can't find any info on Alco brand anything let alone our tablets.
[Android General] NepoRood:
I just now got back to a PC, so I'm going to look into something. And yes, Alco makes all our tablets, through Venture Electronics (or something like that)
[Android General] NepoRood:
Dead end today, but I have an idea to make Franken'TWRP work for backing up the preloader, I'll build it soon and test it. [MENTION=3679990]darkensx[/MENTION], I'll build a CWM recovery for you to test, I'll need to know the screeen orientation, and after that I can build a F"TWRP to test...
[Android General] NepoRood:
This is the ClockworkMod Non-Touch recovery ported for x.10.x firmware users, give it a test please, let me know if it works, and if it does, is it portrait or landscape.
[Android General] darkensx:
Do I need bootloader unlocked to test? I thought boot loops occurred due to that.

Edit: nvm..... It flashed and its in portrait
[Android General] NepoRood:
I keep forgetting that part, sorry. So, we need your lk.bin file to unlock your bootloader, that should be first step (duh, lol)

I'll start looking into that...
[Android General] darkensx:
did flash though and its portrait lol:good:

and it did not boot loop huh.... well thats good

---------- Post added at 12:08 PM ---------- Previous post was at 11:58 AM ----------

also recovery holds if rebooted to android and back to recovery :good::good: :highfive:
[Android General] NepoRood:
Well that's good, I was hoping you'd flash it, lol. Since it's in portrait, the only option for TWRP is the silly one I got :P

Did you test backup and restore, to make sure they work properly? Also, there's an option to back up nvram in the Carliv menu, I recommend you do that too.
[Android General] PhillMc:
Excellent. Back in town; have a few things I have to do today, but I intend on attempting to flash one of the preloaders from a previous model to see if they are compatible -- if your ported CWM recovery does indeed work, then restoration of the x.10.x just got easier, didn't it?
[Android General] darkensx:
Backup of nvram and complete backup were sucessful :good:

should i upload the backups?

---------- Post added at 03:28 PM ---------- Previous post was at 03:26 PM ----------

i think thats what he has in mind ;)
[Android General] PhillMc:
No go on either preloader -- resulting dialogs attached...
[Android General] smartmanvartan:
Did you try flashing the whole thing?
[Android General] Medfordite:
I am out of the game now. Tablet will no longer charge for no reason. I might RMA it once I get enough time to call them (And find my receipt).
[Android General] smartmanvartan:
You should be able to bring her back from the dead.. There is a preloader flashing mode that will bring it back... Do you know what the original build number is?
[Android General] Medfordite:
Look at my past posts and you will see the build number. But how can I get it to charge it if won't?
[Android General] darkensx:
Most of the time battery charging is software controlled on Android the hardware tells the software how much percent is left of the battery then software tell the hardware to enter charging state but if the software is missing or not loading correctly it won't charge.. Android non charge issues have higher chance in it being software then hardware failure.

---------- Post added at 12:36 AM ---------- Previous post was at 12:29 AM ----------

I once had to jump charge a device by taking a USB charger cut the USB part off and crack the device open expose the red and black wires on the device battery connect the modded charger to the black and red wires on the battery and put it in to flash mode then it worked and charged fine but would not boot or charge prior.
[Android General] smartmanvartan:
Try charging with a USB micro and the main charger. Both together
[Android General] NepoRood:
It doesn't have to be charged to flash, you can even flash it with the battery disconnected.

---------- Post added at 12:51 AM ---------- Previous post was at 12:50 AM ----------

That's great, and yes, could you please upload it for us :D

---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------

Since you got 2 differrent errors, give a whole V9 firmware version a shot, by looking at thumbnails, V12 is completely incompatible.
[Android General] darkensx:
sorry for taking so long with the upload it was 2+GB but here it is: https://mega.nz/#!oFAzlISY!aLAcK-1zntU3eYbA7ZNb8UQBa61dgrJoYsHNNx2UxDY
[Android General] Medfordite:
If anyone is interested, the internals of the tablet. I took the back cover off and found the mainboard and battery. Pretty basic installation for it.

I still can not get it to power on. Reason for taking it apart was to disconnect the battery for a minute to see if I could discharge the internals. No dice.