Hello XDA. I was looking through your forums trying to upgrade my android's os and ran into trouble. Any help would be appreciated.
I just broke my android inspire. I tried to root it and once I installed the hack it doesn't boot anymore. It's stuck at the boot screen. My volume down button doesn't work so I can't reset it. Can I reinstall it from my pc? I've got a windows and linux partition. I'm guessing I'm going to need the linux partition because I can't access the file system through My Computer anymore.
What should I do?
Find the forum for your phone and ask there, you will find people that know your phone better. Make sure you have the drivers installed on your computer and try to adb reboot recovery.
Hi there folks,
Hope someone can help me with this as I’ve searched high and low for answers on the interweb to no avail.
I tried installing the CyanogenMod 9 for AllWinner A10 tablets onto my cnmlifestyle table (a cheap tab shipped by the retailer argos).
http://forum.xda-developers.com/showthread.php?t=1760929
The installed failed as I’m getting the “encryption unsuccessful” screen after the initial boot.
I wasn’t too concerned though because I had successfully installed CWM recovery and created a back-up.
But now I can’t get back into CWM recovery?
I still have access to the device via adb but for some reason fastboot won’t work.
When I type “adb reboot recovery” the tablet boots quickly and goes straight into the CyanogenMod splash screen.
I can navigate around the device using adb shell so I’m assuming all is not lost?
Some background information:
The tablet is unsupported but I was pretty sure it was a clone of the Mediacom 907c or Gemei G9 so I used the g9_legacy-compatibility_vX.zip comp zip compatibility pack.
So can anyone suggest some means of either:
Triggering recovery from the PC
Flashing an alternative Rom from the PC using adb
Or getting fastboot up and running.
Any input would be appreciated.
Thanks in advance
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!
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I finally thought that this tablet did not have its bootloader locked. I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
- yo - said:
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I finally thought that this tablet did not have its bootloader locked. I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
Click to expand...
Click to collapse
This is obviously your own fault you should of unlocked the bootloader first before flashing twrp
Your device is basically bricked because u risked your device trying to flash twrp with a locked bootloader
Austinredstoner said:
This is obviously your own fault you should of unlocked the bootloader first before flashing twrp
Your device is basically bricked because u risked your device trying to flash twrp with a locked bootloader
Click to expand...
Click to collapse
As I said, the first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I spent hours searching about that and could not find it. Also, some people were saying that this device doesn't have a locked bootloader.
Is it possible to do anything in this situation ?
- yo - said:
As I said, the first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I spent hours searching about that and could not find it. Also, some people were saying that this device doesn't have a locked bootloader.
Is it possible to do anything in this situation ?
Click to expand...
Click to collapse
I don't know because I don't have that device
- yo - said:
Hi everyone,
I have retrieved a Samsung Tab 3.7.0 SM-T210. The OS was the old KitKat 4.4.2, very slow and buggy. I tried to flash a new recovery and OS and spent the 3 last days getting fails. I think I have read the all internet about this situation and would like to make a last try with your help.
When I got the tablet, I was surprised that in download mode it was indicated custom and custom binary and not official as it has not, I think, been flashed in the past by the people owning it. With HW rev 0x5 at the end.
The first thing I wanted to do was to unlock the bootloader, however, I could not find any option in developer mode talking about OEM bootloader, neither Auto Update. I finally thought that this tablet did not have its bootloader locked. I decided to go further with the flash of a TWRP recovery.
At the beginning the stock recovery was working. I am under archlinux, I have fastboot and heimdall. To do it as right as possible I installed a VM with Windows 10 and tried to flash a custom TWRP corresponding to the tablet with Odin. But the process got stuck at the SetupConnection step. I installed Windows 7 too, tried 5 different Windows OS, tried 4 different USB cables, reinstalled the USB drivers, tried 5 different Odin versions, tried different archives, just recoveries and all stock system. Still getting stuck at the SetupConnection.
I finally decided to try heimdall thinking that the VM could be the problem. With heimdall I run flash commands such as heimdall flash --RECOVERY twrp-3.2.3-0-lt02ltespr.img --no-reboot and got it doing something, the shell was saying it's 100% done and the tablet, in download mode, was showing a complete blue bar. Then, the recovery was just broken. Could not access it anymore, the Samsung Tab3 logo showing up and staying when trying to access it. I tried to flash some others archives, I opened it off and remove the battery for 5 minutes, still the same thing.
The operating system was still accessible and buggy, applications saying connection issues, etc. I did a factory reset from the running KitKat android OS and now have the Samsung Tab3 logo showing up and staying when trying to access it.
Now, I can only access the download mode and that's all. I have the impression that I am not the first one having these kind of trouble with this tablet. Is it a hardware issue on all these tablets ? Should I try something more advanced with heimdall, dd ?
Does someone have a solution in this situation ?
Thanks for your time and help.
Click to expand...
Click to collapse
There is a forum for this device.
Samsung Galaxy Tab 3
The Samsung Galaxy Tab 3, much like its predecessors, comes in three sizes, 7", 8" and 10". The 7" is powered by an Exonys 1.2GHz dual core processor, the 8" is powered by the Samsung Exonys 1.5GHz dual core processor and the 10.1" powered by a 1.6GHz dual core Atom processor. They run on 1GB...
forum.xda-developers.com
Did not know that. Sorry. I am going to post it under the right topic. If someone want to delete it.
So I grabbed a couple of tablets for a project. I might just end up using the lcd panels on a pi but, I'd like to try something with the tablets first.
Trouble is the android install is corrupted. Stuck on a failed update or something.
I can't get into android to enable developer options. So I can't root and flash through fastboot.
It tried to upload img but fails. I'm assuming as I'm not in dev mode.
What I'd like to do is enable bios/uefi so I can boot into x86 os's. (Linux)
I'm pretty sure hardware wise this uses the same motherboard as the Windows version of this tablet, that has bios options.
But first step is to get dev options enabled so I can run fastboot root and flash methods.
Sooo need to repair android.
Anyone know where I can find the recovery image to put on the sdcard to reinstall from droidboot?