[Q] RCA Tablet Need Help with Recovery - General Questions and Answers

Hi,
This is my first post on this website. I have owned a RCA Tablet (RCT6378W2 purchased on Black Friday from Walmart) for about 9 months now. Last night, while using it, it sort of stopped for about a minute. Then the screen had some lines on it, and the unit restarted itself. However, after this, it could not get past the RCA Boot Screen with the dogs on it. I tried leaving on this screen overnight with no success. Because the unit turns on and hangs on the boot screen, I figured it was likely a software or operating system corruption issue. Since then, I have figured out how to enter the recovery system v4.2.01 (holding volume + and Power). I have tried:
1. Wipe Cache Partition --- did not resolve problem
2. Wipe Data/factory reset --- seems to have been successful, but still not boot.
3. Apply update from cache -- there are no choices available to choose from.
It seems that unless I can find a way to make a self-booting SD card (is that possible?), then I am stuck with only 3 options (apply update from ADB, Update RKimage from external storage, and apply update from external storage). I have read many threads and websites, but have had no success. It seems that these are some of my obstacles:
1. I cannot seem to find a stock RCA rom image for this device. It appears that RCA has not made these available as other manufacturers have done. If you are able to find this, please send me a link!
2. I have tried to make a self-booting SD card using Phoenix Card, but can't find an .img that works with it. I have also tried using a generic sd card image and custom rom to install, but have failed at that. I have never rooted a device before or installed a custom rom.
3. I have tried looking for custom roms, but can't find one that is compatable with this tablet (seems they are mostly for the big name tablets). I have tried downloading Cyanogenmod for Nook Color (I heard this would work), but the recovery system does not seem to allow for any other firmwares to be installed (unless I am doing something wrong)
4. This tablet is not rooted, nor has the developer tool options been enabled (which I cannot do now that it doesn't boot)
Do you have any ideas? As stated, I am new to all of this, so please answer in detail if you can. Please help!

Related

[Q] I've tried everything and looked everywhere

Hey everyone, I'm using a GT-P5100 (3G + Wifi) O2 UK rooted tablet and for the last month it has been broken. It started rebooting itself randomly every now and then, and then suddenly it wouldn't even boot up for 15 seconds before it would restart itself again.
I am able to get into safe mode and I can get into the boot options, but when I factory reset it does nothing, I've tried from the boot menu, from safe-mode options and even from the dial up code.
I tried to connect my tablet to my PC as a media device and format it but that didn't work either; I can't connect it as a disk then format it that way because they took out 'mass storage mode' on this firmware.
I then tried to flash a stock ROM in Odin but every time I tried it would fail until I used Odin.v1.3, but guess what, it rebooted itself and my entire tablet is still exactly the same.
(the option was on AP ram in v1.3 not AP nand I don't know if that makes a difference.)
If anyone can point me in the right direction I would appreciate it so much. I have been trying for weeks to fix this and I just don't know what to do anymore, I tried on another forum but nobody answered me.
Everyone else gets replies and I get zilch; amazing. I don't know what it is that is preventing my tablet from wiping itself but it refuses to clear the current data no matter what way I try (ROM, factory reset, computer format). If someone could just tell me what that is and what I have to do about it that would be grand.
You mention "rooted " but you don't mention what current rom or past roms that you may have flashed, you could have some sort of rom cluster [email protected]$k going on in your tab but NO one else will ever be able to help because of lack of INFO or history.
Pp.
I standard rooted it from Odin. This is my first ROM I am trying to flash. I just need to know what would prevent a tablet from rebooting itself properly. Factory reset, format and flash is not working so I must assume that rebooting is the issue here.
If you are running stock rooted rom and having issues like this the only way out is reflashing the stock firmware complete (not just a rom) and see if that fixes it before you try any other roms.
If you can get into download mode thats the fix.
Pp.
To flash it completely do I need more than an MD5 file? (I also have the partition file for my model). Another question, if the tablet is having issues with the reboot after a flash, will updating from a microSD with a zip help? Thanks for the advice.

[Q] Decryption Unsuccessful Error - Cannot boot

I have a Samsung Galaxy tab 2 GT-P5110 which I had successfully installed CM12 onto. I decided to set up work email which insisted that I encrypt the device. I believe that the process completed successfully.
At that point I decided that I would like to flash the device with CM12.1. Restarted the process (Factory reset, Wipe Cache, Wipe dalvik cache) and flash the new CM12.1 zip file from external SD card.
I cannot now get to the recovery mode and the device doesn't always boot into anything recogniseable. The screen goes black and blacker! I have manaed to get to the CM logo and then a screen asking me for the PIN for the encryption. The next screen tells me that the PIN is right but the data is corrupt. It gives me the option to "RESET TABLET" but that really doesn't do anything and won't let me in to the recovery menu.
I can get into the Download mode and connect Heimdall up to it.
Is there anything that anyone can point me at that will help me to unbrick it?
I hope I've passed on enough information to help. It seems to me I need to somehow re-format the internal SD but I can't get to any menu that will allow me to do that.
Any thoughts anyone?
Ta
Fixed It
I seem to have fixed it. I flashed the CWM Recovery rather than the recovery that I had been trying to use and I got control of the device back. Not sure why that made a difference but this time the Android Robot came on screen with the 3D polygon rotating inside it and it seems to be running correctly now and updated to Android 5.1 ... Magic!

Problem with BlissPop: Stuck at "BlissPop is starting..."

Hello to everyone, posting this here as I don't have access to ask in the forum post for BlissPop - I.E fresh user
I'm having issues with my "recalled" shield tablet (wifi), I had it flashed to BlissPop successfully previously but when I tried reflashing it the other day I was met with a major roadbump: It just won't load the ROM.
The tablet freezes at the screen following the installing and optimization of each application - basically my screen is stuck at a small wall of text saying the following:
"BlissPop is starting...
Powered by Team Bliss
Starting apps.
Please wait for the optimization process to finish."
And before you ask, yes I have waited long enough (left it on through the night just to be sure - this thing won't load).
My procedure is as follows.
Bootloader is CWM and it is rooted beforehand.
1st off going into recovery mode.
#2 Wipe data/cache/dalvik cache - done
#3 Installed BlissPop via sideload, then gapps_pico afterwards (I've tried wiping cache+dalvik before installing gapps to no help.)
#4 Rebooting from CWM, here I've tried both allowing and denying CWM to "fix" root settings.
I've tried the first ROM I installed (when wifi/lte versions were available) and the newer releases - same problem with both.
After this I am met with this screen that won't budge, anyone got a possible solution to this issue?
Hey I just received my replacement tablet and was going through this process too. I did some digging around and found / remembered that having an external SD card socketed can cause this problem. So I powered my device off, removed the card and then rebooted without major issue.
Hope this helps.
I don't have any SD card in my tablet though, thanks anyways.
Did you format system?
If not then do format system/data/cache
Sent from my P4S using Tapatalk
Tried doing a format of system as well as data/cache/dalvik, still getting same result :/
Not sure its still helpful or not...i saw the xda thread regarding to this thread and whoever tried to flash the last zip got stuck at boot. So I'm guessing if you will flash a different one (by this time maybe they upload a new one) maybe you could get rid of it..
Sent from my P4S using Tapatalk
When I switched to BlissPop I had to format /data because TWRP was unable to wipe it. TWRP offers that option unter "advanced wipe". Might be the same with CWM.
any help my phone stuck on this boot loop and i dont know what to do now , any fix ? i dont wanna have broken phone i did everything that u guys said nothing works

A handful of problems after performing a factory reset

Hi.
I installed some dodgy app which required root access to operate (but it didn't even though I allowed it in SuperSu) and this is where my problems started.
First of all, I noticed each and every app I tried to run would immediately crash. That included system apps, such as the Settings app. At that stage I was left with only the launcher working and attempts to uninstall apps would also cause a crash. Even the shutdown menu was broken and the phone hung up so I was forced to reboot it by holding the power button for 10 seconds.
After that, the phone would no longer be able to boot, it was stuck in a boot loop, but recovery still worked (TWRP for that matter) so firstly I wiped the cache partitions (including dalvik cache) but that didn't help, as the phone still wouldn't boot. In this case there was only one thing left for me to try and that was the factory reset capability of TWRP which claimed to not even touch internal storage so I was fine with that and did the wipe.
Thankfully, the phone booted afterwards and it welcomed me with the first startup guide (the language selection dialog was really buggy but that's Huawei's fault) and the phone was seemingly ok, except that the whole internal storage had been wiped out but not only that - the external microsd card was empty as well! Could you believe that? I couldn't. TWRP promised not to touch internal storage and the external memory card wasn't even mentioned but why would it wipe it anyway?
That's for the story behind it, now for the actual problems I'm facing right now:
The stock remote app is gone
The boot animation has changed to a different one (now it's a silver "android" logo instead of the "honor" logo)
Battery usage stats are not available (see: http://i.cubeupload.com/BXCknW.png)
Sound quality from the built-in speaker seems noticeably worse
Hereby, I'm asking you guys to help me out with all of this.
The "remote app missing" problem could be solved by someone sharing their apk file with me, that's probably the simplest one to fix.
As for the boot animation, I have no clue as I don't even know what files are responsible for that.
The same for the battery stats problem, I'm already through a couple of full-charge-to-discharge cycles as well as wiping the cache partition, but the problem remains.
The sound quality probably has to do with the DTS sound enhancer. The config file for that is either "/cust/unicom/cn/xml/dolby_config.xml" or "/cust/unicomelectric/cn/xml/dolby_config.xml" and I'm asking you to upload these files somewhere so I can compare them with mine to see if anything is different.
The device I'm using is the H60-L02 variant running the B532 ROM.
Does the 3 buttons method erase internal storage as well? I've already set up quite some apps and having to do it again wouldn't be the most pleasant surprise. But at least in this case I could make some backups and whatnot...
Also, would it work if I flashed B535 straight away or does the 3 buttons method expect the same version which is already installed, in this case B532?
pudup said:
It will wipe internal storage. You can flash any *full* ROM as long as you're not moving up or down from kitkat-lolipop/marshmallow.
Click to expand...
Click to collapse
Okay, so I decided I'd do the whole thing today. I downloaded the full B535 ROM on my PC, backed up all the stuff I care about from the phone to the PC as well, and also I downloaded the MultiTool.
Though the MultiTool thread says this in bold red:
VirusPlus said:
EMUI 3.1 WARNING! Update over rooted or system modded in EMUI 3.1 gives a BRICK.
You have to restore system and REMOVE root before every update in EMUI 3.1 for now.
Click to expand...
Click to collapse
So I also fired up Titanium Backup in order to defrost all the frozen apps, which went fine, and then I wanted to unroot the phone but I've been unable to do so so far.
To unroot, I launch the SuperSU app, navigate to the "Settings" tab and select "Full unroot". The problem being, it just gets stuck on the screen saying "Uninstalling, please wait...". I don't know how long it usually takes to complete, so far I've waited for maybe 10 minutes and nothing seems to change. Should I care about that? Is that warning about updating rooted/modified EMUI 3.1 resulting in a brick still true?
Can I skip this step and just flash the stock recovery followed by the 3 buttons method?
EDIT:
After some trial and error with the multi tool and different recoveries, I was able to finally unroot. Next, I flashed the stock recovery for B532 and attempted to do the 3 buttons method, but it would say "Install failed. The update package does not exist" (could be because I'm doing the update from a USB flash drive as I don't have an micro sd card big enough to fit the package). So I rebooted the phone into system and used the Updater to perfrom a local update where it would let me pick the USB drive. It completed without errors and then rebooted into some kind of updater (black background and some bluish emui colors) where it also took some time to finish thankfully successfully. I can right now see the phone booting and for what it's worth, the boot animation is once again the good old "honor" logo and not that ugly silvery "android" one
And now it's "Optimizing system...". I really hope it finsishes successfully as it's already a bit late here and I wouldn't like the phone to be unusable tomorrow :laugh:
36% ready...
46% it's kind of fun to watch this, and now 49%
I'd like to thank @pudup once more for helping out, I'm not really that much into flashing recoveries, roms and all that myself. Without your help I would probably be too scared to try doing something on my own :crying:
86%, 89%, 95% and 100%. Aww, what a relief Good old stock lock screen and wallpaper.

lenovo a2109a-f Bootloop (can still access with fastboot and the bootloader..)

EDIT: title is incorrect, model is actually S2109A-F
Hi, I'm pretty novice but have searched a solid 2 days about this topic on this device.
The lenovo a2109a-f I recently got (I know, its like 4-5 years old, but for 40$, not a bad 9+" tablet) was in fine working order, but did have some bloatware. Feeling ballsy, I attempted a root, and now it boot loops, meaning it will constantly reboot and show the animated splash screen, and play the synthetic chime sound. Each loop lasts about 1-2 minutes.
Since I can still access the fastboot and the boot recovery I've tried the following:
1) attempt the install of a new rom (original ICS or JB for this device) from a micro SD card inserted into the slot
- no go, it says it mounts the sd card, but wont read from it
2) attempt factor reset (cache, factory reset etc)
- no change and same root file still shows up in the tablet "/sdcard/"
3) Rerun the flash recovery process
- Tablet seems to accept linux (from windows) commands via cmd (fastboot -i <address/commands go here>), but no change for the boot loop
4) attempted other recovery images in fastboot mode
- thought I actually damaged it more. Since it stopped boot looping but wouldn't even boot to recovery at all. I then flashed the original recovery ("CWM_S2109.img") and was able to get the bootloader back and the bootlooping behavior again.
My question for you all, is there something I need to do via the fastboot method to clear the cache of the bootloader, or the memory of the device and install the bootloader that way and hope it accepts a basic OEM rom? Again, I'm no programmer, but am able to follow instructions and would love to be able to fix my 40$ mistake here sometime. Thanks in advance for all your help. I've used a lot of your tips and resources here over the years and have learned a lot from your skills and experience.

Categories

Resources