Database Info

[Q] How to root a tablet that won't boot

Hello,
I have a tablet that has recently stopped booting. The manufacturer does not provide a firmware rom, nor have I been able to recover it any other way. I feel like I have been running in circles in researching ways to recover it (but I have learned alot). I think that I could recover the tablet if I could install a more flexible recovery manager, such as CWM or TWRP. However, to my knowledge, the tablet must be rooted first in order to install these custom recoveries. So that brings mt to my question: How can I root a tablet that won't boot? I have heard many good (and a few bad) things about Kingosoft Rooter and other root methods. However, even Kingosoft requires the tablet to have USB debugging enabled. Unfortunately, I did not have this enabled before my tablet crashed. So:
1. Is it possible to root my tablet that won't boot?
2. Is it possible to enable USB debugging on my tablet that won't boot?
3. Is there any other way you can think of to get this tablet running?
By the way, the tablet is a RCA RCT6378W2 tablet. I can access the stock recovery (android system recovery <3e>, but I can't seem to make it do anything worthwhile. Any ideas? Thanks!

1. You can't root because the tablet must be on
2. You can't enable adb debugging because the tablet must be on
3. I guess that your tablet is a made in china tablet, so there should be a devices that have same or similar characteristics, and maybe there is a stock rom for those devices
Good luck for your tablet :good:

jeremyb234 said:
Hello,
I have a tablet that has recently stopped booting. The manufacturer does not provide a firmware rom, nor have I been able to recover it any other way. I feel like I have been running in circles in researching ways to recover it (but I have learned alot). I think that I could recover the tablet if I could install a more flexible recovery manager, such as CWM or TWRP. However, to my knowledge, the tablet must be rooted first in order to install these custom recoveries. So that brings mt to my question: How can I root a tablet that won't boot? I have heard many good (and a few bad) things about Kingosoft Rooter and other root methods. However, even Kingosoft requires the tablet to have USB debugging enabled. Unfortunately, I did not have this enabled before my tablet crashed. So:
1. Is it possible to root my tablet that won't boot?
2. Is it possible to enable USB debugging on my tablet that won't boot?
3. Is there any other way you can think of to get this tablet running?
By the way, the tablet is a RCA RCT6378W2 tablet. I can access the stock recovery (android system recovery <3e>, but I can't seem to make it do anything worthwhile. Any ideas? Thanks!
Click to expand...
Click to collapse
Wipe cache and reboot and when it doesn't work do you have to try factory reset.

Bink Feed said:
Wipe cache and reboot and when it doesn't work do you have to try factory reset.
Click to expand...
Click to collapse
Thanks to both of you for your suggestions.
@ bink feed - Thanks for those recommendations. Those are the normal recommendations that should be given to most people. Unfortunately, I have already tried both of those options with no success. It seems that many, many people are running into this problem. It makes me wonder if the recovery partition is corrupt or if some system files were somehow corrupted. The "wipe cache" option and "factory reset" option both perform successfully according to the recovery system, but they do not fix the problem with the tablet not booting. I apologize for failing to mention that I have tried these options. If you have other ideas, please let me know.
@ kfarhan57 - Thanks for the suggestion. This seems like a good idea and it is something I have attempted to do. Problem is, I don't know precisely what similarities must be present for this to work. I have tried using ROMs from other tablets that share the same processor and motherboard, but have not had any success. They seem to always fail the verification process. I have very, very little experience in all of this, so it's always possible that I am not doing it correctly too. Do you know of anyone who has successfully done this? (Someone who has restored on device with a firmware from a similar device). If so, I'd like to ask them how they did it. Here is what I have tried:
1. Boot device into Android Recovery System.
2. Select "Apply update from ADB"
3. Connect the tablet to PC using USB cable
4. Load up Cmd terminal in Windows, navigate to folder containing ADB.exe
5. Type in "ADB sideload filename.zip"​The only thing that I have successfully sideloaded (and passed verification with) has been 3 small firmware updates for my tablet. Unfortunately, they are minor updates and do not restore the Operating System or ability to boot into the OS. Presently, I have been toying with the idea of merging one of these small firmwares that pass verification with the factory OS firmware from a similar device. I don't know if this is even possible, and if it is, I probably lack the knowledge needed to do it. If anybody reading this post has a suggestion, please let me know! BTW, one other thing I forgot to mention is this- I have the files copied from a working tablet of the same model. I have the boot.img, recovery.img, system.img, and virtually everything from his device... I just don't have a clue what to do with it. Thanks again. Hope to hear back from one of you!

Broken Screen

Hello guys, my phone dropped today and half of the screen is not working anymore. Also the touch does not seem to work. The problem is I just want to copy my photos to my computer but i cant because of the phone is locked and it needs a pattern password to unlock. Is there anyway without replacing the screen to copy my photos or unlock the phone. Thank you.

Hi,
You can plug an OTG cable and plug in a mouse to work around the touch screen issue. Other possibility is trying to boot in recovery mode to manage the files via USB, though I'm not sure if it would allow you to access internal data using adb or not.
All the best,
~Lord

XxLordxX said:
Hi,
You can plug an OTG cable and plug in a mouse to work around the touch screen issue. Other possibility is trying to boot in recovery mode to manage the files via USB, though I'm not sure if it would allow you to access internal data using adb or not.
All the best,
~Lord
Click to expand...
Click to collapse
Hey i do have the USB OTG and i plugged in a mouse to try to enable the adb debugging but the problem is that i can't see the screen so i am working blindly and trying to 'guess' where i should click.
The thing is i can unlock my phone with the fingerprint, but when i connect it to the computer the files do not show, i believe there is a button i have to click to enable MTP ?
I really can't believe its that hard to copy some files from my phone just because the screen is black

Hi,
Yes there is a button to enable MTP and it is in fact hard to enable it without looking at the screen. Have you tried booting in Recovery to access your files?
All the best,
~Lord

XxLordxX said:
Hi,
Yes there is a button to enable MTP and it is in fact hard to enable it without looking at the screen. Have you tried booting in Recovery to access your files?
All the best,
~Lord
Click to expand...
Click to collapse
Yea but i have the stock recovery is there a process/way to access my files other than just booting to recovert?
My phone has latest stock rom and rooted.
Please any help to recover my files since i was checking a screen repair will cost me around 200$

You must instal twrp recovery, with odin. After boot into twrp. So i rimember, twrp mtps is active defoult.

levanitit said:
You must instal twrp recovery, with odin. After boot into twrp. So i rimember, twrp mtps is active defoult.
Click to expand...
Click to collapse
i tried with my older S3 before doing all this process on the S6. I already have TWRP on the S3 and you are write when i click the button on the right it says MTP is enabled but when i plug it in the PC, the device doesn't show any files? any ideas on how to fix this/ can you try it on your device?
Thanks in advance.

Me too hade same problem. It is usb driver problem. I insttal driver and fixed. but dont rimmeber wich one. Search youtube twrp mtp problem.

I need some help recovering data

Hello guys, I was hoping you could help me with a problem
I've managed to screw up my Note 3's display and I want to take out the data from it.
Now when I connect it to the computer I can't switch the phone to MTP because I can't see anything(and I think touch isn't working either)
I wanted to mount usb storage on CWM but I couldn't manage it blindly, for some reason CWM keeps rebooting.
So is there any way I could access my files, maybe there's a recovery that enables MTP automatically or some other solution?
Thanks!

arboy2 said:
Hello guys, I was hoping you could help me with a problem
I've managed to screw up my Note 3's display and I want to take out the data from it.
Now when I connect it to the computer I can't switch the phone to MTP because I can't see anything(and I think touch isn't working either)
I wanted to mount usb storage on CWM but I couldn't manage it blindly, for some reason CWM keeps rebooting.
So is there any way I could access my files, maybe there's a recovery that enables MTP automatically or some other solution?
Thanks!
Click to expand...
Click to collapse
There are quite a few data recovery programs to recover data using your PC, provided touch feature still works and you can unlock the screen.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
There are quite a few data recovery programs to recover data using your PC, provided touch feature still works and you can unlock the screen.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Well as I stated in the op the screen is pretty much dead

arboy2 said:
Well as I stated in the op the screen is pretty much dead
Click to expand...
Click to collapse
Then you can connect a usb mouse to the device and use it instead of using the touchscreen.
It gets complicated but you can screen cast or VLC to share your screen to PC then use the mouse,to navigate and make selections. You can try finding screenshots of devices just like yours with the same stock firmware or custom ROM as yours has, then use those as a guide to help you figure out where things should be on your screen so can try to navigate to what you need to get the device to share it's screen to PC.
It takes a lot of trial and error to navigate properly until you finally connect the two screens.
Or you can try flashing TWRP on your device then use adb to pull your data.
This CAN be done if you've got the patience.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Then you can connect a usb mouse to the device and use it instead of using the touchscreen.
It gets complicated but you can screen cast or VLC to share your screen to PC then use the mouse,to navigate and make selections. You can try finding screenshots of devices just like yours with the same stock firmware or custom ROM as yours has, then use those as a guide to help you figure out where things should be on your screen so can try to navigate to what you need to get the device to share it's screen to PC.
It takes a lot of trial and error to navigate properly until you finally connect the two screens.
Or you can try flashing TWRP on your device then use adb to pull your data.
This CAN be done if you've got the patience.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
Yeah I thought of that I might give it a try, also I saw TWRP is touch only
What if someone makes a flashable zip that forces MTP on?

arboy2 said:
Yeah I thought of that I might give it a try, also I saw TWRP is touch only
What if someone makes a flashable zip that forces MTP on?
Click to expand...
Click to collapse
It doest matter, just get TWRP flashed and then boot to it then use adb to pull data
Sent from my SM-S903VL using Tapatalk

Droidriven said:
It doest matter, just get TWRP flashed and then boot to it then use adb to pull data
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
is ADB automatically connected?

Need Help! Could not enter the device Pin after restart, cause keybord deinstalled!

hi friends of the android world,
This afternoon I had a new keyboard installed and the default swift key keyboard with root and titanium backup uninstalled. Then I restarted my phone and now I can not enter the devices pin to unlock the phone. can someone help me? :crying:

weso565 said:
hi friends of the android world,
This afternoon I had a new keyboard installed and the default swift key keyboard with root and titanium backup uninstalled. Then I restarted my phone and now I can not enter the devices pin to unlock the phone. can someone help me? :crying:
Click to expand...
Click to collapse
Connect a mouse or keyboard to the device using either Bluetooth or otg USB A to C to access the device and fix the keyboard then.

RJASSI21 said:
Connect a mouse or keyboard to the device using either Bluetooth or otg USB A to C to access the device and fix the keyboard then.
Click to expand...
Click to collapse
Can not I just install it through ADB?

weso565 said:
Can not I just install it through ADB?
Click to expand...
Click to collapse
You might be able to but if you have a Bluetooth mouse or keyboard id find it easier just to use one of those. ADB can be a pain and it feels simpler just to go to the playstore and download the keyboard.

RJASSI21 said:
You might be able to but if you have a Bluetooth mouse or keyboard id find it easier just to use one of those. ADB can be a pain and it feels simpler just to go to the playstore and download the keyboard.
Click to expand...
Click to collapse
I think you misunderstood me, the XZ Premium does not boot up anymore. It stucks when booting up and asks for the PIN. But I can not enter without the Swift Key keyboard.

weso565 said:
I think you misunderstood me, the XZ Premium does not boot up anymore. It stucks when booting up and asks for the PIN. But I can not enter without the Swift Key keyboard.
Click to expand...
Click to collapse
Oh my bad I see what you mean now. Yeah you can try adb but the phone most likely wont be recognised in adb. If it were me at that point id just newflash it or pc companion it. If you use newflasher I think theres away to flash without wiping data so it will just flash the system files including swift keyboard. The whole point of that screen is to prevent computer commands and data from being stolen so I don't think adb would detect the device. Take a look at some of the guides on newflasher since doing that would keep your data and reinstall the system including the keyboard. Alternatively if you have a backup in TWRP assuming your rooted you can use that to restore just the system. Also if you are rooted and have TWRP then adb should work through TWRP.

RJASSI21 said:
Oh my bad I see what you mean now. Yeah you can try adb but the phone most likely wont be recognised in adb. If it were me at that point id just newflash it or pc companion it. If you use newflasher I think theres away to flash without wiping data so it will just flash the system files including swift keyboard. The whole point of that screen is to prevent computer commands and data from being stolen so I don't think adb would detect the device. Take a look at some of the guides on newflasher since doing that would keep your data and reinstall the system including the keyboard. Alternatively if you have a backup in TWRP assuming your rooted you can use that to restore just the system. Also if you are rooted and have TWRP then adb should work through TWRP.
Click to expand...
Click to collapse
ok no problem. i done a default reset of the system and have installed all apps from the beginning

OnePlus One. Not recognized in Windows after installing stock TWRP. Fastboot not showing devices

Hello!
I have tried to upgraded my phone to Lineage 18.1 but it did not work.
This is what I did so far:
1) Installed the NEWEST TWRP and unfortunately I have deleted the OS. After that, the USB connection worked fine and I was able to see all files on my phone.
2) I've found a stock recovery.img that I have used and then the problem started. After installing that recovery.img file now I have TWRP (older version) 2.7.0.0 and:
a) when connected through USB , my computer does make sound, but it does NOT recognize my phone any more. Yes, I do have the newest USB drivers installed
b) when connected through USB and when I run this command: fastboot devices, then it DOES shows my device number, but it DOES NOT any devices using adb command.
c) when booting into fastboot, the phone shows just the black screen with the android faded icon.
d) I can boot into TWRP but there is no system or recovery files in there and it look like it's just useless.
I'm not sure what to do next. It looks like the phone is soft-bricked.
Any help will be appreciated.
Thank you

the first thing i would try is flashing twrp 3.6 (the newest) using fastboot. not sure why you would flash an old recovery version. if data recovery is not an issue then the opo is even fixable after a hardbrick (i used to have it). i used the color os method but that was ages ago. now there is a slightly easier way somewhere here on xda if you want the opo to in out of the box condition.
maybe try the whole thing using a secondary old laptop (if possible) or a virtual machine. otherwise i have no idea. sounds like a lot of trial and error might be needed. good luck.