Related
So, new to this game, but a reasonably good tech head by trade. I didn't see any information outlining the differences between the available GTab ROMs in an apples to apples sort of way. Does anything like that exist currently? If not, is this something the community would be interested in brainstorming in a Google Doc or something? I'm happy to get things rolling if so.
Okay, so, this might be stupid, or a total waste of time, but what the heck:
https(colon,slash,slash)spreadsheets.google.com/ccc?key=0Au8YYie-Ky7kdDNQRG8zN09xYnQ2NTVvOXY1ZTFtMXc&hl=en&authkey=CJC3j5oC
I went ahead and started working up a spreadsheet. Feel free to go in and start editing, adding important features, correcting, or whatever else. If someone else has beaten me to this, just say so.
I actually think it is an awesome idea and should help a lot of people decide what ROM they want to use. I have had my GTab since Christmas and have flashed mine over 20 times. I have tried all of the ROMs available on these forums multiple times and I don't think I would have needed to if a spreadsheet like this was in place earlier.
Okay, I think I seeded the spreadsheet with as much information as I can based on the various ROM threads. It'll be up to the community to help fill in some of the remaining gaps and such. And feel free to add in new feature checkpoints as well that users would find relevant. I'll keep curating the document to keep it consistent, and will fill in more once I actually have my G-Tablet in hand.
Features, add features that we could us, so those of us who want a rom that performs the tasks we want can see which one best suits us.
just some egs
bluetooth gps support
usb gps support (dont think this will be possible till hc is availabe)
usb g3 support
proxy support
external or bt keyboard and mouse support
.....
TheQuicksilver said:
Okay, so, this might be stupid, or a total waste of time, but what the heck:
https(colon,slash,slash)spreadsheets.google.com/ccc?key=0Au8YYie-Ky7kdDNQRG8zN09xYnQ2NTVvOXY1ZTFtMXc&hl=en&authkey=CJC3j5oC
I went ahead and started working up a spreadsheet. Feel free to go in and start editing, adding important features, correcting, or whatever else. If someone else has beaten me to this, just say so.
Click to expand...
Click to collapse
Neither stupid nor a waste of time: I have been wanting to do something similar for a while - decide what/whether to upgrade my TNTLite 2.2 install to, I just haven't found the time or energy.
Your spreadsheet is very helpful. You should start a thread for it in the 'G Tablet Android Development' forum and see if you can get it stickied: I'll bet a LOT of other people will find it useful too. Maybe the various developers will chime in and help you fill in the blanks.
*thumbs up!*
I for one thank you for your time and effort. I am waiting on my Gtab to be delivered and am trying to decide which ROM to use. With this spreadsheet I can see the pros/cons of the major players at a glance. I think I will go with Vega.
Tt
Icedvoco said:
Features, add features that we could us, so those of us who want a rom that performs the tasks we want can see which one best suits us.
just some egs
bluetooth gps support
usb gps support (dont think this will be possible till hc is availabe)
usb g3 support
proxy support
external or bt keyboard and mouse support
.....
Click to expand...
Click to collapse
Tossed some extra fields in for those requests.
999pings, thanks, I'll start a second thread once I have the requisite posts to do so in the Developer forum. I was sort of torn what the right place was to post this to begin with. Mods, feel free to merge the threads if necessary once I get the second one going.
Yeah thanks this would be helpful. It's always easier to have a side-by-side comparison than having to read through a long list of change logs and hundreds of pages of comments on what works and what doesn't. I too am waiting for my tablet to come in the mail and deciding which ROM to go with. I was basing my decision on popularity and that award going to TnT based on thread activity. Of course that doesn't always mean it's the best choice. I'd like to see this spreadsheet take shape in the next few days or so
Perhaps you can model yours after one that SimonNWalker here at XDA did:
http://db.androidspin.com/androidspin_release_matrix.asp
Something along those lines would be nice once I have the data put together from everyone. Likewise, it'd be nice to find a wiki for it to live on, some place that it could continue to be maintained over time. Ideally something like this can take off in a way that it wouldn't need me (or any single person) to constantly curate it.
TheQuicksilver said:
Likewise, it'd be nice to find a wiki for it to live on, some place that it could continue to be maintained over time. Ideally something like this can take off in a way that it wouldn't need me (or any single person) to constantly curate it.
Click to expand...
Click to collapse
I don't know much about it, but there is Wiki functionality within XDA if this gains popularity. The spreadsheet/chart can definitely grow over time especially when Honeycomb comes out. There will be many more flavors of ROMs being released.
http://forum.xda-developers.com/wiki/index.php?title=Main_Page
Dave615 said:
I don't know much about it, but there is Wiki functionality within XDA if this gains popularity. The spreadsheet/chart can definitely grow over time especially when Honeycomb comes out. There will be many more flavors of ROMs being released.
http://forum.xda-developers.com/wiki/index.php?title=Main_Page
Click to expand...
Click to collapse
Oh, fantastic. That'll do great. I'll check into porting the stuff over to that once things fill in. Loves me some wiki action.
g1no23 said:
I actually think it is an awesome idea and should help a lot of people decide what ROM they want to use. I have had my GTab since Christmas and have flashed mine over 20 times. I have tried all of the ROMs available on these forums multiple times and I don't think I would have needed to if a spreadsheet like this was in place earlier.
Click to expand...
Click to collapse
I agree, excellent idea. Thanks for taking the time to do this!
I was about to embark upon getting VPN access working using TNTLite, now I know that I can switch to Vegan if it gets too complicated.
Here is the link since I thing the OP could not post it up
https://spreadsheets.google.com/ccc...NTVvOXY1ZTFtMXc&hl=en&authkey= CJC3j5oC#gid=0
copc said:
Here is the link since I thing the OP could not post it up
https://spreadsheets.google.com/ccc...NTVvOXY1ZTFtMXc&hl=en&authkey= CJC3j5oC#gid=0
Click to expand...
Click to collapse
Yeah, thanks. Forums require a minimum of 8 posts to include links. I just joined, so had to fake it a little, heh.
Thankyou TheQuicksilver!!
Sticky??
I suggest adding a column for stock TNT, and maybe even 1 for stock+enhancement?
That would be helpful for those trying to decide to stay stock or not.
Jim
TheQuicksilver said:
Okay, so, this might be stupid, or a total waste of time, but what the heck:
https(colon,slash,slash)spreadsheets.google.com/ccc?key=0Au8YYie-Ky7kdDNQRG8zN09xYnQ2NTVvOXY1ZTFtMXc&hl=en&authkey=CJC3j5oC
I went ahead and started working up a spreadsheet. Feel free to go in and start editing, adding important features, correcting, or whatever else. If someone else has beaten me to this, just say so.
Click to expand...
Click to collapse
Brand new to the GTab.. Picking a ROM and rooting tonight. This resource helps immensely! Thanks!
Just wanted to say thanks for this. This would be great to have as a "sticky" so we don't have to search for it, and for new owners to see at the top of the page.
Why was I getting that error? It's gone now I just want to make sure it's answered for everyone else. I was flashing a rom and it was doing that. Do a reboot. Your system wont be there so reboot into botoloader and go back into recovery.
I'm getting the same error when trying to flash and when I reboot I can't get past the htc screen. I'm using the twrp recovery and I have tried resetting a few times.
EDIT**
I tried resetting my phone a couple more times and it finally just worked. I have no clue what causes this.
Original poster is correct, this method works for whatever reason. I tried it twice now.........
Same thing
Trying to flash a kernal. I tried several reboots of bootloader and recovery and no luck. I am going to flash clockwork since I am using team wins recovery and see if that works.
Same exact thing......OP's solution worked......Thank you
Yeah had this error too. I think it happens when you try to flash a different kernel on the stock ROM. After I switched to a different ROM the error went away.
Sent from my PG86100 using Tapatalk
I'm having the same issues, but rebooting isn't helping. TWRP needs to be updated to address this issue. Until then, no ROMs for me.
That error will usually occur with signature verification failures, you need to make sure that signature verification isn't turned on when installing an unsigned rom.
It would make sense if this has to do with permissions, but I have signature verification turned off in the bootloader. Is there somewhere else that signature verification needs to be turned off?
I'm getting this error trying to root the phone using the sticky guide. It happens when I try to flash the superuser file.
what the op said worked for me as well...restarted and everything worked fine
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
myn said:
Don't waste your breath guys.
I've tried diligently to work with the devs of TWRP trying to resolve a number of outstanding issues and polish it up and they don't seem to be receptive.
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/12
Click to expand...
Click to collapse
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
I was receiving this error for two days after s-off and updated recovery. I was breaking my head trying to figure out a solution. I tried everything from switching recoveries to even pushing SU again. I also downloaded ROMe using my pc and my phone bc many ppl were calling the ROMs "corrupted." Nothing worked. I even received hate mail from multiple XDA members bc I was posting "too" many questions "without" searching the forum.
Solution, changing out my SDcard. LMAO, yes I know, wanted to run through a wall bc i had thought of it right off the back but did not want to believe my 32 gig card was causing the problem. I replaced with the card that came with the phone and BAM have been switching ROMs ever since.
Food for thought.
AssassinsLament said:
Diligently work with the devs? Like this "issue" ?
http://github.com/TeamWin/Team-Win-Recovery-Project/issues/6
and this:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/7
?
And for everyone in this thread, this issue has been covered many times in our thread. It's due to compatibilities with the updater-binary and accompanying script. As we have adopted update-binary api 3, and sideload errors are because the rom/zip is trying to issue an api command no longer supported in api3. Get your nice "devs" to update their scripts.
Click to expand...
Click to collapse
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
First off, who really cares about "Backup Naowz!" being an issue but you? I mean seriously, you're just trolling. So do you go tell people they can't speak improper english because you don't like it? Come on. We do this for free, for fun. If you paid us to make this recovery for you, then sure, if what you want is Backup Now!, we can do that for you. But you are using it for free. At least feel grateful of what we've done as a hobby for everyone instead of nitpicking 10+ issues on the smallest inaccuracies that go against your perfect world. Seriously, I'm sure others might like the "Backup Naowz!". Anyways, if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Here's the zip that was giving me the sideload errors.
I don't see any issues with the updater-script and the updater-binary is ver 3.
myn said:
Recovery can be a pretty scary place for many folks, For you and I this is our bread and butter, for most it's a rare visit. My goal in everything I've ever developed is to make things easier, friendly and inviting.
One of the many patterns you can use to accomplish this is to use professional and consistent verbiage and provide verbosity where it is appropriate. Usability 101.
I am sorry but "Backup Naowz!" is not clear and certainly not professional. This pro-treys no confidence that the following action is actually going to work.
Regarding the Original Posters message about this error which I also experienced. If this is common and you can trap it through exception handling, why not present a user friendly message to the user?
As I mentioned on IRC, I want this to be a polished product. I really think this can develop into one great recovery but right now it needs a little help. When you're ready to listen, I'm willing to help.
Click to expand...
Click to collapse
i completely agree with polish and consistency portraying professionalism, and we're glad for and always open to suggestions. however, in this case, we purposely used that terminology. we, as teamwin, like to have fun with our projects. some of them are very serious (wimax, hdmwin, kernel manager). others are a bit more on the entertaining side (theninjatweeter, twinpic 3d). with the recovery, we wanted to do something that stood apart from the rest. we do things that reflect our personality as a team.
as for the sideload issues that many are experiencing, we've discussed many times in our threads as well as on twitter and even google+; it is an issue with an outdated updater-binary script. update the scripts, no more sideload errors.
to come out and say we're not willing to listen to suggestions seems a bit presumptuous, even dangerous, when the issues you put on our github were more along the lines of requests.
AssassinsLament said:
...
if you have any suggestion or comments, feel free to do it in our thread, instead of drawing up 10+ issues that are more like "hey can you add this for me? do this for me? change this for me?" issues.
And now you go and try to make it seem like we don't care about helping our users? Nice try.
Click to expand...
Click to collapse
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
myn said:
I apparently didn't realize that your thread was the official authoritative record for bug tracking. As your code is on github I thought the issue/request tracking would be a far better medium to track these. Hence why github has this feature Interestingly enough 4 of the 10 features/bugs you implemented in your 1.3 TWRP release were reported by me at your github issue repo so apparently this is quite effective
Don't worry about the number of issues/requests out there or who put them in. I've got over 250+ issues/requests reported on Synergy and the thing went gold yesterday. Filter your issues/requests by priority and address them top down from highest first. Some you'll never get to and that's fine .
Again, all I want to provide is a better experience for my users who I can hopefully promote to use TWRP. Please don't shoot the messenger.
Click to expand...
Click to collapse
Again, I don't mind real issues... That's not my point. My point is a lot of your so called bugs or issues are the way we cosmetically chose to do it. Your issues are more so opinions, and wish lists. There is a place for opinions, and a place for real bugs. That's all I am saying.
It would be on the same level as me using your bug/issue space to say "hey i don't like that color.", "hey, can you take off myn from everywhere in your rom, I like it without?" <--- these are NOT issues. These are just what I would like/want. Do you understand?
Anyhow, I am looking into your script. Sadly we do not have any documentation of the differences between api's but, I will try to figure it out. It looks simple enough, so it should work. I'll let you know.
I have a Nook Tablet 8gig that I rooted about 10 months ago with no problems. I have had no complaints so I have not mucked around with it, but now I am wondering about updating a bit. The issue is that I want to be able to use an external keryboard dock with my NT, and I read that it was only possible with CM7 (not sure if that means CM7 and above). I rooted the NT using the great instructions and files recommended in the developers thread, but to be honest I have no idea what my nook is rooted with- it works well so I have not messed with it.
I am essentially looking for instructions on how to re-root my NT after I re-set it to factory, or how to alter my current root to run CM7. My screen is half wonked, and I may take it back since I got the extended warrenty, especially if I have to re-root it for this anyway.
Also...what is CM7? Is that an Android version?
As a side note: Can anyone confirm that you can use an external keyboard with CM7 or above?
What do you want to do first?...do you want to return to stock so that you can return your nt...or do you want to flash cm7? (cm7 is a ROM by the way a version of Android os)
Sent from my Dark Unicorn Resurrected v.2.5 using xda premium
systems6 said:
What do you want to do first?...do you want to return to stock so that you can return your nt...or do you want to flash cm7? (cm7 is a ROM by the way a version of Android os)
Click to expand...
Click to collapse
Ultimately what I want to do is run an external keyboard, and the information I have is that they will run on CM7. I will probably (assuming my warranty will cover this) be getting this one fixed to replaced soon, so I will need to re-root when I get it back, but for now I don't see the need to re-root if I don't have to.
What does it mean to "flash" cm7?
drworm73 said:
What does it mean to "flash" cm7?
Click to expand...
Click to collapse
If your nook is broken already, why bother doing anything to it? Just get it fixed then address the things you want to address. And while you are waiting for the replacement see the next line.
After reading above quote along with your original post you honestly need to read...A LOT. You need to learn at least the basic lingo before you even make an attempt to do anything. Failure to have even an iota of understanding will only lead to failure, complaints, and frustration. Spend a few hours going through the posts on here. There are several new user guides. Read them. Re-Read them. Read them again. Learn to understand what people are talking about when someone says something like "Flash x, y, or z".
As for the keyboard question, I am fairly certain that it doesn't work on ANY rom. They are working on getting the OTG portion of the kernel ironed out. While it is called a tablet it is a glorified E-Reader. The devs have done an awesome job making the Nooks into what they are today (for those of us that have modified them),
SlowCobra96 said:
After reading above quote along with your original post you honestly need to read...A LOT. You need to learn at least the basic lingo before you even make an attempt to do anything. Failure to have even an iota of understanding will only lead to failure, complaints, and frustration. Spend a few hours going through the posts on here. There are several new user guides. Read them. Re-Read them. Read them again. Learn to understand what people are talking about when someone says something like "Flash x, y, or z"
Click to expand...
Click to collapse
Any good links to layman information sites or tutorials? I was able to Root it easily (it is pretty simple), but I will admit that some of the android specific terminology does go over my head.
As for the keyboard question, I am fairly certain that it doesn't work on ANY rom. They are working on getting the OTG portion of the kernel ironed out. While it is called a tablet it is a glorified E-Reader. The devs have done an awesome job making the Nooks into what they are today (for those of us that have modified them),
Click to expand...
Click to collapse
I have read several places where cm7 has allowed keyboard use for users. They are not expensive, and I would really like to try.
As for getting it fixed...well I love my nook and use it every day, so I have been loathe to take it in. I suppose that is silly.
drworm73 said:
Any good links to layman information sites or tutorials? I was able to Root it easily (it is pretty simple), but I will admit that some of the android specific terminology does go over my head.
I have read several places where cm7 has allowed keyboard use for users. They are not expensive, and I would really like to try.
As for getting it fixed...well I love my nook and use it every day, so I have been loathe to take it in. I suppose that is silly.
Click to expand...
Click to collapse
You will love it more when it works completely and isn't "wonky". You will survive without it for a little bit. Trust me you won't die. Also because CM7 allows for a keyboard doesn't mean every device running CM7 will. Search the forums for more information. I know that some of the developers have been working on it for CM10 but I don't recall seeing any posts saying that they have it working definitively.
As for specific sites or tutorials. Just visit the various android boards and look for the Noob guides. Search google for more details on subjects you want to know about.
SlowCobra96 said:
You will love it more when it works completely and isn't "wonky". You will survive without it for a little bit. Trust me you won't die. Also because CM7 allows for a keyboard doesn't mean every device running CM7 will. Search the forums for more information. I know that some of the developers have been working on it for CM10 but I don't recall seeing any posts saying that they have it working definitively.
As for specific sites or tutorials. Just visit the various android boards and look for the Noob guides. Search google for more details on subjects you want to know about.
Click to expand...
Click to collapse
Thank, I just took it back to Best Buy and they replaced it with an HD. I thought about an HD+, but I use my nook for reading more than anything (lots of comics, some novels), and the 9" is much less comfortable for that. Now I need to root this bad boy, and I don't have to monkey around with roms other than rooting because the HD already has support for an external keyboard.
This can be closed, as far as I am concerned. Thanks.
First, and foremost, hello. I am new here, and I'm glad to be a part of the forum. Secondly, I'd like to apologize if I am posting this in the wrong section.
The topic I'd like to ask you a few questions about today is ROM Flashing, and the steps I should be taking to stay safe. I originally started playing around with Android devices around a year ago, but I recently started to delve deeper. I am the proud owner of an AT&T ZTE Z998 Mustang, and I have rooted it successfully. While in the process of rooting, I saw all of the warnings of how I should do a NANDROID backup, so that was my first instinct. I tried installing Clockworkmod, but to my dismay, they did not have an official version for my phone. I did happen to get lucky and find a version someone ported on their own. I attempted for a whole night before falling prey to error after error, and decided to give up. I went on without any backups, fiddling with my device. Luckily, I did not mess anything up, except for "accidentally" deleting the AT&T startup animation. (Haha.) Tonight, though, I happened to get the urge again, so I made some more attempts. After receiving the same error, I decided to look that error up word for word, and found that I did not have enough room on my Micro SD. I managed to clear enough room, and jumped in joy when I saw that I could delete an app, then restore and have it be back again. It was quite a big accomplishment for me. I've decided that I want to try flashing a custom ROM. The ROM I have chosen is the MIUI ROM. It seems quite popular, and I enjoy the iOS-esq feel of it, as well as its seamless theme changing. The only problem is, there is not an official release for my device. In fact, I have yet to find any ROM with an official release for my device. That is why I am coming to you guys.
My Questions:
Can I use a ROM that has not been specifically made for my device?
Will I still be connected to the AT&T Network?
If so, can I expect errors?
Am I truly safe with this newly acquired backup?
Anything you think I should know?
I'd like to thank you for any help in advance.
BrendonButton said:
First, and foremost, hello. I am new here, and I'm glad to be a part of the forum. Secondly, I'd like to apologize if I am posting this in the wrong section.
The topic I'd like to ask you a few questions about today is ROM Flashing, and the steps I should be taking to stay safe. I originally started playing around with Android devices around a year ago, but I recently started to delve deeper. I am the proud owner of an AT&T ZTE Z998 Mustang, and I have rooted it successfully. While in the process of rooting, I saw all of the warnings of how I should do a NANDROID backup, so that was my first instinct. I tried installing Clockworkmod, but to my dismay, they did not have an official version for my phone. I did happen to get lucky and find a version someone ported on their own. I attempted for a whole night before falling prey to error after error, and decided to give up. I went on without any backups, fiddling with my device. Luckily, I did not mess anything up, except for "accidentally" deleting the AT&T startup animation. (Haha.) Tonight, though, I happened to get the urge again, so I made some more attempts. After receiving the same error, I decided to look that error up word for word, and found that I did not have enough room on my Micro SD. I managed to clear enough room, and jumped in joy when I saw that I could delete an app, then restore and have it be back again. It was quite a big accomplishment for me. I've decided that I want to try flashing a custom ROM. The ROM I have chosen is the MIUI ROM. It seems quite popular, and I enjoy the iOS-esq feel of it, as well as its seamless theme changing. The only problem is, there is not an official release for my device. In fact, I have yet to find any ROM with an official release for my device. That is why I am coming to you guys.
My Questions:
Can I use a ROM that has not been specifically made for my device?
Will I still be connected to the AT&T Network?
If so, can I expect errors?
Am I truly safe with this newly acquired backup?
Anything you think I should know?
I'd like to thank you for any help in advance.
Click to expand...
Click to collapse
Bump.
Hi there. Welcome to the forums!
Unfortunately, the bad thing about phones that aren't very popular in the grand scheme of things means less people have them = less people making stuff for it. Developers often end up picking phones that are going to have more support from the manufacturer and more people will be able to enjoy the fruits of their labors. This of course, is a general rule, and of course there are exceptions, but your phone doesn't seem to be one of them. Companies like ZTE aren't concerned about putting out the source code for phones like this means that it is hard, to almost impossible, to make a really custom rom work correctly due to driver issues among other things.
So to answer the questions:
1) Sometimes, but very dependent on the models, carriers, and which software updates. General rule of thumb is that if it isn't based off the same chipset, it won't have a chance of working. But there are lots of other things to consider to, like radio versions, bootloader status, partition layout, etc. Long story short, there's no easy answer and there are lots of caveats.
2) + 3) See above.
4) You SHOULD be safe if CWM told you that the nandroid was completed successfully, but just like any other software based things, things happen.
Best way to be safe is to be able to reflash the original firmware for the phone back to it, but not even sure if that's an option for you - which goes back to ZTE not giving a $^!* about these cheap little phones for small prepaid companies. They save money by not doing any extra work like providing firmware, updates, source code, etc.
The only forums I know that mess with these kinds of things are:
http://unleashedprepaids.com/forum-1491.html
Not for your phone specifically, but similar ones:
http://androidarea51.com/zte-phones/
So yea, slim pickings.
es0tericcha0s said:
Helpful Info.
Click to expand...
Click to collapse
First, thank you! I was waiting all day. I was a little disappointed with the answer, though. v.v Do you know if there are any ROMS that will work with ANY device? Like even bare minerals versions of AOSP ROMS that have yet to be touched?
Also, I am slowly saving for a 64GB Black Nexus 5, so I shouldn't be stuck but more than a month or more so.
BrendonButton said:
First, thank you! I was waiting all day. I was a little disappointed with the answer, though. v.v Do you know if there are any ROMS that will work with ANY device? Like even bare minerals versions of AOSP ROMS that have yet to be touched?
Also, I am slowly saving for a 64GB Black Nexus 5, so I shouldn't be stuck but more than a month or more so.
Click to expand...
Click to collapse
No, sorry. It's just not possible. Your best hope would be to use the debloated rom in the unleashed prepaids forum and use the Xposed Framework.
http://unleashedprepaids.com/thread-8769.html
http://unleashedprepaids.com/thread-8771.html
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://repo.xposed.info/module-overview
I have the Nexus 5 (don't think they come in 64 - only 16/32) but it's awesome and there are so many roms that it'll make your head spin. lol
es0tericcha0s said:
No, sorry. It's just not possible. Your best hope would be to use the debloated rom in the unleashed prepaids forum and use the Xposed Framework.
http://unleashedprepaids.com/thread-8769.html
http://unleashedprepaids.com/thread-8771.html
http://forum.xda-developers.com/xposed/framework-xposed-rom-modding-modifying-t1574401
http://repo.xposed.info/module-overview
I have the Nexus 5 (don't think they come in 64 - only 16/32) but it's awesome and there are so many roms that it'll make your head spin. lol
Click to expand...
Click to collapse
Oops, sorry, yeah, that's what I meant. xD
But, I can not wait for it!
Just some final thoughts and questions:
I do have Xposed installed already, but have yet to look around in it due to the hundreds of modules. Do you have any suggestions about which I should look at for cosmetic needs? I have tried to use Gravitybox, but it force closed upon entry every time I used it, so I deleted it.
I understand that the limitation is very high because of the fact that it is a closed sourced company, but many ZTE Devices are listed to have compatible ROMS, such as MIUI ROM. If I try to use a ROM specified for a different phone, do you know what could happen? I feel that it may not even open, or if it does, it'll have tons of errors and not work upon entry, or even work but have certain things like the camera that will not connect. I'm only worried about high margins of fatal breakage. If it is some silly error that I won't have to "worry" about, I'm okay with fooling around.
If I do try to install a new ROM, but want to go back, will it affect anything on my previous backup? I know backups copy EVERYTHING, but I'd just like to make sure I won't do serious damage.
Lastly, thank you for all the help. It means a ton.
BrendonButton said:
Oops, sorry, yeah, that's what I meant. xD
But, I can not wait for it!
Just some final thoughts and questions:
I do have Xposed installed already, but have yet to look around in it due to the hundreds of modules. Do you have any suggestions about which I should look at for cosmetic needs? I have tried to use Gravitybox, but it force closed upon entry every time I used it, so I deleted it.
I understand that the limitation is very high because of the fact that it is a closed sourced company, but many ZTE Devices are listed to have compatible ROMS, such as MIUI ROM. If I try to use a ROM specified for a different phone, do you know what could happen? I feel that it may not even open, or if it does, it'll have tons of errors and not work upon entry, or even work but have certain things like the camera that will not connect. I'm only worried about high margins of fatal breakage. If it is some silly error that I won't have to "worry" about, I'm okay with fooling around.
If I do try to install a new ROM, but want to go back, will it affect anything on my previous backup? I know backups copy EVERYTHING, but I'd just like to make sure I won't do serious damage.
Lastly, thank you for all the help. It means a ton.
Click to expand...
Click to collapse
Gravity Box wouldn't work because it is for more AOSP based things. As far as theming goes, you can try HK Theme Manager or Ex Themer. For the idea of trying to install a rom for another ZTE phone, well, best case scenario is that it doesn't flash at all. Worst case is that it does flash, and you lose something like your IMEI, baseband, or one or more of your other partitions and all of those are potentially unrecoverable, no matter what kind of backups you have. This wouldn't be one of those, "Oh, shoot, that didn't work, I'll just factory reset or restore my backup and be good to go..." kind of situations.
es0tericcha0s said:
Gravity Box wouldn't work because it is for more AOSP based things. As far as theming goes, you can try HK Theme Manager or Ex Themer. For the idea of trying to install a rom for another ZTE phone, well, best case scenario is that it doesn't flash at all. Worst case is that it does flash, and you lose something like your IMEI, baseband, or one or more of your other partitions and all of those are potentially unrecoverable, no matter what kind of backups you have. This wouldn't be one of those, "Oh, shoot, that didn't work, I'll just factory reset or restore my backup and be good to go..." kind of situations.
Click to expand...
Click to collapse
Oh, wow! Thanks! I'm glad you pointed that out before I tried. So, I should be okay as long as I flash that ROM from the Unleashed Prepaid page? Now I am afraid, but curious.
Also, thank you for the theme modules names, I will kindly note them.
Should be fine. It's 95% stock and I'm sure they only had one version of android for the phone so should be pretty close to what you have now. Benefits would be the unsecured boot.img which is easier for root and other things to stick, init.d which allows you to run scripts (everything from being able to mount a partition of an SD card to use for extra space for apps to memory management stuff like V6 Supercharger), and a bit easier to theme and debloat.
es0tericcha0s said:
Should be fine. It's 95% stock and I'm sure they only had one version of android for the phone so should be pretty close to what you have now. Benefits would be the unsecured boot.img which is easier for root and other things to stick, init.d which allows you to run scripts (everything from being able to mount a partition of an SD card to use for extra space for apps to memory management stuff like V6 Supercharger), and a bit easier to theme and debloat.
Click to expand...
Click to collapse
Thank you.
I'll look into it tonight. I will try and tell about what happens tomorrow-ish.
Cool. Good luck.
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
ljwobker said:
I'm currently running an 8.9" HDX with a working AOSP - thanks to all the help I got on this forum and specifically followed this thread:
http://forum.xda-developers.com/showthread.php?t=2582773
but the main applications that I now need to use for work are iOS only (don't ask... NOT happy) so I'm back to carrying an iPad around everywhere and as such I'm going to sell my HDX. Before I do that I need to return it back to stock... I found a number of threads referencing how to do this but wanted to be extra careful. At present I'm just running Safestrap with a second ROM slot that I boot with all the non-standard stuff, I got there via SuperSU.
What's the right sequence of de-activates / un-installs / magic incantations to get this thing back to "boring, stock" just like it would come from Amazon? Is it as simple as re-enabling over-the-air updates and letting it "fix" itself? Or do I need to specifically back out some of the safestrap/superSU stuff first?
Help? (and THANKS)
Click to expand...
Click to collapse
Depends on how you used SafeStrap. If you ONLY installed in the stock rom, then an update likely would do it. If you installed safestrap a second time from the working rom-slot as well, then updates won't work, because the BL & Kernel CANNOT be flashed.
The best thing is to remove all wifi connections with "forget network", then go into safe strap & activate stock rom. Then go back to the boot options & delete the rom-slot you created. Boot back into stock partition, uninstall Safestrap & then reconnect to wifi & check for updates.
I would HIGHLY recommend you follow my directions about forgetting nearby, if not all, wifi networks. If you turn wifi off in a slot, but not in stock, or vice versa, it can cause boot issues , as well as wifi issues.
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
EniGmA1987 said:
I would not return it to stock. That device could go for a premium right now to other users simply because you can get AOSP and so many cannot yet.
Click to expand...
Click to collapse
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
GSLEON3 said:
Why would it go for a premium? It is absolutely 100% rootable. It has not been patched against the VolumeManager/vold ASEC exploit. In fact, I am nearly certain the bootloader can bed unlocked from my investigation. Unfortunately that part is beyond my abilities & exceeds the time I would need to get caught up on the msm89xx+ SoC, but I would just about bet the farm that it can be done.
Click to expand...
Click to collapse
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
EniGmA1987 said:
Because when I posted that we had no root, and it was still a "hopefully sometime soon" with 9/10 of the HDX's on a version that couldnt be rooted.
It is nice that we have one Chinese method now and that you might get something soon, though I think you are suddenly pretty full of yourself on these forums with the little bit of knowledge you gained recently. Much better people at this have not been able to get the bootloader cracked. But best of luck to you.
Click to expand...
Click to collapse
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
GSLEON3 said:
Actually, the little time I've been around is well over a decade. This ain't my first username. Secondly, there is already an ASEC based root that WAS created by someone better with this stuff than me, so it's not full of myself, it is FACT. I am rooted, have been each & every time, without blocking anything & without having to sacrifice connectivity, another FACT. Coincidentally, the reason it was never published, well I'd venture a guess that it's because of stupid posts & self-entitled people ignorantly writing or PM'ing to insist that things be done for them on their terms. Another fact, it was that kind of crap that made me leave this forum a few months ago. So, I don't know what "better people" you are talking about that have failed at it, but I do know the better people that have done it.
Another fact, anyone at all can read & discover just how small the patch for the ASEC vulnerability was. It doesn't take a genius to then decompile the vold & search for the that one event which was used to patch it, which subsequently tells all you need to know.
Click to expand...
Click to collapse
lol. I am glad you know your FACTS. No need to act so butthurt.