I'm curious if someone could put together a one-click root for Mac users. I've been in the rooting game for a while now (had a Droid 2 before) so I know what I'm doing. I just want a one-click in order to save time and convenience.
I'm sure there are other Mac users out there also interested in this. If something for Mac has already been posted then I apologize, please direct me to the appropriate thread.
I could possibly give it a shot. I have to stop this kernel panic on my pc before I boot mac, but it shouldn't be that hard. I'm already rooted, so I'll need some testers, but I'll try a similar method as the one for windows and try to make it mac/linux compatible.
That'd be great! Unfortunately I have a feeling this thread might be deleted since apparently only Developers are allowed to create threads in this section (even if others' posts are on topic).
Keep in touch with me via PM, I'd love to know of your progress.
Please lock this thread mods. I'll start a thread when I finish an alpha for mac/linux. Thank you, and please no one else post so this can die off and not get unneeded attention/wasted space on the forum. Please save for the thread that will contain the root pack.
kdb424 said:
Please lock this thread mods. I'll start a thread when I finish an alpha for mac/linux. Thank you, and please no one else post so this can die off and not get unneeded attention/wasted space on the forum. Please save for the thread that will contain the root pack.
Click to expand...
Click to collapse
Please contact me, want to make sure brick precautions are made.
I'm beginning to think the manual method maybe more reliable from reading post on the easy root
Related
I'm just wanting to change up some font colors and grahics on a rom I have. I was told Eclipse was the way to go, so I set up an Android Dev machine with all the plugins and recommended tools. Now what?
Since no one is willing or able to help, could someone or a Dev be so kind to get me the correct xml file that will change the top title bar fonts to white instead of black. I will put the file in the rom and re-sign it myself.
I am by no means any good at theming, I fail pretty hard, but this might help. http://forum.xda-developers.com/showthread.php?t=535630
Also, maybe try posting in the theme forum. Good luck.
There are different xml files for different stuff. Check out colorchange app. It works with cyanogen to change all stuff. Much easier that the xml stuff we used to have to do. Pm me if you have any specific questions.
If you search for colorchange or even posts by me you will find it. When I turn my pc on later I will post a link if required.
Thanks for the info mates (MontAlbert and bcrook). I will check out the colorchange app. One day I will find some write ups on Elclipse and android rom programming. Will let you know how the app worked out, MontAlbert.
http://forum.xda-developers.com/showthread.php?t=535630
long thread to read through but it has allthe answers you need.
MontAlbert said:
http://forum.xda-developers.com/showthread.php?t=535630
long thread to read through but it has allthe answers you need.
Click to expand...
Click to collapse
Thank you for this. I will have a read later tonight. And thanks for your help. I did find the file you were refering too but am lost on if it is flashed to the phone or loaded into my dev system.
zeroplace said:
Since no one is willing or able to help, could someone or a Dev be so kind to get me the correct xml file that will change the top title bar fonts to white instead of black. I will put the file in the rom and re-sign it myself.
Click to expand...
Click to collapse
You probably want to ask these questions in the Android dev group(s) on Google groups. The digests I get every day indicate there is a lot of activity there.
Rom OP Format...DEVS READ PLEASE
Below is a format that should be used as an example of how a rom thread should look. It doesnt have to be exact. I suggest that you stay creative and use all the features in the advanced panel when creating a thread.
1. Name of rom, team, etc
2. Introduction
3. Changelog in code or php tags
4. What's included in the rom in the (apps, tweaks, scripts, addons, mods) in code of php tags
5. What works/what doesn't work in code or php tags
6. Credits (Users name-with link to (profile/github/or thread u got tweak from embedded), and what they did to help you)
7. Screenshots (2-10 different screenshots of different aspects of rom)
8. Kernel with either link to thread you got it from or github (if stock sense or cm please state that and that is enough)
9. Instructions on how to install the rom (also if special instruction for a2sd or beats audio...etc)
10. Do's and Don'ts of the rom
11. Questions & Answers section (I find this helpful to write out asked questions with solutions at the bottom of the op. I find that it cuts down on the question being asked a million times)
12. Finally the dl link
13. Additional add-ons (this can go into first post or reserved posts after)
I find the embedded link looks and feels better throughout the op if possible.
All sections should have a header with enlarged text and spaced out so people can read it easily.
I am hoping that this helps to make this section a little cleaner and easier. enjoy
The way I look at this is that it takes US weeks/days/hours to make these roms....we can take the time out to make sure that the op looks professional and clean
Also Make sure the op is fully ready before posting. I know we all get excited to release a rom but stating that half the stuff will be updated as time permits just shows that you are lazy and in a hurry which doesnt look good cause if thats the case then how does your rom run....
No posting a a rom thread without a DL link either
(h/t PapaSmurf151)
This is to compliment the XDA Recognized Developer Program Revamp. Aspiring devs showing professionalism are more likely to be accepted and frankly, it will help you immensely in the business world.
Good Luck!
mf2112
Yes ! This is Useful for Beginners !!!!!
Mebin Robin said:
Yes ! This is Useful for Beginners !!!!!
Click to expand...
Click to collapse
I feel this post is for me
I wrote very badly and even if google is good OS should recognize that doing bad translation
I find it hard to make myself understood and understand
I know you are good moderators
I'll make an effort but PLEASE consider my weakness
No worries, we want to try to help.
The Q&A section would be very helpful for first timers and others who find a similar problem. Would appreciate it if everyone could include that.
I tried to post a reply to [HOW-TO]Fix your phone in the developer's section, but since I'm a new user, the system wouldn't let me. However, this post links to a page (imnuts.org/odin-packages/) that has taken down it's most valuable resources, the files needed for a factory reset. So although this might be the correct way to proceed, the missing resources makes it less valuable at this point in time.
victimoflg said:
I tried to post a reply to [HOW-TO]Fix your phone in the developer's section, but since I'm a new user, the system wouldn't let me. However, this post links to a page (imnuts.org/odin-packages/) that has taken down it's most valuable resources, the files needed for a factory reset. So although this might be the correct way to proceed, the missing resources makes it less valuable at this point in time.
Click to expand...
Click to collapse
try to PM some user who post in that section regularly.
he might help you
Sent from my SM-N900 using Tapatalk
hello every one
i have alcatel on touch pixi (4007D)
and i make rom but when i decompile the apk with (apk tool) all thing right :fingers-crossed:
and i change the xml & drawable & values
and come to recompile apk with same programs
Error occurs
please , any Developer help me and take my setting apk and convert to ics setting theme
thanks :highfive:
Apk in the attachments
no one can help me?
bad forum
When you don't get replies, don't just say xda is a bad forum.
The forum isn't the "thing" answering, it's the users. .
Anyways, I have an answer for your problem. And I know what exactly you're talking about.
The reason your "tool" shows an error when it compiles the .apk is because you made an error somewhere in the process of editing. This happens frequently, the easiest way to figure out the cause for this error is to check the error log. It shows precisely where the issue is.
I would help you out by making it for you, but there is two reasons I cannot. One - its too late here and I can't get on my PC, and Two - If we do it, you don't learn anything if you're building or cooking roms.
So what I would like you to do is, get a log of the error you're getting and perhaps I, or someone else could help you.
Also you can "bump" up your thread, read the stickies for rules on this. It'll help. Bumping the thread pushes the thread near the top of list so people see it. You already did this. But in a slightly different way.
Krish
Sent from my Nexus 5 using Tapatalk
Q&A for [ROM][GT-S6310N]GlassROM Young N Installer
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][GT-S6310N]GlassROM Young N Installer. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
I have used the installer from here: adbdriver.com/downloads to install the driver. It solved the driver problem which was the same.
However, the windows script is useless, it freezes the phone, do not waste your time.
martonl74 said:
I have used the installer from here: adbdriver.com/downloads to install the driver. It solved the driver problem which was the same.
However, the windows script is useless, it freezes the phone, do not waste your time.
Click to expand...
Click to collapse
Dude... you should be reporting that it does not work properly, instead of saying "don't waste your time". How am I supposed to fix the script if I don't get constructive feedback?
I didn't have time to try the Windows version, but I worked to make it work. So don't do that.
Sent from my GT-I9100 using XDA Free mobile app
> Dude... you should be reporting that it does not work properly, instead of saying "don't waste your time". How am I supposed
> to fix the script if I don't get constructive feedback?
> I didn't have time to try the Windows version, but I worked to make it work. So don't do that.
Gnmmarechal if you did not test the windows version, then why did you upload it? I am right that wasting time when trying a not tested script. So please do not delete my post again.
When the script runs, it makes several errors, for example this line is invalid:
adb shell rm /system/app/.apk
If you would like, I can upload the screenshot, but after then I have to re-flash the phone, so please ask me if you would really like to solve it. I have tried under Windows XP and Win7 with admin.
martonl74 said:
> Dude... you should be reporting that it does not work properly, instead of saying "don't waste your time". How am I supposed
> to fix the script if I don't get constructive feedback?
> I didn't have time to try the Windows version, but I worked to make it work. So don't do that.
Gnmmarechal if you did not test the windows version, then why did you upload it? I am right that wasting time when trying a not tested script. So please do not delete my post again.
When the script runs, it makes several errors, for example this line is invalid:
adb shell rm /system/app/.apk
If you would like, I can upload the screenshot, but after then I have to re-flash the phone, so please ask me if you would really like to solve it. I have tried under Windows XP and Win7 with admin.
Click to expand...
Click to collapse
That line was a typo, and I believe was fixed on the Linux version. Anyways, I uploaded it because I did not find any errors with it, people would likely want to use it on Windoes, and I didnt test it because I could not. You can, and it is your own fault if you brick anything. It does not hard brick anyways. Also, I did not delete any posts.
---------- Post added at 05:36 AM ---------- Previous post was at 05:05 AM ----------
Anyways, a new revision has been packed and uploaded, could you check it out?
Hello everyone.
First of all thanks gnmmarechal for your work on this unlucky device.
Before flashing current release (0.1.1) I'd like to ask the known issues, if any.
Is this ROM suitable enough for everyday use? I still can't find user's feedback about that.
Second question: what about flashing MammouthKernel v5 too?
It is reported to have some problem with N devices. Can someone confirm?
Thank you for your answers.
Up!
I flashed Emotion V10L... thanx anyway.