[Q] How to root a tablet that won't boot - General Questions and Answers

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!

Related

[Q] Mount USB storage under ClockWorkmod Recovery 6.0.1.0

Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Use this guide to recover your device.
Thanks, but my issue is that I can't install the drivers, could it be a windows 8 thing?
Everything seems to require that I enter USB debugging first, which is impossible for me now.
I think the ADB driver is impossible to install, unless I can do it over CWM, and every fastboot driver I've tried has failed too.
How did you erase everything? Was it through fastboot or CWM?
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
maxmalynowsky said:
I did it through CWM. I had just recently installed Windows 8, and hadn't connected it since then so no drivers are installed.
Click to expand...
Click to collapse
In my opinion, its safer to erase everything from fastboot.
If fastboot recognizes your phone, then you can erase or install whatever you want.
If fastboot does not recognize your phone, then you can't erase it. You then need to find out why. Bad drivers, wrong folders, bad usb cable...In the meantime you phone will still work.
On my windows 7 box, under the administrator account, it took a while to set up the drivers, don't know why, but windows would not take it at first.
Maybe you can mail the phone to a xda member to get it going again...
maxmalynowsky said:
Hello,
My phone had been experiencing a host of problems, so I formatted all partitions. (/sdcard, /system, /cache, /data, /boot)
I planned on using the "mount USB storage" to transfer a copy of CM10 to the sdcard and flash that from recovery,
but the device does not appear in my computer or device manager in windows, and Linux doesn't see it either.
In it's current state, it's soft bricked, is there anything I can do to fix it?
It now says "fastboot mode - no boot or recovery IMG", and I have no drivers to communicate with it under adb or fastboot.
Thanks,
-Max
Click to expand...
Click to collapse
I am sorry to hear about your phone. You are not alone I did the exact same thing a few days ago. Don't beat yourself up I have done that enough for both of us. Through my research into this i found there a few things that you might try (I don't own a PC so I haven't yet)
To get the drivers, I read a couple people had success downloading PDANet and installing them that way. I think they are located in "legacy drivers"
From the original "root, un-root" thread for your model download the stock boot img and try to flash that using ADB
follow the instructions to un-root and start over with rooting.
I also was going to look into Wug's toolkit (in the dev section) it looks like that may be an easy option to flash a working boot and recovery img.
I hope this helps please let me know.
I gave up to quick and ordered a GNex but I'm not touching that until I get my NS4G sorted out (my faith in my abilities is shaken and I could not handle bricking a brand new phone). I will be going to a friends house tonight to use their PC and try to get my NS running. I will be back to let you known what works and what doesn't. If you try or find anything would you please post? Two heads working on this issue are better then one. Thanks and good luck.
Sent from my temp PC36100 while my Nexus is sick using Tapatalk 2
*** success ***
The solution was an easy one thanks to our developers, the hard part was finding the answer and of course, beating myself up for making the mistake in the first place. Here's what you do...
Leave your phone with the battery out for a while. Download "Wug's Nexus Toolkit" In found it in the NS4G dev section but I believe it covers all variants (not sure which you have) at the select your model and custom JB ROM download the drivers (from the actual toolkit) turn on, plug in and select flash stock img, relock boot loader, pick the stock ROM you want and press go and your phone will be flashed and reboot in under a minute. Sign in on your phone (the toolkit should auto populate your new ROM and then just follow the steps to unlock, flash and install a custom recovery then pick any ROM you want and start over.
I really hope this helps you as I'm sure you find the whole situation as stomach-churning as I did. Please PM me and let me know.
If it does work please leave a thank you or donation to the dev for creating such an awesome tool. Again, good luck hope you get your nex back online.
Sent from my Galaxy Nexus using Tapatalk 2
The Nexus Toolkit was actually my first option, it's helped me out before. I went back and tried installing the drivers using the 3 options it gives. # 3 & #2, RAW and Samsung signed drivers don't work. Option #1, the PDAnet drivers didn't work last time I tried it (all 3 options require USB debugging enabled). However, I just tried #1 again by turning on the device in CWM and that seemed to work, but I'm not sure (installation went according to the guide). However, once I tried to flash stock img, it gave me errors about not being able to reach the device in fastboot. Can you elaborate on those two steps, driver installation and flashing? As soon as I can get fastboot to recognize my device I can pretty much take it from there. BTW, I've got a i9020A and using NRT 1.6.1; and what's the significance of leaving the phone with the battery out for a while?
Mine was in the box with the battery out overnight. When I had access to a PC and plugged it in it said something at the bottom of the fastboot screen in grey that it did not before and I actually think that was the trick (System normal or system OK or something like that and when replugged to the USB the message just repeated and stacked up on the lower left of the fastboot screen). Try letting the phone sit for a while. All driver options failed for me except the tool kit.
Sent from my Galaxy Nexus using Tapatalk 2
Tried your fix, but the phone remains unable to have it's drivers installed. It's always giving "USB device not recognized" errors no matter what I do. I'm just going to shelf it and accept my loss. Thanks for the help though!
edit: Tried using some Linux tools, much greater success! This guide finally got my device listed under fastboot: http://forum.xda-developers.com/showthread.php?t=1447040
edit2: Up and running again with the android-tools-fastboot package for Linux and a standard stock image flash: http://forum.xda-developers.com/showthread.php?t=1572307
I am so glad to hear it! I stayed subscribed to the nexus s forum just to keep up on your progress and to try and help. Good for you.
Sent from my Galaxy Nexus using Tapatalk 2

recovery mode not working

hello, i think this forum is my last hope, i have a tablet and i've been searched the correct rom for it, but is not very commun in the market (DOPO), and i am a very noob in this kind of topics, i tried the recovery mode but now shows me a box that says: Android is upgrading, Optimizing app 1 of 39, but never pass the no1, it stays there for hours without anything happening, i guess, i only have the choice to flash the tablet with a rom, but i will apreciate if you guys help me how to find the right way to reinstall my android OS,or find the right OS for my tablet. please, help me
My Tablet:
DOPO Double Power
Model: GS-918
9" multitouch display
8GB Memory
Android 4.1.1 Jelly Bean operating system
1.5GHz Amlogic Cortex A9 dual-core processor
1GB system memory
800 x 480 resolution
sdesignz said:
hello, i think this forum is my last hope, i have a tablet and i've been searched the correct rom for it, but is not very commun in the market (DOPO), and i am a very noob in this kind of topics, i tried the recovery mode but now shows me a box that says: Android is upgrading, Optimizing app 1 of 39, but never pass the no1, it stays there for hours without anything happening, i guess, i only have the choice to flash the tablet with a rom, but i will apreciate if you guys help me how to find the right way to reinstall my android OS,or find the right OS for my tablet. please, help me
My Tablet:
DOPO Double Power
Model: GS-918
9" multitouch display
8GB Memory
Android 4.1.1 Jelly Bean operating system
1.5GHz Amlogic Cortex A9 dual-core processor
1GB system memory
800 x 480 resolution
Click to expand...
Click to collapse
Download This File
https://docs.google.com/file/d/0B8YnQA1FX-_yUU1ERXh1TjNUbnc/edit?usp=sharing
Click to expand...
Click to collapse
Install Cwm On your tab with mtk droid tools (search for it on the internet)
Boot into recovery mode....
The file you downloaded must be in your sd card....
Select apply update from sd card...
Choose the zip file....
Click yes....
The phone will boot normally....
do everything at your own risk... don't forget to make a backup of your tab with mtkdroid tools..... I am not responsible for any harm caused to your device
Click to expand...
Click to collapse
N'ayam Amarsh'e said:
Download This File
Install Cwm On your tab with mtk droid tools (search for it on the internet)
Boot into recovery mode....
The file you downloaded must be in your sd card....
Select apply update from sd card...
Choose the zip file....
Click yes....
The phone will boot normally....
Click to expand...
Click to collapse
wow thank you for the quick reply!
i am trying to do the back up to my rom but the MTKdroidTools does not recognize my device when i plug in with the usb cable to the pc
EDIT: ok i run the the .zip file named dopo7088stk and this is what it says:
install/sdcard...
finding update package...
opening update package...
verifying update package...
installation aborted.
sdesignz said:
wow thank you for the quick reply!
i am trying to do the back up to my rom but the MTKdroidTools does not recognize my device when i plug in with the usb cable to the pc
Click to expand...
Click to collapse
Mtkdroid tools only works with mediatek devices (with a mediatek chip eg mt6577, mt6589 etc) so will not work with your device
What actually is wrong with your tablet?
sdesignz said:
wow thank you for the quick reply!
i am trying to do the back up to my rom but the MTKdroidTools does not recognize my device when i plug in with the usb cable to the pc
EDIT: ok i run the the .zip file named dopo7088stk and this is what it says:
install/sdcard...
finding update package...
opening update package...
verifying update package...
installation aborted.
Click to expand...
Click to collapse
Sorry Then i can't help... But you can try to do factory reset from CWM REcovery... If this helps then you can boot normally.. If this too doesn't works then you will have to give it to SVC.....
Sorry Then i can't help... But you can try to do factory reset from CWM REcovery... If this helps then you can boot normally.. If this too doesn't works then you will have to give it to SVC.....
Click to expand...
Click to collapse
but to do a cwm recovery i need the tablet drivers isn't it?
and i don't have them :/
oscarblue48 said:
Mtkdroid tools only works with mediatek devices (with a mediatek chip eg mt6577, mt6589 etc) so will not work with your device
What actually is wrong with your tablet?
Click to expand...
Click to collapse
it freezes in the operating system start logo, or shows me a box that says: Android is upgrading, Optimizing app 1 of 39, but never pass the 1, it stays there for hours without anything happening. I already tried using the system recovery but it did not work, i tried with diferent roms but nothing :/, i don't have the warranty paper, i guess i'm ****ed :C
sdesignz said:
but to do a cwm recovery i need the tablet drivers isn't it?
and i don't have them :/
it freezes in the operating system start logo, or shows me a box that says: Android is upgrading, Optimizing app 1 of 39, but never pass the 1, it stays there for hours without anything happening. I already tried using the system recovery but it did not work, i tried with diferent roms but nothing :/, i don't have the warranty paper, i guess i'm ****ed :C
Click to expand...
Click to collapse
Can you get into the recovery menu and do factory reset or anything else??
I guess you've tried resetting via the reset button?
There doesn't appear to be a stock rom available for the GS-918 on the Dopo website, have you contacted them to see if they are able to help?
You could try leaving the tablet on when it freezes until the battery runs right down and it turns off, then put it on charge and try it again, not much else I can think of at the moment
oscarblue48 said:
Can you get into the recovery menu and do factory reset or anything else??
I guess you've tried resetting via the reset button?
There doesn't appear to be a stock rom available for the GS-918 on the Dopo website, have you contacted them to see if they are able to help?
You could try leaving the tablet on when it freezes until the battery runs right down and it turns off, then put it on charge and try it again, not much else I can think of at the moment
Click to expand...
Click to collapse
yes i can do everything but it doesn't fix anything :C
and yes, i've tried the ressetting via reset button.
i can swear you there is no dopo GS-918 model drivers or rom in the whole web u.u
I contacted them but they only told me about the recovery menu, and i send them a question but they haven't answered me yet.
((((
now the pc recognizes the tablet via usb, well, it recognized first like vid_1f3a_pid_efe8_driver, then it disappeared and recognized a M3-CHIP driver but with errors (The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver, blabla.)
so i think i need to find the M3-CHIP driver isn't?
EDIT:
I let the battery ran out, and now shows me the box that says: Android is upgrading, Optimizing app 1,2,3,4,5,6,7 of 39, but never pass the 7 now, then i restart the tablet againt, and say: optimizing app 20 of 23, but it freezes,then i restart the tablet... againt, and say: optimizing app 1 of 7, i restart again the tablet, and then it freezes in the first logo forever, the end :C
So, i think one of those last applications is creating the conflict
EDIT 2:
so, now im stuck in the system recovery, i choose reboot system now, and again, i am in System recovery , even if i only press the + volume or -, with the tablet off, it boots automaticly the system recovery :S
sdesignz said:
yes i can do everything but it doesn't fix anything :C
and yes, i've tried the ressetting via reset button.
i can swear you there is no dopo GS-918 model drivers or rom in the whole web u.u
I contacted them but they only told me about the recovery menu, and i send them a question but they haven't answered me yet.
((((
now the pc recognizes the tablet via usb, well, it recognized first like vid_1f3a_pid_efe8_driver, then it disappeared and recognized a M3-CHIP driver but with errors (The drivers for this device are not installed. (Code 28)
There are no compatible drivers for this device.
To find a driver for this device, click Update Driver, blabla.)
so i think i need to find the M3-CHIP driver isn't?
EDIT:
I let the battery ran out, and now shows me the box that says: Android is upgrading, Optimizing app 1,2,3,4,5,6,7 of 39, but never pass the 7 now, then i restart the tablet againt, and say: optimizing app 20 of 23, but it freezes,then i restart the tablet... againt, and say: optimizing app 1 of 7, i restart again the tablet, and then it freezes in the first logo forever, the end :C
So, i think one of those last applications is creating the conflict
EDIT 2:
so, now im stuck in the system recovery, i choose reboot system now, and again, i am in System recovery , even if i only press the + volume or -, with the tablet off, it boots automaticly the system recovery :S
Click to expand...
Click to collapse
I think its banjaxed mate, I think your only hope is if the manufacturer is willing to help you, there are no files available anywhere that I can find, the only thing that might have fixed it is a factory reset, and I guess that is not working from your recovery menu?
Is it out of the question to return it to Dopo?
I suppose you could try running the battery right down again, then leaving it for a while and then restarting again, and keep doing that in the hope that it fires up as its supposed to, but to be honest I have my doubts that it will.
Sorry I cant be of any more help.
oscarblue48 said:
I think its banjaxed mate, I think your only hope is if the manufacturer is willing to help you, there are no files available anywhere that I can find, the only thing that might have fixed it is a factory reset, and I guess that is not working from your recovery menu?
Is it out of the question to return it to Dopo?
I suppose you could try running the battery right down again, then leaving it for a while and then restarting again, and keep doing that in the hope that it fires up as its supposed to, but to be honest I have my doubts that it will.
Sorry I cant be of any more help.
Click to expand...
Click to collapse
well i contacted the dopo tech support guy , to see if i can do something else, i guess there is no mucho to do now, maybe i could sell the tablet for parts :C
too bad because i just have 4 months with it, at least i learned something about android, do a f ucking backup and enable debugging mode xd
thanks for all your help and the given support .
I apreciate your replies and now i know a litte bit of this kind of topics .
oscarblue48 said:
I think its banjaxed mate, I think your only hope is if the manufacturer is willing to help you, there are no files available anywhere that I can find, the only thing that might have fixed it is a factory reset, and I guess that is not working from your recovery menu?
Is it out of the question to return it to Dopo?
I suppose you could try running the battery right down again, then leaving it for a while and then restarting again, and keep doing that in the hope that it fires up as its supposed to, but to be honest I have my doubts that it will.
Sorry I cant be of any more help.
Click to expand...
Click to collapse
The factory reset on these models (DOPO/nobis/apex) only re-initialize the data/cache partitions it will not touch/fix the system partition.
Based on the gist of the initial post -- the only solution is to send the tablet to the factory so that they can reload the firmware.
I am in the same boat right now...
Originally I had some file system errors on the internal nand (on APEX GS-918) that caused the boot animation to loop endlessly -- because I had 'USB Debugging' enabled' I was able to open a adb shell
and run fsck/e2fsck and fix it.
But I have a similar problem now (possibly due to adding an option in build.prop) and also disabled 'USB Debugging' and
I can no longer use adb to open a shell during the boot logo.
PS: I hate to necro a thread -- but people need to know that the issue, described, is by-design........they want you to send it in the factory.
When doing a factory reset, any respectable stock recovery, should restore the system partition.
PPS: I do not believe you can install and update in the stock recovery that attempts to write to the system partition.
I believe that can only be handled by using various amlogic tools (such as amlogic usb burning tool, which requires the firmware image that we don't have)

Help - Need to access Note 3's internal data, phone rebooting

Hi,
I've searched and searched, and posted on other forums looking for help. If anyone can help me, I would truly appreciate it.
My mother's phone (Samsung Galaxy Note 3 N9005) recently updated itself to Android 5.0. This somehow broke the phone, and now it is in a reboot loop. Once the phone starts up, it will reboot itself within a second. I can still run it in "Odin" mode, and in recovery mode. Safe mode doesn't work.
Most people would want advice on how to fix their phone, but I've come to accept that it will need a factory reset/flash. However, I would really like to backup the photos on the internal memory. Is there a way?
I have tried:
1) Deleting the cache;
2) Using Odin tools to load different firmware versions on the phone (4.4.2, other 5.0 versions for different carriers);
3) Safe mode.
Nothing has worked so far. All I want to do is have the phone start up and remain on whilst I plug it into a PC and copy the photos. I'm willing to try anything, so if you have any tips, please share them. If there's anymore technical information I can provide to help, let me know.
Thank you.
If you have installed the TWRP you can try to make a backup and then still via TWRP copy it to the PC by using OTG and TWRP file manager, and then open it
Sent by my iPad using Tapatalk
joe2k01 said:
If you have installed the TWRP you can try to make a backup and then still via TWRP copy it to the PC by using OTG and TWRP file manager, and then open it
Sent by my iPad using Tapatalk
Click to expand...
Click to collapse
Thanks. I've heard a lot about TWRP but haven't used it yet. The phone isn't rooted but I can hopefully root it and try your method. Can you please elaborate on OTG a bit? Haven't heard of it, but I'll look it up.
max planck5 said:
Thanks. I've heard a lot about TWRP but haven't used it yet. The phone isn't rooted but I can hopefully root it and try your method. Can you please elaborate on OTG a bit? Haven't heard of it, but I'll look it up.
Click to expand...
Click to collapse
Ok, so you can install the TWRP w/o root using odin. The OTG is a specification that allows any device capable of acting as a host (such as a smartphone ) , to communicate with USB devices, and so with OTG you can copy files from your phone to a usb or viceversa. :good:

Galaxy Tab 2 GT-P5110 Restarting and does not install stock or any other rom.

Hi guys, after many tries, many googling and youtube research, I dicided to share my problem with our community
1. At sunday, my galaxy tab started to restart continuously, It was recharging and I took some time to see.
2. I tried to activate USB DEBUGGING but when It Restarts, it's usb debugging is disabled again.
3. I'm using Stock Rom Again...was;
4.Using Stock Recovery.
5. Tried to install many others recovery's with odin and it seems to be ok but after a restart, its all back to stock recover.
6. Tried to install Stock FW again by Odin and its stuck about 50% FAIL
7. Tried to install CFW and Other Roms by SD Card but it shows a messege "Failed to check Signature" aborting... maybe because of stock recover.
8. Not rooted, usb debugging DISABLE
9 Tried to activate USB Debugging by odin, installing a patch, without success.
10 Samsung KIES does not recognize it in Download Mode.
11. I have samsung drivers installed.
one more information, when I start in recovery Mode, it shows first an android pic and a messege NO COMMAND, then proceeds to RECOVERY(STOCK).
What Can I do?? I Did Everything I can find on Internet. Is there a phisical problem??
Best Regards!!
Seems like a similar issue like mine. Check my post about behavior of my tab 2 7" (P3100) at https://forum.xda-developers.com/galaxy-tab-2/help/p3100-16gb-bricked-emmc-bug-to-t3707134
If you have symptoms similar to mine or any mentioned in the links in the post, then it seems you have a faulty emmc (internal memory).
The only solution i get to hear up till now is either to get motherboard replaced from service center or get emmc replaced from repair shop or get it jtag'ed.
Other solutions, which would avoid jtag or other service, like dual booting from SD card existed here in xda for p3100 but having stuck in stock recovery brought limitations.
If possible share all things you tried and solution if you found any.
amarb said:
Seems like a similar issue like mine. Check my post about behavior of my tab 2 7" (P3100) at https://forum.xda-developers.com/galaxy-tab-2/help/p3100-16gb-bricked-emmc-bug-to-t3707134
If you have symptoms similar to mine or any mentioned in the links in the post, then it seems you have a faulty emmc (internal memory).
The only solution i get to hear up till now is either to get motherboard replaced from service center or get emmc replaced from repair shop or get it jtag'ed.
Other solutions, which would avoid jtag or other service, like dual booting from SD card existed here in xda for p3100 but having stuck in stock recovery brought limitations.
If possible share all things you tried and solution if you found any.
Click to expand...
Click to collapse
Tks for the answer, I guess we have the same problem, by the way, I already read your topic (lol), Surelly I'm gonna find some technical assistance , the hard thing is to find these kind of stuff, but let's see. I'm gonna share any solution, see ya!
If you install a custom recovery and then reboot to system, it will automatically install the stock recovery again unless you are rooted. To avoid this uncheck the "reboot system when finished" box in odin and after installing the recovery boot directly into it.
Stock recovery is only for installing official updates, not for custom roms. You need a custom recovery for that.
hello
cfautoroot
regards
john99ap said:
If you install a custom recovery and then reboot to system, it will automatically install the stock recovery again unless you are rooted. To avoid this uncheck the "reboot system when finished" box in odin and after installing the recovery boot directly into it.
Stock recovery is only for installing official updates, not for custom roms. You need a custom recovery for that.
Click to expand...
Click to collapse
Thanks, but we I tried this too. The issue is possibly our emmc is gone into permanant write protection state as far as i have studied. i tried unchecking the "reboot system when finished" box and even pulling battery after getting odin status as success for recovery as suggested in some threads but nothing helped.
Even if i do a factory reset from recovery all data would remain as is, nothing deleted!
@blankfile99 i agree its hard to find stuff, for me jtag service is more than 500kms from my place!
I am searching for any possibility to boot from external sd card. The thing existed for p3100 (one mentioned here https://forum.xda-developers.com/showthread.php?t=1866675 which allows sd boot) and the other is the blackhawk NEXT https://forum.xda-developers.com/showthread.php?t=2285366 but this is not suitable for our case where no modifications in emmc contents are possible. Devs were able to carry out sd boot for nook color tab .
But again I am stuck trying the dual boot mentioned above at how to flash the sd boot build rom zip file to sd card since stock recovery gives signature verification failure....
Great struggle to keep the tab working...
amarb said:
Thanks, but we I tried this too. ....But again I am stuck trying the dual boot mentioned above at how to flash the sd boot build rom zip file to sd card since stock recovery gives signature verification failure....
Great struggle to keep the tab working...
Click to expand...
Click to collapse
I had the same issue - here is what I did (I'm writing this as much for me later on, as for you!). This should be fine for your device - but of course, the usual "no guarantees" applies.....
I assume you have downloaded the appropriate files ?
- I used philz_touch_6.57.8-p5100.tar.md5 (google it)
- Odin3 v1.85
1) Install / Start Odin on computer
2) Start device in download mode For my P5100 - I held down power and the UP volume button.
3) Connect USB cable to computer. In ODIN, Click PDA and select the downloaded philz_touch_6.57.8-p5100.tar.md5 (or whatever you're going to use).
4) in ODIN - UNTICK "Auto- Reboot" and Re-Partition is unticked - leave Reset Time ticked.
5) Click start. you should get the "PASS" All threads completed.
6) Disconnect USB cable
7) - important bit - Press and hold down POWER and Volume DOWN together at same time for about 15 seconds. This hopefully will restart into PhilZ mod.
Let me know how it goes.
I have decided to install custom rom on my Samsung tab 2. but it's not connecting with my laptop(not recognized).I think there's a driver problem because in device manager It is showing "Unknown USB DEVICE". Can anyone please send me the Samsung tab 2 gt p5110 driver software or any folders which are use to connect. (I have tried many times but I can't find a good solution )
@Sura 102005
Have you tried reading and following this - also read the older threads
You may need to install Samsung kies
You should also try with a newer / different cable as that could be the issue. I had this same problem and when I swapped to newer cable it solved the issue. Just try different things.
clappertrap said:
@Sura 102005
Have you tried reading and following this - also read the older threads
You may need to install Samsung kies
You should also try with a newer / different cable as that could be the issue. I had this same problem and when I swapped to newer cable it solved the issue. Just try different things.
Click to expand...
Click to collapse
Hi clappertrap, Thank you for your kindness. I have tried Samsung Kies but I haven't tried a different cable I have order for OTG cable and USB male-male cable. I think this will work.

Will Motherboard Replacement Solve Bricked TF300T?

Hi
TF300T JB 4.2.1
Bought new in the US in 2013 so has US SKU. Originally for my wife, but she now has an iPad Pro so I've got the hand-me-down!
Wiped it and unlocked the device successfully using the Asus V8 utility. Tried to flash TWRP from Win7 computer but something went wrong. The interface was still there, it would boot up okay but there was no sign of TWRP. Eventually, I went into fastboot and selected RCK. Nothing happened except the icon turned brown and just sat there. Then I tried a factory reset but it wouldn't have any, nor a cold boot. In desperation I turned the device off and tried to reboot. The initial "Asus" screen came up ("This device is unlocked" in top left-hand corner and the 'Nividia Tegra' logo in bottom right. No spinning circle of dots). It won't boot into fastboot, in fact the volume keys are totally unresponsive. On/off will turn off the device, but it immediately boots back to the same Asus screen. It's not recognised by the Win7 computer so I can't flash anything to it. I think I've tried everything this forum (and a few lesser ones!) could suggest, to no avail.
I believe I now have the proverbial 'bricked' tablet.
Nothing daunted, and not prepared to involve Asus support, I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
I'm no expert on the Android OS so any help from you experts would be much appreciated.
Thanks in advance.
Anyone?
I know the TF300 is a bit long in the tooth now, but all I want to know is whether a bricked one can be recovered by replacing the motherboard. There must be someone out there who has done the replacement and can advise me? Also, I apologise if this in in the wrong section, I guess it should have been in the 'Help' section, but I didn't realise until I'd posted it.
capelyddol said:
Hi
TF300T JB 4.2.1
I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
Click to expand...
Click to collapse
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99
ebonit said:
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99
Click to expand...
Click to collapse
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access. The initial boot-up screen is all I get, in perpetual loop. The only way to shut it down is reset with vol-up., though it's possible it may be in some sort of variation of apx mode at this point as the screen is blank. I've no way of knowing as my win 7 computer only acknowledges an 'unknown device' at that point, and nothing when the initial boot screen is there. Vol-down doesn't seem to have any effect at all. Windows has already installed the drivers so won't re-install, or uninstall them as it's 'unknown'. I did once manage to get it recognised as an 'apx device' but with an '!' (not sure how I did it as I haven't been able to replicate it since!) but I don't think that helps me even if I could replicate it without the '!', Nvflash requires I have the necessary back-up files, which of course I don't. I don't know where to go from here except to replace the motherboard. Once I get the device apart I may try disconnecting the battery, vol-down, and reconnect, to try booting to recovery, but I'm not optimistic of that working.
I'll certainly be very happy to consider any other suggestions you, or anyone else, may have.
I tried Buster99's method, but as my TF300T isn't recognised by Windows that was a non-starter.
Once again, many thanks for your input.
capelyddol
(John)
capelyddol said:
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access.
Click to expand...
Click to collapse
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB
ebonit said:
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB
Click to expand...
Click to collapse
ebonit ~ Thanks for the links. I checked out huebinger's and pulled my motherboard out, then bought the one you linked to on eBay. Hopefully, I didn't do any damage getting the MB out. I'm more used to the tough old internal wiring of desktop computers!
I'd already backed up the data and done a factory reset before I began my abortive attempts at rooting so hopefully I'll be starting with a clean slate once I get the new board installed. It's going to take a while to cross the pond to France, but I'll report on how it goes once it arrives.
Thanks again for your help, it's much appreciated.
John.
(capelyddol)
Hello,
My tf300t got bricked while upgrading twrp.
nothing helped, i put away the tablet, after a year i found her ... so i said to myself "why not" ?! so i ordered from ebay a motherboard, and it's work like a charm, but the tablet is old now ;0
now i want to setup a lite rom ....
mitomon said:
Hello, now i want to setup a lite rom ....
Click to expand...
Click to collapse
What do you mean?
What do you mean?
Click to expand...
Click to collapse
I was wondering that, too!
It's good to know the s/h motherboard cured his tablet's ills, though.
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
Go to folder /Universal Naked Drivers 0.72 you unziped at start on your Desktop.
Select file android_apxusb.inf, then right click -> Install.
Force driver install and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Click to expand...
Click to collapse
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)
capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
Click to expand...
Click to collapse
Congratulations! You did a good job. Thanks for your report.
First of all, to avoid any issues to get your device on N 7.1 Nougatella please follow exactly Tim's install instruction step by step in post #1. https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
You need Kang TWRP as advised by Tim. Don't forget to format data through Kang TWRP before. It takes up to one hour. Then change file system to F2FS for data only no cache and system. Successfully done your device is now ready to install Rom, pico Gapps and SuperSU fresh downloaded via Tim's links there.
PS: About your USB issue take another USB port on your PC not via hub!
Good luck!
Three days with nothing from me, you'd be excused for thinking either I was dead, or my tab was! Thankfully, neither. In fact - SUCCESS!!! We're both alive and well, and for the tablet at least, performing better than ever.
TWRP installation took me two days. First, the computer (Win 7 32-bit) refused to recognize the TF300T and 'fastboot' could have been renamed 'nerverboot'. Strangely, the whole business seemed to evolve over time. Persistence was the name of the game - trying different USB ports, booting and rebooting (both tab and desktop). Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Code:
fastboot devices
returned '???????????????' over and over again. By uplugging/plugging the cable into the tablet a few times I suddenly got a nice long string of letters and numbers. It came and went a few times but after a while seemed to stabilize till I felt ready for the big push of TWRP. I got so many error messages: 'can't find twrp.img' (I'd renamed it); 'can't open twrp.img'; 'insufficient memory', etc, etc.. Suddenly, it worked. It took just over eight seconds to download the 6.95MB. Booting into recovery was rather heart-stopping, but it came up a treat.
After that it was relatively simple to set up the TWRP (I found Djibe89's guide https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744 especially useful and there's a copy in the -djibe Transformer Pad TF300T pack v3' http://bit.ly/djibe-tf300t-v3.
Flashing KatKiss 7.1_TF300T_029, open_gapps-arm7.1-pico, and SuperSU-v2.82 from the microSD I'd copied them to went like a dream and before I knew it the old tab was humming with life once more. I'm a very happy chappy!
I have just two queries (so far ) 1. djibe89 mentions the file 'deviceID.apk' but Tim doesn't. Is it still necessary? I believe it's to keep Google happy, but I've no problems downloading from the Play Store, so I've not installed it as yet.
2) While installing the 'Battery Calibration' app it briefly stated that the tab wasn't rooted. I assume if I've achieved all the above, then it must be?
Now I'm going to play. No doubt I'll be back with a few more queries before too long!
Special thanks to ebonit for his help and support.
capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)
Click to expand...
Click to collapse
hi ,
you said that you succeeded to unlock the tablet ?
how ?!
i tried with unlocker v7 and 8 , i got the network error.
my tf330t is on 4.2.1.
i try hard reset, nothing helped.
i changed the mb, succeeded to root with motochopper.
please , i need help.
thanks
mitomon said:
I tried with unlocker v7 and 8 , i got the network error. My tf330t is on 4.2.1.
Click to expand...
Click to collapse
To avoid any issues please reinstall your system by doing a Buster99 https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. Be sure you have the latest firmware "WW_epad-user-10.6.1.27.5"
After that delete your Google account. Then you may unlock your device with V7.
capelyddol said:
TWRP installation took me two days. Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Click to expand...
Click to collapse
Hope you have Kang TWRP now as required by Tim in post #1!
I'm sorry, but you never mentioned that you cannot access your Tablet via ADB. Therefore please note, the best ADB tool, every Android user may have on his PC, is "Minimal ADB & Fastboot" https://forum.xda-developers.com/showthread.php?t=2317790.
BTW, the answer to your first question is nope, you don't need it. The answer to your second one is yes the device is rooted. However check the update status of your SuperSU. Hope you did fresh download Rom, Apps and SuperSU via Tim's links in post #1 of the Nougatella thread?
I have installed Kang TWRP 2.8.7.2 as per Timduru's link. My tab was wiped before installation so all apps were fresh downloads. SuperSU was 'UPDATE-SuperSU-v2.82-20170528234214.zip' again, as per Timduru's link, as was the ROM ' KatKiss-7.1_TF300T_030.zip'. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!
capelyddol said:
My tab was wiped before installation so all apps were fresh downloads. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!
Click to expand...
Click to collapse
You are welcome! It's good to hear that you did such a good job. Using the thanks button is always greatly appreciated.
Please note, if you have any issues or you are changing the Android system, Format /data through Kang TWRP is always required. Format /data is more than wipe (you did wipe!) or factory reset. It takes up to 1 hour to be successfully. After that your system is really clean.
"Warning: formatting will remove what is stored in your internal storage, so store the rom /gapps/supersu zips onto an external storage (microSD, SD card..) or make sure you know how to push them back through adb." advised by Tim in post #1.

Categories

Resources