Database Info

[Q] Possibly Bricked XT720?

Any help or guidance is greatly appreciated here.
I was helping my friend with his XT720, we first rooted it with Universal Androot, then, tried to partition the SD card with GParted. I thought I had it correct (the first partition was 6.5Gb and FAT32, the second was about 1000mb EXT2, and the third was 128mb linux-swap partition). We then attempted the optimizer script and had nothing but issues. Every time I tried the apps2sd it would give an error, something about the partition extension. So we tried slightly different partition layouts and everytime no luck. Apps2sd still failed every attempt, so we gave it one last try at this and we managed to get Busybox to install, cache-sd, optimized build.prop, (apps2sd still failed) but then when I went to install JIT for Froyo, the phone screen went black..we let is sit for a while and nothing. So we pulled the battery waited a few minutes and put it back in, it went to the all black screen with the Moto symbol.
Thats where we left off. I'm kinda shocked at how any of these steps could have lead to a bricked device and hoping someone can point me in the right direction as to how fix this.
Since I never installed rom manager (is it even compatible with the XT?) I cant just restore from nandroid. Is there a way to get this to factory restore or push a recovery image from adb? I heard RSD lite might be able to help me, but I'm not too familiar with it at all (yet).
Any help or guidance will be greatly appreciated! Thanks in advance.

flash back to stock rom using rsdlite. theres instructions somewhere on this forum

Search for recovery mode. Something like you have to hold in the volume up & the camera mode button while powering up. Clear the data & cache (possibly a few times) & then reboot. If that doesn't work the RSD lite should.
HTH

Thanks for the help guys. So from what it sounds like, it is in fact not a brick and very fixable?
Ill be attempting this shortly.
Sent from my HTC Glacier using XDA App

Also, any advice on how how to partition the SD card for apps2sd?
Sent from my HTC Glacier using XDA App

civicvx94 said:
Also, any advice on how how to partition the SD card for apps2sd?
Click to expand...
Click to collapse
If you have a Linux box around, it provides the best solution. I booted into my Linux partition, put my SD card into the reader slot, and fired ''gparted''. First I shrunk the existing fat32 partition which was occupying whole 8G to 7. So no data is lost. Then create another primary partition of size 1G (whatever left) to ext2 (and format it). No swap needed. Works like a charm, done in 5 minutes, no data backup/restore necessary (though advised).

If you are on a windows machine, you can use MiniTool Partition Manager Home Edition. All partitions have to made "Primary" and the fat32 one to be "Primary" and "Active".
The partitions made by this tool were recognised by both apps2sd and app2card(didn't have to repartition) apps...

Well I successfully restored the device with rsd
I don't have Linux, however I do Gparted live on a CD that I can boot from, so I got that part covered.
Ill attempt the different partition layout mentioned and see if I have better results.
Do I enable Apps2sd with the optimizer script again or is there another method? I'm just hesitant to use it again since I had to restore after last time..
Sent from my HTC Glacier using XDA App

The script is what I used. I've seem some talk of an app called something like "app2card" (not on the market). There is an similar script on the driodformums.net website. It has a customized script for the CBW SBF. That's the one I ended up using, when I tried the version on this forum it kept errroring out at some point. They both do similar hacks (from my limited understanding) so I'm not sure what the problem was.

civicvx94 said:
Ill attempt the different partition layout mentioned and see if I have better results.
Do I enable Apps2sd with the optimizer script again or is there another method?
Click to expand...
Click to collapse
Just ensure that your partition matches the script's assumption. Like the script assumes /system is mounted from /dev/block/blahblah06, the ext2 partition of the SD card is /dev/block/mmcxxp02 ... if yours are different (mine was), edit install.sh accordingly before running it.

I'm having almost the same issue. I feel stupid. Tired after work. Blah!
I tried a similar app and transfered all my apps to the sd card. Partitions are fine.
For some reason my apps were not working though, and I tried some "fix" that started fixing working system apps on my internal memory. Now I only get it to boot the motorla logo.
I got into the repair options and cleared cache but same thing.
My wife has a nexus, I'm wondering if I can swap out the sd card or something. Checking out this thread. I have RSDLite. But I never flashed the rom or anything that I know of. Just rooted.
Time to read more!!!

civicvx94 said:
Well I successfully restored the device with rsd
I don't have Linux, however I do Gparted live on a CD that I can boot from, so I got that part covered.
Ill attempt the different partition layout mentioned and see if I have better results.
Do I enable Apps2sd with the optimizer script again or is there another method? I'm just hesitant to use it again since I had to restore after last time..
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Could you please explain how you restored with RSD? I think something is still on my SDcard or I trashed an app / resource it was trying to fix (App2card)
Phone just stops at motorola logo even after clearing cache / doing reset (holding button combo)
Thank you!

Could you please explain how you restored with RSD?
Click to expand...
Click to collapse
First you have to download & install the USB drivers from Motorola & the original SBF (needs to extracted) from HERE, then power your phone into bootloader mode (I think it was hoding in the volume down & shutter button while turning on the phone). Now when you run RSD you should see your phone in the device list browse to your SBF & start the process. It takes about 10 minutes but when your done your phone should be in a "fresh out of the box" condition. Also I should note that I couldn't get RSD to see my phone on my Win7 64 laptop but it worked fine on my XP machine.
HTH

This is bricked???
guys my phone suddenly stard like this....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
do you think is bricked???
any idea how to fix it???
it just happen when i plug in the battery.... without any combination bottom... on the phone....n my RSD Lite 4.9 did not detect my phone....please guys...help me....

[Q] need help my xt720 briced
guys my phone suddenly stard like this....
any idea how to fix it???
it just happen when i plug in the battery.... without any pushing combination bottom... on the phone....n my RSD Lite 4.9 did not detect my phone....please guys...help me....

Cool, my phone is seen.
Is there a way to save everything? I don't feel comfortable flashing with something from online.
I'm going to see if I can fix it. I tried to "repair/re-install" a system app / resource .apk
I'd like to try and fix it before I flash. I hope even though my phone is not booting past the logo, that I can "save" itin it's current state.
Thank you!!!

reboot it into download mode
hold in the volume up & the camera mode button while powering up
then the RSD will detect it

I had try to reboot n get inro the flash mode but my computer still not detec even i had up grade my driver... (
Sent from my Milestone XT720 using XDA App

What operating system are you using?

Cbw sbf...
Sent from my Milestone XT720 using XDA App

[Q] Is my Galaxy S i9000 Bricked?

Okay so i had my phone rooted for fun and had no original purpose of installing CM7 on it before i read about a thread that displayed that it was a safe method to do according to what was wroten.
The phone (Galaxy S i9000) 2.2.1 Android was however, what i think is "bricked".
The phone starts with a simple picture showing me a phone with a dot-frame going to a triangle (warning sign) and further to a computer screen. Does this mean that the phone is bricked or is this something else?
The phone does not respond to:
Adb (android-sdk) throught CMD (windows 7 32 bit)
Kies
Odin
Droid Explorer
Android Control 1.3
The phone was originally modified with Odin 1.7 and failed after pushing the ROM into the phone. According to what i did, i did everything correct according to what was written in the explenation.
Please answer as quick as possible, otherwise i will try to get out the warranty which i doesn't even have anymore.

This screen means in fact that you are "nearly bricked" but some kind of emergency system is running what should act like the download mode (as I know it from my SGT). I had similar problem and after a bunch of work I found out that it was the USB driver from Samsung. A simple click in the Samsung Kies Software to re-install drivers helped me and I was able to normally flash a new Kernel, Rom, whatever. I guess you have a sync software as well (as well Kies?!), or try uninstalling drivers manually. Might work. May be worth a try.
Edit: Even with broken drivers it seemed that it was working with Kies... sync (with comlications, broke my calendar app after restarting tab after sync), storage mode, everything but no adb and such.
Sent from my GT-P1000 using XDA App

I know tried to:
Re-install Kies completelly
Removed drivers (manually)
Turned of the phone: ripped the battery out
Put it back in
Re-installed Kies (no phone connected)
Kies 2.0 Successfully installed
Re-install drivers throught kies
Checked that the phone was off and repeated step: 3
Put the usb cable in and begged to the god of nerds
Profit? No...
Kies didn't even find any device that it could try to connect to. Neither did any of above written softwares. The pc cant communicate with the phone.
Tried: 3-button-combo: lots of times!!
Adb prints: No device found
Odin: No device
Kies: No device
DroidExplorer: No device
Note that i live in Europe.

Guess you have a nice 450€ brick then... but as I am more a semi-noob than a semi-pro I am not qualified to tell you this as a shure fact... just an opinion...
send from my SGT with Overcome...

I contacted the company that sold my phone, got the number for Samsung Support, they redirected me to the company "Mobilbyrån" which will re-install and make sure my phone starts working as usual for 45 £. All thought i could done it with a jig on my own, but i rather trust a professional company to do this for me in exchange for my warranty (billing only guilty if warranty denied).
According to "Mobilbyrån" or translated "Phone Agency" this is a ordinary errand and that it's highly possible that this will go on my warranty that is still guilty for atleast 8 more months.
Solution for my problem would be to:
1. Build a Jig to hardware boot the phone into download mode
2. Enter Odin and push a new rom inside (preferebly a stock (android))
3. flash kernel (could be done before 2?)
4. Profit

I guess there is no way, even for Samsung, to find out if there was a third party Rom etc is installed as device refuses to do anything. You are only f*** up if they are still able to read out current data somehow... but 45£ is really a fair deal...
send from my SGT with Overcome...

Sucks to hear that about your phone. I have a similar model and I managed to CM7 working. I followed a tutorial on this website and I semi-bricked it too at first although I've never had the same problem as you regarding Odin not being able to locate the phone.
Can you tell me the steps you took in trying to flash CM7 on it?

Also, refer to this topic to see if it can be of any help: clicky

It was when i were to use Odin the second time.
I managed to flash the speedmod kernel into the original Android ROM (stock). I also managed to install one of the zips that were to be installed throught recovery. But after this (when connecting to Odin) and this was the step where only one of the checkboxes (F.Reset Time i think).
So i made this and the Odin 1.7 told me: "Failed" or such. And i then got paniced, i disconnected the phone since i was so frightened something had gone bad, the phone was turned of and i reset the battery (in and out) and started the phone to notice that image (as told above).
Now i thought: Yeah, lets just reset the phone throught recovery and were kind of happy by the thought of it. So i tried to access it with the 3-btn-combo but as i just remembered is that in Europe this is patched to be removed.
So i thought, lets send a adb shell to the phone throught Android-spk and i connected the phone and sent the command: Adb wait-for-device, nothing happened and the phone couldn't be found by above said softwares.
So i thought: "Hmm... this isn't good"... So i started googling for what reason this could be and i believe it's called "Semi-bricked", that is "Almost" bricked phone.
So i were sad, called Samsung Tech support and they told me to contact "Mobilbyrån Stockholm" who were a tech repair support, they wanted either 45 £ or my warranty insurance if i wanted the phone fixed. I thought... yeah right, so i sent my phone to the company and i am now waiting for what they are about to do with it.
I suppose a jig would work, thought no one i know got one and i have poor skills at constructing electrical or related components so i put up a thread (like this one) at Sweclockers.com and found a guy that had one which he could lend for me, super, just have to wait and see what happens.
I suppose this "Jig" method could work, but will the computer really notice my phone as a device? It doesn't do that now, thats why i am asking.
At all moments i used Terminal for Android phones (throught market: Android Terminal) by sending commands (since 3-btn-combo didnt work):
> "Su" <- needed for Superuser allowance for controlling the phone
> "Adb reboot recovery"
> "Adb reboot download"
And the phone starts with this picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, in that correct order.

Random restarts, factory reset and bootloop

I tried using the MIUI ROM http://forum.xda-developers.com/showthread.php?t=1538234 and switched back to XXKPQ (Was using XXKPQ before installing MIUI) now after a months time, I'm getting random restart and bootloops and factory resets. Anybody got any idea what's going on?
Update: I updated once more with XXKPQ using Odin but I'm having a bootloop. But if I CF-Root it, it works fine.

Umm.... it may be some thing wrong with the rom not the hardware, so, you may format the "system":
recovery mode => reset factory => yes => wipe catch => yes => storage and mounts => mount system => format system => yes.
you will have nothing even to boot, so, power off and go to download mode and flash the XXKPE (with pit) and then flash XXKPQ using ODIN.
*Note: you may backup all your data in the internal sd, you may got all of it formatted!
You should have a totally clean rom now with no remains of the old flashed roms.
At last, you may wait another one -more experience than me- to fix the problem before trying mine

For questions, either post it in the respective qna thread in the general section or create a new thread in the general section so that this would not pollute the development section.
Cheers
Sent from my GT-i9003 powered by Stable and Smooth CleanKpu rom

iwih said:
Umm.... it may be some thing wrong with the rom not the hardware, so, you may format the "system":
recovery mode => reset factory => yes => wipe catch => yes => storage and mounts => mount system => format system => yes.
you will have nothing even to boot, so, power off and go to download mode and flash the XXKPE (with pit) and then flash XXKPQ using ODIN.
*Note: you may backup all your data in the internal sd, you may got all of it formatted!
You should have a totally clean rom now with no remains of the old flashed roms.
At last, you may wait another one -more experience than me- to fix the problem before trying mine
Click to expand...
Click to collapse
Thanks a bunch for your help mate. The problem is now solved and my phone is back again to normal. I was unaware of mount storage>format system trick. Anyway thanks for the help.

Sadly, the problem is back and I don't know what to do.

Hello,
Anybody?

did it happen to flash miui again?
or is it happening right now on stock?
cozif its happening clean stock ... you could be suffering hardware issues

Its happening on a stock XXKPE. Hardware issue? What kind of hardware issue?

motherboard

I guess I have to dump this crappy phone. My nokia e71 was much much much better.

StanleyJes said:
I guess I have to dump this crappy phone. My nokia e71 was much much much better.
Click to expand...
Click to collapse
Just don't buy Samsung products unless its their best product. If not go to HTC or LG or Sony. Buy the right ones
Cheers
Sent from my GT-i9003 powered by Stable and Smooth CleanKpu rom

Here is some more details how the phone reset and restart itself ( I used a time lapse cam). The notification bar will display "SD Card removed unexpectedly" then shows, preparing USB storage and it restarts!
I remember once I used a memory Swap to SD script using CWM which actually swaps USB storage and SD Card. I don't know why the script still conflict with my phone even though I did a clean install with XXKPE (using Latona PIT) and later with XXKPQ. Earlier, under USB storage it was showing External SD contents and now its showing internal SD. I'm attaching an image after I removed my external SD
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My Internal SD and External SD card has been swapped!

I wouldn't know if it's the switch external-internal sd card script because I've never used it... But you could try flashing your region's current firmware and bringing the phone in for repairs. Definitely sounds like a hardware issue. If they ask you if you modded anything, just say no. lol

My phone was shipped with froyo arabic rom. Forgot the name though. I guess I have to try that. I forgot the firmware name

noypi_ako said:
motherboard
Click to expand...
Click to collapse
I confirm. It's a hardware failure. It happened on my 9003 (warranty)
The only way to fix it, is replace the mainboard.
(Italy user)

StanleyJes said:
My phone was shipped with froyo arabic rom. Forgot the name though. I guess I have to try that. I forgot the firmware name
Click to expand...
Click to collapse
Go to sammobile.com register and go to gt-i9003 asia.There you'll find the firmware for your region
Sent from my GT-I9003 using XDA

Sorry for bumping this old thread. I got my Galaxy S repaired. I was completely under warranty and Samsung replaced my motherboard. And yes the restart is caused by a hardware issue and there is no other fix other than to remove/replace the internal SD card holder. I'm lucky that the new motherboard I got is having a whooping ~12GB internal SD (~2GB Earlier)
Once again, thanks for everybody who helped me out

submodel
i9003 have many sub-model.
We can identify MB by internal memory (4GB 8GB & 16GB) that's sold on different area.
latona PIT upload from 8GB or 16GB MB(I guess), mean it's not fit to your 4GB MB.
Surprise is "Samsung service center can't find out this problem".
I want to explain more, but my English can't made you understand.
i9003L sell in South America

[Moto G: 1st Gen. LTE - XT1045] Blank screen altought functional.

First of all, thank you for reading my post.
I'll try to point out what is going on right now iwith the phone (never saw it happen, ever).
Phone boots but shows a blank (black screen with faded light in the corners) after booting.
After several tries, found out that the 4G is on and receiving notifications (LED is blinking waiting for my response ) and I'm receiving calls nonetheless, so it is working but I can't use the screen.
The screen IS FINE, the boot shows up properly, the fastboot menu shows up properly, sometimes the icons and widgets shows up where they should be, the "Shut down" button shows up properly.
What seems to be the issue is that the upper tray with the time, data, and other things, and the down one with the "◁ ⭘ ▢" menu doesn't shows up AT ALL, so I just receive a blank screen.
Also, the computer isn't finding the phone even if it is connected through the USB cable.
I'm acessing the "Whatsapp" app in the computer right now, which requires the phone to be online and with a internet connection, meaning that the apps are functional and something really weird is happening.
The phone was working fine until last afternoon, just blanked moments after I got out of my house (when I first noticed the issue).
So... anyone willing to crack heads with me trying to figure out what the hell is happening here?
I'll provide pictures soon.
Thanks in advance!
:highfive:
EDIT1: seems to show this "Unfortunately System UI has Stopped" from time to time.
EDIT2: https://youtu.be/AS-wv0NB-g4 (recorded the issue) the 58s shows what i'm talking about.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Most likely a firmware issue
xtragen said:
First of all, thank you for reading my post.
I'll try to point out what is going on right now iwith the phone (never saw it happen, ever).
Phone boots but shows a blank (black screen with faded light in the corners) after booting.
After several tries, found out that the 4G is on and receiving notifications (LED is blinking waiting for my response ) and I'm receiving calls nonetheless, so it is working but I can't use the screen.
The screen IS FINE, the boot shows up properly, the fastboot menu shows up properly, sometimes the icons and widgets shows up where they should be, the "Shut down" button shows up properly.
...
Also, the computer isn't finding the phone even if it is connected through the USB cable.
...
EDIT1: seems to show this "Unfortunately System UI has Stopped" from time to time.
EDIT2: https://youtu.be/AS-wv0NB-g4 (recorded the issue) the 58s shows what i'm talking about.
Click to expand...
Click to collapse
Most likely a firmware issue - may be a corruption has developed or could be an incompatible app update (Google Play Services or your launcher?) . Are you rooted? You haven't indicated what ROM you have installed (Stock, custom ...?). Is the recovery stock or custom? Can you enter recovery? Does everything look as it should in recovery? If custom, do you have a recent backup and have you tried running it? The 1045 is the US version I believe - are you sure it's not a 1040 (Canada/Brazil)?
Your best bet may be to install/flash another ROM, either stock or custom. Check out lost101's or vpnair's threads for stock firmware for your phone - they've done an excellent service by providing these ROMS and they are great. I've used both at different times to overcome some issues - may be the best way to go at this stage.
Good luck --- S.

Something caused and error in your firmware, you have to do the following:
1.- Try to backup your files. See if you can connect it to the PC and explore the files from there.
2.- Once backup is done, you have 2 ways:
A) Unlock bootloader, then flashing TWRP recovery, then installing a custom ROM like CyanogenMOD or AOSP.
B) Search and download the stock firmware file, extract the files, and then flashing it to your phone using mfastboot excecutable.
You can find the files and the info here in XDA thread, just do it carefully and read instructions.
If you can't find something say it and I can help, but won't spoonfeed you.
Good luck.

sdembiske said:
Most likely a firmware issue - may be a corruption has developed or could be an incompatible app update (Google Play Services or your launcher?) . Are you rooted? You haven't indicated what ROM you have installed (Stock, custom ...?). Is the recovery stock or custom? Can you enter recovery? Does everything look as it should in recovery? If custom, do you have a recent backup and have you tried running it? The 1045 is the US version I believe - are you sure it's not a 1040 (Canada/Brazil)?
Your best bet may be to install/flash another ROM, either stock or custom. Check out lost101's or vpnair's threads for stock firmware for your phone - they've done an excellent service by providing these ROMS and they are great. I've used both at different times to overcome some issues - may be the best way to go at this stage.
Good luck --- S.
Click to expand...
Click to collapse
Stock and yes, 1045.
I've fixed the issue by restoring the phone through the fast boot (but lost all my data because I couldn't create a backup at all).
Case closed, thanks.

moralesnery said:
Something caused and error in your firmware, you have to do the following:
1.- Try to backup your files. See if you can connect it to the PC and explore the files from there.
2.- Once backup is done, you have 2 ways:
A) Unlock bootloader, then flashing TWRP recovery, then installing a custom ROM like CyanogenMOD or AOSP.
B) Search and download the stock firmware file, extract the files, and then flashing it to your phone using mfastboot excecutable.
You can find the files and the info here in XDA thread, just do it carefully and read instructions.
If you can't find something say it and I can help, but won't spoonfeed you.
Good luck.
Click to expand...
Click to collapse
I'll migrate to the Oneplus 3 soon, but just so you know, I'll root the phone later on, couldn't find the cause of the problem and had to wipe the phone in order for it to work, so that's it, case closes. Thanks.

Good to know ...
xtragen said:
Stock and yes, 1045.
I've fixed the issue by restoring the phone through the fast boot (but lost all my data because I couldn't create a backup at all).
Case closed, thanks.
Click to expand...
Click to collapse
If you run into the issue again at any point, your apps and some data can be backed up to your Google account. Additionally, it is worth rooting your phone and installing Titanium Backup (free) available on Play Store to back up all your data. Once rooted, make sure you backup your phone through recovery and copy the contents on your phone over to your computer from time to time, particularly the recovery backups and the Titanium backups. If you haven't created backups on your computer of all your phones folders in the internal and external divisions on your phone through a USB connection, another solution, in the event you lose USB, is to take out your SD card, insert it in a card reader and create matching folders for both internal and external (SD Card) on you computer and copy all the contents over directly from the card.
Takes a little time but backups can save your ass when needed.
S.

[TWRP][ROOT][STOCK ROM] RCA RCT6773w22 v38

BRING BACK A DEAD RCA TAB
Time to set the scene. I had a stock rca tab laying around so I found the thread to a discontinued project on here. I flashed the files and could not get it to boot again. Stuck in an awesome two dog logo. Yay. So after searching a couple days for the stock files I ran across someone comparing this tab to the Cube u25gt-c4y. What do I have to lose. I searched and found the stock files and bam! I had a chinese tablet. Surprisingly it works with just a few flaws. After flashing you will see a nvram error in the wifi. Easy fix. Adb seemed finicky at first but straightened itself out. Screen rotation is also 180 degrees out. You have to tilt it down and lock the rotation. Lastly you have to change the language to english because the default is chinese. Will be trying to get the gps and fm radio working soon.
Step 1.
Install Sp Flash Tool if you have not already. There are many posts on this so I wont repost them.
Step 2.
I used the "Format and Download All" option. I have read dont do it on some threads but I have seen others that said to.
If you want TWRP then rename the file to recovery.img and replace the one in the roms file.
Step 3.
Use Kingroot 4.96.apk and then grab the Super sume to replace the kingroot with SuperSu.
Installing SU from twrp when it asks works fine.
That should be it and now you have a working tab again.
As always USE AT YOUR OWN RISK!!! Nothing to risk though if your tab is already a brick.
Thank you to all the posts I searched to get my tab back working.
https://mega.nz/#F!PY1ExBLB!fns00mTE-hvXsz6sdXdVaA
For the Wifi Nvram WARNING: ERR 0x10 https://forum.xda-developers.com/showthread.php?t=2730486

ADB FIX
So after installing this rom you may have a problem with the adb working. Originally I had this problem and I'm not exactly sure how I repaired it. I believe I had installed multiple "MTP Enabler" programs. After reinstalling I had the problem again and this time found the fix.
Code:
1. Open /data/property/persist.sys.usb.config and change to mtp,adb
2. Open /system/build.prop and add/edit these lines.
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
3. Reboot your phone and wait for the drivers to install. Enjoy.

Installed Wrong Preloader?
Luckily for us we can just open Sp Flash Tool with the correct files then push and hold the Power + Vol Up with the usb connected. After approximately 30seconds it should allow flashing.

jeffmoss1999 said:
So after installing this rom you may have a problem with the adb working. Originally I had this problem and I'm not exactly sure how I repaired it. I believe I had installed multiple "MTP Enabler" programs. After reinstalling I had the problem again and this time found the fix.
Code:
1. Open /data/property/persist.sys.usb.config and change to mtp,adb
2. Open /system/build.prop and add/edit these lines.
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
3. Reboot your phone and wait for the drivers to install. Enjoy.
Click to expand...
Click to collapse
Is your device still working?

leetree2001 said:
Is your device still working?
Click to expand...
Click to collapse
Yes. So far I have found it's hard to kill this unit. I don't have the original firmware but have it working with this firmware where it is usable. Like I stated the worst thing is the screen rotation but all u have to do is lock rotation and it's fine.

Thanks for your response. I have two of the rca6773w22B I will give a try later And post later

leetree2001 said:
Thanks for your response. I have two of the rca6773w22B I will give a try later And post later
Click to expand...
Click to collapse
This is not for the w22B just the w22.

Understand your warning. But had these under the coach
For about a year. And nothing else has poped up on the
Old inter web. Soooo,either this or the trash they go.

I have the 22B version also
leetree2001 said:
understand your warning. But had these under the coach
for about a year. And nothing else has poped up on the
old inter web. Soooo,either this or the trash they go.
Click to expand...
Click to collapse
did this work????

Did it work?
leetree2001 said:
Understand your warning. But had these under the coach
For about a year. And nothing else has poped up on the
Old inter web. Soooo,either this or the trash they go.
Click to expand...
Click to collapse
Im having the same issue looking for a rom for my Voyager 2
Did that sulution work for the w22b version?

Yay my tablet is bricked. Thanks SP flash. frickin crashed

My tablet no longer turns on after I tried SPFlashTools, it started DL process and then timed out. If I connect to windows computer, it makes a connect sound but does not do anything, neither responds to SPFlashTools anymore. Any Idea ?

jeffmoss1999 said:
BRING BACK A DEAD RCA TAB
Time to set the scene. I had a stock rca tab laying around so I found the thread to a discontinued project on here. I flashed the files and could not get it to boot again. Stuck in an awesome two dog logo. Yay. So after searching a couple days for the stock files I ran across someone comparing this tab to the Cube u25gt-c4y. What do I have to lose. I searched and found the stock files and bam! I had a chinese tablet. Surprisingly it works with just a few flaws. After flashing you will see a nvram error in the wifi. Easy fix. Adb seemed finicky at first but straightened itself out. Screen rotation is also 180 degrees out. You have to tilt it down and lock the rotation. Lastly you have to change the language to english because the default is chinese. Will be trying to get the gps and fm radio working soon.
Step 1.
Install Sp Flash Tool if you have not already. There are many posts on this so I wont repost them.
Step 2.
I used the "Format and Download All" option. I have read dont do it on some threads but I have seen others that said to.
If you want TWRP then rename the file to recovery.img and replace the one in the roms file.
Step 3.
Use Kingroot 4.96.apk and then grab the Super sume to replace the kingroot with SuperSu.
Installing SU from twrp when it asks works fine.
That should be it and now you have a working tab again.
As always USE AT YOUR OWN RISK!!! Nothing to risk though if your tab is already a brick.
Thank you to all the posts I searched to get my tab back working.
https://mega.nz/#F!PY1ExBLB!fns00mTE-hvXsz6sdXdVaA
For the Wifi Nvram WARNING: ERR 0x10 https://forum.xda-developers.com/showthread.php?t=2730486
Click to expand...
Click to collapse
What version is this Android OS?
Also: I can't have access to wifi.rar fix file. Where is it?
I am also looking around for stock rom RCT6773W22 (no additional letters or numbers)

I've installed all possible drivers for this tablet.
I physically inspected the USB charging port was not bent and (internally at circuit level) everything is connected, nothing is loose.
When the tablet is off, the device is not seen. But the screen of the tablet shows it is charging from the PC normally.
Windows 10, then proceeds to chime "device disconnected" sound.
If I turn on the tablet, I ask for ADB DEVICES and the tablet is not recognized at all. The tablet stays at logo boot loop.
Maybe I need to install something so the hardware of the tablet grants access to adb commands?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}