yashsingh1/xdaforums huggingface dataset:
[Android General] Jacube22:
How do I turn it off? holding the power button just restarts the bootloop
[Android General] smartmanvartan:
The reset button
[Android General] Jacube22:
nevermind
[Android General] jerryvail35:
Hit reset button on the back
[Android General] jerryvail35:
Look's like everyone has given up on this tablet...
[Android General] smartmanvartan:
Not at all... i just bought a Samsung Galaxy Note 4 and was messing with it this week.. ;) still here..
[Android General] NepoRood:
Me either, I've been working at it every day :)

I even installed BBQLinux to go at it from a different angle...
[Android General] Jacube22:
Can I flash the firmware with a micro usb to usb adapter? or does it have to be a cable?
[Android General] jerryvail35:
Micro USB to USB adapter will work.
[Android General] jerryvail35:
Wish I knew more about bootloader and programing. I did notice that the bootloader for this tab says FORBIDDEN and I didn't see any encoding for the volume keys. Personally I think we are going to need a complete rebuild for the kernel or maybe a Loki work around. A device driver would be really nice as well.
[Android General] NepoRood:
I wish you did too, heck, I wish we all did, ;)

Where did you see the "FORBIDDEN" thing at?

This is what you get when you press the volume up or down (varies slightly, depending on choice):

I/View ( 9889): Key down dispatch to class jackpal.androidterm.TermView(ShellTermSession(1455212945474, null)), event = KeyEvent { action=ACTION_DOWN, keyCode=KEYCODE_VOLUME_UP, scanCode=115, metaState=0, flags=0x8, repeatCount=0, eventTime=31720271, downTime=31720271, deviceId=1, source=0x101 }

Open the "Terminal Emulator", and type: logcat

When it's done scrolling information, press the Volume Up button and compare to the "I/View" statement above (the "ShellTermSession" will probably be different than mine, session ID's are like that, and "eventTime" and "downTime" should be different)

Building a "New Kernel" from scratch is going to be dang near impossible because we would need the RCA drivers from our current kernel. If we had those, we wouldn't be in the current situation.

I'm currently working on a shell script to trigger "keyCode 24 (or Volume Up)", I figure we will need BusyBox installed for this, because it will give us more linux commands to work with. If you haven't installed BusyBox, go to the play store and get the installer by Stephen Ericson, this is the one I'm using.

Also, on a side note, you can do ADB over WiFi (if you have root), by going (once again) to the play store and searching for WiFi ADB (I'm using the one by MetaCtrl)

Hopefully, if we can share more info, we can get this thing cracked open soon.

Regards,

Nepo
[Android General] smartmanvartan:
So i find that the v72 firmware is glitchier on the long run compared to the v70..
[Android General] jerryvail35:
Using notepad++ and going through lk.bin file line 1404. Fastbot reboot to bootloader. I'm sure there is more than one instance of it.

---------- Post added at 09:26 PM ---------- Previous post was at 09:22 PM ----------

V70 does it too , time to time. But since I have installed kernel adiutor with min free task killer most of the glitches have stopped.
[Android General] Bogram:
So it turns out that lk.bin doesn't have a signature check done on it before the preloader fires it up. I've managed to patch the button press (you still need to hit a button), it says unlock succcessful and wipes the data partition. Doing oem lks says that it's unlocked, but if I make any changes to recovery.img it just whitescreens when you hold vol.up + pwr.

lk.bin:

http://s000.tinyupload.com/index.php?file_id=52598551875657650355

Maybe I'm doing something wrong on my end with the recovery image. Since I ran the unlock command before the lock check, someone else do the reverse and see that it says it's locked. Also, I didn't patch the lock command, so you might not be able to relock the bootloader. Hopefully they didn't make it not care about lock status when checking signatures.
[Android General] jerryvail35:
any instructions on how to do this and i will try.
[Android General] Bogram:
Sorry about that, should have included some. That lk.bin needs to be flashed (I used SP_Flash_Tool_v5.1548) to the UBOOT partition using a scatter file, I've included one I extracted from the latest rom on baidu. The lk.bin that I've patched is also from the same rom since the old one didn't seem to have a working bootloader lock check command.

Signed Preloader Drivers: (Found these on the net, they've got a valid signature so you don't have to disable windows signing checks.)

http://s000.tinyupload.com/index.php?file_id=68282426562692133739

Scatter file for RCT6303W87DK:

http://pastebin.com/J8GzaziT

same lk.bin as before:

http://s000.tinyupload.com/index.php?file_id=52598551875657650355

Use fastboot (can be gotten from minimal adb pack) along with reboot into bootloader on the tablet. (Warning, the unlock will wipe your data.)

fastboot oem lks

fastboot oem unlock
[Android General] jerryvail35:
which version are you running? im currently running version v70-v1.12.30-b
[Android General] Bogram:
v66-v2.12.20-B with the v72 lk.bin

I downloaded V72-V1.12.30-B but never installed it after stability problems were mentioned. The scatter and LK.bin are from it. (I originally patched the V66 one but it doesn't provide feedback in the cmd window and oem lks returned error instead of the lock status.)

If you want to attempt the patch on the lk.bin from your own rom, you can try doing a search & replace: (No warranties on the safety of your data, in the two different versions I checked the code that gets replaced only occured once.)
[Android General] jerryvail35:
v-70 shows lock status (bootloader) lks = 1. so all i have to do is switch lk.bin file with your lk.bin patch file . correct?
[Android General] Bogram:
Yeah, just flash the lk file I linked over yours. You can back yours up with the read back tab if you want but to do so you need to enter the uboot partition info manually from the scatter.
[Android General] ewilley2008:
BIG props to Bogram for the bootloader unlock

Im on the v72 rom and just flashed Bogram's lk.bin and edited bootloader.img and recovery.img just with ro.secure=0 and ro.debuggable=1 ... then re rooted with Kingroot and then replaced SU ..... and restored my apps from Titanium Backup.

its all working and by running....fastboot getvar all .... at the bottom shows...

(bootloader) unlocked: yes

(bootloader) secure: no

(bootloader) kernel: lk

but still no ADB access
[Android General] Bogram:
What did you use to modify recovery.img? Twrp Magic makes mine whitescreen even if I only use it to unpack/repack.
[Android General] ewilley2008:
Unpacked with Carliv Image Kitchen then edited with notepad++ and then repack with Carliv
[Android General] jerryvail35:
just tried it on the v70 repacing lk.bin with lk_patched.bin and reflashing all. keys still dont work and it reboots bact to fast boot after 3seconds. but it still boots normally. should i have turned on usb debuging first?
[Android General] Bogram:
Did it say anything in the cmd window on your computer? After the unlock it should kick you back to a fastboot menu where keys don't work, when you restart you should get a screen that says erasing. Check your boot loader status with the oem lks command.
[Android General] jerryvail35:
it did kick me back to fastboot menu. and now it does say (bootloader) lks=0
[Android General] Bogram:
It should be unlocked then, I can't test any further on mine until my computer finishes applying updates.
[Android General] jerryvail35:
it is in fact unlocked.

warranty: no

unlocked:yes

secure: no

kernel: lk

fastboot getvar all
[Android General] NepoRood:
[MENTION=7182821]Bogram[/MENTION], Awesome job man!

I'm pretty sure these "Magic" recovery programs only work with KK or lower, and since we're running LP, we'll need a recovery for that...
[Android General] vampirefo:
So you can now flash custom recovery? Sounds great.
[Android General] smartmanvartan:
Yeah wondeful news!! Will try custom recovery today.. if i got one working ill post it up later. [MENTION=7182821]Bogram[/MENTION], thank you very much for your contribution to our cause. :)
[Android General] vampirefo:
Upload stock recover.img that you currently have installed on your tablet, what is screen size?
[Android General] smartmanvartan:
1280×800

v70 stock recovery:

https://www.dropbox.com/s/svw00queanav3o9/recovery.img?dl=0

V70 stock boot image:

https://www.dropbox.com/s/aul562f13q2n1pu/boot.img?dl=0

I made one with the carliv tool but it wont boot. Some of these mtk devices require the boot image too.. I'm not sure how that works exactly...
[Android General] vampirefo:
I don't have the device, but this is built from source TWRP 3, I only build from source don't use any tools to port recoveries.

Either it will work or it won't 90% it will work.

https://www.androidfilehost.com/?fid=24415232478675285
[Android General] smartmanvartan:
It's a no go on my end.. black screen. I need to find out what these tools do with the boot image for it to work... Thanks tho, really appreciate the help
[Android General] NepoRood:
Thank you for your effort, I was going to ask you if you could help with a recovery (I wasn't looking forward to downloading source code, lol)

I flashed the one you made, it gives a black screen with nothing on it...
[Android General] vampirefo:
This sounds like wrong recovery. fstab can you adb while in black screen?
[Android General] NepoRood:
I didn't try, ADB over USB hasn't worked in the past on this tab, I had to do it over WiFi. I'll give it a shot and get back to you, I've attached the fstab file (I hope it's the one you're looking for, and I had to "zip" it)
[Android General] vampirefo:
Round 2 lol.

https://www.androidfilehost.com/?fid=24415232478675302
[Android General] NepoRood:
Still getting a black screen, anything else I (we) can do to help?
[Android General] vampirefo:
Not with out adb, need to use adb to see what is going on behind black screen.

adb shell

busybox df -h
[Android General] NepoRood:
I can only only use ADB while the system is booted, using an ADB over WiFi app, or the Terminal Emulator.
[Android General] vampirefo:
nothing else I can do without adb info, perhaps those tools mentioned might be able to port cwm.
[Android General] NepoRood:
Thanks for your effort man, it's really appreciated. Hopefully we can figure out a way to get ADB working and get back with you.
[Android General] smartmanvartan:
There is no adb access on this device and i get no reaction when i plug it in during the black screen...
[Android General] Bogram:
Has anyone tried hooking into the usb port the keyboard uses? I'm just wondering if it's a separate one or if it's tied into the other otg port.

Edit: I should have been a little clearer, the contacts the keyboard uses are labeled usb_pogo and have the same number of pins as usb plugs do.
[Android General] NepoRood:
My keyboard doesn't have a USB port...
[Android General] smartmanvartan:
No he means tge contact for the keyboard... they are technically a usb port. Its worth a shot.. ill try it later tonight
[Android General] NepoRood:
Yeah, mine is not a USB Port, it's a 4 point magnetic contact point for the keyboard.
[Android General] smartmanvartan:
Yes so is mine... if you look at the pictures you took in post post #272, you can see it labeled "USB_POGO".
[Android General] NepoRood:
My bad, I noticed the edit from [MENTION=7182821]Bogram[/MENTION], and looked at the pics on my phone :silly:

(In my defense, I was under the "influence" last night, lol)
[Android General] ewilley2008:
I started messing around with [MENTION=7182821]Bogram[/MENTION] recovery image… I first used his .img and merged it over my v72 recovery and edited the recovery.fstab and got it to boot into the twrp recovery but the touchscreen isn't functional… so.. Gonna try some more edits and keep trying things.

Update… touchscreen works just gotta rotate the build.prop value… retrying it now

Tried changing the build.prop values so far no change must be it the twrp files somewhere???
[Android General] jerryvail35:
awesome news
[Android General] ewilley2008:
So far no luck...I'm not sure where to even start to look in the twrp stuff.... the screen touches are rotated 90deg to the left.
[Android General] jerryvail35:
have you tried editing the buid.prop? this is how i have mine set.

ro.sf.logorotation=0

ro.sf.recoveryrotation=0

ro.sf.default_rotation=0

ro.sf.revert_bootanimation_xy=false
[Android General] ewilley2008:
Yeah I've have tried different combinations of values and its still off 90d to the left
[Android General] Bogram:
I'm having a little trouble getting what you mean by 90 degrees but there are compile time options for twrp to do with flipping x, y and x+y for touch. So if touching one side is triggering a press directly across the screen one way or both then that might help.

RECOVERY_TOUCHSCREEN_SWAP_XY, RECOVERY_TOUCHSCREEN_FLIP_Y, RECOVERY_TOUCHSCREEN_FLIP_X

[MENTION=2472806]vampirefo[/MENTION] made the twrp recovery image by the way. No progress with the keyboard connector so far besides verifying that it is usb and it's considered a separate port from the side otg one. (Bus 2 vs Bus 1 in lsusb) I couldnt get a connection to hook anything up to it with what I had around.
[Android General] ewilley2008:
I made up an image to show how the touch points are rotated compared to the menu..
[Android General] Spartan Legionnaire:
I was reading all the progress so far, it is amazing that you were able to unlock bootloader. Congratulations!.

Regarding recovery, I don't know if I'm correct, I don't understand a lot about recovery things, but probably using a recovery, adapting one from another 10.1 inch tablet will work for the touch controls?, or maybe using the no touch version would be better?.

Suggestions only :D
[Android General] NepoRood:
[MENTION=1017124]ewilley2008[/MENTION], can you upload the recovery you got booting? I've tried all kinds of stuff and still can't even get it to boot.
[Android General] Snigglez:
Blessings of Disting, All

My first post, so Hello World! I've been following this thread for some while now; managing to root the device, get Xposed modules running, etc. I am amazed the progress and expertise of the contributors of this thread and I tip my hat to say 'thank you for all of your help.'

Although a native Linux user for years, Android has consistently reminded me that I am still a n00b, and shall remain so always :) So I have a few quick questions, if any of you fellows would be so kind:

I have a few applications by which I've flashed or attempted to flash my device (Flashfire 0.27, Rashr 2.3.9, and Flashify 1.9.2) - by what manner are you flashing the variety of Zip files in the online Chinese directory, and the different recovery images?

I have flashed the small handful of recovery images posted here via Rashr, and I've been 'white-screened,' as well as Lime-green-screened, orange, and bright-red. No kidding, have any of you experienced this?

I am eager to help as I can, and just as eager to get TWRP up and running - so by using the above applications, am I flashing these images correctly, or must they be manually placed/written inside /system/ and/or some other directory?

My build id: RTC6303w87DK-ANDROID5.0-V32-V1.9.1

Thanks and All the Best this day.
[Android General] smartmanvartan:
First off, welcome!..

Second, be very careful what you flash. We use sp flash tool to flash the firmware we have been testing. Most of us are on a different branch of development. If you have read through the posts, you are aware already. However, just in case, your version 1.9.1 is incompatible with ours and you can brick your tablet flashing the firmware we are testing. Hopefully we can help you and you 1.9.1 friends acheive the same goal we are going for. First things first, I'm gonna find a version of the firmwarecommunity with yours,. Then we're gonna try the bootloader that bogram tweaked and we'll see if it works with yours. If you are willing to test some stuff, I'll set you up with the tools you need. ..

Can you confirm the build date, if you are rooted, you should find it in the build.prop. is it April 2015? I may have found your version.
[Android General] vampirefo:
My guess the 70 recovery you uploaded was bad, unpack my recovery and repack with 72 recovery.
[Android General] NepoRood:
It's booting now, thanks to [MENTION=1017124]ewilley2008[/MENTION], buttons are still off though. I've edited the default prop and the xml files, and everything else I can edit, lol

Also, welcome to [MENTION=7276540]Snigglez[/MENTION]
[Android General] vampirefo:
So upload the recovey so I can see what changes were made
[Android General] NepoRood:
All the changes I made were reverted back to original :(

It's like the screen is in portrait mode, but the buttons are in landscape, ideas?
[Android General] vampirefo:
I want to see the recovery.img that boots, no interested in your changes, only interested in seeing the recovery.img that boots.
[Android General] NepoRood:
It's attached...
[Android General] Snigglez:
Yes I am rooted; the build date listed is Wednesday, April 8, and I am more than happy to assist with testing. I forgot that sp flash tool had been mentioned before - excellent; I will check in regularly as possible, and am happy to contribute to this community, thereby helping others while learning more about a branch of Linux that is so far removed from that which I familiar.

All the Best!
[Android General] Bogram:
Just a heads up in case you missed it, if you're flashing roms with sp flash make sure that the preloader is unchecked. If you get bricked the preloader will allow recovery so long as it never got erased or wrote over with an incompatible one.
[Android General] Snigglez:
Thank you kindly for the heads-up! I'm still trying to get SP Tools running on my linux machine, and as soon as I can determine that my laptop detects the RTC via the male to male usb, I will post back with any curious results of my tinkering. Enjoy the evening and a splendid Monday tomorrow!

I shall keep in good cheer, neverminding the fact that I am yet another amongst many held in the darkness of a locked bootloader - for it is by the Virtues of knowledge and Goodwill thus inspired by a lust for Freedom, that I and many others shall be verily unchained - eager to hack the #$%^ out of the RTC.
[Android General] smartmanvartan:
)

So This is your stock firmware(V32 1.9.1)

https://drive.google.com/file/d/0Bz4bOoJ_E5XzeFI5aWo3MGtMWXc/view?usp=sharing

Follow the instructions in post #279

Avoid flashing the preloader(uncheck the first check at the top in the list) so you always have a way back. With your stock firmware available, you can try the bootloader that Bogram posted in post #315 using the scatter file he posted in the same post. and see if it boots. Good luck! let us know how it works out for you.
[Android General] gutclusters:
Hey, just a question. When you say "male to male usb wire," are you referring to an A male to A male cable or a Type-C Male to A Male cable?

This tablet has two different USB connectors and I can't get my computer to recognize the tablet when it's connected to the Type-C port. Windows simply says the USB device has malfunctioned and Linux says the following:

[443985.236048] usb 2-2: device descriptor read/64, error -71

[443985.452043] usb 2-2: new full-speed USB device number 4 using uhci_hcd

[443985.868035] usb 2-2: device not accepting address 4, error -71

I soft bricked this tablet trying to run KingRoot and I am desperately trying to recover it. Thank you!
[Android General] NepoRood:
You need to use the big USB port, male to male, and make sure the device is off while flashing with the SP Tool.

Also, make sure you are flashing the correct version for your tablet.
[Android General] bobl61:
Had the same problem as posted here http://xdaforums.com/showpost.php?p=64201568&postcount=45 After installing Supersu me and rebooting, it was stuck on the Viking Pro screen. Factory reset via recovery didn't work. Thought I was going to have to return it. This procedure brought the tablet back to life :good: Hopefully we can get working custom recovery soon :)

What are the differences in the firmwares, just newer?

RCT6303W87DK-ANDROID5.0-V63-V2.12.20-B-EMMC-user-Kingston-V6.1_20150811(Horisontal Splash)

RCT6303W87DK-ANDROID5.0-V63-V10.12.0_T8515B_V6.3_PCDDR31G_20151106.zip(Vertica l Splash)

RCT6303W87DK-ANDROID5.0-V70-V1.12.30-B-EMMC-user-Kingston-V6.1_20160121.zip(Horizontal Splash)

I used RCT6303W87DK-ANDROID5.0-V70-V1.12.30-B-EMMC-user-Kingston-V6.1_20160121 and seems fine.

Rooted again with KingRoot, and used the mrw trick All good now...
[Android General] Jacube22:
Found a 5.1 firmware for people on the .12 branch of development on that site with the v70 firmware (on page 10)

(be sure to uncheck preloader when flashing just in case)
[Android General] ewilley2008:
If I remember, that 5.1 isn't for the MT8127 chipset
[Android General] Jacube22:
It looks like you're right. In the title I see 8163, which is a different Mediatek chip than what we have. :(
[Android General] smartmanvartan:
Yeah there's also a 6.0 for the 8163 in that list ...
[Android General] Jacube22:
where are you finding that? and if that's true that really sucks
[Android General] smartmanvartan:
It's labeled rct6603w47dk. I haven't found that model anywhere winch leads me to believe that the user is a developer for alco/rca.

What is even more frustrating, is that it uses the same t8515 board we use but with a different chip. And the chip is really different the mt8163 is a 64 bit... :(
[Android General] dashiet91:
Can someone link the stock recovery.img? I tried flashing twrp and now when I try to update the firmware it powers down and comes back to a white screen, shuts down again this time booting in full but the update comes back... ie it doesn't update... Idk what's going on but I've unrooted and tried a few times but nothing...
[Android General] dashiet91:
Is this thread dead?
[Android General] vampirefo:
Yes.
[Android General] Ryuk359:
I hope it's not dead I need that recovery file too. I had the same thing happen and now I have no recovery. I guess if all else fails I'll return it to Walmart but I'd rather just fix it if possible.
[Android General] bradley_e_smith:
What usb driver are you using? I have tried on 2 different computers and the hardware id is USB\UKNOWN, so I can't even get adb to work.

thanks

-brad
[Android General] OrNoX:
I'm able to use adb and fastboot on this device using the usb 2.0 port. I think the microusb port is charging only... which is pretty lame but w/e. Does anybody have a stock system.img i can try out on mine? Ended up bricking it hah.

Anyway, i just used another tablet with a linux chroot that has microusb + an otg adapter and a male/male usb cable plugged between the 2.

As far as I know the bootloader can't be unlocked or i couldnt seem to get it to, since it asks you to use the volume keys which had no response in fastboot, hoping flashing doesn't require a similiar confirmation.

EDIT: You can probably actually just use one of the normal cables between 2 devices if you want, but I'm tired.

I may end up just dumping the system.img off of somebody else's I know and upload it here if it works for me.
[Android General] James101:
I could use the image too! or else this tablet is going in the garbage.
[Android General] bradley_e_smith:
Oh, okay....so the micro usb isn't what I plug into.

---------- Post added at 10:32 PM ---------- Previous post was at 10:29 PM ----------

If I get adb to work I will try and get an image for you all