Related
Rather than clutter up other threads, such as the blocking 1.41 OTA update thread, I propose we put thoughts/frustrations here. As such, here is what I think:
Upon thinking about this more, this is really just the final wedge that B&N put in place to separate the people here, versus the people who are locked into B&N content.
We/I had been hoping that maybe someday they would change their mind and open up the NT so it would act the way the NC would. But, this is a clear message to consumers on how they want to proceed with their product. There will be no unlocked bootloader in the future. There will be no use of outside apps from other markets.
I can't blame them for trying to make money. They put together a nice piece of hardware, and are probably making little to no profit on the hardware. The real bummer here is, for me at least, I would have likely purchased non-apps(see books) from B&N and used the software originally provided by them to view the books. But now with this update, I am basically forced to do the full bloatware removal, and I will get books through other means.
For me, the NT is more a toy for apps and less for reading. Utilizing the B&N app market, which as others have said, is very limited and often pricey, does not make sense. Could I spend some more money and get a full android tablet? Sure, but if I've learned anything from these forums in my short time here, its that it is fun to work together on tweaking something and making it better than what it was originally intended for.
Your thoughts?
I think it's only a matter of time before the devs figure out a way around their "block" of nonBN apps. All they did was take out the ease of sideloading out of the box.
I still haven't gotten a Nook Tablet. I still plan to. I have no doubt that this will be a temporary setback. The locked bootloader is, no doubt, a challenge. Rooting the device after this update, however, shouldn't be nearly as significant an issue, I wouldn't think.
I have the same feelings about the device - it will be a fun toy and useful device and will serve less as an eReader.
For the time being, I will be reading the forums to see what new developments come along in this drama.
CapsLockKey said:
I think it's only a matter of time before the devs figure out a way around their "block" of nonBN apps. All they did was take out the ease of sideloading out of the box.
Click to expand...
Click to collapse
It sounds like they already have, but the point remains that it was a slap in the face to anyone that has been previously side-loading apps and customizing their NT without rooting.
If you've read some of Indirect's posts before, i believe he debloats most if not all of BN's stuff. Changing the db values worked for the Nook Color, and i assume it's just a matter of hours before one of us work out a quick workaround to rescuing those who got bumped to 1.4.1. I suspect it's gonna be something like this:
1) Using SD card method to restore to 1.4.0
2) Identifying the culprit to push/pull OTA on the NT
3) debloat B&N footprint to minimal so that the NT will be a stable platform to research the bootloader issue.
I'm really surprised so many people start thinking returning their NT because of one minor update. As long as there's one copy of rooted NT among us, i think we'll be able to propogate and beat BN at their game.
I pulled this from the "How to block B&N 1.41 update" thread.
AdamOutler said:
http://forum.xda-developers.com/showthread.php?p=20502705#post20502705
Click to expand...
Click to collapse
For my fellow XDA noobs, fear not and don't lose faith in the brilliance of this community.
Here is a fine example(see post above): AdamOutler is amazing and comes through for XDA often like so many others.
Watching him and Loglud give NT bootloader the business in the Development thread is impressive even though I don't fully understand. I see though that they are making progress. They prove that there are many ways to crack the NT nut.
Remain calm and keep reading.
HMG10 said:
It sounds like they already have, but the point remains that it was a slap in the face to anyone that has been previously side-loading apps and customizing their NT without rooting.
Click to expand...
Click to collapse
If I took offense at every manufacturer that has "slapped the face" of their market, I wouldn't own anything. I would live in the woods because the people that made my house cut corners to line their pockets. My shingles wouldn't be prematurely failing. I would have sold my Prius immediately when I found out about the cover-up of some very important safety information. I would start a class-action suit over the burst capacitors on my motherboard due to the manufacturer using questionable sources for their electronics. I would never buy a toy for my kids because most are made in China using questionable labor tactics.
If people choose to take this personally, fine. Return your devices. Please also take stock of what you own and what pains you go through daily because capitalism encourages these behaviors. Then, sit back and ponder how you, as a consumer, contribute to the issue.
Am I unhappy about the decision? Yes. I'd rather thumb my nose at B&N by being patient and using whatever new tricks are up people's sleeves to use the device in a way "I'm not supposed to be able to" than not even buying one. Does this make me a hypocrite by making a rationalization to own a device while still supporting the very practices that perturb me? Perhaps.
Moved my thoughts from the other thread:
I think B&N is going to be surprised at the number of returned NT's- I'm betting far beyond their 3% estimate. 3% is probably people like on this site, average/above average tech users. Well beyond that are many others who buy NTs based on a recommend from the 3%, who then just follow the instructions for sideloading/rooting.
Personally, I've recommended the NT to about 4 other people who bought as Christmas presents. If there will be a constant worry for them about sneaky updates wrecking their NT's, my only advice will be to return while they can and get something else. I recommended based on the NT's ONLY real advantages- that it can be rooted and sideloaded. It sucks, and now I regret recommending this, and from now on I won't. I don't mind being responsible for the NT I bought my wife for Christmas, but not anyone else's.
In the end, B&N and others who go this crazy locked down route will lose- more and more people are tech savvy enough to know they're getting the shaft. B&N needs to develop a better app store, like Amazon. People willingly put Amazon's app store on their devices, including the Nook. I wonder how many KF users willingly put B&N crap on their devices?
They think they can just force people into a crappy walled garden like they are Apple, but with a subpar app store, charging even for otherwise free apps. It's not gonna work, and unfortunately the NT will eventually sink in a sea of better tablets that aren't locked down.
I'm not so sure that people will be returning their NTs with this update. Most of us have had ours far past the two week return period. Even if we returned them, it would be for store credit.
sonicdh said:
I'm not so sure that people will be returning their NTs with this update. Most of us have had ours far past the two week return period. Even if we returned them, it would be for store credit.
Click to expand...
Click to collapse
return window for "holiday" purchases has been extended to 01/31/12 if purchased between 11/14 and 12/31.
is it really worth returning it for a little reason like this? Heck, even Amazon have done the same thing in the past couple days. Granted you have the option of flashing a new ROM onto the KF but what about the people who have just bought it and it comes with the new FW or they haven't seen the post on the new FW?
I agree with most saying that B&N are doing what is best for them, which makes sense in a business aspect and everyone who bought this for a cheap colour e-reader have no concept about it. We get upset, someone finds a way to fix it, we move on to something else.
I too considered returning mine but A) it won't do me any good B ) Other "cheaper" tablet developers seem to be doing the same thing.
Final thought - Might as well keep it and patiently wait for something to change from here.
Being a total noob to all things android and not a very adept at computers, I was so happy to compare the Nook Tablet and the kindle fire side by side. I picked the nook tab because I saw that I could side load all the kindle book store and Amazon apps to the Tab. Also because of the hardware improvements.
Now I feel like I've been baited and switched. I do believe that I will be returning the Nook Tablet I have purchased. Before I do, I have a few questions. Please excuse my ignorance.
1. where do I go to buy the refurbished nook colors for 130.00 ?
2. If I buy an upgraded nook color, will I be able to load the kindle bookstore and my kindle books on to it?
3. Will I have access to sideloading all the things I want on the nook color?
4. How do I save the content I now have to move over to the nook color?
5. Will the 16gig SD card I bought for the nook tablet work on the nook color?
If all these things can be done with the nook color, then I must vote with my wallet and return my tablet if for no other reason than principle. I purchased a product from a company that performed a certain way and I wake up and find they have disabled the functions that mattered to me the most. I didn't rent or lease the product. I purchased it. It should be mine to use or modify as I please.
With my needs, it appears that the nook color will do me just fine. I don't plan on watching movies or TV on it.
As others have noted, my frustration is this... I bought (3 in total) and recommended several others buy over things like the Fire because one could sideload without rooting.
I'll be the first to state that I am perfectly content rooting my own NT (as I did for my NC previously), but I have two other NTs in my household as well. It is neither practical nor desirable to have to root all three and maintain all three for less savvy users who want software not available in the BN store.
The capability to sideload made the selection of the NT an easy choice. Blocking sideloading without rooting makes the choice to return two - if not all three - an easy choice as well.
I hope this helps with your questions.
1. where do I go to buy the refurbished nook colors for 130.00 ?
Ebay
Google Search
2. If I buy an upgraded nook color, will I be able to load the kindle bookstore and my kindle books on to it?
No. It has 1.41.
Go to the "Nook Tablet Android Development - [Stock Firmware]Restore Barnes & Nobel Nook 1.4.0 from SDCard" to understand how to undo.
3. Will I have access to sideloading all the things I want on the nook color?
Only with a rooted 1.4 or custom rom. Unsure how 1.41 might impact a custom rom or if this would even be an issue for custom rom.
4. How do I save the content I now have to move over to the nook color?
SD card and/or Dropbox or some other way to access later.
5. Will the 16gig SD card I bought for the nook tablet work on the nook color?
Yes from what I have read.
PlacidCat said:
I still haven't gotten a Nook Tablet. I still plan to. I have no doubt that this will be a temporary setback. The locked bootloader is, no doubt, a challenge. Rooting the device after this update, however, shouldn't be nearly as significant an issue, I wouldn't think.
I have the same feelings about the device - it will be a fun toy and useful device and will serve less as an eReader.
For the time being, I will be reading the forums to see what new developments come along in this drama.
Click to expand...
Click to collapse
This update demonstrates that B&N is openly hostile to the dev community. Most manufacturers (even Apple!) take a laissez faire approach to outside development - they don't go out of their way to help, but they also don't go out of their way to break things. Kindle Fire updates, for instance, are a minor inconvenience for rooters, and rerooting is very easy.
A lot of people were willing to live with the locked bootloader because, in the end, you can still achieve most of what you want simply through sideloading. All the bootloader really curtails are those ugly themes that rom chefs seem to love so much. But stopping sideloading? Ugh, no way.
By doing this, B&N has proven that they are not happy with sideloading and I believe it is within their power to disable it permanently. And even if it is always possible to circumvent, you'll see the community here get smaller and smaller until there aren't enough people willing to bother.
So I would say do not get a Nook Tablet if you are not happy with using the pure stock experience without sideloading.
Gotta vent too. Blocking sideloading is a total f u in our faces. We also can't root it with ZergRush. What do we have left? Total waste of hardware if you lock it down like this. Might as well get the simple touch ereader. You can't call it a tablet if it can't do tablet things!
If it's going to affect their revenue stream, they're going to look for a way to block it. there's no getting around it. they don't have the ecosystem that Amazon has, so they can't afford to have people go elsewhere for some of the more mainstream apps that they have in their store.
the solution to that it that B&N needs to aggressively expand their app store and price at least close to the Android Market prices.
at least then, there's a reasonable retort, despite how we may feel. still, I paid for the device, I shouldn't have them decide how I should be able to use it.
Mama Luigi said:
<SNIP>
So I would say do not get a Nook Tablet if you are not happy with using the pure stock experience without sideloading.
Click to expand...
Click to collapse
As I said, I'm waiting and watching. My "plan to" is not 100% firm. I'll leave it to the devs to decide if they want to stick with this or not and base my decision on their progress, not what people are saying now in frustration. There are still ways around the issue and OTA updates appear to be (hopefully) already circumvented if people installed Gapps as part of the basic root procedure outlined on this forum.
To simply say "do not get... unless you want stock" is quite premature. Again, I have bigger worries on my mind - if Toyota was late on reporting a safety issue that could have affected my life and my family members', I have far more reason to turn away in disgust. Will I turn away from a reading device that STILL offers a tablet experience if people follow directions just because of B&N's asshattery? No.
JoeM01 said:
If it's going to affect their revenue stream, they're going to look for a way to block it. there's no getting around it. they don't have the ecosystem that Amazon has, so they can't afford to have people go elsewhere for some of the more mainstream apps that they have in their store.
the solution to that it that B&N needs to aggressively expand their app store and price at least close to the Android Market prices.
at least then, there's a reasonable retort, despite how we may feel. still, I paid for the device, I shouldn't have them decide how I should be able to use it.
Click to expand...
Click to collapse
Personally, I don't like being locked into a B&N app store. For my next tablet/phone/android device, it won't necessarily be a nook, but it will run android, therefore google market is still the best bet. Google market is there and established. B&N should focus on making profits via ebooks, magazines and other media.
Is the extended return policy specific to purchases at the B&N stores? I purchased mine at Best Buy.
A month ago I sold all of my tablets and have bought the Wacom Cintiq Companion Hybrid.
Primarily verifiable need for it to work. But since I now possessed no other tablet, I quickly found that my root right for certain things missing for recreational use. To use the Sixaxis app for example.
So I wanted to ask here if maybe a developer have already dealt with it, to root the device.
Would be really happy.
sorry for my english, my best friend is google translate
regards
Alex
It's pretty much a Raw Android Tablet and should work with anything in the play store. No one seems to be looking in to doing anything with this tablet since it's so expensive and it's made for such a specific use. I asked questions about it for months and no one acknowledged me about it.
Sinsecond said:
A month ago I sold all of my tablets and have bought the Wacom Cintiq Companion Hybrid.
Primarily verifiable need for it to work. But since I now possessed no other tablet, I quickly found that my root right for certain things missing for recreational use. To use the Sixaxis app for example.
So I wanted to ask here if maybe a developer have already dealt with it, to root the device.
Would be really happy.
sorry for my english, my best friend is google translate
regards
Alex
Click to expand...
Click to collapse
+1
Tablet malfunctioned and I lost some files. Would love to be able to use a recovery program to get them back (need root to do so).
Test this https://github.com/linux-shield/shield-root/blob/master/README.md
Use adb reboot bootloader
Test unlock bootloader only
Sorry for my bad english
Any news ?
c4b4l3 said:
Test this ...
Use adb reboot bootloader
Test unlock bootloader only
Sorry for my bad english
Click to expand...
Click to collapse
Sorry to revive the thread but since I am considering buying one.
Did any one try to root it with success ?
JediRemi said:
Sorry to revive the thread but since I am considering buying one.
Did any one try to root it with success ?
Click to expand...
Click to collapse
I find it unlikely that anyone who owns it has tried rooting the CCH yet, Myself included. Of course, I am tempted to root it, but I wouldn't do it until I am sure I can restore everything in case it messes up. The android system recovery that comes with the tablet has no commands for the user, so even a custom recovery would be required to backup/restore. It's not exactly an easily replacable tablet, and the device is quite expensive after all. The reason I am tempted to root is not related to wacom and their tech at all, but once you have root, you end up wanting it across your devices. Unless you want root for a specific app, and unless you're ABSOLUTELY sure that app can benefit from the cintiq, I wouldn't take the risk that comes with trying to root.
That said, you will not be disappointed with the tablet without root, it really is a cintiq on the go, as well as a Tegra 4 android tablet. Really rock solid performance, excellent battery life( I actually did clock 12 hours straight on high performance), and pretty much pure android without any fancy changes.
Maybe I'll succumb and try to root someday, but that's a remote possibility. Unless I end up damaging it somehow, and replacement seems inevitable, in which case I'll try it before replacing.
This is Wacom's reply to an enquiry about rooting: http://forum.wacom.eu/viewtopic.php?f=12&t=15901
This is a nearly two-year-old thread, but now that I have my own CCH thanks to a bit of luck on eBay, I should report that yes, you CAN root it!
Wacom's complete negligence in updating it does have one benefit: towelroot still works due to the old January 2014-dated kernel, but you need towelroot v1 and not v3 as currently offered on towelroot.com. I figured this out when I looked up other Tegra 4-based systems and how well towelroot worked on those.
From there on, just let SuperSU update the binary, and then you're good.
I feel like this is just the beginning of figuring out how to update the CCH to a recent version of Android, since Wacom themselves have been even less than useless with properly supporting it during its lifespan and have now discontinued it with no pretense of further support. @aniruddhahar, you with me here? We both know what this thing's capable of if they'd just updated it past Jelly Bean, and with Android N on the horizon and finally baking multi-window into base AOSP, the timing couldn't be better!
This is indeed some heartening news, thanks @NamelessFragger ! The CCH hardware checks out to run at least lollipop/marshmallow, and frankly I'd be happy to even get past Jelly Bean to KK or Lollipop. However, the problem is the role the CCH plays at work. It's easy to replace a smartphone or a tablet, but a damaged Cintiq could mean 1000-2000 USD for replacement. Having said that, I'll be trying to root it at least. But unless we get some info about the hardware switch from android mode to desktop mode, I find it doubtful that we may be able to upgrade the device while still retaining the Cintiq capabilities which are vital to any CCH artist using the device in daily production work.
Also, I cannot find links to the v1 APK of towelroot anywhere. Could you please upload it here?
I wonder if this news should also be shared on the Wacom forums...
@aniruddhahar: I figure that's one of the major reasons the CCH dev scene is nonexistent - the likelihood that anyone who is willing to pay well over $1,000 for one of these things depends on it working reliably and without issue to make a living. Not only would it be expensive to replace, but the downtime until replacement is a major setback to an artist's livelihood who needs it to work.
It's not a toy - it's a tool, and one that can do something that almost no other tablet computer can do nearly as well as it does.
However, while Wacom doesn't feel like handing out the source code that would reveal whatever kernel modifications they made to make the monitor mode switch work, I have a feeling that with enough effort, we could reverse-engineer their implementation. The Tegra 4 sources for other devices like the NVIDIA Shield Portable is already floating around out there, and that could be a potential launching point for an updated Android ROM, even if it might take a while before we get the monitor mode switch going. We might even have pen digitizer-related sources from Samsung's various Galaxy Note products that may also help to a limited extent, differences in digitizers aside.
There's more important things to tackle before any custom ROM efforts, however, like getting a custom recovery set up so that we can easily flash Nandroid backups and future custom ROMs.
As things currently stand, I haven't seen Wacom put out any ROM images and PC-based flashing utilities like most other Android manufacturers, so unless your idea of a recovery is hard-dumping the NAND with an eMMC reader and hard-flashing it with a known good dump if your system becomes unbootable, tread carefully.
towelroot v1
any safe links to towelroot v1?
did you try v3 and it failed?
I am a dev... In fact, I'm working on a custom filesystem at work right now. I have a CCH and like many.. I find it difficult to look at knowing how awesome the hardware is and how Wacom abandoned it. I was doing everything with this unit... movies, video games, video conferencing, etc. I read comics, and holding the unit vertically makes for an excellent digital comic book experience.
It is, quite frankly, the best tablet experience I've ever had. And it's sitting there on Jellybean.
How close are we to pulling he trigger on a GPL violation submission? I understand they've "lost" the source?
bumpity bump bump
Would really like to see some progress here.
Did someone actually root the Hybrid with towelroot v1? Did we ever hear back from Wacom on getting the source?
They shut their forums down, unfortunately. This is really the only other thread on the internet discussing the cintiq hybrid. Such a shame.
-toad
I rooted my Hybrid last November, but I didn't use towelroot, so I can't speak to that method. I used KingoRoot v1.4.2 for PC. It's been a while (not to mention the long parade of root tools/apps that failed before that), so I don't remember exactly, step-by-step, how I originally did it.
In the hopes that this might help other Hybrid owners, I've scoured my Hybrid and computer for any related files, zipped them and posted a link below for posterity.
EDIT: Unfortunately, I mostly lurk here, and the site won't let me post outside links until I have at least 10 posts--which I don't--so I had to get creative with the urls. :\
Files I'm including:
KingoRoot Apk v1.9
com.kingoroot.com-2.apk
KingoRoot v1.4.2 for PC
android_root.exe
KingoUser Apk v2.0.5
KingoUser.apk
Kingo Android Root.url
The files are provided AS-IS. I make no guarantee that they won't blow up your device. If your device explodes into a barrage of radioactive shrapnel, I am NOT responsible. These files worked for me. They may not work for you, and I have no idea if newer updates work either. Your mileage may vary.
**TRY AT YOUR OWN RISK**
So... Doom and gloom aside...
dracolusus.com/xda-developers/devices/cintiq-companion-hybrid/cintiq-root.zip
You can visit KingoRoot's website here:
kingoapp.com/android-root.htm
I think I installed the PC program first, plugged the tablet into the comp, and the program pushed KingoUser.apk (SuperUser) to the device. I'm not sure about the KingoRoot apk, though; I may have downloaded it from the play store separately either before or after rooting, or it could have been pushed by the program too, but I don't remember now.
More Bump
I got my Companion Hybrid about a year ago, and was astonished that Wacom didn't even try to provide updates for the Cintiq. I love the thing, but there is no immersive mode, the notification bar crashes the UI sometimes, and whatever background I have set will reset to the default jelly bean one after about a week. It's infuriating that someone could put so little effort into providing stable software, but still lock out people who are willing to put the work in.
When I called Wacom's support about getting root access, the guy who helped me just said its not possible, that there will be no updates ever, and that Wacom no longer supports the Companion Hybrid at all beyond the 1-year replacement warranty.
My biggest complaint of all is that when the tablet is in Android mode all the hardware buttons are pretty much useless.
This is all just a big rant I guess, but I would LOVE to see this thing running Android 5 or 6. This tablet has so much untapped potential.
Slightly off-topic but CCH owners are very hard to track down and Wacom forums are down so cannot ask there. I recently acquired a CCH by pure luck but the previous owner reset it before sending and that wiped some fix to the camera that he had applied which means when I open camera app in Android mode it shows 'Cannot connect to Camera'. He swears there was a fix for this which he can no longer find.
I don't want to send it back but just trying my luck here to see if anyone knows of this issue and the possible fix? When connected to PC, the front camera works fine with Skype with notification blue LED and all..
Sorry if it is the wrong thread but since my new thread will probably not catch you attention I thought I will post here.
Thanks.
I wasn't aware of any camera issue, since my camera has always worked fine. I got mine second hand off e-bay, though, so maybe its original owner applied the fix. I didn't pay too close attention to whether or not it had been reset before being sent to me; I was more focused on getting it rooted.
I did a quick google search for the issue, but only this thread and some post about the Surface Pro camera app came up. If you could post some more info about it, I'll see if I can find any useful files on mine.
Hopefully, a more experienced user will grace us with their expertise...
Camera never worked on mine, any camera or gallery app just crashes. I got it off eBay on July 2014 and it was factory reset when I got. Did some firmware update using Wacom settings app but didn't fix camera.
As for original question: KingRoot (kingroot.net/tutorials) worked perfectly for me.
Me 2!
if anyone ever figures this out- please please email me! I use cch as my daily work tool and so disappointed from day one on the android mode. Thought I would be able to use it as a bring home, over coffee at Starbucks, hotel lobby art pad; but instead its locked in at work, poorly connected with its craptastic matrix like cable system, nearly immobile.
need to crack this egg [email protected]
I realize this is a bit old, but for anyone looking to do this, New King Root works just fine.
Sinsecond said:
A month ago I sold all of my tablets and have bought the Wacom Cintiq Companion Hybrid.
Primarily verifiable need for it to work. But since I now possessed no other tablet, I quickly found that my root right for certain things missing for recreational use. To use the Sixaxis app for example.
So I wanted to ask here if maybe a developer have already dealt with it, to root the device.
Would be really happy.
sorry for my english, my best friend is google translate
regards
Alex
Click to expand...
Click to collapse
Bump
Any progress? I found this thread a few years ago and have waited for it to update lol
I've basically had mine since release, neither camera worked. It just crashes.
I still don't trust KingoRoot after all the reports of stealing IMEIs and other such data. towelroot is proven, and I'll toss up a Dropbox link for you all if needed. It's actually taken from an archived version of the site anyway.
http://web.archive.org/web/20140616011907/http://towelroot.com/
Both of my cameras work, though neither are particularly good in the image quality department. Not sure what to say there regarding the camera app crashing.
Also, I apologize for being many months late to this, but ever since the Wacom forums went down and this thread got buried, I didn't think I'd get in contact with the CCH community at large again:
cloudtoad said:
any safe links to towelroot v1?
did you try v3 and it failed?
I am a dev... In fact, I'm working on a custom filesystem at work right now. I have a CCH and like many.. I find it difficult to look at knowing how awesome the hardware is and how Wacom abandoned it. I was doing everything with this unit... movies, video games, video conferencing, etc. I read comics, and holding the unit vertically makes for an excellent digital comic book experience.
It is, quite frankly, the best tablet experience I've ever had. And it's sitting there on Jellybean.
How close are we to pulling he trigger on a GPL violation submission? I understand they've "lost" the source?
Click to expand...
Click to collapse
I tried v3, and it failed. v1 worked.
I've had no updates on the source code situation over these past few months, so consider that trigger pulled, even if they've lost the source.
Anyway, let me reiterate my findings, many of which are going to make development on this a pain:
-There is no fastboot mode. Seriously, I have yet to find a way to get it to work, because the usual adb commands don't work. It may not even be present. Because of this, I don't even know if the bootloader's locked or unlocked. We can only pray it's the latter.
-APX mode is present like you'd expect on a Tegra device (assuming ExpressKeys on left, hold the top two buttons down while powering on until the status LED flashes red), but without a proper image to use with Nvflash, it's of no use. I doubt Wacom has such a recovery image to give us in the first place.
-The stock recovery is the most useless stock recovery I've ever seen! Your only option is to hit the center rocker button or the power button to reboot normally, as there's no menu.
-Backing up the boot and recovery partitions is trivial with Flashify, or more recently, FlashFire once you're rooted. What ISN'T trivial is just unpacking and repacking them consistently, such that the repacked version with no change to the contents is identical to the original. Maybe I just haven't found the right tools yet.
-I have not tested any attempts to reflash the recovery partition yet. Compiling TWRP is a bit in over my head, especially for a device without proper kernel sources, and the CWM Builder site's long dead. TWRP has no equivalent. At least you don't have to worry about things like getting Cintiq mode working in recovery, which should simplify things should we have to resort to using generic Tegra 4 sources.
-NVIDIA's dropped software support for Tegra 4, so it doesn't have official kernel/driver/whatever code updates for Android Marshmallow onward. Porting the latest Nougat over may prove even more troublesome as a result, and it's already confirmed that the Remix Ultratablet (which uses the same SoC) won't be getting RemixOS 3.0 officially because of it.
The cards are stacked against us, but nevertheless, I still feel this is one piece of hardware that deserves some community support since Wacom let everyone down on updates.
I want to do something with 13.3.2.8, if I can...
I was running 13.3.2.1 before, and everything was working fine but one day the OTA update showed up and messed up everything.
I know in previous threads about 13.3.2.8 they have said you can't do anything with it (root, TWRP) , but is there any way I can go back to 3.2.1?
You can still root and install Safestrap (as well as ggow's HDX Nexus ROM) on x.3.2.8.
EncryptedCurse said:
You can still root and install Safestrap (as well as ggow's HDX Nexus ROM) on x.3.2.8.
Click to expand...
Click to collapse
after i install the HDX Nexus ROM can I install TWRP then upgrade to CM11?
Iamreallybadwithusernames said:
after i install the HDX Nexus ROM can I install TWRP then upgrade to CM11?
Click to expand...
Click to collapse
No, you're stuck with Safestrap (which means no TWRP or CyanogenMod).
Iamreallybadwithusernames said:
I want to do something with 13.3.2.8, if I can...
I was running 13.3.2.1 before, and everything was working fine but one day the OTA update showed up and messed up everything.
I know in previous threads about 13.3.2.8 they have said you can't do anything with it (root, TWRP) , but is there any way I can go back to 3.2.1?
Click to expand...
Click to collapse
If you have a "legitimate" excuse for what was messed up, you could consider complaining to Amazon and see if they will roll you back (as they have done for people from 4.x to 3.2.8. They probably won't want to, and will probably lie to you and say it can't be done (as they said to many people asking for 3.2.8)... but, again, if you have a good reason, you could get away with it. I'd suggest reading up on the 3.2.8 rollback threads to see what worked for those people.
If you DO come up with a way to have them roll you back, I'm sure others would love to do this as well, so I'd also advise you to read up on how to "capture" the OTA rollback, so that you can share it with others here... just like people did with 3.2.8. We would all be very appreciative!
schwinn8 said:
If you have a "legitimate" excuse for what was messed up, you could consider complaining to Amazon and see if they will roll you back (as they have done for people from 4.x to 3.2.8. They probably won't want to, and will probably lie to you and say it can't be done (as they said to many people asking for 3.2.8)... but, again, if you have a good reason, you could get away with it. I'd suggest reading up on the 3.2.8 rollback threads to see what worked for those people.
If you DO come up with a way to have them roll you back, I'm sure others would love to do this as well, so I'd also advise you to read up on how to "capture" the OTA rollback, so that you can share it with others here... just like people did with 3.2.8. We would all be very appreciative!
Click to expand...
Click to collapse
I don't believe Amazon agents intentionally 'lie'. Recently there has been little/no pushback on downgrading thor (7") devices from 4.x to 3.2.8. At least not reported in the forums. The confussion came with 8.9" devices as Amazon attempted to distinguish between and develop policies for Apollo and Saturn. A few users with 8.9" devices got rolled back; most others were denied until things got sorted. That created an uproar. Today Apollo (older 8.9") devices can be rolled back; Saturn (newer 8.9" w/2.5GHz processor) can not. Of course, individual agents understanding of the policy will vary. Sometimes it's just easier to call back and hope the next agent is a little more knowledgeable.
There is no need to capture the rollback file for thor; done quite some time ago.
Hey, I am no Amazon fanboy. They got dem warts like everyone else. But I do believe Amazon tries hard to make things right (when reasonable) and generally provide a level of service far superior to almost any other device manufacturer. Apple might be the exception. Oh wait, they don't roll back either ...
@Iamreallybadwithusernames: If you got upgraded to 3.2.7/3.2.8 you can not roll back. There is no evidence Amazon has ever rolled a user back from these versions. If you got upgraded to 4.x you can probably roll back to 3.2.8 ... but no further.
Davey126 said:
I don't believe Amazon agents intentionally 'lie'. Recently there has been little/no pushback on downgrading thor (7") devices from 4.x to 3.2.8. At least not reported in the forums. The confussion came with 8.9" devices as Amazon attempted to distinguish between and develop policies for Apollo and Saturn. A few users with 8.9" devices got rolled back; most others were denied until things got sorted. That created an uproar. Today Apollo (older 8.9") devices can be rolled back; Saturn (newer 8.9" w/2.5GHz processor) can not. Of course, individual agents understanding of the policy will vary. Sometimes it's just easier to call back and hope the next agent is a little more knowledgeable.
There is no need to capture the rollback file for thor; done quite some time ago.
Hey, I am no Amazon fanboy. They got dem warts like everyone else. But I do believe Amazon tries hard to make things right (when reasonable) and generally provide a level of service far superior to almost any other device manufacturer. Apple might be the exception. Oh wait, they don't roll back either ...
@Iamreallybadwithusernames: If you got upgraded to 3.2.7/3.2.8 you can not roll back. There is no evidence Amazon has ever rolled a user back from these versions. If you got upgraded to 4.x you can probably roll back to 3.2.8 ... but no further.
Click to expand...
Click to collapse
You're too peaceful for an internet forum, Davey126 But, seriously, you are correct. They may not intentionally lie, but I do take offense when people answer something without being 100% sure and/or asking if they are even a little unsure. Too often, CS agents take the shortcut and just keep following the script even when presented with contradictory evidence. As for the lack of training/forwarding of the "new" information, I can't blame anyone but Amazon for that. Yes, they do a better job than others, but that's not saying much as I think we both agree... so setting the bar that low isn't good enough and I feel they should be called out on these issues when they appear. In the end, I think we are on the same page... just wanted to clarify my point there.
As for the rollback, IF (and that's a big IF) this person can get them to perform a rollback to an earlier version, then great. I just hope they can learn the capture process and share it with others. Fact is, there is nothing technically preventing Amazon from providing an older rollback... they just don't want to for their own reasons (ie, they want to keep the device locked down). Frankly, I hate the fact that any of these devices are locked down at all. Consumers ran into this back in the early days of computers, where we were "locked down" to the OS provided, hardware originally sold, etc, which was absolute crap. Heck, remember when telephones were similarly locked down? Ridiculous. These devices should similarly not be "allowed" to be locked down.... and it's annoying to see such a backwards step in technology "policy" especially when there's no reason for it.
Lastly, regarding the Amazon customer service. Normally, I agree, they are pretty good. In the case of this device, I am VERY disappointed. I bought this device with the intent of using a specific app on their appstore. They have since removed the app from their store (it's still available on other appstores) with no explanation to me or the app maker. Furthermore, the app-maker says Amazon will likely be blocking some of the app's functionality in the near future, thereby breaking it. The device is still under warranty and I have spent many hours with Amazon support on this matter (phone, chat, and email) and I just get a runaround, repeated suggestions that I've already told them do not work, etc... and keep getting no answers (much less solutions) to anything. So, I'm rather annoyed and upset with Kindle support on this one.... hence my (hopefully understandable) attitude on the matter....
schwinn8 said:
You're too peaceful for an internet forum, Davey126
Click to expand...
Click to collapse
Lol! There is a pretty heavy filter between brain and fingers. We are probably further apart than you might think. As a consumer I wish all devices came unlocked. From a business perspective this makes little sense. In Amazon's shoes I would behave the same way, although I might release an unlocked 'developer' edition at a premium price point to help quell the small but vocal enthusiast community. I also understand your frustration with Amazon support. Having managed a call center (not boasting; just part of my portfolio) trying to keep agents on the same page is akin to herding cats. There are a host of reasons behind this which I won't delve into here for fear of offending someone. It's a tough job - especially given the economic pressures facing both employer and employee. That does not mitigate your personal experiences; I'd be a bit miffed too.
Ignore this post, didn't quote accidentally
Davey126 said:
Lol! There is a pretty heavy filter between brain and fingers. We are probably further apart than you might think. As a consumer I wish all devices came unlocked. From a business perspective this makes little sense. In Amazon's shoes I would behave the same way, although I might release an unlocked 'developer' edition at a premium price point to help quell the small but vocal enthusiast community. I also understand your frustration with Amazon support. Having managed a call center (not boasting; just part of my portfolio) trying to keep agents on the same page is akin to herding cats. There are a host of reasons behind this which I won't delve into here for fear of offending someone. It's a tough job - especially given the economic pressures facing both employer and employee. That does not mitigate your personal experiences; I'd be a bit miffed too.
Click to expand...
Click to collapse
Iamreallybadwithusernames said:
Sorry. had some complications on my side figuring out how to log back in when I initially made this account with my google account....
Anyways, some users have tried manually downgrading with the 3.2.5 file, and have failed (in some cases even bricked their devices). So it actually isn't possible (someone probably could hack the device to figure out how to allow it to roll back from 3.2.8, but that would probably take longer than figuring out TWRP & other root things for 4.5.3)
My device DID come with 13.3.1.0, I wanted to stay on stock (a mistake) so I used one of those OTA disablers, which (as the title states) didn't work.
but amazon decided that they didn't care that I got rolled back, and one morning when I turned it on, I was back on 4.5.3.
I wonder if I could make up some drama about my device having some issues or whatever, and they would replace it and maybe it would come with 13.3.1.0? (it actually has been picky about WiFI, so maybe I would actually legitimately get it replaced)
Click to expand...
Click to collapse
Sorry for double posting, I accidentally didn't quote you.
schwinn8 said:
You're too peaceful for an internet forum, Davey126 But, seriously, you are correct. They may not intentionally lie, but I do take offense when people answer something without being 100% sure and/or asking if they are even a little unsure. Too often, CS agents take the shortcut and just keep following the script even when presented with contradictory evidence. As for the lack of training/forwarding of the "new" information, I can't blame anyone but Amazon for that. Yes, they do a better job than others, but that's not saying much as I think we both agree... so setting the bar that low isn't good enough and I feel they should be called out on these issues when they appear. In the end, I think we are on the same page... just wanted to clarify my point there.
As for the rollback, IF (and that's a big IF) this person can get them to perform a rollback to an earlier version, then great. I just hope they can learn the capture process and share it with others. Fact is, there is nothing technically preventing Amazon from providing an older rollback... they just don't want to for their own reasons (ie, they want to keep the device locked down). Frankly, I hate the fact that any of these devices are locked down at all. Consumers ran into this back in the early days of computers, where we were "locked down" to the OS provided, hardware originally sold, etc, which was absolute crap. Heck, remember when telephones were similarly locked down? Ridiculous. These devices should similarly not be "allowed" to be locked down.... and it's annoying to see such a backwards step in technology "policy" especially when there's no reason for it.
Lastly, regarding the Amazon customer service. Normally, I agree, they are pretty good. In the case of this device, I am VERY disappointed. I bought this device with the intent of using a specific app on their appstore. They have since removed the app from their store (it's still available on other appstores) with no explanation to me or the app maker. Furthermore, the app-maker says Amazon will likely be blocking some of the app's functionality in the near future, thereby breaking it. The device is still under warranty and I have spent many hours with Amazon support on this matter (phone, chat, and email) and I just get a runaround, repeated suggestions that I've already told them do not work, etc... and keep getting no answers (much less solutions) to anything. So, I'm rather annoyed and upset with Kindle support on this one.... hence my (hopefully understandable) attitude on the matter....
Click to expand...
Click to collapse
This is the third one of the same, I meant to quote you and dave but accidentally quoted myself and dave instead. oops.
Sorry. had some complications on my side figuring out how to log back in when I initially made this account with my google account....
Anyways, some users have tried manually downgrading with the 3.2.5 file, and have failed (in some cases even bricked their devices). So it actually isn't possible (someone probably could hack the device to figure out how to allow it to roll back from 3.2.8, but that would probably take longer than figuring out TWRP & other root things for 4.5.3)
My device DID come with 13.3.1.0, I wanted to stay on stock (a mistake) so I used one of those OTA disablers, which (as the title states) didn't work.
but amazon decided that they didn't care that I got rolled back, and one morning when I turned it on, I was back on 4.5.3.
I wonder if I could make up some drama about my device having some issues or whatever, and they would replace it and maybe it would come with 13.3.1.0? (it actually has been picky about WiFI, so maybe I would actually legitimately get it replaced)
Iamreallybadwithusernames said:
I wonder if I could make up some drama about my device having some issues or whatever, and they would replace it and maybe it would come with 13.3.1.0? (it actually has been picky about WiFI, so maybe I would actually legitimately get it replaced)
Click to expand...
Click to collapse
If the device is still under warranty and you are having troubles with WiFi then I would not hesitate to engage Amazon on remediations which likely will entail swapping out for a refurbished unit. I think it unlikely the replacement will arrive with 13.3.1.0. Not what you wanted to hear but 13.3.x.x is getting long in the legs. Amazon would rather you be on 13.4.x.x and likely is imaging refurbished units accordingly.
just had kindle fire hdx replaced
Davey126 said:
If the device is still under warranty and you are having troubles with WiFi then I would not hesitate to engage Amazon on remediations which likely will entail swapping out for a refurbished unit. I think it unlikely the replacement will arrive with 13.3.1.0. Not what you wanted to hear but 13.3.x.x is getting long in the legs. Amazon would rather you be on 13.4.x.x and likely is imaging refurbished units accordingly.
Click to expand...
Click to collapse
Amazon just replaced my kindle fire hdx about a week ago and the reverb unit I received had 13.3.2.1 on it. This is the second referb I have gotten from amazon with 13.3.2.1 so there is at least a chance if they send you a replacement that it will have a 13.3.2.1 on it just be sure to keep WiFi off cause it will try to update as soon as it connects to wifi. Until you get root with towel root and use hdxposed to prevent updates. Good luck
ja49902 said:
Amazon just replaced my kindle fire hdx about a week ago and the reverb unit I received had 13.3.2.1 on it. This is the second referb I have gotten from amazon with 13.3.2.1 so there is at least a chance if they send you a replacement that it will have a 13.3.2.1 on it just be sure to keep WiFi off cause it will try to update as soon as it connects to wifi. Until you get root with towel root and use hdxposed to prevent updates. Good luck
Click to expand...
Click to collapse
Alternatively, use HDX Toolkit which offers both root and OTA blocking along with several other features. Hdxposed it it can become disabled (including the OTA blocker) if, for whatever reason, xposed framework doesn't load properly at boot. HDX toolkit disables and/or renames OTA services. I have yet to hear of a Kindle auto-updating after applying this blocker.
BTW - great to hear a Amazon is still distributing refurbs with 3.2.1! Kinda amazing given the aggressive steps (efuse) Amazon took in later versions to block rollbacks.
(running KitKat) I received this for my birthday, and was advised by Linux tech friends to come straight here, greets everyone.
My goal with this tablet is to watch tutorials and grab faster bandwidth for uploads and downloads when in range - nothing too exotic.
I'm hoping to persuade the goods out of anyone familiar with this. If it's TOO bad there's time to return it, but my real concern is just battery life and if a ROM can help it to OTG while charging at the same time, or alternate means to power it if I go camping or am away from power.
All I've done in the meantime is disabled apps I know I don't want, and rooted it for a while (Kingo Root) just for AppFreeze but ditched both.
Any and all info and comments, even bad ones, are really appreciated! I have decades on Windows Mac and bits and pieces of Linux. No Android but I can find my way around.
Was this worth buying?
JoeyTablet said:
(running KitKat) I received this for my birthday, and was advised by Linux tech friends to come straight here, greets everyone.
My goal with this tablet is to watch tutorials and grab faster bandwidth for uploads and downloads when in range - nothing too exotic.
I'm hoping to persuade the goods out of anyone familiar with this. If it's TOO bad there's time to return it, but my real concern is just battery life and if a ROM can help it to OTG while charging at the same time, or alternate means to power it if I go camping or am away from power.
All I've done in the meantime is disabled apps I know I don't want, and rooted it for a while (Kingo Root) just for AppFreeze but ditched both.
Any and all info and comments, even bad ones, are really appreciated! I have decades on Windows Mac and bits and pieces of Linux. No Android but I can find my way around.
Was this worth buying?
Click to expand...
Click to collapse
I definitely think it was worth buying. It's fast and has a nice screen for not being HD. I was in a bad accident a month ago and my mom bought it for me to waste time in the hospital and skilled care facility. I haven't found any roms for it yet, I just opened a thread about that.
Sorry I don't have any more info for you, I'll be keeping an eye on this thread for sure.
First of all I hope you recovered well - I hadn't logged in here for ages. Super nice of your mom to get you one in your time of suffering and recovery.
Lately I've hoped this could upgrade to at least Android 5 because of an app that would allow me to use the tablet as a remote control for the audio workstation Presonus Studio One.
I emailed the G5 people (they seem gone now) who told me they didn't have a ROM to upgrade the tablet.
Any upgrade is better than where I stand with Android 4.4. Nothing that matters runs on it and the tablet sees wasted with no use.
I've been trying to get this device how I wanted it to be ever since I beta tested it, but due to life, law school, and marriage, I have been noticeably absent from the dev community lately. For that I apologize.
As I am concluding my legal studies, I have began revisiting some of my old broken-ish but bootable code from my Lollipop build, and am considering, if enough people are still using this thing, to try and build Nougat.
The chipset is identical to the Galaxy Nexus, as I am sure most people know at this point, and wollac has did one helluva job putting in the work to form a solid base to build upon. Admittedly, this is going to be a moderately-difficult project, bordering on a labor of nostalgia, but if there is enough interest, I will get to work so we can keep using this obsolete bowling ball for another year or two. I still use the KitKat build as an amp and NES emulator.
Let me know what you guys think.
-JM
I'm definitely interested, I would love to be able to use my Q with the original LED functionality
+1 on the LED functionality, but I fear that there aren't many in circulation anymore... Mine is gathering dust underneath the TV, a chromecast does its intended functionality much better :/
I just bought one, and I'm not sure how I can even use it at this point. Are you still considering development of something for the q?
I still have mine literally sitting there until something comes along. I would welcome any development on the Q!
I'll echo the others... I have mine sitting the corner of my office, under the printer waiting and hoping for it to be usable one day. I unfortunately bought mine right after they pulled the plug, not know about it so it has never actually worked! I really just hope to be able see the LEDs and stream music to it, even if just through chromecast. I heard it had a great amp and I have some old quality speakers laying around somewhere.
I'm interested as well. I'd love to be able to use it as a chromecast audio, or something similar. Personally, I'd prefer to be able to use it without a display.
does anyone know how to get the Nexus Q software? Got one without the manuals or software
I am interested. What would be the goal though?
There has to be a limited amount of these in existence and it would be neat to be able to use it for something useful.
Is a Chromecast type device reasonable? I'd use it in my office just as a novelty.
I would love something newer than the 4.4 build on this forum currently, and get some use out of this dustcollector. Personally i would like to just get the amp working, any other functionality I really dont care too much about.
Anything Lollipop or better would be great. I use the Google ADT-1 with stock Lollipop and really like it. Works fine for me. Maybe Kit Kat could be OK but I'm not sure.
I am interested. How do I get started?
I'll give this a +1
I still got mine and been thinking what to do with it... any new development i wouldnt mind trying.
I am interested in the restart as well
I have two and would love to use them.
Hi. I interested in Android 7. Youtube and youtube Music still working on Android 7, so i can build media-center on Q with android 6+.