Related
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
Anybody have one? It's Best Buy's brand tablet.
insigniaproducts.com/products/computer-speakers-accessories/NS-14T002.html
(can't post a link...)
Just picked up a Flex 8 on Black Friday. Not bad for $80. Not sure if I'd pay full price for it though.
It seems good for the price so far, except I'm having a rough time trying to root it.
Anyone have one and root it?
Employee here and I had to pouch one up as well for the price of $80. Now to figure out root.
Sent from my SPH-L710 using xda app-developers app
Let us know if you get it.
I've tried Bin4ry, doomlord, tpsparky, played around with it myself a bit. Still not luck. Closest I got is normal on Bin4ry. Just when it reboots, it has no root privaledges. su is in /data/local/tmp but it fails to do anything...
I haven't messed around with it until this very moment. I will admit that the price is killer but initial impression with the device could be better. I was impressed and I mean really impressed with its quadrant score. I'll root this device later today. Black Friday sales and I am tired.
---------- Post added at 01:20 AM ---------- Previous post was at 01:18 AM ----------
I found a link to root this device on both ICS and jellybean. I will personally look into it tomorrow but I will post it if you would like to go ahead. The guide itself was written for ICS but later down the thread you will find another link to a working root for jellybean.
http://androidforums.com/insignia-flex-all-things-root/661247-how-root-insignia-flex.html
Please root at your own discresion and I sure hope you purchased a protection plan (GSP) for your tablet.
also picked this up at my BB, was surprised when i walked in at 3pm and they still had about 10. i want to root too
We had a large quantity to sell as well and they all went. It is honestly not half bad. And I would really recommend getting the GSP for the tablet in case of anything. Will report back after rooting.
Let us know if you have any luck. I found the link you posted before which led me to try Bin4ry. The script seems to be updated for JB in general but still had no luck. I'm on a Mac and haven't tried any of the windows rooting apps, like posted at the bottom of that thread. I do have a windows partition and would be willing to try that method if needed. That chinese one at the bottom seems shady regardless though.. I hope there is an alternative to that
Is there a way to flash clockworkmod onto this tablet?
rekagear20 said:
Is there a way to flash clockworkmod onto this tablet?
Click to expand...
Click to collapse
I managed to get the CX-803 version of CWM for Rockchip 3066 from AndroTab.info to work by replacing its kernel with ours by unpacking and repacking with RK3xxx-Firmware-Tools by Sergio.
Note: This is for the Insignia NS-14T002 (aka iRiver NS-14T002) tablet that shipped with Android 4.2.2
Be EXTREMELY careful! Highly recommend you dump your current kernel and recovery partitions and save them somewhere before flashing anything.
If for some reason the recovery doesn't work, you can flash your stock recovery back as long as you can get back into root shell. But, if it fails to boot normally, I have no idea how to fix it. I have not been able to get any of the Rockchip flashing utilities to recognize the tablet so far, in bootloader mode (these devices have no fastboot) or otherwise. So don't blame me if you somehow brick your tablet.
You have been warned!!
CWM & Stock* Recovery image for NS-14T002
* if for some reason you can't back up your own, but again highly recommend backing up your existing recovery in case it's different from mine
You need root, and you need to do the install from root shell (don't forget to su) as described here.
I used /data/local instead of /dev - anywhere writable should be okay.
To boot into recovery:
adb reboot recovery
power off tablet, disconnect USB, press and hold Vol+ and Power until recovery comes up.
USB disconnect is not a strict requirement, but the battery status thing tends to get in the way.
In stock recovery, push Vol+ and Vol- simultaneously to bring up the menu. CWM menu should be visible at launch.
install petrus's Reboot App and use it to Reboot into recovery
Note: In CWM recovery you can swipe up for Vol+ (move up), swipe down for Vol- (move down), swipe left for Power (select), and swipe right for Back.
Re:Insignia Flex Tablet
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers. I have used this program to root several Android devices and haven't had a problem thus far!
http://www.kingoapp.com/
cramamarshall said:
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers.
Click to expand...
Click to collapse
Great news! I didn't have luck with that one but it might have been the machine I was using at the time.
Just to confirm, your model came with Jellybean 4.2, Model NS-14T002?
The previous version with Ice Cream Sandwich 4.0 was easier to root.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
bhiga said:
Great news! I didn't have luck with that one but it might have been the machine I was using at the time.
Just to confirm, your model came with Jellybean 4.2, Model NS-14T002?
The previous version with Ice Cream Sandwich 4.0 was easier to root.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
Click to expand...
Click to collapse
Yes my device came with 4.2.2 Jelly Bean! My first attempt using Kingo Root it did not see my device. Windows would not install the drivers needed. So I installed PDA net for windows and choose other in the program and once it was done installing it had configured the necessary drivers for Kingo Root to find my tablet and it rooted fine within a couple minutes after that! :good:
help!
klowdhaus said:
Anybody have one? It's Best Buy's brand tablet.
insigniaproducts.com/products/computer-speakers-accessories/NS-14T002.html
(can't post a link...)
Just picked up a Flex 8 on Black Friday. Not bad for $80. Not sure if I'd pay full price for it though.
It seems good for the price so far, except I'm having a rough time trying to root it.
Anyone have one and root it?
Click to expand...
Click to collapse
I was wondering, because I rooted my insignia flex 8 tablet and downloaded an app to try and customize the navigation bar and the developer provided a way on how to do it but said it was risky and took the risk anyway. Unfortunately, after turning on my tablet, it gets stuck on the insignia logo which I'm assuming it is stuck in the boot screen. I emailed the developer on how to fix this and said to flash a ROM to it. But I am just wondering if I am able to still do this even if my tablet gets stuck on the boot screen and freezes. I used ultimate dynamic navbar lite to try and customize my navbar.
arahmahndy said:
I was wondering, because I rooted my insignia flex 8 tablet and downloaded an app to try and customize the navigation bar and the developer provided a way on how to do it but said it was risky and took the risk anyway. Unfortunately, after turning on my tablet, it gets stuck on the insignia logo which I'm assuming it is stuck in the boot screen. I emailed the developer on how to fix this and said to flash a ROM to it. But I am just wondering if I am able to still do this even if my tablet gets stuck on the boot screen and freezes. I used ultimate dynamic navbar lite to try and customize my navbar.
Click to expand...
Click to collapse
I don't have the tablet anymore as it was a gift for a family member that lives elsewhere (I just wanted root so I could remote control it with TeamViewer QuickSupport), but will try to help from my notes and memory.
Flashing ROM may be difficult.
There is no fastboot on these Rockchip devices...
I couldn't find a way to flash without it being bootable and accessible via ADB
None of the Rockchip flashing tools would recognize it, even when I thought I got it booted into flash mode - it loaded drivers, but the flash tools still didn't see it.
The only way I know how to flash is to use a flash tool via ADB root shell.
Have you tried plugging it into USB on computer and booting it? Even if it doesn't reach the launcher, maybe it is accessible from ADB?
If you can access ADB, you may be able to reverse whatever the app changed from ADB shell and uninstall the app. (Politely ask the author for help)
You might be able to flash the system image I took too, but that has potential to brick it even worse.
If you have custom recovery loaded, you should just be able to restore from a backup.
If you don't have custom recovery loaded, things get a little more hairy...
You can try booting into Safe mode, maybe it'll bypass the offending app.
Power off tablet
Unplug USB*
Press and hold Vol- and Power until (hopefully) it completely boots
Try booting into standard recovery and see what your options are there - Factory Reset might help (depends what was changed and where)
Power off tablet
Unplug USB*
Press and hold Vol+ and Power until recovery comes up (Android with open chest)
Press Vol+ and Vol- simultaneously to bring up the menu.
* while unplugging USB isn't really required, because a battery app launches shortly afterward, it can make getting into recovery and safe mode more difficult
The folks over at Freaktab and Vondroid are really the experts at this Rockchip stuff.
For reference, the platform is RK3066, but there are many variations of the platform (different WiFi, memory configuration, etc) so you can't just grab any ROM.
Thank you!
bhiga said:
I don't have the tablet anymore as it was a gift for a family member that lives elsewhere (I just wanted root so I could remote control it with TeamViewer QuickSupport), but will try to help from my notes and memory.
Flashing ROM may be difficult.
There is no fastboot on these Rockchip devices...
I couldn't find a way to flash without it being bootable and accessible via ADB
None of the Rockchip flashing tools would recognize it, even when I thought I got it booted into flash mode - it loaded drivers, but the flash tools still didn't see it.
The only way I know how to flash is to use a flash tool via ADB root shell.
Have you tried plugging it into USB on computer and booting it? Even if it doesn't reach the launcher, maybe it is accessible from ADB?
If you can access ADB, you may be able to reverse whatever the app changed from ADB shell and uninstall the app. (Politely ask the author for help)
You might be able to flash the system image I took too, but that has potential to brick it even worse.
If you have custom recovery loaded, you should just be able to restore from a backup.
If you don't have custom recovery loaded, things get a little more hairy...
You can try booting into Safe mode, maybe it'll bypass the offending app.
Power off tablet
Unplug USB*
Press and hold Vol- and Power until (hopefully) it completely boots
Try booting into standard recovery and see what your options are there - Factory Reset might help (depends what was changed and where)
Power off tablet
Unplug USB*
Press and hold Vol+ and Power until recovery comes up (Android with open chest)
Press Vol+ and Vol- simultaneously to bring up the menu.
* while unplugging USB isn't really required, because a battery app launches shortly afterward, it can make getting into recovery and safe mode more difficult
The folks over at Freaktab and Vondroid are really the experts at this Rockchip stuff.
For reference, the platform is RK3066, but there are many variations of the platform (different WiFi, memory configuration, etc) so you can't just grab any ROM.
Click to expand...
Click to collapse
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
arahmahndy said:
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
Click to expand...
Click to collapse
If you can access ADB then try loading the CWM recovery I posted above. If you can at least get CWM up, at worst case I can give you a copy of my stock backup to restore.
Sent from a device with no keyboard. Please forgive typos, they may not be my own.
arahmahndy said:
Thanks for the information! I know I have ADB from rooting my tablet so I'm gonna check how that is when I get home and I have found some rockship information on vondroid so I will check that out also. Thanks for the reply again!
Click to expand...
Click to collapse
Did you get things sorted out?
If anyone is interested or needs it, Insignia sent me the GPL source.
You can also request it directly from them like it says on the website but it took a week or two (they might not have had a procedure in place yet, the agent had to forward my request to a different department) and I had completely forgotten until an unexpected package arrived.
Performance NS-15at10, ta120, ITQ701
Just thought someone might want to know, kingo root works, updated to 4.4.2, Booster plus battery saver pro is worth the money, better than 3c so far, still looking for more sources, any advice or help is appreciated especially for a recovery, dual bootloaders, ugh
cramamarshall said:
I actually just purchased one of these last night. It was on sale at Best Buy for $99! I have successfully rooted it and it actually works great! I used Kingo Root to root but first I installed pda net first to install the necessary drivers. I have used this program to root several Android devices and haven't had a proble
Can I install drivers without PC?
Click to expand...
Click to collapse
So I want to install the latest 4.4.4 Kit Kat on my Transformer Infinity because the latest Jelly Bean on it is extremely slow. Through research and google I found that the only way to root it was go back to an earlier version of Jelly Bean. Otherwise the motochopper program was denied access so I was unable to root it. So I found the right Jelly Bean update and stuck it on my SD card and it showed up in the notifications as an update to fall back to. Installed it and the motochopper app worked and rooted the tablet. I tried to use the Asus unlocker tool but it always says to try back later as it is trying to unlock it. Some info on the internet says that app doesn't work with jelly bean some says it does. So I thought i would roll back to Ice Cream Sandwich. In order to do that the info. on the internet says to hold the down volume button along with the power button and you can go to some menu that will allow you to install earlier version of android. Which I have an ICS for the infinity on the SD card. Problem is the volume down button plus power button does nothing. It has no effect. I'm at my wits end here. Everything I have found on the internet doesn't work. I'm fairly new to rooting, unlocking, and installing a custom android. I have done this once for a Kindle Fire tablet and it was MUCH easier then this Infinity tablet.
You do not need to downgrade to ICS (and you can't - at least not with stock firmware) The unlock tool version 8 works fine on JB roms - if it works at all. You really have to keep trying. For some people it literally took 50 tries or more and all the sudden it worked... And for some it never worked. There's no rhyme or reason for this except that Asus is not trying very hard to make this work for us. They enable it, but do not support it.
Google "unable to unlock TF700" and you will get a dozen threads discussing this and a few more strategies you can try.
Sent from my DROID4 using Tapatalk
That was kind of how the root tool worked I had to try it over and over I think about the 5th or 6th time it worked.
Well that was relatively painless then - happy flashing
I'm not quite to 50 times yet but I still get "an unknown error has occured. The network may be down please try again later" error.
So i'm all rooted and unlocked now. I have a snapshot version of 4.4.4 for transformer infinity. The cyanogen mod program says the TF700T isn't supported and aborts. I've tried the Clockwork Rom recovery program and it says the TF700T isn't supported either only the TF200 is it says. What is the best way to install this ROM?
So I tried Rom Toolbox. When the tablet reboots to boot into the recovery where you can install the rom it just sits at the asus logo screen forever. I don't think I have a recovery boot anymore. When I hold the power button and volume down button which is supposed to allow you to boot into recover nothing ever happens.
It's probably a little late, but to install a custom rom you have to install a recovery compatible with your bootloader and the rom you intend to flash.
You flash this recovery (TWRP or CWM) in fastboot, then you can boot into it to install a rom.
If you can't boot into the bootloader with Power and Volume Down and you did not generate nvflash blobs prior to all this, I'm afraid it's a brick.
Try every combination you can think of: Holding the buttons a very long time, use the reset pin hole on the side in conjunction with Volume Down, let it sit for hours and hope it sorts something out.
You need some magic to give you access to the bootloader menu and fastboot - that's your last hope.... Sorry
I can still boot into the version of jelly bean I have on the tablet fine. I did manage to get it to finally boot into a recovery console. it might have been a fluke I tried like 20 times and it finally just booted into it from the Rom Manager program. I tried installing my rom image but it would fail every time. I just rebooted and it went back into jelly bean. No idea what to do from here. The power button and volume down still don't do anything. And I haven't been able to reproduce getting it to boot back into the recovery again. At least it isn't bricked but I hate this tablet so much I might just take a hammer to it and give up.
If you have the time can you walk me through putting a decent version of 4.4.4 on here if it will work? Apparently I either don't know what i'm doing, the guides I have tried online are missing important steps, or my tablet is just "special". I do know that it is rooted and unlocked and that is where its at right now.
This guide seems like a good place to start but I don't see how to get through it when the volume down and power button doesn't do anything
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
kahless1979 said:
If you have the time can you walk me through putting a decent version of 4.4.4 on here if it will work? Apparently I either don't know what i'm doing, the guides I have tried online are missing important steps, or my tablet is just "special". I do know that it is rooted and unlocked and that is where its at right now.
This guide seems like a good place to start but I don't see how to get through it when the volume down and power button doesn't do anything
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
I know when I'm upset with this thing I start doing things wrong....make sure you are actually using the vol down button and not the Up button. It's an easy thing to do when you're in PO'ed mode.
You're lucky to be unlocked! I bet I have run that unlock tool a million times to no avail.....
kahless1979 said:
If you have the time can you walk me through putting a decent version of 4.4.4 on here if it will work? Apparently I either don't know what i'm doing, the guides I have tried online are missing important steps, or my tablet is just "special". I do know that it is rooted and unlocked and that is where its at right now.
This guide seems like a good place to start but I don't see how to get through it when the volume down and power button doesn't do anything
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Click to expand...
Click to collapse
You cannot use ROM Manager on the TF700!!! That is the fastest way to a hard brick I know on this tablet. Forget ROM Toolbox, ROM manager and all the other tools! You have to get ADB and fastboot working on your computer and my guide you linked to is a good start.
I have no idea why you cannot boot into the bootloader if your rom boots fine????
You are pushing Power and Volume Down until you feel the tablet vibrate TWICE?
Get the ADB drivers installed on your PC and with the tablet booted into your rom type this in a command prompt:
Code:
adb devices
What do you get?
berndblb said:
You cannot use ROM Manager on the TF700!!! That is the fastest way to a hard brick I know on this tablet. Forget ROM Toolbox, ROM manager and all the other tools! You have to get ADB and fastboot working on your computer and my guide you linked to is a good start.
I have no idea why you cannot boot into the bootloader if your rom boots fine????
You are pushing Power and Volume Down until you feel the tablet vibrate TWICE?
Get the ADB drivers installed on your PC and with the tablet booted into your rom type this in a command prompt:
Code:
adb devices
What do you get?
Click to expand...
Click to collapse
Volume Down and Power yields one vibration and nothing happens after that. I have tried holding them down longer to no avail and released them after one vibration and nothing still.
I would use ADB to push the rom to the tablet and that is what I did with a Kindle Fire a couple years ago and worked great. But your guide still calls for being able to use the volume down and power button. I guess I got a real lemon of a tablet here.
I get List of devices attached
C7OKAS090001 device
kahless1979 said:
Volume Down and Power yields one vibration and nothing happens after that. I have tried holding them down longer to no avail and released them after one vibration and nothing still.
I would use ADB to push the rom to the tablet and that is what I did with a Kindle Fire a couple years ago and worked great. But your guide still calls for being able to use the volume down and power button. I guess I got a real lemon of a tablet here.
I get List of devices attached
C7OKAS090001 device
Click to expand...
Click to collapse
Well that's good. You seem to have ADB access. Try this command:
Code:
adb reboot - bootloader
That should reboot your tablet into fastboot mode. If it does, use this command:
Code:
fastboot devices
That should return a (different) alpha-numeric string and you would be in business to flash. But let's not get ahead of ourselves...
adb reboot - bootloader
That command restarted my tablet.
So just type "adb fastboot devices" at the command prompt?
kahless1979 said:
adb reboot - bootloader
That command restarted my tablet.
Click to expand...
Click to collapse
The correct command is:
Code:
adb reboot-bootloader
_that said:
The correct command is:
Code:
adb reboot-bootloader
Click to expand...
Click to collapse
I took out the spaces between the hyphen. Same thing, it rebooted the tablet right back to the android desktop.
kahless1979 said:
I took out the spaces between the hyphen. Same thing, it rebooted the tablet right back to the android desktop.
Click to expand...
Click to collapse
I'm stumped... @_that you have an idea why it doesn't boot into the bootloader? I thought maybe the Volume button is bust - but now...IDK
berndblb said:
I'm stumped... @_that you have an idea why it doesn't boot into the bootloader? I thought maybe the Volume button is bust - but now...IDK
Click to expand...
Click to collapse
Is it possible I messed something up when I downgraded from Jelly Bean 4.2.1 to 4.03? The reason I had did that was a guide somewhere for this tablet said the ADB motochopper program wouldn't root 4.2.1. Which I could never get it to work. But did fine once I went to 4.03. I did that by downloading that update from asus's website and putting it on my SD card and it found the update and asked me if I wanted to fallback to an older one.
kahless1979 said:
I can still boot into the version of jelly bean I have on the tablet fine.
Click to expand...
Click to collapse
kahless1979 said:
Is it possible I messed something up when I downgraded from Jelly Bean 4.2.1 to 4.03?
Click to expand...
Click to collapse
So what version of Android is now actually running on your device? 4.2.1 or 4.0.3 (which is ICS)?
You also speak repeatedly of some version 4.4.4 you are trying to install - the latest version of Android as of today is 4.4.2.
Note that there are multiple ways to hard brick your tablet if it is unlocked - don't do anything you don't understand.
Hi all,
Today I tried to flash an older version of the stock rom (v1.2.1) and thought I didn't need to flash userdata.img. That was a big mistake..
Now the tablet stuck at a bootloop. After that I thought I could simply flash twrp over the bootloader to peform a /cache & /data wipe so that I can fix the bootloop.
And now we come to the other BIG problem. I can't access the bootloader. It directly boots up the tablet with the Nvidia logo. Is there any solution to fix the tablet?
I tried at the bootloop to enter via adb into the bootloader but my PC isn't recognize my device (probably no usb debugging).
There is no way to rescue it? No apx drivers out there?
Your message seems to be unclear about one very important thing:
1. Are you able to successfully access the bootloader? I don't mean your custom recovery. I mean the black screen with very small font words with your serial and shows whether your bootloader is Locked or Unlocked.
From where I'm sitting, it looks like you flashed v1.2.1 without using "flash -w", as well as forgetting to flash ALL the stock img files. Next, it looks like you're expecting a direct boot into the bootloader, which is not possible. You need to hold down the Vol_down button and then hold the Power button until the screen comes on, THEN you need to let go of the Power BUT KEEP HOLDING the Vol_down. If done correctly, you should be at the bootloader.
From the bootloader, you will not be able to run adb commands. Instead, the bootloader takes "fastboot" commands. All this is assuming you've installed the latest nVidia Shield Family drivers from the nvidia gameworks download site.
amartolos said:
Your message seems to be unclear about one very important thing:
1. Are you able to successfully access the bootloader? I don't mean your custom recovery. I mean the black screen with very small font words with your serial and shows whether your bootloader is Locked or Unlocked.
From where I'm sitting, it looks like you flashed v1.2.1 without using "flash -w", as well as forgetting to flash ALL the stock img files. Next, it looks like you're expecting a direct boot into the bootloader, which is not possible. You need to hold down the Vol_down button and then hold the Power button until the screen comes on, THEN you need to let go of the Power BUT KEEP HOLDING the Vol_down. If done correctly, you should be at the bootloader.
From the bootloader, you will not be able to run adb commands. Instead, the bootloader takes "fastboot" commands. All this is assuming you've installed the latest nVidia Shield Family drivers from the nvidia gameworks download site.
Click to expand...
Click to collapse
Thanks for your answering. I flashed all .imgs, the blob file and the .dtb file . Everything but not the userdata.img. I can't access the bootloader with holding down the vol down + power button. I only can access the apx mode with power + vol up.
ThunderArts said:
Thanks for your answering. I flashed all .imgs, the blob file and the .dtb file . Everything but not the userdata.img. I can't access the bootloader with holding down the vol down + power button. I only can access the apx mode with power + vol up.
Click to expand...
Click to collapse
I notice in your sig that you do in fact seem to have a fully working new replacement tablet. That got me thinking along the following:
1. new tablet is fully functional, old one is not
2. both tablets have the same hardware spec
3. pull firmware from new one, and somehow get it onto the old one
4. hopefully old tablet should work!
The biggest problem is step 3... I only know of nvflash that might be able to help here, but I've never used it myself so I'm completely useless here. Maybe someone more knowledgeable could help out here, but otherwise it seems like you might be out of options.
If you do want to take a stab at nvflash yourself, THIS PAGE has a nice writeup of what some commands do, BUT BEWARE! It's not for our device, so don't just copy-paste commands! As long as you're not writing things to the new tablet, it couldn't hurt to try stuff, right?
It wish someone could help me with NvFlash because I have no knowledge with it.
So it's possible to make a copy of the system of my working tablet and flash it on my old tablet with NvFlash?
I hope someone helpful with NvFlash experience could help me out.
Btw I need to have an un-blob'd stock rom version to get it back alive? Afaik is there no public version.
NVflash is only useful if you have backed up using it BEFORE you brick it.
sbdags said:
NVflash is only useful if you have backed up using it BEFORE you brick it.
Click to expand...
Click to collapse
I have a replacement tablet. I could make a backup from it and use it with my bricked tablet. Do you know how this could work? (As I said I don't have experience with Nvflash yet.)
-deleted-
ThunderArts said:
I have a replacement tablet. I could make a backup from it and use it with my bricked tablet. Do you know how this could work? (As I said I don't have experience with Nvflash yet.)
Click to expand...
Click to collapse
No the blobs are specific to the device.
sbdags said:
No the blobs are specific to the device.
Click to expand...
Click to collapse
Okay. So it seems that there is no way to rescue it. Btw is there no accessible bootloader in OTA 1.2.1 because I flashed the boot.img without any error and I don't understand why I can't access it.
sbdags said:
NVflash is only useful if you have backed up using it BEFORE you brick it.
Click to expand...
Click to collapse
can you actually back up anything for nvflash? afaik there's nothing that works on the tegra k1 yet
Bogdacutu said:
can you actually back up anything for nvflash? afaik there's nothing that works on the tegra k1 yet
Click to expand...
Click to collapse
Indeed - I was just talking about nvflash use in general. I haven't seen it used since tegra 3.
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