I have both input and questions.
First question, directed mostly to the devs who've started this and the average transformer owner's impression of what's going on:
What do you see the future of this tablet being? do you see it as very successful with a lot of roms, or do you see it as something that slides by with not much more dev than modified stock roms?
I will update this post with information for people interested in buying the Transformer and explicitly interested in development as soon as there is new information.
Another set of points:
I've seen people ask several questions in this forum, and i've congregated these ideas and some of my own.
CyanogenMod (with enhancements from the viewsonic Gslate)
Ubuntu
Multi-booting off SD or 16g main partition
Other roms from other tablets (as cool device-manufacturer software overlays come out)
AOSP for development (honeycomb of course, google has to release source )
KERNELS KERNELS KERNELS (i can see already that this is the strongpoint in XOOM development insofar)
I will update this list as necessary.
Thanks for reading. This thread will hopefully become a congregation of information for people who WANT TO BE DEVELOPERS and are considering BUYING THIS DEVICE. I want this Tablet to be as good as a platform as my G1 has been (it's still hoppin' in there ), and what i've seen spring up on devices like the Galaxy S line (2 of those devices here), and with the xoom already.
Thanks.
I will be responsible and be updating this thread. I may imitate RoyalKnight's Rom Bible in this thread (cf. G1 or MT3GS DEV)
I also have interest in becoming a Transformer Mod, let me know if that's available (of course i want to buy the thing first) lol.
Paul at MoDaCo has one. This is good. Also no offense to BadWolve1, I didn't know there was already a Mod for this section, i'll leave the above up for timesake.
jcarrz1 said:
I also have interest in becoming a Transformer Mod, let me know if that's available (of course i want to buy the thing first) lol.
Click to expand...
Click to collapse
Theres a long list
I'll leave this in Dev, as it does contain Development info.
Badwolve1
Transformer vs Iconia
http://forum.xda-developers.com/showthread.php?p=15960291#post15960291
I'm not attemption to make "one of those threads" again in each forum. Instead I am attempting to make one streamlined thread with all of the information someone would need to make an educated decision about which tablet they would like to buy. All input is very appreciated.
Thanks.
monkeychef said:
Transformer vs Iconia
http://forum.xda-developers.com/showthread.php?p=15960291#post15960291
I'm not attemption to make "one of those threads" again in each forum. Instead I am attempting to make one streamlined thread with all of the information someone would need to make an educated decision about which tablet they would like to buy. All input is very appreciated.
Thanks.
Click to expand...
Click to collapse
Did you really just make a thread linking to another thread you just made?
Also, there is already an extensive TF VS Acer thread that you'd might of found if you looked.
monkeychef said:
Transformer vs Iconia
http://forum.xda-developers.com/showthread.php?p=15960291#post15960291
I'm not attemption to make "one of those threads" again in each forum. Instead I am attempting to make one streamlined thread with all of the information someone would need to make an educated decision about which tablet they would like to buy. All input is very appreciated.
Thanks.
Click to expand...
Click to collapse
If you are 'educated', you're not seriously thinking of buying an Iconia over a Transformer anyway are you?
Of all the tablets available at the moment:
Transformer
Xoom
GTab 10.1
Iconia
Archos
Vega
It woud be a difficult choice for a worse tablet than a Xoom or an Iconia, both have screens that can only be described as ****! which is surely worth noting when buying an Android tablet.
There's only one at the moment that can compete with the Transformer and it's not even out yet!
Let's do a petition to unlock the nvflash function on the new bootloader.
For that i need same help because a can't write well in english (i'm portuguese ).
Try it's free so i think we must try!
12345
GO GO GO :laugh:
EDIT:
The petition is ONLINE
Hey mates! I know some of you were very disappointed when they realized Asus prevented NVFlash in there OTA 9.4.5.30 and higher...
So we decided over at the TF300 forums to make a petition and also to include TF700 as both TF300 and TF700 are suffering from the same problem.
You can vote for the petition here!
Share this with all android enthusiasts you know so we get as much votes as possible and Asus reverts their changes! If we have some votes together we can send them an E-Mail with the petition or make a suggestion here... But for now, vote and send the petition to everybody you know!
If there is some positive feedback over here too I'll contact a mod to make the thread sticky, because it's pointless if I don't know if you really want it
For those who don't know what NVFlash is: Dev Thread, xda developers wiki
Click to expand...
Click to collapse
Many thanks to user -angel* that make this possible!!
Let's sign!!
Facebook Page: here!
SHARE, SHARE AND SHARE
Where do you want send this petition? In JB bootloader APX mode is locked. You can enter Apx, but It won't work.
Hazard17 said:
Where do you want send this petition? In JB bootloader APX mode is locked. You can enter Apx, but It won't work.
Click to expand...
Click to collapse
to asus..this petiton it's to unlock the nvflash function.
Also each one of us can send a email to asus asking for that function
nuno407 said:
Let's do a petition to unlock the nvflash function on the new bootloader.
For that i need same help because a can't write well in english (i'm portuguese ).
Try it's free so i think we must try!
12345
GO GO GO :laugh:
Click to expand...
Click to collapse
I highly doubt that'll work - I just remember how supportive HTC was when DHD users tried to get at least something released for their devices so ICS would work properly on the device...
But if it should happen that a petition like you mentioned is created - I'll sign it
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
nuno407 said:
to asus..this petiton it's to unlock the nvflash function.
Also each one of us can send a email to asus asking for that function
Click to expand...
Click to collapse
lol, guess the mail would result in more
l33ch0r said:
I highly doubt that'll work - I just remember how supportive HTC was when DHD users tried to get at least something released for their devices so ICS would work properly on the device...
But if it should happen that a petition like you mentioned is created - I'll sign it
---------- Post added at 10:21 PM ---------- Previous post was at 10:19 PM ----------
lol, guess the mail would result in more
Click to expand...
Click to collapse
Asus may be a little different. We are able to unlock the bootloader with an app provided by Asus because of a past petition.
[Petition][UPDATED]Unlock the bootloader for the Asus TF300, Unlock is Here!
tobdaryl said:
Asus may be a little different. We are able to unlock the bootloader with an app provided by Asus because of a past petition.
[Petition][UPDATED]Unlock the bootloader for the Asus TF300, Unlock is Here!
Click to expand...
Click to collapse
Well, I heard about that as well - but nonetheless I doubt that something like that could happen again. But if you try anyways, count me in
Re: [Petition] NVFlash on JB bootloader
Its worth a shot. We have nothing to loose. Count me in.
@OP I was asked in the nvflash thread to make a formal online petition using petitiononline.com... What do you think? Will this thread be sufficient? PM me. I am willing to help in anyway I can.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Well then lets make a petition. Anyone?
I would do it but I wouldn't know what to write. If I look at this old petition for unlocking bootloader it seems to be the work of someone who really knows, what he's talking about.
Where are the geniuses around here?
Re: [Petition] NVFlash on JB bootloader
l33ch0r said:
Well then lets make a petition. Anyone?
I would do it but I wouldn't know what to write. If I look at this old petition for unlocking bootloader it seems to be the work of someone who really knows, what he's talking about.
Where are the geniuses around here?
Click to expand...
Click to collapse
I also dont know what w e should write :/
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
nuno407: Thanks alot grimsonfart for the idea
grimsonfart: no problem
Re: [Petition] NVFlash on JB bootloader
grimsonfart said:
nuno407: Thanks alot grimsonfart for the idea
grimsonfart: no problem
Click to expand...
Click to collapse
?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Well, we could just take the one from bootloader unlock tool and then change the things that were bootloader unlock with nvflash compatibility, but what should be our arguments? It's just a thing like "We don't want to software brick our tablets, because then we'd have to send it to you with what you make cash", but if we get this together I think the formal thing won't be too hard
/e: the only thing would be like that customers would be more safe to optimize there tablets, so there would probably more developers which would also give them more customers?
What exactly would we want from Asus in order to get NVFlash working?
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
-angel* said:
Well, we could just take the one from bootloader unlock tool and then change the things that were bootloader unlock with nvflash compatibility, but what should be our arguments? It's just a thing like "We don't want to software brick our tablets, because then we'd have to send it to you with what you make cash", but if we get this together I think the formal thing won't be too hard
/e: the only thing would be like that customers would be more safe to optimize there tablets, so there would probably more developers which would also give them more customers?
Click to expand...
Click to collapse
Had to laugh at your argument with softbricked
More customers was also a reason in the bootloader unlock petition - seems to have worked
nuno407 said:
?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Im the one who originally asked for a JB nvflash on q&a section, and you commented that you may make a petition for it. Im just being a bit cheeky now
---------- Post added at 08:11 PM ---------- Previous post was at 08:00 PM ----------
But now i bit more on-topic. I dont see why ASUS should say no. There is only ONE reason most people unlock, and that is because of how ****ty the tablet is stock. Its slow and painfull to use, and that is not our fault, so therefor we seek ways to get our tablet to run better but thoose ways are risky. If ASUS would say no, then hell, they should start optimizing their ROM a biiiiiit more
Re: [Petition] NVFlash on JB bootloader
grimsonfart said:
Im the one who originally asked for a JB nvflash on q&a section, and you commented that you may make a petition for it. Im just being a bit cheeky now
---------- Post added at 08:11 PM ---------- Previous post was at 08:00 PM ----------
But now i bit more on-topic. I dont see why ASUS should say no. There is only ONE reason most people unlock, and that is because of how ****ty the tablet is stock. Its slow and painfull to use, and that is not our fault, so therefor we seek ways to get our tablet to run better but thoose ways are risky. If ASUS would say no, then hell, they should start optimizing their ROM a biiiiiit more
Click to expand...
Click to collapse
You think Asus would admit that it's running ****ty? (i don't know if it does, don't owe it yet)
But since Asus was cooperative with Bootloader unlock,I guess if we finally set up a petition, they'll be cooperative again
Sent from my Desire HD using Tapatalk 2
Hm, I made s quick (!) rewrite of the Unlock Petition with main things changed - maybe we could kind of make it like this (but I don't know how this change.org works...)
Dear ASUS/Nvidia,
We are owners and prospective owners of the new ASUS Transformer Pad TF300. However, we were very disappointed that the JB bootloader prevents to use the NVFlash Tool.
While we trust that the TF300 will be well-supported with official updates, this tablet has the potential to be an excellent platform for development by enthusiasts as well, and we think NVFlash would make it even safer for developers and customers. The current inability of the TF300 to use the NVFlash tool is already dissuading some from buying this tablet.
In the past we had already been able to use NVFlash which saved many devices from a brick and buying a new (maybe Non-Asus) tablet which is very appreciated in the Android community. That makes this all the more frustrating that another petition seems to be required for the TF300.
Please consider giving us the ability to use the NVFlash tool on the TF300 again. We assure that this tool will faster a vibrant development community around the TF300 and will promote sales and establish ASUS' reputation in the community as an excellent and receptive supplier of mobile devices.
Yours faithfully,
The Undersigned
-angel* said:
Hm, I made s quick (!) rewrite of the Unlock Petition with main things changed - maybe we could kind of make it like this (but I don't know how this change.org works...)
Dear ASUS/Nvidia,
We are owners and prospective owners of the new ASUS Transformer Pad TF300. However, we were very disappointed that the JB bootloader prevents to use the NVFlash Tool.
While we trust that the TF300 will be well-supported with official updates, this tablet has the potential to be an excellent platform for development by enthusiasts as well, and we think NVFlash would make it even safer for developers and customers. The current inability of the TF300 to use the NVFlash tool is already dissuading some from buying this tablet.
In the past we had already been able to use NVFlash which saved many devices from a brick and buying a new (maybe Non-Asus) tablet which is very appreciated in the Android community. That makes this all the more frustrating that another petition seems to be required for the TF300.
Please consider giving us the ability to use the NVFlash tool on the TF300 again. We assure that this tool will faster a vibrant development community around the TF300 and will promote sales and establish ASUS' reputation in the community as an excellent and receptive supplier of mobile devices.
Yours faithfully,
The Undersigned
Click to expand...
Click to collapse
Nice! Now who has ever done a petition?
Short-form petition
-angel* said:
Hm, I made s quick (!) rewrite of the Unlock Petition with main things changed - maybe we could kind of make it like this (but I don't know how this change.org works...)
Dear ASUS/Nvidia,
We are owners and prospective owners of the new ASUS Transformer Pad TF300. However, we were very disappointed that the JB bootloader prevents to use the NVFlash Tool.
While we trust that the TF300 will be well-supported with official updates, this tablet has the potential to be an excellent platform for development by enthusiasts as well, and we think NVFlash would make it even safer for developers and customers. The current inability of the TF300 to use the NVFlash tool is already dissuading some from buying this tablet.
In the past we had already been able to use NVFlash which saved many devices from a brick and buying a new (maybe Non-Asus) tablet which is very appreciated in the Android community. That makes this all the more frustrating that another petition seems to be required for the TF300.
Please consider giving us the ability to use the NVFlash tool on the TF300 again. We assure that this tool will faster a vibrant development community around the TF300 and will promote sales and establish ASUS' reputation in the community as an excellent and receptive supplier of mobile devices.
Yours faithfully,
The Undersigned
Click to expand...
Click to collapse
How about:
Listen Asus:
We want you to work on an NVFlash version for JB Bootloader and release a working version within this deadline (Date). We are your customers, i.e., we make you what you are. The reason, you ask? If you'd done your homework, such retort would be absolutely superfluous. Now, be a man about it, have some decency and honor your part of the contract. :laugh::laugh::laugh:
Re: [Petition] NVFlash on JB bootloader
graphdarnell said:
How about:
Listen Asus:
We want you to work on an NVFlash version for JB Bootloader and release a working version within this deadline (Date). We are your customers, i.e., we make you what you are. The reason, you ask? If you'd done your homework, such retort would be absolutely superfluous. Now, be a man about it, have some decency and honor your part of the contract. :laugh::laugh::laugh:
Click to expand...
Click to collapse
They won't be making nvflash for us I don't think as each device needs its own specific files to access nvflash. What we need to do is ask Asus to give us some way of disabling or bypassing their new 128 bit encryption key on the jb boot loader. Then we can flash the androidroot boot loader, generate the files needed for wheelie and generate the brick safe files using nvflash. I believe that's all we need... Asus to allow us access to the boot loader and the android root team to make a compatible andriodroot boot loader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Hi, on october I tried posting the following suggestion to the ASUS customer center:
I've read that, after installing the firmware update containing version 4.1 or higher of
Android, the installed bootloader has changed; more precisely, even if still unlockable,
it is digitally signed by ASUS and blocks the backup of its files or the installation of a
new one. This appears wrong and unfair, since ASUS voids their warranty upon unlocking
the bootloader, but leaves the customers with some essential parts of the
device locked. Making the bootloader compatible with backup and flashing tools again
would ensure that software issues will always be recoverable without intervention
from ASUS, as it should be if you promise us that we can trade our warranty for a
device with no constraints.
Therefore, implementing this essential improvements in a future firmware update
would give a better service for the customers.
Click to expand...
Click to collapse
They replied with a standard "thanks we'll take note"-kind of mail, but if you want to take something from it and put it into a petition feel free to do so.
I hope there's a way to convince them that if they let us use NVflash before they should do it again.
For anyone who has purchased the new Kindle Fire HD7 (KFSOWI) please be aware this is not the same device as the 2012 Kindle Fire HD7 (KFTT) and therefore none of the advice posted in this forum is applicable.
I'm posting this before we see multiple posts re bricked devices from people who have been misled by Amazon's naming conventions.
Link to Amazon's specs for all their Kindle devices are here. Its pretty easy to identify what device you have.
https://developer.amazon.com/sdk/fire/specifications.html
IMO This device should be included in the HDX forum along with the other two 3rd gen devices. I've just acquired my first Kindle (KFSOWI) and am loving it but quickly became aware that there is very little support for it on XDA.
It would also be useful if Amazon's device naming conventions were followed in the various Kindle threads. This is the practice for other devices listed on XDA. eg International SGSiii is GTI9300, US LTE Version GTI9305 etc...
Perhaps a mod could look at this and sort it out?
EDIT - I have started a new thread in the HDX forum for discussion of the KFSOWI as i think it would be best discussed in that forum. Link
corrsea said:
For anyone who has purchased the new Kindle Fire HD7 (KFSOWI) please be aware this is not the same device as the 2012 Kindle Fire HD7 (KFTT) and therefore none of the advice posted in this forum is applicable.
I'm posting this before we see multiple posts re bricked devices from people who have been misled by Amazon's naming conventions.
Link to Amazon's specs for all their Kindle devices are here. Its pretty easy to identify what device you have.
https://developer.amazon.com/sdk/fire/specifications.html
IMO This device should be included in the HDX forum along with the other two 3rd gen devices. I've just acquired my first Kindle (KFSOWI) and am loving it but quickly became aware that there is very little support for it on XDA.
It would also be useful if Amazon's device naming conventions were followed in the various Kindle threads. This is the practice for other devices listed on XDA. eg International SGSiii is GTI9300, US LTE Version GTI9305 etc...
Perhaps a mod could look at this and sort it out?
Click to expand...
Click to collapse
Good post. Hopefully others have read around the forum and seen the many other posts noting that none of the newer Kindle's have any root or other exploits available. I suppose an official sticky type of warning would not be such a bad idea though.
corrsea said:
For anyone who has purchased the new Kindle Fire HD7 (KFSOWI) please be aware this is not the same device as the 2012 Kindle Fire HD7 (KFTT) and therefore none of the advice posted in this forum is applicable.
I'm posting this before we see multiple posts re bricked devices from people who have been misled by Amazon's naming conventions.
Link to Amazon's specs for all their Kindle devices are here. Its pretty easy to identify what device you have.
IMO This device should be included in the HDX forum along with the other two 3rd gen devices. I've just acquired my first Kindle (KFSOWI) and am loving it but quickly became aware that there is very little support for it on XDA.
It would also be useful if Amazon's device naming conventions were followed in the various Kindle threads. This is the practice for other devices listed on XDA. eg International SGSiii is GTI9300, US LTE Version GTI9305 etc...
Perhaps a mod could look at this and sort it out?
Click to expand...
Click to collapse
Wow. Thanks! Guess I can stop trying to root my KFSOWI. Tried several times, and thought it was the drivers...
LinearEquation said:
Good post. Hopefully others have read around the forum and seen the many other posts noting that none of the newer Kindle's have any root or other exploits available. I suppose an official sticky type of warning would not be such a bad idea though.
Click to expand...
Click to collapse
Good to know! It's so confusing, Amazon UK currently have the 16 GB Fire HD on sale for £99, but it seems unclear which version that is. It lists a front-facing camera and microphone, so presumably it's the older model? Still, if there's a chance of getting the other one it wouldn't be worth the risk for me. CM still sounds kid of buggy on the KFTT anyway, so a Hudl might be the better option.
It says last generation right on the title of ad. Also, no camera and no HDMI output for 2013 KFHD firmware 11.xxx
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
So can anyone create a new topic about 3rd gen Fire HD?
because I'm trying to find something and at all forums I see mixup between old-hd7 and new-hd7 and no any new-hd7-specific threads.
So new topic will be pretty helpfull!
FAzzzer said:
So can anyone create a new topic about 3rd gen Fire HD?
because I'm trying to find something and at all forums I see mixup between old-hd7 and new-hd7 and no any new-hd7-specific threads.
So new topic will be pretty helpfull!
Click to expand...
Click to collapse
Thank you for this clarification, thought I could save money with a kindlefire hd but i lost 100bucks and got a useless piece of plastic.
Now I can stop loosing time try to root it for 1 weeks , good luck for the new devices root research !
EDIT : after little reading it seems HDX got rooted today ( http://forum.xda-developers.com/showthread.php?t=2542508 )
Does anybody may now if this root works also on KFSOWI 11.3.1.0 ? ( since KFSOWI got same OS it might maybe work ? )
At the moment it's only working on the 8.9 hdx (KFAPWA & KFAPWI). But it's only a matter of time before the other 2 new devices have root as well. I would advise owners of all 3 devices to use the hdx forum as that is where all the development for these devices will occur.
EDIT - I have started a new thread in the HDX forum for discussion of the KFSOWI as i think it would be best discussed in that forum. Link
Sent from my GT-I9300 using Tapatalk
Kakuhin said:
Thank you for this clarification, thought I could save money with a kindlefire hd but i lost 100bucks and got a useless piece of plastic.
Now I can stop loosing time try to root it for 1 weeks , good luck for the new devices root research !
EDIT : after little reading it seems HDX got rooted today ( http://forum.xda-developers.com/showthread.php?t=2542508 )
Does anybody may now if this root works also on KFSOWI 11.3.1.0 ? ( since KFSOWI got same OS it might maybe work ? )
Click to expand...
Click to collapse
Tested it and adresses wont match. I have a pretty slow internet connection, can someone download this:
https://s3.amazonaws.com/kindle-fire-updates/update-kindle-11.3.1.0_user_310084920.bin
and extract boot.img and build.prop (with winrar) and reupload it to this thread?:
http://forum.xda-developers.com/showthread.php?t=2542456
The developers could change the kernel adresses fitting to our device and compile the exploit for us.
FAzzzer said:
So can anyone create a new topic about 3rd gen Fire HD?
because I'm trying to find something and at all forums I see mixup between old-hd7 and new-hd7 and no any new-hd7-specific threads.
So new topic will be pretty helpfull!
Click to expand...
Click to collapse
There is a root available for all the newer Kindle now. Do a search and profit.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
LinearEquation said:
There is a root available for all the newer Kindle now. Do a search and profit.
Click to expand...
Click to collapse
Or make use of the internet-feature named "links"
Root KFSOWI: http://forum.xda-developers.com/showthread.php?t=2544736
By the way: The question was asked here before the above root posting was created.
emale999 said:
Or make use of the internet-feature named "links"
Root KFSOWI: http://forum.xda-developers.com/showthread.php?t=2544736
By the way: The question was asked here before the above root posting was created.
Click to expand...
Click to collapse
Who cares when it was asked. I answered it.
Sent from my Amazon Kindle Fire HD running CM 11 KitKat 4.4 using xda app-developers
Currently, there is confusion between the different ASUS MEmo Pads (Good job with the naming ASUS!), do you think we could split the conversations between the ME572C and the others? I am afraid that advice and comments are being mixed and could lead to bricked devices and other results (Like me getting hopeful for a ROM for the ME572C, when it is still bootloader locked :crying: , only to find out it is not for us)
Etterbeek said:
Currently, there is confusion between the different ASUS MEmo Pads (Good job with the naming ASUS!), do you think we could split the conversations between the ME572C and the others? I am afraid that advice and comments are being mixed and could lead to bricked devices and other results (Like me getting hopeful for a ROM for the ME572C, when it is still bootloader locked :crying: , only to find out it is not for us)
Click to expand...
Click to collapse
I think splitting them into separate forums would help. It is confusing that several different tablets are lumped into the MeMO Pad section here. I think we need a ME572 and a ME176 sub forum. Is it possible that all of the ME17X's could be grouped together? At the very least I would add to the forums rules that posts must identify the Model Number in the title...
Agreed.
Etterbeek said:
Currently, there is confusion between the different ASUS MEmo Pads (Good job with the naming ASUS!), do you think we could split the conversations between the ME572C and the others? I am afraid that advice and comments are being mixed and could lead to bricked devices and other results (Like me getting hopeful for a ROM for the ME572C, when it is still bootloader locked :crying: , only to find out it is not for us)
Click to expand...
Click to collapse
muiriddin said:
I think splitting them into separate forums would help. It is confusing that several different tablets are lumped into the MeMO Pad section here. I think we need a ME572 and a ME176 sub forum. Is it possible that all of the ME17X's could be grouped together? At the very least I would add to the forums rules that posts must identify the Model Number in the title...
Click to expand...
Click to collapse
mikemikemikexxx said:
Agreed.
Click to expand...
Click to collapse
Usually we'll do a split when there is an active development section to avoid people flashing the wrong software to the wrong device. We don't have that problem here since the development sections are pretty quiet. However, if you guys think it prudent, we could add two more General sections for ME572 and ME176. I just worry that doing so will add unnecessary clutter (currently people are doing a good job tagging their threads with the tablet model within the title). Thoughts?
My concern is with Asus's asinine naming convention that people will get them mixed up (which they do thinking about it buying accessories). While there isn't much custom ROM flashing going on (yet), there is a lot of stock ROM flashing that happens so that Root can be (re)obtained. I will defer to what you think is best. I was thinking until Asus gets smart and starts numbering them, list them by year?
I think there are more than three 7" Memopad models but at least it could be cleaned up via year.
As far as I can remember there is :
Asus MeMO Pad HD 7 - 2013
Asus MeMO Pad 7 (176C)+(CX) - 2014
Asus MeMO Pad 7 (ME572C) + (CL) -2015
Okay, I understand the reasoning you are putting forth here. It does amaze me however that this device (ME572) is flying so far under the radar. It has a great price/performance ratio that I think is basically unmatched at this point.
Preventing the flashing of the wrong files onto one of these devices would be a good thing. I do wish that Asus would revisit the locked/unlocked decision however the accounting department must believe that returns would go up if they opened up the device...
I can live without a split as long as we all try to clearly tag the model in our thread titles...
svetius said:
Usually we'll do a split when there is an active development section to avoid people flashing the wrong software to the wrong device. We don't have that problem here since the development sections are pretty quiet. However, if you guys think it prudent, we could add two more General sections for ME572 and ME176. I just worry that doing so will add unnecessary clutter (currently people are doing a good job tagging their threads with the tablet model within the title). Thoughts?
Click to expand...
Click to collapse
Trying to get some info because the lolipop update is bugged.
For me it was very confusing till I discovered there was an earlier version with the same name.