Database Info

Xoom Wifi "Failed image LNX 0x0002 / RSD mode 2"

Hey everyone. I figured id make an official thread,although a thread a few down is very similar but still quite different.
I attempted to re-lock my XOOM wifi and I got the error.
-only able to get into RSD mode 2 or Fastboot protocol
-pc will not recognize through adb or RSD 5.0
-tried various command and no luck
-Screen wont turn off unless battery dies.
- reinstalled sdk, drivers etc.
I might of missed a few details, but ive been all around the forums and have yet to see a solution for this other than send it to Motorola. Ha just curious to whether anyone could shed a little more light on this situation. Not being able to RSD or adb seems like a bad situation, even if we did have that darn sbf id still be stuck! Thanks guys!
Sent from my DROIDX using Tapatalk

Try to get the xoom back into fastboot by rebooting (vol up + power) and then immediately holding vol down + power until the fastboot screen comes up. From there try pushing system and boot .img's through fastboot. Then you should be able to reunlock from the fastboot command on your pc. There is no way that I know of to re-lock a wifi only xoom as of yet.

Yeah, my bootloader screen says that im "Starting Fastboot protocol service" but I get no response from my PC. I've never had problems with adb recognizing my xoom before this. Its like the drivers arent even compatible with the device anymore?? For craps i attempted to send some commands through adb even though it didnt recognize the device, and had no luck. ADB simply replies "waiting for device" for all of them.

try reloading your moto drivers

Make sure you aren't using a front panel port. I had thus problem for ages, XOOM is a power hog. As for the LNX failure its the result of relocking with an invalid image, don't do it.
Sent from my HTC Desire using Tapatalk

Yeah, i spent days trying to figure that one out with the front ports vs. the back ports with my droid. I could never get it to remount in RSD when flashing a .sbf.
Thanks for the heads up though. Im not sure what made me think that it would be ok. My failure to do some research always lands me in pretty much the same spot! Here.
I reloaded all the drivers ect and have been unable to get anything. My droid works great, but no xoom.

Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)

Xezuka said:
Had this exact thing happen to me today. What fixed it for me was
- boot into fastboot (Power+Vol Up then immediately hold Vol Down until you see it display the fastboot message) and push the stock boot/system images found all over this forum for your model (Wifi/3G)
Now obviously your ADB isn't seeing your device... neither was mine
- Go under Device Manager on your PC and uninstall your Motorola drivers from whatever devices are listed
- Do a fresh install of the Moto Drivers and restart your PC
- Run, 'fastboot oem lock' to allow RSD to do it's work
That's what it took for me. If that fails, unplug your Xoom from the PC and set to debug mode, then plug back in and let Windows find your drivers. Windows could take some time, and actually took me unplugging/replugging twice until it decided it found them.
RSD is a load of junk, but when it works it's like the miracle worker =P Good luck and keep your head up! These things are harder than people think to completely wreck =)
Click to expand...
Click to collapse
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?

This is the same of my problem:
http://forum.xda-developers.com/showthread.php?t=1052762

tritran18518 said:
Just curiousity, if we can't boot our xoom, how can we enable USB debug mode?
Click to expand...
Click to collapse
Sorry I guess I didn't mean to set it to Debug from the Xoom, but as in to remove it and boot into Fastboot. Then plug it back in and allow Windows to install the drivers.
I had a hard time getting it to work, but after uninstalling and reinstalling the drivers, it recognized it and allowed me to flash the SBF.
Correct me if I'm wrong here! It's what worked for me. My Xoom went down like this and I resurrected it this way. Been working flawlessly on Tiamat 1.3.1 ever since.

Sorry guys, but the condition I'm in is becoming popular lately. I'm able to get the XOOM wi/fi to show "starting fastboot protocol" but absolutley no recognition on the pc. RSD or ADB. Therefore all commands sent from the ADB simply respond with "waiting for device" and unable to flash any images onto the device. Its in a real brick mode. At least for the time being with the lack of software communication on the pc and no .sbf yet. I sent the device into motorola for repair. They said the repair would be under the warranty and free of cost. I was honest as well, telling the repp I had unlocked the device and attempted to re-lock. Thanks for all the suggestions and input guys.

follow up?
hello i am curious what happened with your returned brick? did moto replace it?
I ask because i have the exact same issue and have gone through all the suggestions.
same error, cannot get into fastboot, no adb, no RSD, nothing. tried the various vol power button combos etc. no recognition on PC at all. yes i re-installed drivers etc etc etc... i have been reading...
it seems only option is to wait on SBF or return?

Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny

OK well its good to know I am totally screwed!!! thanks for the reply...
I told the rep on the phone what I did but I don't think he had any clue what I was talking about... he asked to me to reboot with vol up, then try to boot into fastboot, but didn't once say fastboot, just said vol down, then said he would send me a shipping box.
Get it today!!

I am in this situation after trying to re-lock in order to install the 3.1 update. I tried re-installing and updating the Moto drivers, rebooting etc but I can't get my PC to recognise the device in fastboot or RSD. I am on a stock Canadian ROM (but unlocked obviously).
I have sent an email to Motorola and been honest with them. Will see what they say.

That's the thing - moto provides all the tools to relock for US ONLY! There is no official way for canadians, which makes no sense. So us canadians can unlock no problem, but cannot relock, yet US units can? Strange to me...

chaz03 said:
Yeah the only solution would be an sbf flash. But even with that i do not know how because the RSD lite does not recognize the device either.I simply placed an order online, they sent a box the next day, sent it and got it back in two days. Extremely fast. I told the tech rep over the phone that i had unlocked the device and and then downloaded an app that starting causing for restarts and so i attempted to re-lock the device and from there it was officially a true brick. I was honest and they seem to be very understanding. Im sure they understand that the lack of support for the device is evident and we are all beta testers. SO let em know whats going on. I also let him know i was a developer, whether it mattered or not i dont know, but i was just being honest. Its all covered under warranty he said. I didnt pay a penny
Click to expand...
Click to collapse
Try rsdlite 4.9 or earlier it should see it then.

I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App

footboydog said:
I tried RSD 4.9 and no luck. I think it just doesn't work with Wi-Fi only zooms.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.

crushsuitandtie said:
Anyone who locked the zoom back and now can't boot, try my instructions from another thread...
1) Turn the xoom on and leave it plugged into USB. 2) When it says Starting RSD Mode 2, type the following in your command prompt in windows "fastboot oem unlock"
*Make sure you are typing these commands within the directory where your fastboot and .img's are located. ( I dropped mine in C:\Android-sdk\platform-tools\*The Xoom will not respond initially and your command prompt will say "waiting for device".
3) Hold the power button and volume up to reset the xoom. The fastboot command should intercept the xoom booting and take you to the unlock prompt again. Follow the on screen instruction.
*This will wipe the device again, which I'm assuming you did when you locked it with a custom kernel (boot.img)
After it is completed, type "fastboot reboot" in windows command prompt or just reboot however you can.
Click to expand...
Click to collapse
I have just tried this and still no luck. Fastboot just sits there with the "waiting for device" message and the Xoom just boots with the "Starting RSD mode 2" message. I also tried your suggestion with rebooting into fastboot mode by holding the vol down button and that doesn't work either.
BTW I don't have a custom boot.img. I am on a stock ROM but I just had the bootloader unlocked.
Incidentally I have tried RSD lite 4.8, 4.9 and 5.0 now and none work.

[Q] Can't unbrick. Tried nigh everything.

Greetings! First of all, I would like to thank anyone who takes the time to help me diagnose and resolve this issues, let alone anyone who takes the time to read this thread.
I've been having issues with my Xoom (ICS 4.0.0) for about 3 weeks now.
A brief history of the issue's occurrence:
-I unrooted the device and returned it to stock.
-Everything was fine and dandy until one day it spontaneously said something along the lines of 'Android is upgrading..', and then performed a reset.
-Since resetting, it bootloops.
The device only turns on when plugged into a charger and hard reset.
The device only turns off when allowed to boot loop for minutes and then hard reset (it simply does not reset, and just turns off).
I'm not the most technically-savvy person with android devices but here are some things I've done/noted.
When trying to use adb commands, it does not recognize the device or properly issue commands.
I've tried wiping data/clearing cache to no avail.
EDIT: I've tried fastbooting, but the bootloader will not unlock. When trying to unlock, it simply resets and then acts as though it was never unlocked.
I have no idea how to return it to a stock image. All I know is that I have a micro-SD and some spare time.
Could anyone help me understand what exactly is going on with my Xoom?
If I can provide you with any more information, please let me know.
Thanks again. (=

If it was stock and spontaneously upgraded it sounds like a bad OTA upgrade. I've been rooted from the start so never have taken an OTA upgrade...don't you need to accept it or can it just upgrade on it's own?
Anyway, can you get it into fastboot mode?
Volume up and power, then at dual core screen, press volume down...if you see something like "entering fastboot mode" you're not bricked. You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
If you haven't done so, just google 'recovering Xoom using fastboot' and you should get some good information.
Good luck!

Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools -
http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
As Always If This Was Helpful Hit the Thanks!

Yeah, what Mjamocha said...

okantomi said:
Yeah, what Mjamocha said...
Click to expand...
Click to collapse
LOL Thanks.

okantomi said:
Anyway, can you get it into fastboot mode?
Click to expand...
Click to collapse
Yes, I can. But so far nothing has been successful in terms of fastboot commands.
okantomi said:
You do not have to re lock your bootloader. Just make sure you have downloaded the correct stock files for your Xoom model to your PC and flash it.
Click to expand...
Click to collapse
When I try to execute fastboot commands such as 'fastboot flash boot boot.img'.. it says the following:
Device still locked. Device must be unlocked first. Failed to process command error(0x8)
Whenever I try to unlock the bootloader, it appears to be successful at first and then the device reboots. But it just reboots to a bootloop, and the bootloader still says its locked. Perhaps I made a mistake in communication. The bootloader is currently locked and will not unlock, as just described.
When I try to unlock it and it reboots, even if I access the fastboot menu right away, it still says the device is still locked.
Thoughts?

Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.

slacka-vt said:
Can you get into recovery? With the Xoom off (to make sure it's really off, hold volume up + power for a few seconds), hit the power button and when you see the M logo, wait a very brief moment (like a fraction of a second) and hit the volume down button. When it says "recovery" on the top left, hit the volume up. If you can get in there, either restore a nandroid (if you have one) or do a factory reset.
Click to expand...
Click to collapse
Yes, I can get into android recovery. However, within a second of switching into recovery mode, the robot falls down and there appears to be a red triangle caution sign containing an exclamation point.
When trying to do a factory reset, it says all data is wiped (as normal). Upon rebooting, it continues to bootloop. So essentially the factory reset and cache clear options in the Android Recovery menu do not produce the expected results.
Pretty odd. I didn't mess with the Xoom at all prior to this issue.

Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.

slacka-vt said:
Try flashing just a recovery img to hopefully get your recovery working again. I think you can flash a custom recovery even if the bootloader is locked (i could be wrong but worth a shot) I attached the Rogue "recovery-rogue-1.3.0.img". Try a "fastboot flash recovery recovery-rogue-1.3.0.img"
EDIT: Sorry, I guess you can't flash a custom recovery with a locked bootloader.
Click to expand...
Click to collapse
Yeah, just tried it to no avail. Thanks so much for your help anyway. (=
I'm not sure what to do now.

I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.

slacka-vt said:
I would keep trying to unlock it using different USB cables and different USB ports on your computer. I've had unlocks fail a bunch of times and for some reason, it was because of a $hity USB cable and/or a bad port on my computer.
Click to expand...
Click to collapse
I hear ya. I've tried 2 different cords and 3 different computers. I'm using a Mac (10.6.8) right now, but have used 2 PCs (Vista + 7).

Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?

slacka-vt said:
Out of curiosity, when you tried to flash the custom recovery, did you get the same "device still locked" error or did it appear to flash but then recovery failed?
Click to expand...
Click to collapse
I got the 'device still locked' error. Weird, huh?

How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.

slacka-vt said:
How about trying to lock it again even though it says it's locked -maybe it's stuck in an "in-between state"? Try a "fastboot oem lock" and if it finishes then try a "fastboot oem unlock". I know, I'm grabbing at straws here. I thought I bricked my Xoom last week. All I did was an "adb reboot bootloader" and the device went to a black screen. Volume Up + Power did nothing. I ended up buying a T5 (Torx 5) bit at the store, removed the back cover and disconnected the battery for 30 seconds using a piece of paper to separate the contacts. The Xoom booted right up after that.
Click to expand...
Click to collapse
Yeah I tried that. Won't lock or unlock successfully. Locking produces no difference, and unlocking produces the same 'device still locked' error. This is getting out of hand! Thanks so much for your advice. You think I should open it up?

I hate to be so persistently annoying about this, but could anyone possibly suggest a method of working around the locked bootloader?
Is there anything I can do with an SD card to remedy the device's stubborn foolery?

I think you should give it a try, I have bricked my xoom a few times and have always been able to flash the stock imagine to recover. You really have nothing to lose by pulling the battery pin just be careful.
Sent from my Xoom using xda premium

I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?

cherlamperter said:
I don't know if I'm technically-equipped enough to do that. )=
Sounds easy, but I imagine it would be rather easy to screw something up? Essentially what I should do is unseat the battery, right?
Click to expand...
Click to collapse
I have looking for a utube how to guide but no luck, I just might make one for you so you will know what to expect. Give me a few and I will get back to ya.
Sent from my Xoom using xda premium

help- bricked it, no recovery, what now?

Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...

Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
The only way to download the stock rom backups is to remove the sd card from your phone, plug your sd card into a PC or other device with a card reader, download the stock backups, and place the stock backup rom files on your sd card. Finally place the sd card with the stock backup downloads into your phone.
These backups and information on how to go through this process can be found in this thread on page 2: http://forum.xda-developers.com/showthread.php?t=2001226
The key is to make a backup of your existing rom with twrp and then move the stock backups from your sd card to the twrp/backups/yourdeiceserial/ directory. That creates a backup directory which twrp knows to look for backups in.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Once unlocked flash the custom recovery of your choice (I like twrp). You can boot into custom recovery by holding volume up and the power button from a powered down state. Here is the link for instructions on how to flash twrp:
http://forum.xda-developers.com/showthread.php?t=1887070
Then you can download one of the stock backups for the Q posted in the development section and restore them using the custom recovery. Most of the ones I have seen have been compatible with twrp.
Don't feel bad, I've been in that state several times since getting the Q, live and learn.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
If that does not work you could drop it in water or something. You have not officially unlocked boot loader so you still have warranty. Or you could just tell sprint it quit working and act completely clueless. At least its bricked with warranty still intact.

matt2k12 said:
Hey yall. I had the phone for 6 days before I bricked it. I am wondering if there is any stock recovery mode or anything or what I shsould do? I think something went wrong due to using the root toolbox pro app. I have done some backups within the ap as well as Titanium Backup but now the phone will not boot up and I dont know if/how to put it in factory recovery mode. Soft reset does nothing. The Motorola logo will show on startup but then the screen just blacks out forever, not off, just colored black.
A few details, the phone was rooted with Motofail2go, with no recovery and bootloader still locked as far as I know.
Should I take it to Sprint for a factory reset? Is this even an option? What are my other options?
Next time I will probably use the Moto unlock key so I can open the bootloader all legit like and have a recovery mode...
Click to expand...
Click to collapse
Both of the methods above are very effective. When I had the first photon I bricked it and just dropped it in water and did a claim. Depending on the insurance you have that way may cost you $100. The other method should work. When I first got this phone I did the exact same thing and to go back and unlock then flash twrp and in stall a stock backup someone had posted.
Sent from my XT897 using Tapatalk 2

UnicronAlpha99 said:
Try holding power button and the down volume key to power off. Once you power off press and hold them again. This should boot you into fastboot, Motorola's adb shell basically. This can take a couple tries, make sure the phone is powered down completely before hitting volume down and power button to get into fastboot. If you can boot into fastboot you can unlock using this guide: http://www.droid-life.com/2012/08/20/how-to-unlock-the-motorola-photon-q-bootloader/
Click to expand...
Click to collapse
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.

Hi again yall. You know once I got to thinking about it, I decided to check out the return policy on Amazon Wireless. They will accept any device under warranty for the first 30 days and it is up to Moto for the next 11 months of warranty coverage. They email me a packing label and it ships out 1 day and they ship out the new phone 1 day shipping. Hard to beat, just takes 2 days of shipping and some more fun times with my Epic, 10.1CM style, in the meantime.
Who's to say it wasnt some sort of hardware or software glitch that bricked the phone rather than my screwing around? Nobody knows and it isn't up to the consumer to prove his innocence. I bought everything legally, all the apps at the app store, and only ran the motofail2go root method. Wasn't running any custom Roms, Mods, or anything. I don't feel bad after they got me for another 2 grand for 24 months, and since I have been with Sprint for 10 years;l I have spent well over 10k or 15k with them lifetime.
If any other method pops up between now and when I ship it out I may give it a shot but if not, ah well, capitalism.

matt2k12 said:
Thanks for the response. Is there anything extra extra special about getting into factory fastboot mode? I can't seem to get it done. Is there an official set of instructions anywhere? Does the phone need to be plugged into the PC? It was always my understanding (for the last week) that Power and Vol Down was the soft reset mode which reboots the phone. Therefore it always tries to reboot in normal mode. This is what keeps happening. It never powers completely down using this method.
Anyhow, once I follow your instructions, the Moto logo appears, no Sprint logo appears, the phone "powers on" but the screen is blacked out (not off). After waiting for a while at the blank/black screen, or holding down several buttons like vol or camera I get the first attachment: "Process system is not responding. Would you like to close it?" When I wait nothing happens. When I push OK nothing happens. By chance, I held down power during the notification and the power menu came up behind the ANR notice (second/third attachments). So obviously there are some things working but the main system isn't booting up. And either factory fastboot is nuked or I can't figure it out. When I power down from this accessible power menu and try to do the fastboot (Power / Vol Down) I still havent gotten it to work.
Any other ideas before I take drastic measures?
Since I bought it from Amazon would that be my best route for return or should I go thru a Sprint store?
Thanks in advance.
Click to expand...
Click to collapse
Try using adb. If your computer has drivers on it for phone you might able to get into fast boot. If that does not work I would try Sprint store first. Have locked my phone up several times while hacking wife off in progress and have used adb every time. Only time i have been truely scared is when i soft bricked my nexus 7. had to stay at work for two hours after i got off to get it to recover because i was scared of her lol.
---------- Post added at 02:05 PM ---------- Previous post was at 01:57 PM ----------
If you get adb to recognize device you could take chance and officially unlock boot loader. Then flash twrp. There is a thread in general section about having trouble getting official update. It has a stock recovery in it. Trick would be moving files to recovery section of twrp

I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app

UnicronAlpha99 said:
I have gotten the phone to soft power down and get into fast boot and custom recovery. It's a bit tricky with timing, I usually wait for the screen to go black after soft reset, let go, and immediately hold power and volume down. If you can not boot into fastboot I honestly don't know what you can do either than return the phone.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.

I don't blame you, it sounds easier to exchange in your case any way. The main suggestion I have is if you are getting into any type of build.prop or operating system tweaks that have potential to lead to boot loops or cause the phone not to boot, then unlock the bootloader and install custom recovery.
The Moto-fail method seems limited to only be able to run apps that require root. For me this has no use as I want to be able to have complete control over all aspects of the Android OS. There is not a huge mod community for the Q as yet but I believe Cyanogen will be a reality as Interloper continues working on it. I came from an Epic with Cyanogen and soft-bricked it a minimum of 50 times. CWM was very forgiving on that phone, the Q is a lot more finicky and frustrating.
If you have insurance through the carrier then you are going to pay $150 for a refurb if something goes wrong and you hard brick the phone. If you unlock bootloader and install custom recovery then you have a fail-safe in the form of nandroid backups and restores. Then you can mod away with little fear.
Good luck on the new phone and I hope you don't give up after six days of modding with the Q!
Sent from my XT897 using xda app-developers app

matt2k12 said:
Thanks for the help Unicron. I think Brandons method might be my only alternative... but you know what? I already have the box packed up to ship back to Amazon! I am still a noob; I dunno if I could go the distance on this one. I have been updating my Android SDK files since I got the phone but I never got it to recognize boot up thru ADB fastboot. disclaimer* I havent tried it in a couple days since all teh SDK updates completed.
I dunno though I am a big time DIYer when possible. If it werent for the massive amount of tape I put on the box and packing label I would already be trying this method. I can't convince myself just yet. Amazon makes it too easy. I could have the *new* phone by Friday. Then I wouldn't be wasting my remaining work week trying to hack into my personal Christmas present in order to make it function...........................................
Edit - Yes I'm impatient. My job is too demanding and I am trying to set a good precedent for 2013. Wasting the first 3 work days on a phone is not how I intend to start off the year. There is probably a valuable lesson to be learned from this as far as hacking experience and to be honest with the responses here I think I could get it to boot up from PC in SDK/ADB mode and go from there. I just didnt know if that was possible until after I made the claim with Amazon. I still have an entire day today and tomorrow if I want to indulge myself. It doesnt matter if I mail the package today or Wednesday, I can still get it by Friday. I believe this thread is still valuable because we have patterns of repeating past failures and I may find use of it when I recieve my new phone and, darn it, it mysteriously bricks as well. in the same fashion.... the only thing I was really trying to do was get all my apps on my SD card... sad huh?
Edit 2 - Opened up the box, tried fastboot and adb, nothing. Off she goes.
Click to expand...
Click to collapse
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.

befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?

matt2k12 said:
Sure wish I would have known that ahead of time. Does this work without any recovery mode and with the bootloader still locked?
Click to expand...
Click to collapse
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.

befrosty8612 said:
It does work without any recovery mode and I believe it still works without the bootloader being unlocked, I didn't know about this myself until after I had already unlocked it. Sorry I couldn't help out sooner.
Click to expand...
Click to collapse
Awesome, I am wanting to do the backdoor root method again but, of course, may brick it. I dont think Amazon will keep sending me new ones.... but maybe!

befrosty8612 said:
FWIW, pressing vol down + power til it resets then pressing the camera button + power once the screen is black gets you to the Boot Mode Selection Menu, where you can start recovery, fastboot, BP tools (still not sure what that is entirely) and some others. Seems to be a fairly reliable/easy method for getting to both recovery and fastboot from any point.
Click to expand...
Click to collapse
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?

matt2k12 said:
For anyone concerned, I knew it would only be a matter of time until bricking my new device. This damn Root Toolbox Pro did it to me again, and on a simple, menial task. I am going to be working thru the motions on getting this to work.
Using the instructions quoted I did get stock recovery to work or at least flash on the screen for a split second. Seems like there is a timer on the recovery screen. I am having trouble with the fastboot prompt though on the PC. Do I do it in the "platform-tools" folder which contains fastboot or in the "tools" folder of the main SDK directory? I am really a noob, can you give me the cliff notes of how to get into ADB, fastboot, etc on the Photon Q in order to do a factory reset? I already have Android SDK installed and completely up to date so that is done. And Fastboot is installed. I'm just having trouble crossing the finish line here... I can get the fastboot page opened in the stock recovery but from there I'm lost. I dont know what to type into the command prompt, in what directory, or what.... Also when I open the command prompt in the SDK folder on the PC with fastboot in the directory and type "adb reboot bootloader" it says "device not found". Maybe (surely) that is the wrong prompt?
FWIW my phone is showing the dead android guy. I didnt do anything besides try and clear up my Play Store download list which required a reboot. The phone never started back up. I dont know how much damage was done or info was lost or whatever, but seeing as how I was rooted but still locked, I had no custom recovery. So no back ups. Is there anything to restore or am I looking at a full wipe and restore?
Click to expand...
Click to collapse
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?

befrosty8612 said:
As abnormal as it seems, your situation seems pretty normal... at least from my shoes. I went through the same scenario... I didn't know what adb was, or fastboot, etc. So, here's what I know
the fastboot commands work even if adb doesnt see it in the list of devices attached. Somehow it just works (as long as the phone is in fastboot mode).
If you're able to get to the fastboot mode, things should be okay. Just open a windows explorer window to the Platform-Tools, hold the shift key and right click on a blank space within the window, then click open command window here.
you should be able to pass any adb (if the phone is on and recognized) or fastboot (if phone is in fastboot mode) commands from that command prompt.
Also, if you have a stock recovery, CMW, or TWRP image, this is the folder to copy those .img files to. Once you get your phone into fastboot mode and its plugged into the computer, just type into the command prompt:
Code:
fastboot flash recovery recovery.img
If you're just looking to reboot the phone into recovery
If you have a CWM or TWRP recovery just replace the recovery.img with whatever the .img file that you have. Also, as a tip instead of writing the entire file name, just press the first couple letters then press the tab key within the command prompt, it should fill in the rest. keep pressing tab until you get to the .img file name you want.
To avoid doing this again, maybe I can help... what were you trying to do to begin with? From the sound of it, you were trying to root the phone with the Root Toolbox Pro but it bricked, and then you tried to reboot into recovery and then got the red android... ?
Click to expand...
Click to collapse
Thanks for the response. So, all I have to do is: go to fastboot and flash a stock recovery image file and it will automatically wipe the phone, cache, everything, and restore the operating system? Sounds awfully easy! I found some stock files in this post : http://forum.xda-developers.com/showthread.php?t=2001226&page=2 Are these the ones you used before?
Last question: I can flash CWM or TWRP but wont be able to access them if my bootloader is locked, correct? So flashing a stock recovery will allow me to have my stock phone back again, locked and un-rooted? I guess if I cant get it to work with the stock recovery then I can unlock the bootloader and do a CWM or TWRP recovery and then flash the stock .img files?
Thanks again for your help. I already had root with the motofail2go method which I like using but seems like when I try and use some generic root feature from apps from the app store that it will crash/brick the phone cuz obviously those apps are generalized and likely to brick certain percentage of devices....

Ok what does this mean? Something with the bootlaoder obviously. Does it need to be unlocked?
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y qrecovery1.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (5962 KB)...
OKAY [ 0.479s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.755s
C:\Program Files (x86)\Android\android-sdk\platform-tools>
And on the phone screen it says "invalid image size for partition recovery" twice for both times I tried this method.

You will need to flash the system image as well if you want those, as the recovery image will only flash the recovery. The files in that link are for twrp only... so you'll have to be able to get there first.
With the custom recoveries, I'm not 100% sure whether or not you will be able to use them without being unlocked. I would wait to see if anyone else can answer that question for you, but if you did try it without an unlocked bootloader, you at least have the stock recovery to fall back on if needed.
Sent from my XT897 using xda app-developers app
---------- Post added at 09:16 PM ---------- Previous post was at 09:12 PM ----------
I'm thinking it could either be that your phone is full and the image you're flashing is too large to fit on the space available...
Or you're trying to flash custom software on a locked phone.
Hopefully someone is able to answer that a little better...
Sent from my XT897 using xda app-developers app

You can't alter the stock recovery (flash a custom recovery like twrp or cwm) in fastboot without having the bootloader unlocked. Your options are to unlock your bootloader, flash custom recovery, create a backup of your current setup, download one of the stock working backups, place it in the backups folder for twrp on your external sd card, and restore one of the known working backups in the development section (befrosty linked to one). Or you could use RSD lite to return to stock using a stock factory firmware flash. That involves connecting your phone to your PC and flashing the phone back to factory stock. Information on RSD Lite and links to the FXZ's can be found here.
http://forum.xda-developers.com/showthread.php?t=2095536
Sent from my XT897 using xda app-developers app

Need help rooting a RCA Voyager Pro RCT6773W42B tablet

Is there an easy way to root this tablet?
The tablet is a RCA Voyager Pro. Model number is RCT6773W42B. It's running Android 5.0.1 Lollipop. Build number is RCT6773W42B-ANDROID5.0-V 19-V1.12.50-KC-B.
I want to root it so I can use the WWE App (No luck with Google Play or 1Mobile or Aptoide). I would so like to use some videogame roms also if possible. That's what I mostly would like to do. Nothing much else. I am not too computer savvy but I do know the basics. So anything that would be pretty easy/simple would be awesome.

Looking for root also. Tried everything to no avail. Hopefully something comes out soon.

+1

MobileGo
brokenjimmy said:
Is there an easy way to root this tablet?
The tablet is a RCA Voyager Pro. Model number is RCT6773W42B. It's running Android 5.0.1 Lollipop. Build number is RCT6773W42B-ANDROID5.0-V 19-V1.12.50-KC-B.
I want to root it so I can use the WWE App (No luck with Google Play or 1Mobile or Aptoide). I would so like to use some videogame roms also if possible. That's what I mostly would like to do. Nothing much else. I am not too computer savvy but I do know the basics. So anything that would be pretty easy/simple would be awesome.
Click to expand...
Click to collapse
Wondershare MobileGo. Free trial, but it works. Download it to pc and connect tab. It will install a "connector" app on the tab, then hit the "one click root" button and let it reboot the tab 3 or 4 times. It may stick on the dog splash screen for a while but don't panic. I did at first, but when it came back up it had root.

Don't use wonder share!!!
This tablet is not root capable out of the box, the reason for this is that the boot loader is locked which prevents any kind of modification of firmware as well as root. Now, I have not unlocked my boot loader yet on mine so I can't tell you if unlocking will allow installation of root but to unlock the boot loader first, read all instructions before attempting and I'm not responsible if your device bricks!
1. Turn device off
2. Hold volume up key then hold power key
3. Let go of power key once it starts booting but continue holding power up key until you in the recovery menu
4. You will see option to reboot to boot loader, navigate to it using volume key then select it using power key
5. You should see fastboot in the corner, now you need android SDK tools and adb ect. Which if you don't have you can google it.
6. Open command prompt from the sdk/adb folder by holding shift, right click, open command prompt.
7. Type adb devices to make sure your device is connected. If not make sure you install correct drivers for this tablet.
8. If everything is good continue by typing "fastboot oem unlock" without quotes it should pop up a screen on the device asking to unlock boot loader or it will automatically unlock it. Now you can try different programs like kingroot or manually install root with command prompt.
I can not confirm this will work as I have not had time to unlock mine yet. And again I'm not responsible for anything that may happen to your device bricked ect

icy201 said:
Don't use wonder share!!!
This tablet is not root capable out of the box, the reason for this is that the boot loader is locked which prevents any kind of modification of firmware as well as root. Now, I have not unlocked my boot loader yet on mine so I can't tell you if unlocking will allow installation of root but to unlock the boot loader first, read all instructions before attempting and I'm not responsible if your device bricks!
1. Turn device off
2. Hold volume up key then hold power key
3. Let go of power key once it starts booting but continue holding power up key until you in the recovery menu
4. You will see option to reboot to boot loader, navigate to it using volume key then select it using power key
5. You should see fastboot in the corner, now you need android SDK tools and adb ect. Which if you don't have you can google it.
6. Open command prompt from the sdk/adb folder by holding shift, right click, open command prompt.
7. Type adb devices to make sure your device is connected. If not make sure you install correct drivers for this tablet.
8. If everything is good continue by typing "fastboot oem unlock" without quotes it should pop up a screen on the device asking to unlock boot loader or it will automatically unlock it. Now you can try different programs like kingroot or manually install root with command prompt.
I can not confirm this will work as I have not had time to unlock mine yet. And again I'm not responsible for anything that may happen to your device bricked ect
Click to expand...
Click to collapse
You're not going to be able to unlock it.. there's another thread on this and it's got nothing to do with any human.
Bootloader is locked. Gotta try other stuff. I've had this for months and it's a piece of junk.. frankly, to me, anyway.. it's worthless without root privileges.
---------- Post added at 03:01 PM ---------- Previous post was at 02:08 PM ----------
dogboy322 said:
Wondershare MobileGo. Free trial, but it works. Download it to pc and connect tab. It will install a "connector" app on the tab, then hit the "one click root" button and let it reboot the tab 3 or 4 times. It may stick on the dog splash screen for a while but don't panic. I did at first, but when it came back up it had root.
Click to expand...
Click to collapse
... nope. Still no root. Even said "root failed" .. I'm just gonna see if anything else is updated. I've had this tablet for a couple of months thinking there'd at least be a few exploits to use but there's almost zip that I've been able to see. and I'm not the only one that can't unlock the bootloader with fastboot. Not sure what else to think at this point.. but this was a waste of time.

So why is the boot loader non-unlockable?

Re: Wondershare
icy201 said:
Don't use wonder share!!!
This tablet is not root capable out of the box, the reason for this is that the boot loader is locked which prevents any kind of modification of firmware as well as root. Now, I have not unlocked my boot loader yet on mine so I can't tell you if unlocking will allow installation of root but to unlock the boot loader first, read all instructions before attempting and I'm not responsible if your device bricks!
1. Turn device off
2. Hold volume up key then hold power key
3. Let go of power key once it starts booting but continue holding power up key until you in the recovery menu
4. You will see option to reboot to boot loader, navigate to it using volume key then select it using power key
5. You should see fastboot in the corner, now you need android SDK tools and adb ect. Which if you don't have you can google it.
6. Open command prompt from the sdk/adb folder by holding shift, right click, open command prompt.
7. Type adb devices to make sure your device is connected. If not make sure you install correct drivers for this tablet.
8. If everything is good continue by typing "fastboot oem unlock" without quotes it should pop up a screen on the device asking to unlock boot loader or it will automatically unlock it. Now you can try different programs like kingroot or manually install root with command prompt.
I can not confirm this will work as I have not had time to unlock mine yet. And again I'm not responsible for anything that may happen to your device bricked ect
Click to expand...
Click to collapse
I wouldn't make up a story if it had not rooted. Yes it said "root failed" the first few cycles of rebooting, but after several cycles it rooted. Now... if Wondershare is malware, this may be related... a week or so later the touch screen developed two rectangular "dead" spots that no amount of factory resetting could fix. I could not even type wifi password without rotating it in circles to avoid the dead spots. If you want a decent tablet for under 100, spend 30 more and get the Nextbook Ares 8. Very hard to root as well, but TWRP did the trick.

Wish i could root mine. RCA voyager pro 16gb. Is this bootloader just so hard to crack its not worth it? Or is the device really that crappy that no one wants to bother? I've tried unlocking it manually with adb and i cant select the yes option. Why the hell not? The no option works just great, clicking yes does not a thing. Hitting power after or not. No option for bootloader unlock in the settings. Yes i don't know where to even start when trying to figure it out myself. Justdont think the thing is so worthless it cant be done. I haven't had any issues with it at all, other than not being able to unlock it.

SkyLo420 said:
Wish i could root mine. RCA voyager pro 16gb. Is this bootloader just so hard to crack its not worth it? Or is the device really that crappy that no one wants to bother? I've tried unlocking it manually with adb and i cant select the yes option. Why the hell not? The no option works just great, clicking yes does not a thing. Hitting power after or not. No option for bootloader unlock in the settings. Yes i don't know where to even start when trying to figure it out myself. Justdont think the thing is so worthless it cant be done. I haven't had any issues with it at all, other than not being able to unlock it.
Click to expand...
Click to collapse
That's exactly why I said you cannot unlock the boot loader.. that's the only way to do it unless you use some dev's app around here that types the same command and tries no matter what.
Regarding it being rooted.. I've been trying for months now.. I'm actually trying again after giving up for a lil' bit.. SRSRoot said they picked it up but that just says it roots and then reboots.. and I see no sign of superuser/supersu or any sort of system apk to manage it, even if the damn app says "unmounting /system" and "remounting /system, rebooting.. Root success!" ... yeah even after that, I saw nothing when it booted back up. Tried Kingo only God knows how many times.. even tried other little exploits, tried to manually root it but unless you have r/w access to /system, which a custom recovery can give.. it won't happen unless someone literally takes what's on the RCA and they more or less just have a pre-rooted stock rom to start.. 5.0.1, whichever.. I haven't done any updates and I'm not gonna try. I'm gonna going to try and cycle through six-seven more times before I just eventually give up. I'm sure something will come along eventually, but right now I'm not getting ****, and not being able to unlock the boot loader isn't much of a help. I can't even load MTK Droid Tools with this, yet, it's got the same 8127 chipset as a rooted Lenovo that I have (running KitKat 4.4.2) .. i was able to install PhilZ with that.. but the boot loader is still locked.. I didn't even try to unlock it.. it's just like how FlashFire operates.. stay in Android but mount only what needs to be mounted.
If anyone see's something that really does root this thing or has a damn /system partition that they can friggin' send to someone (I'd be happy to at least try) to wipe everything and install a custom rom.. I don't know. I'd rather just manually root and then have this as a backup. This is what makes me regret grabbing some RCA even if it was 40 bucks with a keyboard. Useless without superuser permissions.
---------- Post added at 10:38 AM ---------- Previous post was at 10:33 AM ----------
dogboy322 said:
I wouldn't make up a story if it had not rooted. Yes it said "root failed" the first few cycles of rebooting, but after several cycles it rooted. Now... if Wondershare is malware, this may be related... a week or so later the touch screen developed two rectangular "dead" spots that no amount of factory resetting could fix. I could not even type wifi password without rotating it in circles to avoid the dead spots. If you want a decent tablet for under 100, spend 30 more and get the Nextbook Ares 8. Very hard to root as well, but TWRP did the trick.
Click to expand...
Click to collapse
Oh, and um.. Wondershare just adds a service.. at least under Windows 7 x64.. it's easy to remove so I'm not really worried and.. honestly.. I don't see a correlation between dead pixels and software unless it's immediate impact.

dogboy322 said:
I wouldn't make up a story if it had not rooted. Yes it said "root failed" the first few cycles of rebooting, but after several cycles it rooted. Now... if Wondershare is malware, this may be related... a week or so later the touch screen developed two rectangular "dead" spots that no amount of factory resetting could fix. I could not even type wifi password without rotating it in circles to avoid the dead spots. If you want a decent tablet for under 100, spend 30 more and get the Nextbook Ares 8. Very hard to root as well, but TWRP did the trick.
Click to expand...
Click to collapse
Still no dice with Wondershare, but it does do exactly as you said.. I'm wondering if you were thinking of the correct model and OS. This specific model never had KitKat (4.4.x) for it.. it's 5.0.1 only. Some people mistake this model for the other one with the same NAME but one different thing.. at the end of the model number, the ones that have actually a possibility of being rooted... they have a 22 at the end.
this is a 42. 42B. Now if he has that, then me trying this for the 12th time might have a shot at working. I might just do a factory reset.. like... as it was out of box.. aside from enabling USB debugging mode. I might try a few different drivers as well. It just fails and fails and fails and you know what it suggests to "manually" root? It recommends SuperOneClick which is no longer even used unless you have a really old device..
lol. I'll update you guys if I somehow find something. I'll try all the one-click tools a try but SuperOneClick? I actually have that in my archive but.. I don't really think it's necessary nowadays. If only I could get this damn boot loader unlocked.. I mean there's no way that they'll send anything anyway.. I'll try using MTK Droid Tools due to it having an MT8127 chipset.. every time it just says it can't load adb.. makes no sense to me. I have it installed system-wide with Environment Variables..
I know this thing can be rooted.. it's just gonna take longer, probably a year or more.. mostly because no one even gives a ****. I think it's pretty good if I just had the su binary in /system actually there, even temporarily.. I could easily make it permanent if we have even a glimmer of it for just a few minutes.. that's all I'd need. I'm not a dev but I know my way if I'm given at least SOME time.. Just run an sudaemon and what happens is you can actually remove what's considered "root" regarding the app.. this is actually well-instructed in a post that has to do with removing KingRoot and putting SuperSU on it to replace it. .. and I'm not talking about SuperSUme.. I mean it takes a little bit of knowledge... but not that much.

SkyLo420 said:
Wish i could root mine. RCA voyager pro 16gb. Is this bootloader just so hard to crack its not worth it? Or is the device really that crappy that no one wants to bother? I've tried unlocking it manually with adb and i cant select the yes option. Why the hell not? The no option works just great, clicking yes does not a thing. Hitting power after or not. No option for bootloader unlock in the settings. Yes i don't know where to even start when trying to figure it out myself. Justdont think the thing is so worthless it cant be done. I haven't had any issues with it at all, other than not being able to unlock it.
Click to expand...
Click to collapse
For the record.. Most don't care about a 30 dollar device with a damn keyboard unless they're literally sitting at a Command Line or using ADB for transfers etc instead of copy/paste. The reason that KitKat/4.4 works here is simple.. It doesn't have any way to patch PIE unless you're rooted already or if you've somehow got your tablet looked at as another device for unlocking the boot loader.. and I do remember, one time, I saw this first install the driver for an HTC One..
it's just an idea.. I'm not responsible if you **** anything up for your tablet. If you don't need root, then just don't worry about it or keep using stuff. PIE just stands for Position Integrated Executable.. and the error it gives every single 5.0+ tablet that has barely anybody looking at it.. well, that's why they're not working.. it literally gives the message when you attempt to root it manually.. "error: only position independent executables (PIE) are supported." ... now there are plenty of threads on here with this and ways to "bypass" it.. hell they even have something called "patch-pie" to flash in a custom recovery.. not the manufacturer. So if you somehow unlock the boot loader and you know what to put on it.. Then you're in. That's usually what happens here.. the methods are fine, they all work, it's just some firmware isn't ever really looked at with brands that have barely any purpose. Most of these types of tablets run 4.4.x on there and that gives them no errors... so it's really easy to root it if you get past it. I've seen it in SRS root right before my eyes and even doing so when trying other things not root-related in adb. Fix that and you'll be able to do it.

Disclaimer: If anything happens to any of your devices as a result of anything in this entire thread, post, or even the links from this entire thread and entire post.. doesn't fall on me, not my fault. If your wife or side girlfriend decides unlocking the boot loader with a hammer, I'm very sorry, but it is not of my doing. This is all for testing purposes. That being said.. I don't see how you screw this up. Don't try to unlock the bootloader, by the way. It's not happening.
The latest KingRoot works. I did a Factory reset prior, I had no clue it'd actually work. just.. clear cache and dalvik basically, install this:
http://forum.xda-developers.com/devdb/project/dl/?id=18893
xda approved obviously... after that, either use Super-SUME or the following guide to remove and replace KingRoot. It's originally made for some Amazon Fire phone but the whole thing is perfect to replace KingRoot and furthermore the correct binaries; At times it'll say it's an incorrect command or that something does not exist.. don't worry about it. It's Ancient but works just fine.. I did this just two days ago. Copy/Paste it line by line, not all at once... or make a script. up to you:
http://forum.xda-developers.com/fire-phone/general/root-fire-phone-supersu-t3105546

Need Custom Rom for custom rom rct6773w42b
Please where can I found a Custom Rom for RCA tablet 16 GB rct6773w42b, is bricked software for repair this.
Thank in Advance.
Bekel

Anyone have the original rom file? I did a factory reset in recovery and it keeps boot looping back to recovery. Would like to update via sd card option or adb. Please Help!!! I couldn't find anything online, it is the RCT6773W42B.

hey guys my bf found a way to unloclk the bootloader...once in recovery screen...when prompted ...go to bootloader but use the physical keys up/down and press enter to get it to work. volume keys dont work and it works . mines unlocked...just trying to find root solution now,. help??

Bootloader unlocked, full systemless root attained by using Kingoroot PC Version, SuperSU Me Pro to replace the Chinese binaries with proper SuperSU binaries. SuperSU 2.79-R3 installed on Android 6.0.1 Stock ROM. Bootloader is not encrypted. Only requires OEM Unlocking enabled in Developer options, connected to PC with micro USB syncing cable, rebooted into AP Fastboot Mode. Minimal ADB & Fastboot needs to be installed on PC (or the full Android SDK). Open a command prompt in the adb/Fastboot directory if using minimal adb & fastboot and simply type fastboot oem unlock and watch tablet screen for a prompt using the Volume buttons. Contrary to earlier statements this tablet is fully root ready out of the box, and bootloader is definitely not encrypted. Currently working on a TWRP port for this device as well as a deodexed and debloated stock ROM preinjected with root binaries, and optional insecure boot.img with init'd support running stock.

What wonderful work! And many thanks for your efforts. Do you think that your instructions and future ROMs would work with the RCT6873W42KC?
For more reference: https://www.amazon.com/gp/product/B01M7TSY16/ref=od_aui_detailpages00?ie=UTF8&psc=1
Well, well done,
Jake

jakfish said:
What wonderful work! And many thanks for your efforts. Do you think that your instructions and future ROMs would work with the RCT6873W42KC?
For more reference: https://www.amazon.com/gp/product/B01M7TSY16/ref=od_aui_detailpages00?ie=UTF8&psc=1
Well, well done,
Jake
Click to expand...
Click to collapse
Well, my objective is to modify a stock ROM that can be flashed on any RCA Voyager 7" variant running either Lollipop or Marshmallow. This includes the Voyager, Voyager II and the Voyager Pro. I would like to be able to offer both 5.1 and 6.0.1 ROMs. As long as the filesystem does not in anyway forbid a downgrade in firmware or OS, users running Marshmallow Builds would be able -- with an unlocked bootloader of course -- to flash either a Lollipop or Marshmallow Deodexed, Rooted, & Debloated Stock ROM. A Lollipop OS would offer the advantage of a System-Based Root versus the Systemless method required on the 6.x.x Builds.

Use KingRoot Worked for mine. Looking for custom ROMs

Moto G (falcon) - Recovery img problem

Ok, I've been reading around the forum for about a week, trying to solve a problem with an original moto g (falcon). Basically my cousin got the moto g a few years back, and I, in my ignorance, tried to root the device for him. What I can remember was oem unlocking the bootloader with Motorola's unlock code through their website and adb. then my cousin freaked about the warranty warning on the boot animation, and decided against it. So cut to now, I'm a little more experienced, the phone's years old now, and he'd like to refresh it with a new rom, which I suggested, trying to help him. So forgetting what I'd originally done those years ago, I started the process of rooting the phone, installing a custom recovery, to hopefully put a lighter rom on it for him.
OK so it's a UK Retail on tesco mobile, moto g xt1032 running Android 5.1.
in bootloader menu it says "Device Locked status 2", dunno what this is in relation to.
first I checked the bootloader was still unlocked, and adb said it was. so I tried to use CF-autoroot to finish the job, but there was issues. it restarted the phone into fastboot mode, but when the script started, pc end did nothing, on the phone it said, "flashing unlock" and just sat there for 10-15mins doing nothing (i left it the time, just incase it was doing it).
So i read a little more, and found because i'd already unlocked the bootloader, I could just flash a custom recovery and root from adb? so I downloaded the latest twrp and tried. I was unable to do so. it said the partition wasn't the right size? should have documented it, but really didn't expect to run into any problems.
So I restarted and tried to do my usual fallback, and flash the factory image and start again, But couldn't find a source for the specific img, and tried to keep fighting on.
So I noticed that the phone wouldn't respond to adb or fastboot once in fastboot mode, when in android with usb debugging, no problems, in fastboot, didn't show up as adb devices?
I tried booting into the recovery from the bootloader menu, and got a no command. So there isn't a recovery, and I can't flash a new one? if i could find the stock recovery, I would try that.
so apart from deleting all his apps and settings, I hadn't solved the problem at all, and had to leave the job there as I couldn't find a solution.
I know this isn't the most detailed, but I've done this with quiet a few phones now, and felt I was pretty competent. I see everyday as an excuse to learn more, and like to think I have humility. So, I'm assuming I did something those years ago to damage the recovery? I'm running out of ideas, and was hoping someone could point me in the right direction?
I've lurked on xda for years, and learned so much about this kind of thing through my past experiences, but I'm stumped this time, and feel obliged to resolve the problem, as it was me who caused it.
TL DR
Can't flash recovery, no command when I try to open recovery, trying to either factory image back, or root/custom recovery it.
any insight would be much appreciated.

Hi. I just rooted and installed CM13 on an old XT1034 about two days ago. I am also sort of a ROM noob, I have ROMed a few devices, but usually but following strict step by step guides I have found here on XDA. Over the years I have some minor understanding of the process now.
I also got the "No command screen" when trying to get into TWRP recovery. The issue seems to be that if you reboot via ADB and the ROM launches it will automatically rewrite the recovery to the stock one, and when you try to go to recovery from fastboot, it gives you the "no command" error. Apparently you can get to the stock recovery from there by a hardware key combo, something like holding up vol for 10 sec then a quick press of power (I can't remeber the exact key sequence or what forum I read it in). If it does this you have to reflash TWRP again. This issue is mentioned here (http://wiki.cyanogenmod.org/w/Install_CM_for_falcon) in step 8 about installing recovery. What I ended up doing was after the flash of TWRP via ADB, I manually powered down, then manually bood into fastboot by holding volume down and power, and selecting recovery. This was a bit fiddly and I had to attempt it a few times but eventually it worked and TWRP installed.
The issue with the phone not being recognized may be due to incorrect drivers. I had no issue with this because I installed the official driver package from Motorola. It is available in their website in the developer section. I don't have the URL right now.
Hopefully this helps, for me CM13 Official has been an a stable fresh start for this old device.