yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] synius:
Vampirefo method requires a couple things

Custom recovery= on this note an reading yur previous post

You fixed a v28 with v31 files? Or v28 files with v31 scatter

I've been thinking depending on how you fixed that other borked tab

Bryant

I need specific info

Are they both the same revision?

The update probably only shows up on the untouched v28

If v31 worked for v28 you may be in luck and be able to use v31 twrp for adb

The update won't show on the v28 flashed with v31

Do not try this until advised by someone else on this

The reason is if v31 files worked and touch screen works on the fixed tab

Then chances are twrp might be compatible and we can knock out 2 birds one stone

The problem is I've made a v28 scatter but its no where close to v31 scatter addresses and I'd rather not mess with the original device

The + side is you fixed it and it works, so you could fix it again if your willing to test

Is the v28 untouched ? for the most part u need root, terminal, busybox

We will pull files using dd if=/ of=/ The mtd@ file images

The idea is flashing borked tab with the initial v28 tabs files with my scatter for v28

One unit remains as it was and we have a tinker toy to test scatter and recovery for compatablility

This way if it fails you could flash v31 back into place and it be working

This will also help in case we bork the update and it gets applied (gives us more then one chance)

This is a process but I really want that update to compare scatter addresses

Anyone else's suggestions regarding this would be appreciated

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] bryantjopplin:
I have an untouched v28 besides root and some frozen/removed apps
[General Questions and Answers] synius:
That's what I mean,

We need root, terminal emulator for android, busybox on untouched v28

This is for copying system images.

Explain to me what u flashed on borked tablet? Original revision was v28 before flash?

Is it everything from v31 ROM and scatter? Have you tested and confirmed touch works?

I crafted a v28 scatter based off of [MENTION=5922811]Xactot[/MENTION] device although I can't confirm its correct until I view update

If v31 works as it should there's the safety net.. But.. V31 addresses for recovery may not be correct for the original v28

Which is why we need system images to produce v28 ROM to flash back on ur revised v28 so it will ask for the update on it

Its a good idea xactot is on file images stage and will provide links for it along wit lcd=

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] bryantjopplin:
I never fixed any tablet or anything
[General Questions and Answers] synius:
Ok I reread everything I'm following a few devices. My apologizes

Xactot has provided base info in regards to v28 scatter and is also providing dd files

could you terminal this Bryant or xactot

Su

Cat /proc/cmdline > /storage/sdcard1/cmdlinev28.txt upload this we need to check lcm= located in this file

LCM= might match v31 (wishful thinking)

V31 twrp might be compatible with v28 depending on above

Which has adb support

Bryant

u have a pending update

And seems you provided images ( I haven't looked at them are they the

Mtd@ files located in root directory?)

The alternative is risky

pulling mtd@recovery as recovery.img and unpacking it

modding build.prop to allow persist.adb

And repacking it

Then flashing it

That's the risky part

1 cud use test scatter I dont recommend

2 safer route fastboot flash recovery.img not sure of the exact command

I'm sure someone can help with this

Modified stock recovery

Not sure if that's accurate

But would b as vampirefo described to pull update.zip

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] bryantjopplin:
No update has been downloaded yet. And yes when I get home this week
[General Questions and Answers] TripFX:
based on the dumchar_info for v28. it is a v38 variant not a v31

easiest way to tell is dumchar_info for v31 variants give actual info where as the v38 variants dont.
[General Questions and Answers] synius:
That means v28 scatter is useless as v38 was

Only way to get proper addresses again is that update

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] bryantjopplin:
So we need the update right?
[General Questions and Answers] TripFX:
perferred yes
[General Questions and Answers] Xactot:
[MENTION=2670928]TripFX[/MENTION] Here's the link to the root folder that will contain all files from my tablet version(v28), both now and in the future.

The img files that I've pulled are in the Step 3 folder. Let me know if you need me to do something.

http://www.tinyurl.com/xactov28
[General Questions and Answers] TripFX:
codelover and I have decided it will be much easier to only maintain the v31/v38 only. Our reason is a simple one. v28,v32,v21 etc that have already been mentioned is just older rom versions. So as it stand currently

If lcm=cpt_clap070wp03xg_lvds < you need to use v31 files

If lcm=1-lxjc070whm270_18a_rgb < you need to use v38 files (when its ready)

and we do not need anything from you. aside from a v38 variant to upload us the rom ota zip. V31 we dont need anything and we do not need anymore v38 variant roms just the OTA zip. If your lcm does not equal the above and is a RCA 7 Voyager RCT6773W22 please use the guides found in this thread for how to obtain the info, files, and anything else needed. Thanks
[General Questions and Answers] synius:
Make sense.

So Bryant the update is pointless as v28 is a variant of v31 as the lcm indicates

You could however use v31 twrp files

Which has adb support if u want to continue

Make sure only recovery is checked in spft if you try to flash v31 twrp recovery

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] TripFX:
no no v28 is a v38 variant after looking at the files uploaded by [MENTION=5922811]Xactot[/MENTION] i was easily able to tell so yes we would need it
[General Questions and Answers] bryantjopplin:
So tomorrow I'll be home and if I need too, I'll be able to get what's needed I hope. But your not working on v28 anyways right? So I really don't need to do anything right?
[General Questions and Answers] synius:
Xactots lcm matches v31 tho your post confuses me sir sorry

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] bryantjopplin:
Didn't they say they aren't working on anything but v31 or v38 right?
[General Questions and Answers] TripFX:
oh you are correct and by doing so i just realized something. I looked at his dumbchar_info.txt and at first it appeared it was a v38 variant as the starting addys where hidden but ya your right his lcm gives v31. So yes use v31 for v28. if you want to make sure you are safe flashing it. its simple use the dd command to backup recovery which i believe is mtd7. So yes we do dont really need ota from v28 but but honestly i would still like to have it if possible.
[General Questions and Answers] synius:
Byrant it is not that they are not working on anything else

Everything else so far is a variation of the first revisions

V31 and v38

its not 100% the addresses are the same

But its 100% v31 twrp is compatible with v28

dd if=/mtd@recovery of=/storage/sdcard1/stock/recovery.img

Will backup stock

To place v31 twrp we can either flash it using spft + v31 scatter

Or use

Fastboot flash recovery recovery.img

I do believe [MENTION=2472806]vampirefo[/MENTION] used this method to provide the initial update we

have, but used his own modded recovery

Place twrp recovery.img into fastboot folder (if its installed system wide it should be c:/adb)

rename twrp recovery to recovery.img

This method hasn't been tested on our devices but it provides the ability to flash without the need for addresses

Straight to recovery partition

The choice is up to you

Been lookin into unpacking boot.img for CPU related

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] TripFX:
I will be releasing a app that will safely flash the recovery as well as allow you to make a backup of stock and restore it as well tomorrow. been sick for a week got over that 2 days ago but was really busy both days with daughters H.S. Graduation. So i will be able to work more on the v38 as well as release the flasher. it will work for both variants. without spft or risk of brick
[General Questions and Answers] synius:
[MENTION=5922811]Xactot[/MENTION]

Problem solved

[MENTION=2670928]TripFX[/MENTION] is the best

There is nothing related to CPU in boot.img ramdisk

It must be within the kernel

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] Xactot:
Awesome, as soon as it's out just lemme know and I'll give it a whirl ASAP.
[General Questions and Answers] TripFX:
Here is the first initial release of TWRP Flasher. Being my tab is currently down i have got to test for bugs. That being said i need feedback after you try the following steps.

What you need

ROOT

ADB Debug Enabled

TWRP Flasher

flash_image

twrp.img for your variant

Please read what it says inside app for where to place "flash_image' and "twrp recovery.img" files as it will tell you and open the directory for you to place or verify it is in the right location. You can also find out which twrp recovery you need with app if you dont know.

Make sure you are powered into android

1. First open

TWRP Flasher.exe

as it will create a directory located

C:\Users\%USERNAME%\TWRP Flasher

2. Make a backup with TWRP Flasher first and verify that recovery.img is located in

C:\Users\%USERNAME%\TWRP Flasher\Backup

3. If recovery.img is not located there. Stop don't do anything else but exit the app and report not working. if recovery.img is located in directory go to step 4

4. Now you will want to install "flash_image" on your device (only has to be done once unless you wipe out rom or delete from your device)

5. You are now able to flash your twrp

EDIT

TWRP Flasher has been updated to v1.0.0.1b
[General Questions and Answers] Xactot:
Ok, so after running the backup option, I get the results in the first screenshot. However, as seen in the second screenshot, the recovery image was copied. Did it still successfully complete? And if it didn't, can I still proceed, having previously dd' all of the img files and copied them to my computer? I checked the file sizes and it's the same as the recovery.img file that I'd already dd' and copied.
[General Questions and Answers] TripFX:
ah thanks for the feedback. I forgot to add the adb shell and su commands. The recovery it copied was the one you dd before. please make sure recovery.img is not on your sdcard on phone and the recovery.img and retry with updated TWRP Flasher when i reupload it as i found others typos
[General Questions and Answers] Xactot:
Glad to offer. I'll try it again now. Also, I'm having trouble flashing the flash_image (first version). Whenever I try, it can't find the file. Since I'm running it with administrator privileges on my non-administrator account, the TWRP Flasher folder gets created here: "C:\Users\Xacto T\TWRP Flasher" (admin's user folder) . But when I select the option to flash it says: "Make sure "flash_image" is located in the open folder" and then opens up an explorer window for here: "C:\Users\Xacto_2\Documents" (standard user's folder which I'm currently logged in under).

EDIT: Just thought about it: It's opening it in different folders because it doesn't rights to open the admin users explorer folder. I don't believe that affects why it's looking in the wrong place though. Also, the dd command still is not working.

Even more confusing though is the message afterwards stating:

cannot stat 'C:\Users\{username}\Documents\TWRP Flasher\flash_image\flash_image'

: No such file or directory

So I'm guessing it's pointing to my Xacto_2 standard user folder and not the Xacto T admin one? Also shouldn't it be looking within the "%username%\TWRP Flasher" folder and not the %username%\Documents\TWRP Flasher" folder?
[General Questions and Answers] TripFX:
ya noticed that and a few other things. FIxed now check orignial twrp flasher for updated version.
[General Questions and Answers] kormasah7410:
RCA RCT6773W22KB Touchscreen Tablet Boot Issue

All,

I am not a programmer but really need help with this tablet. An online search landed me here. I have a couple of these and they are stuck on the RCA boot screen and that's it. This forum has given me hope and was wondering if anyone could point to a step by step guide on how to get a working Rom on these or pages that will help me. Your help is really needed and appreciated.

Thank you
[General Questions and Answers] synius:
Any particular reason for boot loop?

OK first shut down these devices

Hold power and vol up button device should shutdown

Release these and do it again

This time allow it to shutdown and reboot this time you should be in recovery

Keep in mind battery level devices don't charge in recovery just need a little bit

Then you can shut these off

In here

Identifie your version of tablet

an example: it appears in red at the top of screen in recovery

RCT6773W22-4.4.2ANDROID-V1401-(V31-1.10.0)
[General Questions and Answers] kormasah7410:
Thank you very much for the response. I will get these done as soon as I get home from work and post the results here. Once again, thanks to all of you wonderful people who are making things happen here.
[General Questions and Answers] kormasah7410:
Folks, It appears each of these tablets I have different versions. I got so discouraged, I could only get these five below: Whatever assisatnce you provide is appreciated, if not, I still say thanks and appreciate everything you all do for this community.

1. RCT6773W22-ANDRIOID4.4.2-6378-V17-V1.7.20

2. RCT6773W22-ANDRIOID4.4.2-1401-V18-V1.6.60

3. RCT6773W22-ANDRIOID4.4.2-3101-V21-V1.3.0

4. RCT6773W22-ANDRIOID4.4.2-6378-V28-V1.7.21

5. RCT6773W22-ANDRIOID4.4.2-1401-V02-V1.6.30
[General Questions and Answers] synius:
I need [MENTION=2670928]TripFX[/MENTION]

What do you think these are all bootloops

I'm thinking readbacks on revisions that haven't been done to check for variant

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover

---------- Post added at 12:26 PM ---------- Previous post was at 12:23 PM ----------

Unfortuently v2 is another revision surfaced

But seeing as there bootloops you could try flashing v31 on v28

The others I'm not 100% on that

Tripfx will advise on other models that may have hope

For v28 flashed with v31 if you need help that can be arranged

Please note it hasn't been tested and should be applied as directed and at your own risk

It may not work, may work with errors, may work flawlessly feedback is appreciated as your testing solutions

We feed you,

Announcement thread has a flashing guide if u need assistance inquire

http://xdaforums.com/showthread.php?p=60216237

This is for flashing

You need http://www.mediafire.com/download/cwn2ucrpwq5qvkf/SPFT.zip

V31 prerooted stock ROM

http://www.mediafire.com/?f077ahhtdycmiyw

Twrp for v31

http://xdaforums.com/showthread.php?p=60320883

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] kormasah7410:
Thank you very much. I have been looking online for instructions on flashing etc. I have never done any of these before. If it goes bad, I will still say thanks and I will post results here. Wherever I get stuck, I will inform or inquire from you guys.
[General Questions and Answers] synius:
This can only be done on v28 revision right now

Reminder

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] TripFX:
you have a few options you could try to get some of your tabs working atleast all v31 variant tabs.

1st is obvious but saying it anyways. try a factory restore.

if failed then you have 2 routes you could go

Find your lcm via spft+hex/ida ( safe )

1st. spft do readback start address

0x9800000

and for the length

0x400000

2nd use any hex editor or what i personally like better ida pro (free version works just fine) and open the file you just made doing the readback

3rd use the search function. if you find

you can use spft+v31 files to restore those tabs. if you get

just stop and set it aside as there is no current fix yet for v38 variants.

NOT SAFE WAY

if you dont want to do the safe way and wish to take a faster way which i do not recommend. try flashing all with v31 files. I recommend taking the safe way as eta for v38 fix is still unknown. we have narrowed it down massively.

hope this helps
[General Questions and Answers] kormasah7410:
Thank you TripFX but to be honest, I will have to read on all those things you just wrote as I am a completely newbie to this.
[General Questions and Answers] TripFX:
There's plenty of info found in this op and or in the releases op here
[General Questions and Answers] void513:
tried flashing

i tried flashing with 3.1 every thing went fine after going threw the longing to goolge and try install app.it either freeze or if i power off it get stuck on first rca logo screen with 2 dog i get out of this and flash with system.img again but if i power off or if freezes up i have do it over again.it acts like having prob reading from storage space
[General Questions and Answers] synius:
Those are on originally v28 tablets

Just a thought tripfx

Can you flash the dd files as is Once the files have correct extensions?

Just a thought flashing xactots v28 dd files in place of v31 file images

And partition size adjustment based from device v28 with start addresses of v31

Would that be sufficient for v28 users if they keep having partition issues?

I imagen that's why there are storage issues incorrect partition sizes since there the v31 sizes

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] ShadowCX11:
possible new root method

I don't exactly have a 7 Voyager, but I have an 8 Apollo, and I figured out that rooting with KingRoot works perfectly! At least then you don't need to hassle with cables and adb drivers...
[General Questions and Answers] void513:
new i try replace system.img 31 with 38 it boot up right but touch screen did not work right but i actualy restart the tablet and would boot up correctly.unlike the prob i was having with 31 from prev post
[General Questions and Answers] synius:
If was confirmed awhile ago v31 and v38 use 2 different touch drivers

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] TripFX:
only 2 things are known to be broken when using v31 on v38 tab or v38 on a v31 tab. Touch breaks and charging breaks. wifi and everything else appears to work just fine. Also i have notified rca about the issue even told them we have successfully fix v31 variants. Well they did confirm there is only 2 variants and the issues people have been having. They will NOT give us firmware but said that we can send it in and they will reflash it. Im sorry but that defeats the purpose as most if not all didnt get the warranty also they did not say if it it would cost anything. On the bright side they are aware that we have rooted and have been doing things that technically would void any chance of them fixing it but are still willing to do so.

Here is where v38 is currently at as far as progress goes. we have narrowed it down to 3 total possible problems. using all v38 except preloader and lk the tablet will boot to first rca screen but being lk is from v31 it bootloops but can enter recovery. so either preloader or lk is messed up (which is unlikely as we have multiple v38 files from users here including some of the variants. or the more likely cause is that being we dont know the real start address the partitions are aligned properly for the kernel. some of the erasesizes are wrong when using v31 scat. So what will be going on is lots of testing and guess work to see if we can find the correct starting address also i will start work on modifying the v31 files to fix the 2 known issues when using straight v31 files. In the mean time if someone with a working v38 variant that hasnt updated to v38 yet would be so kind to get us the ota update.zip file and upload it here for us that would be great. Im sorry v38 variants is taking so long to fix but without the proper info needed we have to do a lot of guessing, trial, and error.
[General Questions and Answers] synius:
A note added I'm writing a script for ROM tool box pro thatll dd all the file images and copy them to sdcard1/backup/img/

Simplistic nature is it'll be automatic just import script and run it wait for it to finish

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] void513:
got it flashed and working

ok i used 28 system.img i think was posted in this thread and rest where 31 files flashed it .and works great so far.

Thanks for the help synius
[General Questions and Answers] synius:
To the user testing v28

Test ur device thoroughly if everything's working flawless for 3 days no issues

v28 can be added to the roster of fixable

Updated:

The script I've been working on is finished

What it does is make a directory for files first then

Copies mtd, dumchar_info, and cmdline as txt

Then copies all the partitions except cache and userdata

(I will fix this to export the files in the proper file extension's) there all set to .img files for now

If used remember to add version info to zip name..

All you need is root, external sdcard,ROM toolbox to execute script and it will notifie when finished running

Figured extracting these files is a pain to explain so here's a script that does it all

(Link posted after I've tested and fixed file extensions output)

Updated:

Tested on my own device it takes roughly 30 minutes for script to finish

I'll post link after file extension correction

(Tripfx can I export the files like your ROMs preloaded.bin example)

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] TripFX:
you could just pull the version from build.prop
[General Questions and Answers] synius:
[MENTION=4893922]codelover[/MENTION]

[MENTION=2670928]TripFX[/MENTION] I need to ask a couple questions using the v31 scatter

And testing script

I place the extracted files into same folder as scatter

preloader_rct6773w22.bin from script

Preloader also states to check file as may be incorrect directly from device

Using ROM v31 preloader_rct6773w22.bin

It doesn't say anything about checking file and loads as it should

Modified scatter to flash each file

When I sent my v31 images. How were preloader.img, uboot.img and logo.img converted to bin files

Just extension changed?

Do those particular files need to be bin rather then img files?

Sorry I'm just curious why its giving me an error when loaded with preloader from device

And the differences between the 2 files from device and from v31 ROM release

Another question what happens to the rest of the img provided in the stock images beforr ROM release for v31 just curious why some were left out?

Were they unneeded images as the partitions get flashed but without a file? But populate durn factory reset

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover
[General Questions and Answers] synius:
Looking thru this forum and a couple other we do not have any v38 mtd@ files. Anyone with a working v38.1.8.0

sent from my RCT6773W22-V31-1.10.0-TWRP-V2.8.6.0-Compiled-by-Codelover