Guineapig for devs - Acer Iconia Tab A100

I know and understand that full root, and to even have the tweeks to do anything with will still take some time, but I would like to use my tab as a tester for any new root methods (one click or any of the sorts), recoveries, Roms, and even kernels. Please keep me in mind when you need someone daring!
Mod, if I posted this in the wrong place, please move me to the right category, as I still don't get when and where would be the right place for a matter like this.
Thanks for all the hard work you guys put in for us!
Sent from my A100 using xda premium

Related

Little nevous so I have to ask.

I am thinking about rooting using unrevoked 3. I am pretty sure that is strait forward. After that I should install titanium back up and do a nand back up? Then after that I should be able to delete the sense apk and htc lock apk screen and it should be stock vanilla 2.2 right. If I want to restore for a OTA can I just use the nand backup?
Then if I want to try flashing Roms what should I do? Is the Rom manager app all I need?
I usually try to ignore these threads but jesus man read a lill first
Sent from space
venom_762 said:
I am thinking about rooting using unrevoked 3. I am pretty sure that is strait forward. After that I should install titanium back up and do a nand back up? Then after that I should be able to delete the sense apk and htc lock apk screen and it should be stock vanilla 2.2 right. If I want to restore for a OTA can I just use the nand backup?
Then if I want to try flashing Roms what should I do? Is the Rom manager app all I need?
Click to expand...
Click to collapse
OK.
First, wrong section. This should be in Q&A whether anyone responds to it there or not.
Second, Titanium doesn't do NAND backups. That's a job for the recovery.
Third, deleting two apks will not make the ROM "vanilla". It will only mess things up and ruin your experience. If you want "vanilla", there are plenty of AOSP ROMs you can flash after you root.
Fourth, you don't do OTAs after you're rooted. It would unroot you, and you'd have to start all over, and there's no guarantee there would be root available for the new OTA. You should just stick to flashing rooted stock ROMs.
Fifth, I would personally advise against ROM Manager and tell you to learn to do it manually. It's not difficult at all, just a matter of learning a specific sequence of simple steps.
I think that about covers everything. I'm sure someone else will fill in the pieces I've missed.
venom_762 said:
I am thinking about rooting using unrevoked 3. I am pretty sure that is strait forward. After that I should install titanium back up and do a nand back up? Then after that I should be able to delete the sense apk and htc lock apk screen and it should be stock vanilla 2.2 right. If I want to restore for a OTA can I just use the nand backup?
Then if I want to try flashing Roms what should I do? Is the Rom manager app all I need?
Click to expand...
Click to collapse
You should probably do some more reading. Titanium back up only backs up apps. If you want a nand back up you do it through recovery. Deleting that stuff does not make it vanilla lol. If you want a vanilla build run a AOSP rom. I don't use Rom manager it crap I flash manually
Sent from my PC36100 using XDA Premium App
Please post your source codes along with the ROM/APP/Development you are doing in this thread.
if not then you realize this is not in the right section. not to be rude but its pretty straight forward with the unrevoked..dont be a ***** and just do it. Otherwise just leave your phone alone.
THIS MIGHT HELP YOU
http://www.xda-developers.com/announcements/a-reminder-from-the-xda-moderator-team/
Google is your friend, learn to use it. Also not trying to scare you, but you could get stuck in bootloops so its better to read everything first then try flashing something.
Your post shows that you are completely clueless, so I really recommend that you read and research before you even attempt to do anything to your device.
Google the following:
1) how to root android
2) how to install custom roms
3) how to use Titanium backup
4) Difference between ASOP and Sense
5) Search in this forum "How to unroot your Evo in two easy steps" if you dont understand or cant follow the instructions there, you may want to reconsider rooting your device. Since if something goes wrong, you will need to unroot the device before taking it to Sprint, etc.
Also dont get offended by these comments because XDA isnt usually like this. But when its very clear that a member hasn't done any research, and expects to be spoonfed all the info, you will get flamed.
How did OP even start this thread in this section? He only has 5 posts... Did the rules change?
wow, my mistake. I'll just stick to Android central.
venom_762 said:
wow, my mistake. I'll just stick to Android central.
Click to expand...
Click to collapse
The reason you got the response you did is because you posted in the wrong section. Whike I know you are new to the forum out is always a good idea you read the stickies on any forum you visit.
Tons of new people make the same mistake.i wouldn't let it turn you of but use it as a learning experience.
Xda is an amazing forum (if you are willing to take the time to search post in correct places and do a little work yourself by researching.)
If you aren't willing to do those things then you will find it a cold unfriendly place.
Fort better or worse it is not always newbie friendly. On the plus most of the major developers are here so once you learn you have tons of resources.
Sent from my PC36100 using Tapatalk
As others have stated previous, irritation arose due to posting in the wrong section (initially) and coming to the table without having first exhausted all resources outside making a new thread (see: Google, searching XDA, other forums, YouTube, even).
There are many guides to help you out there, many on these forums specifically. As one other said previously, as well, don't let this shown irritation from other users discourage you from using these forums. XDA is, by far, the best place regarding the rooting, flashing, development, and customization of our phones. You would be wise to stick around and learn the ropes a bit.
Next time, if you have a question, try posting what you did in the body, explaining what research you have done and what did or didn't work before you decided to post a new thread. This will help others see that you have indeed looked around some and tried some things out instead of rushing to post a new thread without seeing if your question(s) was/were already answered.
Overall, your experience can be very good and you can learn a lot from these forums. I'm still pretty new myself, but I visit these forums every single day and read up on things and just take it all in.
Have fun with everything! If you have any specific questions, feel free to PM me and I'll do my best to help. But do some research before, if you do!
I would suggest reading and asking lots of questions and reading and asking lots of questions and reading and asking lots of questions before doing anything to your phone....
I think all of these responses would make me a little nervous as well...
EndlessDissent -
I have found Rom Manager to be quick and painless, why would you advise against using it?
fyi - I use it w/clockwork recovery instead of Amon-RA. And have downgraded it because of some kind of edify scripting problems. is this less than optimal?
Ok I think I have read all I can and watched all the youtube videos I can handle. It looks pretty strait forward and seems to be easier that the palm pre.
Now can anyone recommend a GB Rom? I would love a pure nexus s expirence. I plan to get it when it comes out.
I would recommend CM7, but some would say no cuz of weird instances that happened to a couple people. Evervolv, Salvage, king's ultra, and miui all have gingerbread though.
venom_762 said:
Ok I think I have read all I can and watched all the youtube videos I can handle. It looks pretty strait forward and seems to be easier that the palm pre.
Now can anyone recommend a GB Rom? I would love a pure nexus s expirence. I plan to get it when it comes out.
Click to expand...
Click to collapse
I second CM7. There are thousands of users, thus lots of potential help. It is a ROM that has been for awhile and they have really worked out quite a good percentage of the bugs that will inevitably come with any GB ROM.
Flash CM7 and get a good feel for it before you start hopping ROMs. Also do yourself a favor and make sure you use the search button liberally before you post questions/issues in the CM7 threads and provide some info on what you did to resolve your issues (you will have issues). If you do that the chances you'll get help rather than flames goes up 10,000%.
I would strongly recommend against MIUI. It is unquestionably the best ROM I have ever used, but it is really not a good ROM for an EVO rookie. The quirks in the flashing process are plentiful and the preciseness required by the nature of the ROM will suit you much better a month from now.
I'm sure there will be people who disagree with me, but I help people everyday who would not have needed help if they had learned a little more about the process on a more basic ROM with lot's of support and fewer bells and whistles. Just my two cents.
The options in teh roxxorz's post are good options as well.
teh roxxorz said:
... miui ... gingerbread...
Click to expand...
Click to collapse
Here I edited teh roxxorz's post to weed out the erroneous stuff and highlight what's important.

[KERNELS] Looking for Kernel Developers for Kernel Manager!

Hey everyone! I wanted to introduce a new project with a very simple but ambitious goal: create a place where all kernel developers can submit kernels easily and reach a much wider audience with ease.
Using Kernel Manager to flash kernels takes less than 30 seconds, generally, and it is extremely simple for end-users to find a kernel, filter by kernel features (BFS, CFS, HAVS, SBC, etc) download/install kernels, and submit ratings for their favorites.
We need from kernel developers like YOU! Submitting a kernel to Kernel Manager is totally free and we even provide hosting for you! Submitting kernels is easy, and kernel developers receive a FREE copy of Kernel Manager Pro when they submit a kernel to Kernel Manager!
If you use IRC, join us in freenode in #kernel-manager!
THIS LINK IS FOR KERNEL DEVELOPERS SPECIFICALLY! Go to http://kernels.teamw.in and register for an account! Once it's approved, you can easily enter new kernels, which immediately show up in the app. The app is currently available in the market.
Please feel free to provide me with any feedback you have, or feature requests in order to make this a great tool for all of android to utilize!
Should I submit my kernels to this? This guy is making dough off this which I have no issues with at all...
Just wanted some opinions from you guys...
If it makes easier for us to keep up with your work, then whynot?
How many other Dev's have starrted using?
It's like Rom Manager for kernels, no?
If this had other features developed into the app and happened to support kernel downloads it'd be one thing, but I will not be paying someone else so that I can have access to the kernels that originate here. I'll save my money for the kernel devs. That being said if others find value in this, or if the dev community thinks it will do some good I'm all for it.
I see a **** ton of people having problems and coming straight to you faux.
I say make em flash the old fashion way... it at least deters some of the noobs. Making it something where anyone can one click change kernels.... sounds like opening a big can of worms.
Just my 2¢.
Sent from my HTC Glacier using XDA App
I dont know, i would wait and see how it effects other kernel devs.
camalus said:
I see a **** ton of people having problems and coming straight to you faux.
I say make em flash the old fashion way... it at least deters some of the noobs. Making it something where anyone can one click change kernels.... sounds like opening a big can of worms.
Just my 2¢.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
+1 I would like to see less repitition in the forums of "help I'm bricked!" Then 3 posts from a senior member with some knowledge "oh I just had 2.5.1.2 installed or 3.0.0.5" then there's the others like (this still makes me laugh) my internets slow, must be the sim card! Lol. Sorry rant I think it'd be a good app if only available to more seasoned users to inhibit the amount of screw ups..
Sent from my HTC Glaciee using XDA Premium App
Faux you are the kernal king !!! thanks alot for all your cool kernals dude. but i would just submit one and see what happeneds !!!
Good idea, but I agree with the others posts. It would be helpful to have everything in one spot, even with older versions, but him making scratch on you, with you as basically free support?
Unless you want to get your name out there to more people, then go for it.
Thank you for everything so far and in the future.
The problem is, we have so many different roms, and some of them require different kernels.
At least in the kernel threads they can see what works with what. An app like this will see ro.product.device=glacier and pull all the kernels. making it easy for someone to screw up and flash the wrong kernel.
option94 said:
The problem is, we have so many different roms, and some of them require different kernels.
At least in the kernel threads they can see what works with what. An app like this will see ro.product.device=glacier and pull all the kernels. making it easy for someone to screw up and flash the wrong kernel.
Click to expand...
Click to collapse
Yeah good point... I will wait a bit and see how other kernel devs react to this...
Sent from my HTC Glacier using XDA App
darinmc said:
If this had other features developed into the app and happened to support kernel downloads it'd be one thing, but I will not be paying someone else so that I can have access to the kernels that originate here. I'll save my money for the kernel devs. That being said if others find value in this, or if the dev community thinks it will do some good I'm all for it.
Click to expand...
Click to collapse
Just to clarify something - it costs nothing for a dev to host a kernel, and it costs nothing for someone to download that kernel through the app.
Kernel Manager provides kernel devs a super easy way to distribute their work for free. Kernel Manager Lite can download and flash kernels for free, so I'm not sure why you feel like you need to pay for anything?
xdviper said:
If it makes easier for us to keep up with your work, then whynot?
How many other Dev's have starrted using?
It's like Rom Manager for kernels, no?
Click to expand...
Click to collapse
Currently we have 37 developers signed up and submitting kernels.
I make my kernels for ME but share them because it is the proper thing to do. Feel free to use them, host them whatever. I do not want to make any money off of them because I did NOTHING. If you want to make money off of them, or share them feel free. Depending on what you do, I will have more (or less) respect for you. But really, who cares. I respect shiznzul (so far), so have fun and good luck.
option94 said:
The problem is, we have so many different roms, and some of them require different kernels.
At least in the kernel threads they can see what works with what. An app like this will see ro.product.device=glacier and pull all the kernels. making it easy for someone to screw up and flash the wrong kernel.
Click to expand...
Click to collapse
Shinzul,
How is this handled in your app?
ziggy34 said:
Shinzul,
How is this handled in your app?
Click to expand...
Click to collapse
The app only displays kernels that are your for your particular device so there's no chance of flashing a kernel that's for the wrong phone.
If there's any question about what type of phone you have (see: samsung phones...), it pops up a message asking you to confirm which of the options your phone is.
Shinzul said:
The app only displays kernels that are your for your particular device so there's no chance of flashing a kernel that's for the wrong phone.
If there's any question about what type of phone you have (see: samsung phones...), it pops up a message asking you to confirm which of the options your phone is.
Click to expand...
Click to collapse
What about seperating for different versions. We have two different Aosp formats... and two or three sense formats that we use on the 4g.
How does your app keep other kernels seperate so it doesn't screw up peoples phones?
That is the biggest issue I think most of us on the 4g see.
Sent from my HTC Glacier using XDA App
being that it's in the market there is always a chance it will become a paid app. I just don't want devs to become dependent on it, that's all. I like reading into what I'm doing, so I guess I should ask, is there a section for a changelog, install notes, etc?
darinmc said:
being that it's in the market there is always a chance it will become a paid app. I just don't want devs to become dependent on it, that's all. I like reading into what I'm doing, so I guess I should ask, is there a section for a changelog, install notes, etc?
Click to expand...
Click to collapse
There will always be a free version that provides access to the kernels. There is a free version (Lite) and a cost version (Pro) right now.
Pro will just have more features, but everyone will still be able to download+flash kernels for free if they like.
camalus said:
What about seperating for different versions. We have two different Aosp formats... and two or three sense formats that we use on the 4g.
How does your app keep other kernels seperate so it doesn't screw up peoples phones?
That is the biggest issue I think most of us on the 4g see.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
I am going to add a confirmation on the android flavor (AOSP vs Sense). I might add a filter option for it, but it's difficult because that field is developer-input. There isn't a standard list.

Porting Roms from *** To the Evo

I assume this is the correct forum otherwise please move this.
What is the best article(s) to read if you want to start learning how to port roms from other android phones to the Evo? I've been searching on here and on google and it seems most articles are either outdated or only talk about editing existing cooked roms so I finally broke down and posted this. Yes I do use Linux and I do program in Java and .NET and do have a bachelors in software development but I have just never looked into doing this type of work until now.
Thank you, any direction I'm pointed in is appreciated.
I'll direct to you the Q&A forum.
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
sirmx said:
I'll direct to you the Q&A forum.
Click to expand...
Click to collapse
Thanks sirmx, I did do a search there but again came up short.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Sounds good, what I'll do is go ahead and start one, nothing special maybe even ones that already been done just to get the experience under my best.
ThatSmartB0y said:
Side Note:This goes in General,but im nice so ill answer you question.
There is no real BOOK to read, a java book is a good start, but you say you know java, so you can probably skip that.
Basically, this is all you have to do.
Download "Dsixda's Kitchen" to your linux distro(amazing software)
Grab a rom from another device.
Grab one of our(evo)stock roms(deodexed Stock 3.70 is good for froyo port,4.12 for gingerbread)
Open the kitchen, and find the option(#19 i think it is), and follow the steps to port it(hold on, your not done yet)
From there you will need do some manual work by tinkering with libs,tinkering with the boot.img, bascally just tinkering with everything related to booting(libs,ramdisk,hw-libs,etc.) untill you can get it to boot or bootloop.
If it boots, thats great, if it bootloops, youlle need to logcat it then debug it.
If you need help with something, pm me, other than that, thats basically(*note: i said basic, more complexed roms like sense 3.0 and non-htc device rom may require extra work)(*note2:alot of times, its going to be a no-booter, but just keep trying.)
Click to expand...
Click to collapse
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is if friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
What about something A LOT simpler like adding the CRT animations to a ROM? any pointers? Any TUT you can point me to?
ThatSmartB0y said:
ah yes, forgot about build.prop,and i think the kitchen takes care of updater script(unless the device has specific mount pointsor you want text or to clear cache and system). i was just getting the basics to boot, from ther he can debug the errors out of the log.
Click to expand...
Click to collapse
Oh I hear ya. Just throwing in my 2 cents. Found that having a clean updater-script is half the battle.
Sent from my PC36100 using Tapatalk
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
evomattnc said:
I'm actually glad this thread is still here we don't get to learn much from the devs here. I mean its mostly do it yourself but a getting started guide isn't a bad thing. Mods are quick to move and people are quick to flame but I say leave it, where else is the knowledge pool? Can you really learn this stuff in Q and A seems like it would be mostly help my phone doesn't boot...
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well said. People love to flame anyways and XDA is famous among other Android forums for being so harsh. This thread helped me out big time, and it's especially nice to see Leoisright and myn in here giving up a few pointers, because I too was curious about porting. I never worked up the confidence to ask, just too worried about it being passed over or getting flamed because I'm young and curious.
Sent from my PC36100 using XDA App
Yah, Q&A never got me anywhere, i learned off of trial and error, still learning now.
EDIT:OP:IF you want you can ombine mine and leo's tuts together, to make this thread permanent.
Subscribed!!!!!!!!
Good stuff!
Sent from my PC36100 using Tapatalk
Yeah I want to thank the devs that have stopped by so far and gave tips, already using them . Hopefully most of them drop In at least once and leave one tid bit that would make this thread awesome!
Sent from my PC36100 using XDA App
Ha, you taking applications for an apprentice myn?
myn said:
Check out the APKTool, APKManager threads. Lots of great valuable information in there.
I sometimes wish XDA focused more on the "HOW TO" and less on the delivery aspect. The more folks developing, the further we will be along
Another great way to get started is to mentor with another established developer.
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
Yes I was afraid to post this at first which isn't good, you shouldn't be afraid to ask questions but I get that sometimes the same questions have been answered 100 times prior so I understand the quick to judge portion of it. But I want to thank everyone who has contributed tips, advise and places to start. Thank you.
Leoisright said:
Don't forget some of the most important stuff is in the build.prop and update-script.
Word of advice, look at a sense 2.1 and check out the base that was used. You can also use beyond compare and basically skip Linux all together. Using kitchen to deodex the ruu is a good first step. Choose option 11 in the menu.
Personally, I would start off with a working port and changing apps and moving stuff around. Also get a good list at which libs are associated with what. But use stock bins, etc, xbin, hw libs, and ported apks, framework, and software associated libs. Stock boot.img and a good updater-script. Also know key
Things like the EVO density is 160, vold_stab is usb, amkd is rotation, gsl hw accel stuff like that.
But first things first, Google is ur friend and use the q&a section.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
So I've been looking at beyond compare, did you use this from everything and just edit all the non evo files to match existing evo ones from within windows?

[Q] Should we start a consolidated information thread?

I was wondering if maybe we could use a post to organize some of the Mods/Tweaks we as A100 users can do. Especially since it may be a while before we have a custom ROM. Seems like a more central list of mod options would be useful. I would be happy to work on this.
Things we could incdlude
=======================
Improving Poor Viewing Angle(everyone complains about this)
-Turn the device upsidedown, as someone else posted a while back if you turn the
A100 so the "home" button is on the left instead of the right.
ALLOT of things seem to work better. The viewing angle is good,
the front viewing camera is no longer under my hand, and the
antenna is in a better position too I bet. It almost seems like that was the original orientation
Rooting(a100 and now a101 too)
- temp and perm install/uninstall, script & by hand)
Status of Custom ROM Development
Status of safe mods for: Build.prop, init.d, gps.conf, etc
- what mods can be done, the result, the versions tested on, etc
Making Recovery Images
-known methods, risk/benefit of them , links to instructions and files
Using Recovery Images
-known methods, risk/benefit of them , links to instructions and files
Boot Animations
-known methods, risk/benefit of them , links to instructions and files
Hulu fix(s)(lib mod, or huluplus(working on A100?))
-known methods, risk/benefit of them , links to instructions and files
Hidebar, Honeybar, NOT-VERY-INTERESTING BAR
-risk/benefit of them , links to instructions and files
UOT Kitchen(?)
-Can we use it? what features work?
General Suggested Utility Apps List Maybe
- I know the forum has an apps section already. Im just thinking the most basic things. Stuff like which busybox, terminal, file manager, etc are known to work well on our a100.
Maybe a running list of Any known major FUBAR apps. or features within apps that would for sure brick ur device.
Sounds more like a general FAQ to me, but a good idea. All of the mods I've released so far are in my sig for this very reason.. I was receiving lots of pms (hey where's xyz mod) lol!
Only bad thing is who's going to keep it up to date? Also it'll need to be stickied so that it doesn't get lost in general.
Sent from my MB860 using XDA App
Yep. I wouldn't be able to stickie it far as I know. I just keep thinking we have allot of cool stuff that can be done. However it takes hours and hours of reading to start to find that out . So I'm thinking it might be something I can do to contribute.
It would almost certainly help new comers figure what they have available.
I am new to the A100, so this is great idea for people in simular positions.
NoSudo said:
Yep. I wouldn't be able to stickie it far as I know.
Click to expand...
Click to collapse
No worries on that one, I can help with that
Sent from my MB860 using XDA App
good idea...but honestly compared to the other devices forums i frequent this one is the cleanest..mostly because we actually dont have a whole lot of mods for our A100s. once a device has custom roms, radio releases,kernels and 18 different rooting methods thats when things get lost. the one thing that always was handy was creating a device wiki, that way its one page to keep up to date and can include everything. just the way ive seen things..when i first got my desire z the xda wiki was the best source for concrete information and guides.
just my .02 i still like your idea dont get me wrong! but maybe making a wiki would be a better idea than just a sticky?
Sent from my SGH-I897 using xda premium
I'd say that a kind of central knowledge base would be a great idea. Back in my Desire days they had just this sort of thing in the dev forum for kernels, sense and non sense roms etc. It was fantastic.
Spreading the word is one of the best things we can do to help others help themselves ;-)
Sent from my A500

[Q] Root issue

I installed eclipse 4.1.1, it has superuser in it. Tibu works, but when I try to use trickster mod, it says I don't have root access. I used root checker, and sure enough it says I don't have root access on my phone. What's going on with that? What can I do?
I'm not sure of the technicalities causing your issues.
But I can recommend flashing SuperSU in ClockworkMod after installing TricksterMod. Also make a backup beforehand.
Sent from my Galaxy Nexus using Tapatalk 2
Just tried that, didn't work. I don't understand how I don't have root access but one app that required it works and another doesn't.
tried to re-root the phone using the nexus toolkit, no go either. tibu still works but not trickster.
dont use a toolkit. srsly, since you dont know what the hell you're doing.
Sent from my i9250
Thanks, that was real helpful.
Try updating the su binaries from super su app... That's worked for me before. If that doesn't work try flashing an updated rom since they all have su built in.
Sent from my Galaxy Nexus using Tapatalk 2
Tried that too.ended up going to baked black bean ROM.thanks for the input.
bk201doesntexist said:
dont use a toolkit. srsly, since you dont know what the hell you're doing.
Sent from my i9250
Click to expand...
Click to collapse
There's no need to be rude to him. We've all been new at this at some point.
Sent from my Galaxy Nexus using Tapatalk 2
Thank warner. I don't know why some people think if you own a certain phone you should know right away how to do everything the "right" way. If you shouldn't use the toolkit, then take it off the forum. Otherwise people are going to use it like me.
t1.8matt said:
Thank warner. I don't know why some people think if you own a certain phone you should know right away how to do everything the "right" way. If you shouldn't use the toolkit, then take it off the forum. Otherwise people are going to use it like me.
Click to expand...
Click to collapse
just because you find a tool on the table doesn't mean you should take an engine apart without any knowledge before hand.
Some things to search before rooting:
1. What does "root" mean and what does it change?
2. Why do I 'need' root?
3. Differences between soft and hard bricks and how to recover from them.
4. What is and how to use ADB.
5. an extra but, if you were to make this phone unrecoverable or unusable for a degree of time, is this a possibility you can accept? (i ask this because ive worked with those that brick their phone they use for work and then they rush through trying to fix it and make it worse).
We aren't trying to be mean or chase away new users, it's always a great thing when people learn to use their phones. The only thing that can cause bitterness is when users buy a phone and come home and root it because they heard thats what you do with android phones and how to get cool stuff or free apps. Im not saying that is you, likely it isn't from what i've read.
Bottom line, read and learn as much as you can because there is no such thing as too much knowledge. There is nothing more satisfying than figuring out the problem yourself and fixing it instead of 'calling tech support for help' on xda.
I do understand what you're saying. I'm not trying to come off as cocky or I know it all but I have been doing these things with android for a while and do understand how some things work and how to do them. This whole unlocked phone is new to me, and I've never been completely comfortable or able to use fast boot methods which I know is the right way to do most things. I try to learn things about these phones on a daily basis which is why I ask questions and try new things all the time. I appreciate what you have said and am trying to learn how to do things properly, this is just new to me and I appreciate people who have patience to help people like me out.
Darunion said:
just because you find a tool on the table doesn't mean you should take an engine apart without any knowledge before hand.
Some things to search before rooting:
1. What does "root" mean and what does it change?
2. Why do I 'need' root?
3. Differences between soft and hard bricks and how to recover from them.
4. What is and how to use ADB.
5. an extra but, if you were to make this phone unrecoverable or unusable for a degree of time, is this a possibility you can accept? (i ask this because ive worked with those that brick their phone they use for work and then they rush through trying to fix it and make it worse).
We aren't trying to be mean or chase away new users, it's always a great thing when people learn to use their phones. The only thing that can cause bitterness is when users buy a phone and come home and root it because they heard thats what you do with android phones and how to get cool stuff or free apps. Im not saying that is you, likely it isn't from what i've read.
Bottom line, read and learn as much as you can because there is no such thing as too much knowledge. There is nothing more satisfying than figuring out the problem yourself and fixing it instead of 'calling tech support for help' on xda.
Click to expand...
Click to collapse
I do agree that learning as much as we can and being able to fix a problem ourselves without asking for help is extremely satisfying. At the same time though this is the q&a forum and he did try to fix the problem himself through the use of a toolkit, which I agree cuts out a lot of the learning that can be achieved through using fastboot and adb. I think in this forum especially it is better to try to help and make constructive comments than to be rude and post a reply that doesn't help and could possibly chase off a newcomer to modding their device. I appreciate your comment though trying to explain the benefits of learning yourself in a respectful way.
Sent from my Galaxy Nexus using Tapatalk 2
Exactly. I'm not asking anyone to come to my house and fix my phone. But it helps when someone explains what I'm doing wrong and how I can fix my errors in what I'm doing. Thanks for your help everyone who did but I'm going to move on and learn from this experience.
Yes it's a Q&A, but this is a question that asked a lot.
A little bit of reading tell you how to use the forum properly, and you probably find the answer already solved.
Toolkits have there place & for newbies i guess it's the fastest way to get it done, but if you read through the Q's you will find most rooting issues are related to the use of toolkits. Great if they work, but as soon as there is an issue, users are left in the situation you are in now.
efrant & jubakuba have guides in the Q&A section on unlocking, rooting and installing roms with the use of fastboot/adb, all the commands are given.
Good luck
If root is not working as it should, just re-flash the superuser package again. See here.
It's likely an issue with out-dated files or with permissions.
if you use a toolkit, you're on your own - since neither you or us know what happened. it's your fault, for rushing things.
google won't help you either. that's why we say things like that.
Ok, got it. Thanks. Bye.
t1.8matt said:
Ok, got it. Thanks. Bye.
Click to expand...
Click to collapse
Hey I'm a seasoned user here and I'm having the exact same problem with Trickster Mod... you fanboys need to kick it back a notch and try to help someone once in awhile.
Thanks for the info. For now I moved on to Epic V5, maybe when Nitro comes out with the 16 update I'll try it again, cause I really do like that dark eclipse Rom.

Categories

Resources