yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] PSCGOhio:
We've managed to get this rooted (see other thread) but now after an adjustment I made, mine's bootlooping.

I did a ton of digging and while there's no apparent ROMs out there, this is a generically made tablet under several brands and makes beyond RCA. RCA and Voyager (RCA Tab parent) claim not to have the ROM for downloading, but that makes no sense for three reasons:

1) How did my tablet know if I had the latest firmware version, etc? It had to surf somewhere and do a check, why can't that also be public or can anyone determine it and we can snag a copy ourselves to distribute?

2) What're they going to do with it if we send it back for 'repair'? I haven't found anyone who has but I'd bet if you tracked the Serial # it'd just be different and they bulk the bricked ones back to China for reloading and resale as 'refurbished'.

3) How exactly did this sucker get MADE? If you had the ROM to load it, hand it built for you, why can't you get it (and back to the updating issue)?

I've discovered this is a Gigabyte based setup, they have a similar model showing but that doesn't mean they made it either - just the hardware states that's what it is. We can't do a ROM that doesn't work on an ARM7 CPU, so the Intel Inside stuff's worthless.

Here's a China declaration about this unit:

We company SHENZHEN ZOWEE TECHNOLOGY CO.,LTD hereby declares:

The product model(s):

DPM7828,DPM7827,DPM7826,TM7005,TM7006,TM7008,NB7856,NB7866 is

identical in the same PCB layout, interior structure and electrical circuits with

the model M7054 which tested in Shenzhen Huatongwei International

Inspection Co., Ltd, the only differences are the model name for commercial

purpose.

The trademarks TMAX, APEX, DOPO, NOBIS, DAGE, NUVISION will be

selected by different customers owing to commercial requirements.

I looked up all those models and brands, again similar stuff but customized for their resale and none have a ROM anywhere that seems to be close!

So any further info you find, tag it onto this thread and if anyone can find a ROM that'd at least get back to access I'd be grateful!

I can ADB, but only sideload.

I can use the microSD, can even push a load to the tab with something on the card but can't find anything.

Have done the wipes, etc. and regardless it keeps rebooting over and over endlessly.

Last change I did was to make Titanium Backup convert to a System file and force it thus I think that's what it's doing and I can't stop it. I'm not that experienced enough with Android (vs. Linux and servers, etc.) to be able to get to and edit some files others have noted that might get me back to normal booting, but without anything but ADB sideloading that may be kinda pointless anyways.

Open to any ideas, thoughts and otherwise! This is a nice, basic tablet with some decent power for the price so if you're hear to just bash stuff or make stupid comments please look elsewhere. Hundreds of us are looking so the solution finder would be a hero!
[General Questions and Answers] PSCGOhio:
We've been discussing the root part of this here: http://xdaforums.com/general/help/root-rca-7-voyager-rct6773w22-tablet-t2954669
[General Questions and Answers] PSCGOhio:
Additional info on this unit from the other thread

Big thanks to another determined rooter/hacker on these RCA's!
[General Questions and Answers] PSCGOhio:
So far, no good...

At this stage it's just hitting walls and stuck in a bootloop. RCA/Venturer/ALCO 'support' is obviously screen-reading trained monkeys so you won't find help there. I've hit up the Hong Kong parent to see if I get really lucky, but everything I've tried is nothing but that bootloop.

I can add that I've found a ton of FCC filings by ALCO for this sucker including PDFs that show the insides, outside and everything they had to get US certified to import this specific tablet. The more interesting part of that is this thing HAS a CPU that includes WiFi, Bluetooth, GPS and an FM radio receiver! And they're simply just shut off for this version whereas the 'deluxe' apparently has software that turns these other features beyond WiFi on. Also, this tablet was submitted as a 1920x and NOT a 1200x resolution! So there's more hiding in there too, possibly limited in hopes the quad core won't overload. Also I'm seeing news of that CPU being clockable at 1.5Ghz and possibly 1.7Ghz naturally so there could be hidden speed inside.

The pics show a stock tablet, nothing fancy by any means and it looks like many others with just a case switch compared to some. So there are other versions out there, but it's not clear if the boot ROM is specifically and unchangably programmed with all these limits or if the bootloader can make changes if we hacked that up. I believe in my case I told Titanium Backup to make a move that fouled my bootloader up. My understanding now is that while the bootloader can be editable and get modified, the Factory Wipe/Reload only takes all the data files out and puts Android back to stock. Thus the bootloader IS NOT Android and that feature's rather worthless if yours is bootlooping or bricked til we get that figured out.

There is a backup, but so far loading one up may not work because it may not be signed. If someone can run a backup on an unrooted tablet and get it up here, testing on that can happen but the ones I've tried fail immediately. Some were for comparable tablets as well. The 'apply update' seems to only apply to Android updates which won't really take out the bootloop or a bricked one.

Open to any and all ideas, contributions and more!
[General Questions and Answers] PSCGOhio:
FCC files link (too big for here) of tablet

Use these links to get to the FCC files (PDFs) of the Interior (2), Manual and Specifications for this tablet!

Specs:

https://www.dropbox.com/s/sfag3332vw2ahgf/RCA Tablet FCC Specifications.pdf?dl=0

Manual:

https://www.dropbox.com/s/jik79ljfqwfrh0y/RCA Tablet FCC Manual.pdf?dl=0

Internal Images 1 of 2

https://www.dropbox.com/s/lrk9rcd6ov5alqu/RCA Tablet FCC Interal Images.pdf?dl=0

Internal Images 2 of 2

https://www.dropbox.com/s/75hkwijrqmaz60g/RCA Tablet FCC Interal Images 2.pdf?dl=0
[General Questions and Answers] Nate2:
Battery looks like a 1000mAh (or less). But it maintains pretty good (50% charge even after 3 days):
[General Questions and Answers] PSCGOhio:
It's said they underamped the battery to be cheap, but I've had the same results (when it was working) with longevity of the battery and that's with everything cranked up like the brightness, etc. to max. Standy's about the same, I can turn it on and leave it in sleep for hours on end and come back to a 60-75% charge. That's what kills me even worse that it's bootloped, I LIKE this stupid thing and loved using it! Hopefully we have a solution (another thread) and it may turn on other options hiding inside.

Big trick is the bootloader seems to be corrupted from the system app setting of Titanium Backup, so replacing it's the first hurdle. And as restricted as this tablet is for recovery booting, that ain't easy.
[General Questions and Answers] Nate2:
They might also have under-clocked the 1400 Mhz cpu (actual hardware spec) to 1300 Mhz to stretch battery life. But it is still faster than my 2012 Nexus 7 - http://xdaforums.com/showthread.php?t=2304369
[General Questions and Answers] QkTreasures:
Happy holidays ppl!!!! :sly:
[General Questions and Answers] PSCGOhio:
Actually we've found the Cube GT25/GT27 version of this (same tablet) has gone up to 1.7Ghz and 1920x1200 resolution so I'm dying to get back inside!
[General Questions and Answers] Nate2:
The U25GT looks fairly identical - http://www.cube-tablet.com/cube-u25...-tablet-pc-bluetooth-gps-fm-hdmi-1gb-8gb.html

The U27GT uses a different processor and has a 3G radio - http://www.cube-tablet.com/cube-tal...ore-android-4-4-bluetooth-phone-call-8gb.html
[General Questions and Answers] PSCGOhio:
Yep, my bad upon further digging;

The U27's are NOT the same and a different underlying MediaTek part that would cause issues with the ROM.

The U25 though, is an exact duplicate from the same manufacturer, the main difference being the outer case and the looks of the back with speaker holes, etc. Otherwise inside's the same from the docs I'm finding. That pic shows the HDMI port that we don't have, we're only missing the socket and the hole - the mobo's are duplicates. There's a GPS, FM and Bluetooth setup hiding in there to be released as well if we can and I've read others who have.

Still, the way mine's freaking out there doesn't appear to be a way to short-boot before the preloader or the dalvik cache to get a ROM in there or at least not an exact match from the RCA setup. The Cube may be signed differently and therefore not seeming to work.

I'm still after anyone who can figure that part out regardless of ROM, I hit up ALCO in Hong Kong and so far, nada. But I expected that too. At this point from what I've found on Androids, the core ROM portion that gets us to the Recovery only screen is hardwired but the NVRAM has the dalvik cache and the programming that cause the bootloop from some bad instruction/install. That could be modified, but we can't get shell ADB access to snag and push corrected files back. Far as I can piece together, there's 2 caches both the Dalvik and the running cache. When we factory reset and wipe the cache, we only get the 2nd one and NOT the Dalvik and that could be where the bootloop issue is.
[General Questions and Answers] xChowderrrx:
I read through all 15 pages of the other thread as well as this one in hopes that someone would've come along and figured it out, lol. My girlfriend, sister and I all got one of these for Christmas, with only one fully working, which I gave to my girlfriend. My sister's loves to reboot, and mine has been in bootloop since day one. It had occasionally pushed past the loop, but when it got to the initial setup screen Google Play Services would immediately force close 4 times in a row and then restart. I tried factory recovery a few times but to no avail and ended up getting frustrated and leaving it on the charger for a few days, hoping some magic may happen. I pulled it out again today and now it enjoys freezing on the black RCA screen. It has made it to the startup screen a few times but touch appears not to work. It feels like an electronic photo frame that I can't load pictures into :(

I'm super anxious for any sort of fix to come out because of how great this tablet seems it could be. Thanks for all your research!
[General Questions and Answers] PSCGOhio:
Sorry you're having the trouble! We've been trying to get this figured out and it's been frustrating. We HAVE rooted it in a variety of ways, but then you have to be careful with settings on the root tools afterwards not to send it flying into a bootloop.

The one that's rebooting, I'd return/exchange that! You've got 30 days if it came from WallyWorld, even online you can get a return form to print and take into a store (even though the price went up there, it's an even exchange). But that sounds fully mechanically defective, no doubt.

The one that's looping, yah that's just weird. They shouldn't do that and we've found a good percentage of them were damaged in shipping even though it wasn't obvious or defective and never tested in China. I believe some even just overheated in the container shipped over here as well or at least were banged around getting loaded and unloaded to cause some of this. If you can get a good one, never let it go!

Subscribe to at least this thread, we'll post more as we hopefully find some results!
[General Questions and Answers] Xactot:
I can do the backup. I'm guessing you mean through adb right?
[General Questions and Answers] PSCGOhio:
We're limited on ways to do it, so it'd have to be something that can be loaded through the Recovery menu.

In this case, there's a Backup and Restore option in that Recovery Menu that should work because the tablet won't know the difference (AFAIK). ADB will only work with sideloads and Updates. The lack of signatures to the 'update' you'd have to load via ADB, Cache or from the SD is why it's believed we're hitting the failures.

If you can run the Backup in Recovery mode and send that file, it'd be great! I believe it'll have everything you have so be careful of any personal data, etc. and PMing it or contacting me to send it by email is totally understandable to see if it'll even work. The only concern with a backup is that it may only cover the data portions that a normal wipe/System Restore would do and not fix the cause of the bootlooping and other errors some of us are getting.

There's instructions around here on doing a full ROM dump and turning that into an installable ROM that we would actually put in thru ADB or the other two methods, but no one's made one yet that's worked! LOL
[General Questions and Answers] Xactot:
I just finished the backup now. I'm not too worried about personal data since I just started using it. What's interesting is that it (for me at least) appears a the HTC Dream in under ADB Interface in Device Manager. Could that help figure out anything?
[General Questions and Answers] PSCGOhio:
LOL, well thanks! I hope it works! I always like to mention the fine print though so nothing bad happens. My backup didn't work because it was after I got the bootloop, so it would've just put it back. I'm just dying to get back inside, rootings easy enough now that we know how and the FIRST thing on the list is ClockworkMod so I have a real backup in the future! And, of course, not doing stupid things like I did. :)
[General Questions and Answers] Xactot:
I'm not even going to touch the idea of rooting when it comes to this tablet for the time being lol. I'll just stick to being content with my rooted EVO 4G until a recovery has been confirmed to work for sure. And yeah, I think it only covers what will be cleared by a Factory Reset; I have two of these tablets, one used one not. The backup size of the unused tablet is 82 MB while the backup of the used table is already 540 MB lol. I just uploaded the 82 MB one to my Google Drive and the link is below

https://drive.google.com/file/d/0B6Yc110W0bfmVlFNQzVhX0k4elE/view?usp=sharing
[General Questions and Answers] PSCGOhio:
So far, no good. It's hitting a 'checksum compare fail' and I've researched how to screw with that - none have worked either. But in that search I found mention that this is just the user data, not the ROM which would relayer what's causing my bootloop situation and others who've bricked theirs as well. Looks like we're going to need a proper ROM to shove in there to have a shot, but I appreciate this effort! At least we can rule this one out. It may've worked wiping out the rooted stuff, but the MD5 blockade's the situation.

Side note on that, I got into that file - blanked it even - still mismatch. Then I decided to go for the actual backup.

CHINESE. 100% string of pure language symbols, so no way to even see patterns in it to attempt to make an MD5 replacement! Gotta love China junk.

I have a ROM, but it fails on the signature from RCA. I think. Might be the MD5 but that just errors out instead of a mismatch, I may hack on that a bit.
[Nexus 4 Q&A, Help & Troubleshooting] xilefian:
This is a weird one;

I'm a developer so naturally all my devices are plugged in lying on the desk, this Nexus 4 used to be my day-to-day phone, I got it on release from Google Play.

Within the first two weeks I got it I was commuting on the London Underground and it was a crammed train, so I got squashed and my Nexus 4 was crushed, adding a crack to the top of the back of the phone, I was upset but didn't think anything of it as it was cosmetic damage, so I bought the Google bumper for it and I've been happy since.

Today, device lying on desk, I use it daily for work, lying on the desk plugged in, today I was testing the a website with the browser and then I put it down, pick it up again and suddenly the T on the soft keyboard doesn't work, it only worked when I turned it to landscape.

I got a touch test app and it turns out I have a dead vertical strip from the bottom of the phone to the top that completely covers the T key on the Google keyboard.

Incredibly annoying.

Called up LG, they were organising the in-warranty repair, then they asked if there is any other damage, I mentioned that there is cosmetic damage at the back of the device from January 2013, but the device has been perfectly fine until just a moment ago.

At this, the help guy said because it has damage it is no longer in warranty. Great.

Is there a known software fix for this?

Is the warranty really voided from cracks on the back of the phone?

Do I need to repair it myself?

Does Google Play have a service to handle this or is it all through LG?

I'm a bit annoyed as it happened so spontaneously, and this crack on the back of the phone has meant it's been out of warranty nearly since I bought it.
[One (M8) Q&A, Help & Troubleshooting] JWD1993:
Last weeks my phone time after time suddenly shuts off due to no battery left.

without even giving the usual warning popups.

Check the photo to see what happens.

Already did battery test, no unusual results.

also the factory reset didnt help.

How to solve this?
[One (M8) Q&A, Help & Troubleshooting] Bobbi lim:
It could be due to calibration issue. Try using your phone's battery all the way to 0% and it'll shut down automatically and turn it off to charge all the way to full and use it. If the problem still persists, there could be some issues with the battery but if the issues doesn't exist anymore, it could be calibration issue.
[One (M8) Q&A, Help & Troubleshooting] JWD1993:
more info

Check the photo's
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I've seen this happen (either to me, or reports by others) on just about every recent Android device I've owned (4 different devices), not just HTC, but Samsung as well. The battery seems to tank instantaneously, losing 30 or 40% of its charge or more, and the device shuts down. Doesn't usually happen often, just rarely. And some folks will probably never see it happen.

As mentioned above, I can only assume its a metering glitch. Just recharge the device (recalibrate the meter, if you like), and move on.
[One (M8) Q&A, Help & Troubleshooting] clsA:
found this somewhere a while ago ..it's worth a shot

I have also charged the phone to 100% reboot to TWRP charge to 100% then shut down and charge to 100%

all three locations monitor the battery differently. In fact TWRP sometimes showed 93% when the OS said it was full.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
I've never heard of button combos affecting the battery calibration, and it sounds like a placebo to me. I also think the trick of charging the phone while off was disproved as baloney, a long time ago.

All the meter needs to do is set "high" and "low" flags to corresponding voltages. I seriously doubt any button pushing will affect this. Let the phone charge to 100%, let it stay on the charge for a while to ensure any saturation charge. Then drain to close to empty. I don't personally advise to drain to shutdown. I understand its not zero voltage or anywhere close (more like 3V). But its also not good for the battery.
[One (M8) Q&A, Help & Troubleshooting] clsA:
Well the information come from the Android Forums ...it has worked for others
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Citing the source and providing details makes it sound a little less hokey. Still, probably impossible to say whether it really "works", or just a placebo.

Not sure what "coordinates and normalizes charging" if anything. But battery stats was debunked some time ago as something even worth wiping (since its wiped every time you charge): http://www.xda-developers.com/android/google-engineer-debunks-myth-wiping-battery-stats-does-not-improve-battery-life/
[One (M8) Q&A, Help & Troubleshooting] clsA:
yeah maybe the OP [MENTION=6262292]JWD1993[/MENTION] can test it and let us know
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Agreed. And thanks for the additional info, in any case.
[One (M8) Q&A, Help & Troubleshooting] JWD1993:
...

Tested it a few times last days.

when the battery dropped from around 40% to 0% (and device went off).

i charged it for about 10 minutes.

then dit the trick with the three buttons.

i was surprised to see that after rebooting the battery level was 35%.

Before i did the trick the phone showed 5%

But sad enough the device went off after 15 minutes..

and the percentage was 0 again.

This doesn't happen rarely.. it happens every day :(
[One (M8) Q&A, Help & Troubleshooting] clsA:
that's pretty crazy and at 10:10 at night ... do you work late or what happens at 10:10 PM
[One (M8) Q&A, Help & Troubleshooting] JWD1993:
Nope, most of the time im just checking social media.. or chatting at whatsapp
[One (M8) Q&A, Help & Troubleshooting] clsA:
I was referring to the time the battery dropped in the last graphic
[One (M8) Q&A, Help & Troubleshooting] JWD1993:
Yeah sorry, misunderstood.

Edited my post

And as you could see i barely used my device today..

so it should last a way longer than this after a half year of use
[General Questions and Answers] Pipe Smoker:
At first, greetings to all people here in forum, I just joined!

As title said, I have ZTE Blade Q Maxi.

(Sorry, I must have 10 posts to add links here)

Here is specifics:

NETWORK	Technology

GSM / HSPA

LAUNCH	Announced	2013, October

Status	Available. Released 2014, January

BODY	Dimensions	143 x 72 x 9.1 mm (5.63 x 2.83 x 0.36 in)

Weight	130 g (4.59 oz)

SIM	Yes

DISPLAY	Type	IPS LCD capacitive touchscreen, 16M colors

Size	480 x 854 pixels, 5.0 inches (~196 ppi pixel density)

Multitouch	Yes

PLATFORM	OS	Android OS, v4.2 (Jelly Bean)

Chipset	Mediatek MT6572

CPU	Dual-core 1.3 GHz Cortex-A7

GPU	Mali-400

MEMORY	Card slot	microSD, up to 32 GB

Internal	4 GB, 1 GB RAM

CAMERA	Primary	5 MP, 2592 х 1944 pixels, autofocus, LED flash

Features	Geo-tagging

Video	720p@30fps

Secondary	VGA

SOUND	Alert types	Vibration; MP3, WAV ringtones

Loudspeaker	Yes

3.5mm jack	Yes

COMMS	WLAN	Wi-Fi 802.11 b/g/n, hotspot

Bluetooth	v4.0, A2DP

GPS	Yes, with A-GPS

Radio	FM radio

USB	microUSB v2.0

FEATURES	Sensors	Accelerometer, proximity, compass

Messaging	SMS(threaded view), MMS, Email, Push Email, IM

Browser	HTML

Java	Yes, via Java MIDP emulator

- Active noise cancellation with dedicated mic

- MP4/H.264 player

- MP3/WAV/eAAC+ player

- Document viewer

- Photo viewer/editor

- Voice memo/dial

BATTERY	Li-Ion 2000 mAh battery

Stand-by

Talk time

MISC	Colors	White

I have another problem:

I Install AppMgr III SD2 to my phone. Try to move movable items on SD card, but, I received a message that the phone does not support the option of switching to SD. Try install few another applications Appto SD2, I have same problem - still don't work,

Please, if anybody know, is there exist program with whom I switched already installed applications on SD2? Is there any procedure? Supposedly Android Studio doing this job, but, honestly, I do not know what I have to download and what should I do.

I cordially thanks if anyone might be able to give me instructions, or brief instructions how to transfer already installed applications on SD2.

Thanks,

Igor
[General Questions and Answers] TheLastStego:
You're going to have to root your phone in order to be able to do that then.

Doing a little bit of reading, others have had success with Framaroot. which can be downloaded here:

http://xdaforums.com/apps/framaroot/root-framaroot-one-click-apk-to-root-t2130276
[General Questions and Answers] Pipe Smoker:
Thank you for answer, TheLast!

I download and install latest Framaroot, after that install Super SU, click Boromir, reboot device, but nothing happened? Did I miss something? Start framaroot again, he's offering me just instalation. :(
[General Questions and Answers] TheLastStego:
It should have worked fine. Have you tried downloading a root checker to confirm if you do or do not have root? A simple play store search for "Root checker" will provide you with plenty of choices.