Database Info

[APP] z4root - root android in one click from an app

Having trouble rooting your phone? This might be just for you!
Credits
z4ziggy
Sebastian Krahmer's rageagainstthecage
What this does
It is an app you install (currently you must side load it, but it will be on the market once it's had some testing here on XDA), that has a single button that will root your device. Should work on ALL Android devices -- please leave a note if it works or doesn't work on your device.
How safe is this?
Should be 100% safe - nothing on disk is changed besides the root binaries, so if something goes wrong, simply rebooting the device should fix up any and all issues. Let me know if you find any bugs!
{
"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"
}
Changelog
V1.0.0 : Initial Release
V1.1.0 : Will now open the application settings page if USB debugging is not enabled.

New version 1.1.0 uploaded with detection for USB debugging not being enabled.

This looks really cool! But, is it just a shell root? Not a nand unlock?

RyanZA said:
New version 1.1.0 uploaded with detection for USB debugging not being enabled.
Click to expand...
Click to collapse
It does not seem to work on my Archos 101 Internet tablet, it just reboots the device.
Edit: Busybox says it isn't rooted.

Will this do a Full root on X10 Mini Pro? just as this tool is suppose to do? Unfortunately that tool keeps looping even if I tap usb debugging for hours...
So Root and Shell Root and Superuser and allow non-market apps (thought that was just a normal setting in Android..)?

awesome app, I just did this on Sony x10, although I can't confirm that it installed busybox. I loaded it from the market and it didn't detect it.
Install on busybox 1.17.1 worked good

Thanks.
It started the process and rebooted, but hadn't installed Busybox, so downloaded it from the Market and it confirms the phone is actually rooted. Good start but far from perfect.

Does this work on the HTC Evo?

Any1 tried on the dinc???

Just use in unrevoked HTC devices are harder to root
CoryKalis said:
Any1 tried on the dinc???
Click to expand...
Click to collapse
Sent from my Incredible using XDA App

Worked great on my EVO.

Working on GSM HTC Hero 2.1 with original spanish Orange rom, AFAIK. The screen says "wait for root to complete and reboot your phone", stays there forever and after 1 hour I decided to go back. Rebooted manually and there it was, just downloaded Busybox from Market and working fine.
Its been the only working method for me, so saying thanks is actually less than needed.

partyman1971 said:
Worked great on my EVO.
Click to expand...
Click to collapse
Worked great on my Droid 2
Thanks so much for this.

Indigon said:
Worked great on my Droid 2
Click to expand...
Click to collapse
i have a droid 2 also and really wanting to root was this root way painless and is everything working ok?

reyrey2435 said:
i have a droid 2 also and really wanting to root was this root way painless and is everything working ok?
Click to expand...
Click to collapse
Everything works perfect on my Droid 2, fast and easy one click root like it says.
Been waiting for something like this, so glad I did it.
Opens a whole new world of great rooted apps and
getting rid of that unnecessary bloatware.
Remember to first enable (turn on) usb debugging: Menu> Settings> Applications> Development> USB Debugging
Kudos! Thanks again to the Dev!

I tried Superoeclick yesterday only my X10 Mini (2.1 firmware), which tells me the phone is rooted, but still won't allow me to delete apps
just tried this and it ran, rebooted the phone as it should but when I try to remove some apps it still won't let me
forgot too add, it didn't install Busybox either

It worked flawlessly on galaxy s jm1,
great app !
Sent from my GT-I9000 using Tapatalk

Works on DX! (Mine froze and required a reboot after the first try, but worked like a charm the 2nd go round)

petter11 said:
It does not seem to work on my Archos 101 Internet tablet, it just reboots the device.
Click to expand...
Click to collapse
Install busybox and see if it rooted it; where did you get a 101, I thought they weren't released yet...

worked on an og droid running frg22d
thanks

Captivate and a Hackintosh

Hey guys...I have a spare PC that I just converted to a Hackintosh. Everything went flawless with the install of OSX, but when I plug my Captivate in, it forces OSX to tell me I need to power it off and power it back on. I've tried this multiple times. I've even set the phone to have USB debugging on, and the same problem continues. Anyone have a suggestion?

Hmmmm
Ive never herd of this problem. It could be because its a hackintosh. I have a macbook pro and the captivate connects and does everything perfect. If you used a custom rom on the phone that can be an issue. It could be a bad flash. If you have stock then im not sure what the problem could be.
Sorry hope you fix this problem!

Probably not going to be much help but I have a hackintosh and my phone and PC play nice together
OSX is telling you the phone needs to be rebooted? Am I understanding that right? I can fiddle around and see if some settings make mine do the same thing

Are you using a pure vanilla untouched OS X build, or one of those crappy thrown together modded kernel deals.
Used to triple boot Windows, Linux, and OS X on my laptop before it fell off a table.

if you're running a vanilla build then it should work but you probably aren't. what version of OSX and what distro are you using? I suggest posting over at insanelymac since this is most likely a hackintosh issue.

How did you make your hackintosh? Feel free to PM me.
Ethere said:
Hey guys...I have a spare PC that I just converted to a Hackintosh. Everything went flawless with the install of OSX, but when I plug my Captivate in, it forces OSX to tell me I need to power it off and power it back on. I've tried this multiple times. I've even set the phone to have USB debugging on, and the same problem continues. Anyone have a suggestion?
Click to expand...
Click to collapse
Sent from my SGH-I897 using XDA App

seclm193 said:
How did you make your hackintosh? Feel free to PM me.
Sent from my SGH-I897 using XDA App
Click to expand...
Click to collapse
google can be your best friend.

I have no PC. I use XP with Parallels and Bootcamp, and It still is very finicky. Never had a Hackintoch but the newer Macs are Intel. Not sure where I'm going with this, but, yeah.

i dont have any problems with my captivate and my hackintosh. using the vanilla kernel.

Thanks for all the replies everyone. Here's the rundown:
I installed OSX directly following this guide:
http://tonymacx86.blogspot.com/2010/04/iboot-multibeast-install-mac-os-x-on.html
I am running Cognition 3.04 on my phone. And the minute I plug the phone into USB, this is what I see on the screen. This is not my computer, but it's an image I found on google images, but that's the exact error. I guess it's a kernel panic.
{
"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"
}
Doesn't matter if I have USB debugging on, or not. I've pretty much exhausted everything I can think of at this point, unless someone else has a suggestion. On my Windows computer, the phone is seen just fine btw...not sure what the problem could be.

Ethere said:
Thanks for all the replies everyone. Here's the rundown:
I installed OSX directly following this guide:
http://migre.me/3JFmQ
I am running... is not a phone issue but a hackintosh issue.
Click to expand...
Click to collapse

"Telling me to reboot" and "kernel panic" are two very different things.
Now it's definitely a problem for these guys:
http://www.insanelymac.com/forum/

Yeah, I posted a thread right on TonyMac's website too and they had no clue as to why that happened. Thanks for the link Mike. I'll check it out with them and see what they suggest.

this may be related
From the Heimdall ( http://www.glassechidna.com.au/products/heimdall/ ) FAQ:
What platforms does Heimdall run on?
Linux, OS X and Windows (XP, Vista, 7 etc.)
Although Heimdall runs on OS X all Galaxy S devices tested thus far contain a bug in the secondary boot loader that prevents the device registering itself with OS X. This may change if Samsung release an updated secondary boot loader.
Update: Samsung have released an updated secondary bootloader that corrects the issue. The correct bootloader is included in the official Froyo release. Obviously you have to get Froyo on your device somehow, but from then on it’s smooth sailing.
Note: Keep in mind if the version of Froyo you’re running is not official then the updated Sbl.bin may not have been included.

Hrm, you may have something there. I'll flash back to stock tonight and see if the Captivate works after that.

[Q] One click root not working

Tried running the program provided in this thread:
http://forum.xda-developers.com/showthread.php?t=1644167
I followed all the steps (there hard to mess up, haha) but when running the .bat it says root then this happens...
{
"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"
}
I'm so confused what am I doing wrong? I've tried in charge mode only and mounting the sd card nothing changes..
I've reinstalled the drivers, download the .zip again, reset my phone to factory. What else can I do?
EDIT: USB Debugging is enabled, I enabled it before plugging it in.
UPDATE: It's still not giving root access, I updated my sdk tools after this error still nothing

Enable USB debugging.
Sent from my HTC One X using Tapatalk 2

Make sure you have debugging enabled on your phone.

Sorry I forgot to add the fact usb debugging is enabled.

EDIT: nevermind... re-read your post again.

For some reason sometimes you need to enable debugging before you plug it in.

How long does the rooting process take from where it says "PUSH FILES"? It just seems to sit there for a few mins on my end.

For me it took like 5 min I wan say maybe les, just make sure u guys read everything and don't skip any steps.

So does this work for the at&t? Has anyone tried it?
Sent from my HTC One X using XDA

Your drivers aren't talking to adb. I had an issue yesterday, couldn't install the drivers to save my life. Installed SDK tools, still no go. Everytime I tried to root I got the same error as you.
Try this: Do all of the steps again.
This time, Kill the ADB process tree.
Now, hit the root file again. That may work. Some users are saying that adb won't work for them until they do this.

I've had similar problems on my atrix before. If I remember correctly, it seemed to help when I extracted root files to my desktop.
Sent from my HTC One X using Tapatalk 2

htcvarona said:
So does this work for the at&t? Has anyone tried it?
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Yes, the title of the One Click root says AT&T in it.

XNine said:
Your drivers aren't talking to adb. I had an issue yesterday, couldn't install the drivers to save my life. Installed SDK tools, still no go. Everytime I tried to root I got the same error as you.
Try this: Do all of the steps again.
This time, Kill the ADB process tree.
Now, hit the root file again. That may work. Some users are saying that adb won't work for them until they do this.
Click to expand...
Click to collapse
No cigar, was there 2 adb.exe processes running for you? At first one took me to htc sync so I uninstall sync. When I tried again killing one the other would just keep the CP open.
BBock9 said:
I've had similar problems on my atrix before. If I remember correctly, it seemed to help when I extracted root files to my desktop.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
That didn't seem to help either

Thank you to everyone that's trying to help, its still not working but I appreciate the community's help!

make sure HTC Sync service is not running

Pirateghost said:
make sure HTC Sync service is not running
Click to expand...
Click to collapse
I actually uninstalled it, Sync just didn't seem necessarily if its not supported by the HOX. Then again I could be having a driver issue and it just wasn't seeing the device in Sync. Would anyone recommend the first root method? I'm just running out of ideas...

droidnamedjakke said:
I actually uninstalled it, Sync just didn't seem necessarily if its not supported by the HOX. Then again I could be having a driver issue and it just wasn't seeing the device in Sync. Would anyone recommend the first root method? I'm just running out of ideas...
Click to expand...
Click to collapse
At this point, try it on a different computer if you have one available. That will quickly eliminate any problems that could be causing this on the computers end.
Sent from my HTC One X using Tapatalk 2

Have you tried copying all the files required for root to the c: drive on your computer and then running it from there via command prompt? also, i didnt see it mentioned, but what about running as admin?

BBock9 said:
At this point, try it on a different computer if you have one available. That will quickly eliminate any problems that could be causing this on the computers end.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Bazinga! I have no clue why my gaming rig wouldn't accept the drivers but my little brothers scrappy hp ran everything without a hitch! Many thanks!

droidnamedjakke said:
Bazinga! I have no clue why my gaming rig wouldn't accept the drivers but my little brothers scrappy hp ran everything without a hitch! Many thanks!
Click to expand...
Click to collapse
LOL. My 3K watercooled rig wouldn't install the HTC drivers, my GF's 600 dollar rig did it without a hitch. Glad to see you got it sorted!
I hate Windows.

[Toolkit] Wug's Nexus Root Toolkit v. 2.1.9

Unlocking, rooting, relocking and unrooting simplified! (and much more!)
VERSION 2.1.4 - This program will automatically bring together all the files you need to unlock and root your device in a few clicks, or flash it back to stock and re-lock it. You can also use this program to backup/restore all your important data, flash zips, set file permissions, push and pull files, install apps, generate logcats/bugreports, and much more! With the included file association options, you can perform tasks like flashing zips, installing apps, restoring android backup files, and flashing/booting img files with just a double click! The program includes a full featured interface for automating tasks in TWRP, enhanced restore features, an in-built auto-updater/notification system, ‘any build’ mode, advanced restore features,’NRT- Live Log’ for viewing the adb/fastboot cmds that are run in the background, quick tools utilities, and tools for taking screenshots/screen-recordings. All the latest official Android builds and Nexus devices are supported. The program intelligently and selectively downloads the files it needs for your device and makes sure you are using the latest files available. The program can even auto-detect your device and build. This release brings full Marshmallow root support plus all automated features by utilizing a new system that no longer requires modified boot.imgs. Check out the updated changelog for a more comprehensive breakdown of the feature set and changes in this release.
~ my goal for this project is make the entire process as smooth and simple as possible ~
{
"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"
}
Please read the FAQs before posting questions: http://www.wugfresh.com/nrt/faqs/
Looking for a walk-through? >> Excellent Instructional/How-To Videos: http://www.wugfresh.com/videos/
More information & Download Links: http://www.wugfresh.com/nrt/
Changelog: http://www.wugfresh.com/nrt/changelog/
Enjoy! ^_^
{{ WugFresh }}

Hey, great work! Have you ever thought about making a mac or linux port? I'd really love to help you make one!
Email me: [email protected]

I'm going to try this. I didn't have much luck using the other one-click out there. But this kit can restore to stock, so I'll do that and try this rooting stuff all over again.

Does this work with the new 4.1.1 on nexus 7?
Sent from my HTC Vision using xda app-developers app

everything works great except, I'm not going through with the root. I get stuck on fastboot mode with a message at the top saying "Booting downloaded image". But no action happens. fastboot is frozen and my computer has a message "Waiting for your device to finish booting up..."
Any idea what's going on? The kit worked really well unlocking and locking and restoring stock
I tried all of this on both 4.1 and 4.1.1 and get the same stuck screen results on the root feature, regardless of flashing CWM or not, just plain frozen

EVOXGSR said:
everything works great except, I'm not going through with the root. I get stuck on fastboot mode with a message at the top saying "Booting downloaded image". But no action happens. fastboot is frozen and my computer has a message "Waiting for your device to finish booting up..."
Any idea what's going on? The kit worked really well unlocking and locking and restoring stock
I tried all of this on both 4.1 and 4.1.1 and get the same stuck screen results on the root feature, regardless of flashing CWM or not, just plain frozen
Click to expand...
Click to collapse
Ok. That is strange. Add me on gchat and hit me up and I will try my best to troubleshoot with you to find out the cause of your problem.
{{ WugFresh }}

mintaeroboy said:
Does this work with the new 4.1.1 on nexus 7?
Sent from my HTC Vision using xda app-developers app
Click to expand...
Click to collapse
Man, that was quick.. I thought I was up to date.. lol.. development is never ending. I will push an update out asap. Looks like I need an updated Superuser. Can you do me a favor and try flashing this in Temp CWM recovery;
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Edit.. I just realized that you phrased that as a question. Try it out. It should work. No harm in trying. I included the latest SuperSU in the toolkit, and had success with it. So go for it.
Cheers
{{ WugFresh }}

WugFresh said:
Ok. That is strange. Add me on gchat and hit me up and I will try my best to troubleshoot with you to find out the cause of your problem.
{{ WugFresh }}
Click to expand...
Click to collapse
Same error here... Did you reach any resolution?

NZtechfreak said:
Same error here... Did you reach any resolution?
Click to expand...
Click to collapse
He did not get back at me, but maybe you can help me. Can you try replacing the modified boot.img in the toolkits data directory with this one instead: http://wug.rootxs.com/modified_boot_nakasi_4.1_JRN84D.img
So by default, you would place it here:
Code:
C:\Wugs_NexusRootToolkit.v1.5\data\modified_boot_nakasi_4.1_JRN84D.img
And then retrying the process. If that is it, I am going to feel very silly.
{{ WugFresh }}

WugFresh said:
He did not get back at me, but maybe you can help me. Can you try replacing the modified boot.img in the toolkits data directory with this one instead: http://wug.rootxs.com/modified_boot_nakasi_4.1_JRN84D.img
So by default, you would place it here:
Code:
C:\Wugs_NexusRootToolkit.v1.5\data\modified_boot_nakasi_4.1_JRN84D.img
And then retrying the process. If that is it, I am going to feel very silly.
{{ WugFresh }}
Click to expand...
Click to collapse
Heh, already got Root using the tried and true ADB method. Restoring stock so I can try and help you out

NZtechfreak said:
Same error here... Did you reach any resolution?
Click to expand...
Click to collapse
NZtechfreak said:
Heh, already got Root using the tried and true ADB method. Restoring stock so I can try and help you out
Click to expand...
Click to collapse
Thank you very much!
{{ WugFresh }}

Same thing
Will head back to ADB method as I actually need Root right now, but will try and help later if I have time and it hasn't been resolved yet.

NZtechfreak said:
Same thing
Will head back to ADB method as I actually need Root right now, but will try and help later if I have time and it hasn't been resolved yet.
Click to expand...
Click to collapse
I would really appreciate your help when you are available. I would like to get the resolved asap. My gchat is wugfresh at gmail, that would be the best way to figure this out if you have the time. I am certain the solution is simple. Thank you for your help so far.
{{ WugFresh }}

WugFresh said:
I would really appreciate your help when you are available. I would like to get the resolved asap. My gchat is wugfresh at gmail, that would be the best way to figure this out if you have the time. I am certain the solution is simple. Thank you for your help so far.
{{ WugFresh }}
Click to expand...
Click to collapse
Never mind.. I am pretty sure I know what the problem is. I will post up version 1.5.1 later today.
{{ WugFresh }}

WugFresh said:
Never mind.. I am pretty sure I know what the problem is. I will post up version 1.5.1 later today.
{{ WugFresh }}
Click to expand...
Click to collapse
Cool, will definitely confirm if your fix works, will do a guide for the blog/YT and would rather use your guide than ADB since newcomers won't cope with ADB.

Anyone have a mirror? Current one is down.

dEris said:
Anyone have a mirror? Current one is down.
Click to expand...
Click to collapse
It's down because the new version is up. Check the OP. Once I heard you guys having trouble here I knew something was up, so I have been at it all morning and got a fix now. Version 1.5.1 just released. Such an epic fail of a mistake, so small.. yet screwed up my whole root script. Now everything should work properly. Let me know if any of you still have problems.
{{ WugFresh }}

NZtechfreak said:
Cool, will definitely confirm if your fix works, will do a guide for the blog/YT and would rather use your guide than ADB since newcomers won't cope with ADB.
Click to expand...
Click to collapse
Cool. Thank you! I am pretty certain everything works now. I agree, sometimes people don't find cmd line utilities friendly, although to others they become second nature. My goal has been to make something as simple as possible, and try to explain it along the way.
{{ WugFresh }}

If it works, this should be stickied, so that noobs like myself know the best/easiest way to proceed (there are already a few guides and toolkits, but this one seems to be much simpler!).

For anyone on the fence...
THIS WORKS!
You will not find better or easier!

[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"
}