Develop Bugs

Easy rooting with 'Simple Root' (EVO 4G) - Also possible for Desire?

I am sorry if this should have been posted in general, but I think it has to do with development.
I just found some info about a program called 'Simple root', currently only for the Evo 4G. From what I have read it is a program to root your device with just a few clicks (so noob proof).
I wanted to notify you about this, first of all. Second, do you guys think it is possible to make something like this for the Desire? Or does the one for Evo also work for the Desire?
I am really a biiiiig NOOB regarding rooting etc, so this would be perfect for me. And I think a lot of other noobs would be happy as well.
Again, sorry if I did something wrong here (duplicate thread, wrong section, etc)
Kind Regards, Mark
Edit: THE LINK down below
forum.xda-developers.com/showthread.php?t=706411

that would be too awesome

Honestly, I'm sorry, but what's the point? The current methods are easy enough - if you can't (not saying you, just someone generally) can't follow those, I can see a few stupid threads coming up:
i tried 2 root my desire bt it sed it failed wot do i do
Click to expand...
Click to collapse
And they'll be clueless as to how to extract debugging messages. I may be alone in my opinion, but I thought I'd share it

jayshah said:
Honestly, I'm sorry, but what's the point? The current methods are easy enough - if you can't (not saying you, just someone generally) can't follow those, I can see a few stupid threads coming up:
And they'll be clueless as to how to extract debugging messages. I may be alone in my opinion, but I thought I'd share it
Click to expand...
Click to collapse
i second that

jayshah said:
Honestly, I'm sorry, but what's the point? The current methods are easy enough - if you can't (not saying you, just someone generally) can't follow those, I can see a few stupid threads coming up:
And they'll be clueless as to how to extract debugging messages. I may be alone in my opinion, but I thought I'd share it
Click to expand...
Click to collapse
Yeah, it should be kept as elitist as possible. I think only people with 10 years coding experience and a self compiled version of their own linux kernal should be allowed to root their phones.
Seriously, come on. Making it friendly is not a bad idea. I know what I'm doing, and I'd still rather press 1 button over all other current options. It makes no difference because I had no trouble following rooting instructions from r1 up to r6. I just think simpler is better.

jayshah said:
Honestly, I'm sorry, but what's the point? The current methods are easy enough - if you can't (not saying you, just someone generally) can't follow those, I can see a few stupid threads coming up:
And they'll be clueless as to how to extract debugging messages. I may be alone in my opinion, but I thought I'd share it
Click to expand...
Click to collapse
Dude, 1-click root is a better method than buying 3/4 sd cards to create a gold card. Whenever a better solution/design comes up, people leave the old stuff behind.

unclesomebody said:
Yeah, it should be kept as elitist as possible. I think only people with 10 years coding experience and a self compiled version of their own linux kernal should be allowed to root their phones.
Click to expand...
Click to collapse
maybe not this pro but if someone is rooting a phone, that person should know a little bit about what he is doing. its not rocketscience, every body can learn it, but if we start making stupid-one-klick-iam-an-idiot-rooting than no one will try to learn it.....

i agree with last post but....
nowhere in development does it even explain what things like dalvik cache or kernels actually. i reckon alot of people here into flashing and tinkering with their phones are just following instructions. ie there's a difference between a qualified mechanic and someone that messes around under the bonnet at the weekend.
in terms of rooting i found this guide the most useful, it has all the files you need and has a VIDEO walkthrough. SIMPLE really SIMPLE. requires no linux, coding or anything.
http://theunlockr.com/2010/06/07/how-to-root-the-htc-desire/

tuntang said:
nowhere in development does it even explain what things like dalvik cache or kernels actually.
Click to expand...
Click to collapse
XDA is a resource, a good resource is that, but it is not complete. Even Wikipedia is not complete, if you think about it.
Copying everything to one place will just cause redundant (and possibly outdated) information. Let the people who know what they're talking about, do so (i.e. Cyanogen).
unclesomebody said:
Yeah, it should be kept as elitist as possible. I think only people with 10 years coding experience and a self compiled version of their own linux kernal should be allowed to root their phones.
Click to expand...
Click to collapse
I can't even tell if your misspelling of "kernel" is intentional.
unclesomebody said:
Seriously, come on. Making it friendly is not a bad idea. I know what I'm doing, and I'd still rather press 1 button over all other current options. It makes no difference because I had no trouble following rooting instructions from r1 up to r6. I just think simpler is better.
Click to expand...
Click to collapse
So the current version is unfriendly? Another reason against making this process wholly autonomous is that you'd then have to waste someone else's time writing an application to fix the USB issues, because there's going to be people who got used to the easy of a giant button labelled "Click here to root" so now do not know what adb is.
Simplification can cause loss of information. Suppose the case comes around where the program crashes in a rare event, but the adb connection stays open. It's also far too cumbersome to catch every error, such as an invalid goldcard or the SD card being out of space. If the rooting process was a kernel exploit, this wouldn't be a problem. See below.
mr.r9 said:
Dude, 1-click root is a better method than buying 3/4 sd cards to create a gold card. Whenever a better solution/design comes up, people leave the old stuff behind.
Click to expand...
Click to collapse
This is a completely different argument. You have assumed there is a 1-click rooting method available, which there isn't (yet). The only way your argument would hold is if there was a kernel exploit available currently that gave you root, but you only got it uncompiled and had to do the legwork yourself - which isn't the case. The actual argument was about converting the existing method to a few clicks as possible.

It's easy enough as is. We're not iPhone users after all, we don't need big shiny buttons to understand

starchildx said:
maybe not this pro but if someone is rooting a phone, that person should know a little bit about what he is doing. its not rocketscience, every body can learn it, but if we start making stupid-one-klick-iam-an-idiot-rooting than no one will try to learn it.....
Click to expand...
Click to collapse
this is true - but there are developers and there are consumers.
anything that represents 'progress' should be seriously looked at.
I think fake-flash is just one excellent example where something that wasn't especially complicated in the first has been made way simpler.....

My reply was deleted?
Current method is easy enough. We need FULL root, easy way or not =)

cr1960 said:
this is true - but there are developers and there are consumers.
anything that represents 'progress' should be seriously looked at.
Click to expand...
Click to collapse
Sure,but i think there are more important things to do than making a 1-click-root.

starchildx said:
Sure,but i think there are more important things to do than making a 1-click-root.
Click to expand...
Click to collapse
There always will be something more important than something else, but it's in no way an argument against doing it.

[ROM]DL17/Deodexed/Rooted/Busybox/Debinged/Debloated

Hey folks,
This is a very basic DL17 rom. It has been debloated, debinged, rooted, deodexed, and zipaligned. Does NOT include radio or kernel.
Download link:
http://www.mediafire.com/?wdv53fbgl18988i
This should serve as a decent base for folks to build their future roms.
Credit to bubby323 for providing me the DL17 system dump.
credit to Logan302 for testing in IRC.
Patch
------
http://dl.dropbox.com/u/2056318/update-template/email_continuum.zip This should fix email issues.
http://dl.dropbox.com/u/2056318/update-template/social_apps.zip Social apps.
use at your own risk. I am not responsible for anything you do to your device!

DD
Tested it, and it worked absolutely perfectly my market its even working again xP bonus
Thank you so much for your time and effort! xD

Thanks for sorting out the issues with the syslinks.
Sent from my SCH-I400 using XDA App

Flashed this, This morning and it works awesome. I also flashed the test kernal you provided a week or so ago and its working great together.
Thanks for this.

Well just noticed some sort of bug on my phone at least.
When i try to add a facebook account to my ticker it fails and when i click on adding an email to my ticker it locks up my phone and i have to pull my battery. It doesnt even get me to a enter email and password screen.
Honestly to me its not a big deal im not a big facebook or email guy so it doesnt bother me.
Also i was wondering if you knew if any of the themes for the fasinate will work for this? I doubt it just wondering.

Fascinate themes must be ported. I'll look into the facebook and email issue fi possible.

Patch added for email.

adrynalyne said:
Fascinate themes must be ported. I'll look into the facebook and email issue fi possible.
Click to expand...
Click to collapse
Any idea how i would go about porting them?

There are theme porters out there. I'll get some input from others.

CrazyKnight122 said:
Any idea how i would go about porting them?
Click to expand...
Click to collapse
adrynalyne said:
There are theme porters out there. I'll get some input from others.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=932856
the theme porters that are out there...well they most just copy images with the same (or very similar) file names over one another...the post i linked above is my horribly incomplete but still useful attempt at helping people get into themes for the fascinate.
all the tools neccessary are linked in the posts there.
since the fascinate dj05/dl09 update appears very similar to dl17 porting our themes shouldnt be difficult image wise...however there are several xml changes that must be made (especially for black menus)
if anyone is really interested in starting to theme for the continuum look through the above thread and feel free to pm me here with questions or hop into the fascinate irc...im usually in there during the week throughout the day...or others im sure can help too
i had briefly thought about throwing a theme together for the continuum for fun right before dl30 (froyo) leaked...but now i have too much on my plate reporting stuff

While posting an Android ROM, can you guys PLEASE mention what Android version it is? Is this Eclair or Froyo? 2.1, 2.2, 2.2.1...which version? DL17 might explain everything to a developer but not to a user who just wants to flash a ROM on his system and needs to know what Android version it is before actually flashing it.

With all due respect, if you aren't familiar with the naming convention, i.e. don't know what DL17 means, you have no business flashing a rom (until you do). You are gonna end up breaking your device.
2.1Update-1 is the only OS currently available for this device. So.. labeling is a bit redundant right now.

Hey, you guys made the news...
http://www.androidcentral.com/samsung-continuum-sees-its-first-custom-rom
Sent from my SCH-I400 using XDA App

adrynalyne said:
With all due respect, if you aren't familiar with the naming convention, i.e. don't know what DL17 means, you have no business flashing a rom (until you do). You are gonna end up breaking your device.
2.1Update-1 is the only OS currently available for this device. So.. labeling is a bit redundant right now.
Click to expand...
Click to collapse
Thanks for your response and the clarification and with all due respect, the standard naming convention for Android operating systems is in the format of Android <version number> <dessert codename>. I have been flashing ROMs to several devices before there was any Android and have been doing so on a dozen or so Android devices that I have for the past 6 months as well as guiding others in doing so by writing about it - I write about these for a living.
However, one can't be expected to know all about these non-standard or manufacturer-specific ROM naming conventions for all the Android devices out there and unfortunately, I do not have every single device available to test the ROMs on before I write about them. That is why just a few words by the developer in the OP mentioning what Android version it is make things a lot easier for many of us, plus there are several users who are just starting at the flashing business and it makes things more clear to them as well on what they are getting into. Simply saying that if one doesn't know about these non-standard conventions, one shouldn't be trying these things out is similar to saying if one doesn't know how to swim, one shouldn't be getting into the swimming pool. No offense intended. =)
All that being said, keep up the good work - I really appreciate all the hard work you guys put into what you do. Please don't take my comments as a flame - they are just my views on how things can be improved for a lot of us just by a tiny bit of effort from you guys. =)

It is well known that the continuum only has 2.1. Therefore unless there was a 2.2 leak for it (which would be noted) it can be assume by any reasonable person that its a 2.1 rom.

nitsuj17 said:
It is well known that the continuum only has 2.1. Therefore unless there was a 2.2 leak for it (which would be noted) it can be assume by any reasonable person that its a 2.1 rom.
Click to expand...
Click to collapse
Agreed but 'well known' can be relative =) What's well-known to the developer community for a particular device might not be well-known to many who are coming across the flashing scene for the device in question for the first time, despite their prior experience with other Android devices. And as leaks are not out of the question either, just adding two words about the Android version just makes things a bit more clear for everyone, that's all I meant to say.

Coverage
Here's some more coverage for you:
http://www.addictivetips.com/mobile/install-clockworkmod-recovery-on-samsung-continuum/
&
http://www.addictivetips.com/mobile/install-dl17-clean-rooted-android-2-1-rom-on-samsung-continuum/

HQRaja said:
Agreed but 'well known' can be relative =) What's well-known to the developer community for a particular device might not be well-known to many who are coming across the flashing scene for the device in question for the first time, despite their prior experience with other Android devices. And as leaks are not out of the question either, just adding two words about the Android version just makes things a bit more clear for everyone, that's all I meant to say.
Click to expand...
Click to collapse
That goes back to this:
adrynalyne said:
With all due respect, if you aren't familiar with the naming convention, i.e. don't know what DL17 means, you have no business flashing a rom (until you do). You are gonna end up breaking your device.
2.1Update-1 is the only OS currently available for this device. So.. labeling is a bit redundant right now.
Click to expand...
Click to collapse
If you don't know what OS your phone is already running, or how they're doing the naming convention, you are likely going to cause yourself massive problems soon. If someone can't figure out About Phone to compare build versions, they likely can't figure out how to get CWM on their phone to even flash this, so it doesn't matter if the OS version is in the title. Once Froyo drops, then it may be different, but until then, you have a very thin argument at best, regardless of how many ROMs you may or may not have flashed in the past.

imnuts said:
That goes back to this:
If you don't know what OS your phone is already running, or how they're doing the naming convention, you are likely going to cause yourself massive problems soon. If someone can't figure out About Phone to compare build versions, they likely can't figure out how to get CWM on their phone to even flash this, so it doesn't matter if the OS version is in the title. Once Froyo drops, then it may be different, but until then, you have a very thin argument at best, regardless of how many ROMs you may or may not have flashed in the past.
Click to expand...
Click to collapse
In my experience, not knowing the device-specific naming conventions has never bricked any of the dozens of devices I have flashed, as long as I have known that it is a ROM meant for the particular device in question. However, knowing what Android version the ROM is based on without having to ask only makes sense. This isn't about this one device in particular - the Android scene isn't similar to the iPhone scene where there is just one developer (Apple) rolling out just one OS for all the devices on the market. Android is quite fragmented and I believe simply mentioning the Android version with the ROM regardless of whether any other version is out *yet* or not only makes sense as one never knows when a newer version or a leak might be available.
It is all for the purpose of keeping things as clear to someone at first glance, as possible. Now I do know that no other version but this one has been out for the Continuum but that has been after this discussion. All I am requesting is that the OPs should consider mentioning it with the post so that even a newbie wouldn't have to ask for information as basic as this.
What I fail to see here is why this simple, rather humble request should be seen as such a debatable topic by you guys, when it doesn't even require much effort. Heck, all it requires is typing 'Android' followed by the version number. Is it asking for too much?

Okay, this is getting really off-topic and degenerating fast. There are plenty of other threads saying what DL17 is so just hopping out to the Android Development forum would have answered your question. That said, Android ROMs do often include the version, but not always.
It's not that big of a deal. Let it go.
Sent from my SCH-I400 using XDA App

Roms w/ descriptions... WHERE?

Hi, to this and i'm looking to install a new rom on my Epic 4G but like every person, I am afraid to damage my new equipment.
I'm looking for some stable Roms to flash my Epic but don't know where to look for them with a good description of what does work- what doesn't-what will improve with it... Thing's like that. If anyone can help me, i'll apreciate. =)
Sent from my SPH-D700 using XDA App

3ndless said:
Hi, to this and i'm looking to install a new rom on my Epic 4G but like every person, I am afraid to damage my new equipment.
I'm looking for some stable Roms to flash my Epic but don't know where to look for them with a good description of what does work- what doesn't-what will improve with it... Thing's like that. If anyone can help me, i'll apreciate. =)
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
This took like 0.1 sec on google:
http://alchemistar.blogspot.com/2010/11/samsung-epic-4g-custom-rom-list-1110.html
A list is not maintained on XDA.

Go here! Click on your model below
http://forum.xda-developers.com/wiki/index.php?title=File:Samsung_Epic_4G.png

3ndless said:
Hi, to this and i'm looking to install a new rom on my Epic 4G but like every person, I am afraid to damage my new equipment.
I'm looking for some stable Roms to flash my Epic but don't know where to look for them with a good description of what does work- what doesn't-what will improve with it... Thing's like that. If anyone can help me, i'll apreciate. =)
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Just look up "Samsung Epic 4G Rom XDA" on google and you'll find a whole selection of roms. Then just read their descriptions and some comments to find out what they're all about. I'm a little disappointed that this was you first contribution to the XDA forums...

RandomKing said:
Just look up "Samsung Epic 4G Rom XDA" on google and you'll find a whole selection of roms. Then just read their descriptions and some comments to find out what they're all about. I'm a little disappointed that this was you first contribution to the XDA forums...
Click to expand...
Click to collapse
Wow, don't need to be so "Humble" you guys, thanks anyways...
Sent from my SPH-D700 using XDA App

3ndless said:
Wow, don't need to be so "Humble" you guys, thanks anyways...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Oh relax, it's all in good fun. We answered you .
But you'll have a lot of questions, we all do, and you'll get your answers faster 9 times out of 10 by checking if someone already asked them first.

RandomKing said:
Oh relax, it's all in good fun. We answered you .
But you'll have a lot of questions, we all do, and you'll get your answers faster 9 times out of 10 by checking if someone already asked them first.
Click to expand...
Click to collapse
Ok, really sorry for the bother I could cause its just that i've been looking in Google about this and its very confusing. ALWAYS appears something new about this theme & I want to already finish with it to fully enjoy my equipment.
Sent from my SPH-D700 using XDA App

Theme? What do you mean?
-Sent from my custom INC Epic.

Hey I was new to it myself and as long as you can put your phone in dowload mode you have really nothing to worry about just make sure your cable is good and you have the stock rom and your good
Sent from my SPH-D700 using XDA App

3ndless said:
Wow, don't need to be so "Humble" you guys, thanks anyways...
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Random's post was actually very humble, some people get crucified for not searching lol

We do need a clearer documentation of ROMs
Personally, I think OP's request is completely valid. There are a multitude of ROMS. The roms really don't have any specific vision statement such as "My goal is to be the most stable rom" "my goal is to be the most bleeding edge ROM" "my goal is to be the quickest ROM" or "my goal is to be the fastest ROM, even if stability suffers". Instead each rom seems to be a person who then does some personal tweaks and incorporates the generally available tweaks others have posted.
There's also not a clear change from version to version other than, (hopefully), the release notes which may list "teaked X", "changed Y" which doesn't help me understand if the next build is more stable, smaller, faster, or what.
Also, it's hard to tell the riger put into the software development process. While some ROMs are team built and significantly tested, it's hard to tell which. I assume ACS and Bonsai both have many people testing for many weeks prior to releasing a ROM, but I don't know that. And for the smaller ones, I have no clue.
Ultimately, it would help for someone who has enough experience with each ROM to document the differences. Alternately, a template for ROM developers to fill in each version might help. Something like.
GOAL OF ROM: (if multiple goals, list in order of importance to the developer)
DEVELOPER/DEVELOPERS: (by name, handle, or # of developers)
MAJOR BUILDS INDICATE A CHANGE IN... (time, tweaks, base build, etc)
CODE MANAGEMENT PROCESS: (formal repository, versioning in development package, 1 set of source files edited in VI with no backups or versions)
TEST PROCESS: (length of test, number of test subjects, any stress tests/unique situations/or boundary scenarios included in testing)
SUPPORT OPTIONS: (post on board, email development team, IRC, fire and forget, normal response time, etc)

You need to do what I and most of us did....read the threads following the ROM releases. Every phone is different but if 10 people on the ROM thread report Bluetooth issues and BT is important to you, don't use it. There are no info shortcuts here. Read the ROM threads.
Do you BONSAI?

Unfortunately, it's completely impractical to read through hundreds of posts per ROM to understand the pre-existing bugs with each ROM. Additionally, those bugs are tied to a build. The build they are associated with is usually not apperent from the posts.
The only way to keep up is to skim each rom regularly so you can maintain the current state of each ROM. it doesn't allow people to come in from a cold start and understand what's going on. That would be a good thing to add to the manifest listed above though:
KNOWN OUTSTANDING ISSUES:
REPORTED BUGS:

gdbassett said:
Unfortunately, it's completely impractical to read through hundreds of posts per ROM to understand the pre-existing bugs with each ROM. Additionally, those bugs are tied to a build. The build they are associated with is usually not apperent from the posts.
The only way to keep up is to skim each rom regularly so you can maintain the current state of each ROM. it doesn't allow people to come in from a cold start and understand what's going on. That would be a good thing to add to the manifest listed above though:
KNOWN OUTSTANDING ISSUES:
REPORTED BUGS:
Click to expand...
Click to collapse
Most of the big developers make an effort to list the large and recurring issues in the first page of the thread. Most other bugs tend to be one-offs caused by a bad flash or failure to wipe data prior. I understand where you're coming from, as I felt the same way when I first jumped in. Mind you, I got the phone in November of 2010, began actively following various threads within a few weeks, gained a vast amount of knowledge on the matter, didn't first root until the EB13 update in February, and didn't even sign up to the forum until March, after which I began helping others with problems I had found answers to months before even making my first post.
I don't preach hypocrisy. I generally criticize an oft-repeated question while also answering it or linking it to one of many long-existent answers. I preach learning by reading. If I tell you how to fix something today, you'll come back with a problem tomorrow because you didn't earn the knowledge for yourself, and you didn't understand what you did. The age-old parable:
"If you give a man a fish, you feed him for a day. If you teach a man to fish, you feed him for a lifetime!"
I strongly suggest everyone read as much as they can to understand as best they can! Take your epic to the toilet and read in your spare time!
While your idea is a noble one, it's a much larger undertaking than you're giving it credit for. Developers would have to collaborate to give a list of specifications, known bugs, etc. to one thread. Someone would have to oversee this thread, take in additional posts to this thread, and append them to the front page continuously. The end result would be roughly what each individual thread already attempts to achieve, with a much larger scale of chaos and a huge problem with out-of-date details.
The list Kenny linked contains a list of known Epic roms and their latest update. You could make this an XDA thread, but I can't say that trying to include every detail and bug beyond that of every rom is a good idea.
That said, look around. Find a Rom. Read about its details. If it sounds good to you, give it a test run! Use what works for you, don't obsess about which one is the "best".
-Written by a man with nothing to do during his lunch break.

No one should be "jumping in cold" and rooting and throwing on ROMs. I got my phone in September, read through posts on ROMs that had features I liked, then 6 weeks later rooted and tried a few ROMs. There are videos now in the General stickies to help cut down on the reading but as stated every phone is different right out of the box. One ROM may cause a messaging issue with a small group whereas another Bluetooth issues. Most developers list known bugs being worked on in the OP.
Do you BONSAI?

try this on youtube
qbking77 on youtube. put in search box 'How to Root Samsung Epic and flash SyndicateFrozenRom 1.1.0/1'. cannot post a link at this time, I'm too new

Actually, I read XDA every day (work's been slow recently). I've rooted my phone and installed more roms than I can count. (Also rooted my wife's and her viewsonic gtab.)
I agree that the major rom builders do a much better job of managing and documenting their development process than most 1-man outfits. However, I still can bearly tell the difference from 1 ROM to the next or 1 build of a ROM to the next. (As far as I can tell, what we have are pretty much the same ROM a dozen different times with slightly different bugs.) A standard for ROM developers to fill in would hopefully help them in focusing their ROM as much as it helps people in understanding the goals of their rom.
As for the effort involved in keeping it up-to-date, most of the worthwhile developers update their main post or start a new one at each major build. Adding some structure to that update wouldn't be a significant increase in hastle.
on a completely separate note, I understand where you are coming from with the "teach them to search" montra. (I helped moderate a very large everquest form for years.)
Since then though, I've realized that, while it's very popular on message boards, it's not very useful. You have to either have a very good understanding of where on a message board to look for the information you are interested in or you need to be a very skilled searcher. Otherwise you end up spending a significant amount of time pouring through poorly summarized search results which don't address your question without knowing if there IS an answer somwhere. While the (here are similar threads) function of vBulletin is reasonably useful, the xda search powered by google is impossible.
Wiki's form a MUCH better way of collecting answers to message boards than bulletin boards do. Unfortunately, you need your WIKI and your forum tightly integrated, (which means a CMS rather than vBulletin + mediawiki). Also, you need forum posters who, after answering a question on the forum, turn right around and post the answer into a wiki page to ensure it was there for the next person

(Actually, it'd be really cool if every Q&A forum on XDA, instead of pointing to a normal forum, pointed to a wiki answers type software install (http://wiki.answers.com/) tailored for XDA. That would hopefully significantly cut down on re-asking of questions. )

3ndless said:
Hi, to this and i'm looking to install a new rom on my Epic 4G but like every person, I am afraid to damage my new equipment.
I'm looking for some stable Roms to flash my Epic but don't know where to look for them with a good description of what does work- what doesn't-what will improve with it... Thing's like that. If anyone can help me, i'll apreciate. =)
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
You can look in the development area, the threads are there for the ROMs. Typically the first few posts of a ROM thread will be the information about it. Then read a few of the pages (near the beginning and the last few) to get a feel for what users are experiencing during their use of the ROM.
That should give you the information you're looking for.
Good luck

I would suggest you look into the following excellent ROMs
Midnight v 5.3 which is based on Bonsai. This is my favorite and Rob is very helpful about his and other peoples ROMs
Bonsai itself which you have to go to their site for
Syndicate Frozen 1.1.1 from ACS.
Frankenstein when ecooce finishes the newest one. This is based on the ACS ROM
There are some other ones on here that I just don't know as much about. All of the developers use each others stuff so no matter what you go with it is better than stock.
You will learn a lot from your mistakes when flashing ROMs but the trick is to read a lot through the forums so you can learn from others mistakes.
Samsung Epic Midnight

Screenshots for Android Development

Hi all,
I think it would be great if some guides to do certain things like downgrading firmware or turning S-OFF to have screen shots because somebody like does not know what to enter in each step because in command prompt you need to set a directory when you want the command to work. It would be great for everyone to follow instructions. Just like the HTC Dev Unlocking Bootloader website where they show photos with a screenshot on what to do next.
I know that storing images into a server can use up a lot file but I think this would be a great idea.

If you want to write a guide to doing those things with screenshots, all power to you I am not sure how this relates to XDA, its not like they have ever phone ever made available to them todo guides for, and each phone is generally slightly different.
As far as hosting, even photobucket will do the job nicely.

knightslay2 said:
Hi all,
I think it would be great if some guides to do certain things like downgrading firmware or turning S-OFF to have screen shots because somebody like does not know what to enter in each step because in command prompt you need to set a directory when you want the command to work. It would be great for everyone to follow instructions. Just like the HTC Dev Unlocking Bootloader website where they show photos with a screenshot on what to do next.
I know that storing images into a server can use up a lot file but I think this would be a great idea.
Click to expand...
Click to collapse
The guides that are posted are done so with the point of learning what to type where. Modding your phone is not something to do because you think it is cool. IT carries real risks. Remember this is a development site. Not a How To site. If you want to do this as stated above feel free. Just keep in mind that it is expected that when you attempt to do anything to rewrite the vase OS of your phone that you have done the proper research and thought about it long and hard.

zelendel said:
The guides that are posted are done so with the point of learning what to type where. Modding your phone is not something to do because you think it is cool. IT carries real risks. Remember this is a development site. Not a How To site. If you want to do this as stated above feel free. Just keep in mind that it is expected that when you attempt to do anything to rewrite the vase OS of your phone that you have done the proper research and thought about it long and hard.
Click to expand...
Click to collapse
"Modding your phone is not something to do because you think it's cool"
XDA has more than 3 million members who would disagree with you on that. What is not cool about rooting and modding your device?
"Remember, this is a development site, not a how to site"
Not entirely true. While XDA's main purpose is to provide a forum that encourages developers to be creative and share their hard work with the community, developers include detailed instructions on "how to" install/flash a ROM or MOD. XDA is also about teamwork, and encourages experienced members to guide new members in the right direction.
"Just keep in mind that it is expected that when you attempt to do anything to rewrite the vase OS of your phone that you have done the proper research and thought about it long and hard."
Not sure what there is to think long and hard about. Most people are here because of the freedom and flexibility the Android platform has to offer. Rooting and modding is not rocket science, nor heart surgery; but rather fun and interesting. I think it's safe to assume that most people who come here, do so to test the limits of their devices, while adding customizations that express who they are. For every mistake made by an inexperienced member, there is usually a workaround to remedy the issue.
While XDA encourages members to read, read, and read some more before attempting to root or mod, it's not done to discourage people from modding/rooting but rather a "proceed at your own risk" approach to prevent inexperienced members from flooding and overwelming the developers with support questions when something goes wrong.
My point is that rooting and modding is fun; A LOT of fun, and very interesting. The ability and freedom to customize your device to your liking, while increasing the performance, and pushing your device to the limits is what made XDA what it is today; One gigantic family of people who share a common interest.
Sent from my Galaxy S II ( SGH-i777) using XDA Premium.

knightslay2 said:
Hi all,
I think it would be great if some guides to do certain things like downgrading firmware or turning S-OFF to have screen shots because somebody like does not know what to enter in each step because in command prompt you need to set a directory when you want the command to work. It would be great for everyone to follow instructions. Just like the HTC Dev Unlocking Bootloader website where they show photos with a screenshot on what to do next.
I know that storing images into a server can use up a lot file but I think this would be a great idea.[/QUOTE
You didn't provide enough information in your OP. You might get more assistance if people knew which device you have.
Sent from my Galaxy S II ( SGH-i777) using XDA Premium.
Click to expand...
Click to collapse

[Q]How to perma-brick via Android OS or TWRP?

Howdy folks. I'm not much of a developer, so I need a bit of help trying to make my concept a reality. Obviously if I'm successful, I'll give credit where credit is due. That being said, I'm looking for a way to hard-brick Android devices from either within the OS itself, or from a custom recovery, preferably TWRP. A kind of "self-destruct", if you will. And it has to be doable, or at least triggerable, from Android itself, so I can set it up to be activated remotely, via Tasker or what have you, nothing that I would need to connect the phone to a computer to use. So I guess what I need is either a script, or a recovery flash zip. I'm hoping for a universal solution, so it could be used for any Android device, not just mine. But if that's not available, my current devices are a T-Mobile S3 (obviously), HTC One, Motorola Xoom LTE (aka Wingray), and Galaxy Note 10.1 2014 Edition (P600), and I'd like to have it working with any and/or all of my devices, at least. So, is there any way I can achieve this?

On a public forum accessible to unregistered users, such a discussion can and will open a can of worms. Yes indeed there are ways to do this. However I am sure ways of wanton destruction will violate XDA rules. Who knows, some unsavory folks came across this and sent it as a bomb to all ? You see where I am going ?
Having said that, I think your genuine intent is to make your device unusable in case of theft. Towards this, there really are several nice apps and services. Starting with Google's own Device manager to Where's my droid and quiet a few others. Please explore what they can do.

You're right about my intentions, but I don't just want to wipe my device if it's stolen, which is all those apps can do. I want to render it completely unusable, so whoever has taken it can't do anything with it. So what you're telling me is, if I DO come up with a way to do so, it's probably not a good idea to share it here?
Edit:
Perseus71 said:
Who knows, some unsavory folks came across this and sent it as a bomb to all ? You see where I am going ?
Click to expand...
Click to collapse
I'm not looking for something to send to my phone. I'm looking for something that would take an extensive set-up procedure. Something like a script, started by Tasker, in response to a VERY specific text message. Or maybe instead of a script, a zip being flashed, although I haven't quite figured out how to do that with Tasker yet. You're probably right about the XDA rules though, I didn't think about that.
Sent from my SGH-T999 using XDA Premium 4 mobile app

Device encryption and Screen lock are supposed to serve precisely that exact purpose you are describing. Please explore. Do understand some of the other apps in the category of Lookout do offer a lot more features and functions. Please explore one or two of them.