Related
Hi guys,
I've been reading this forum for almost a month now (since I got my Epic), and I still haven't seen any description for a lot of the software you're using. I'm not an idiot here, I made a joeykrim exploit uninstaller of my own shortly after noobnl posted the one click exploit. Still, I'm not a mind reader. How do you guys even keep up with this?
ClockworkMod - The website describes it as, "An open source recovery image used by many phones". Not very helpful. There's a post on their forums asking what it does, with no response.
Andromeda - Apparently a ROM Manager with built in root. Not very helpful. Starting from the top, why would I need a ROM manager? Does this run on the phone? Why would I want a ROM manager on my phone? Doesn't this serve the same function as ClockworkMod?
AOSP Magic and Tha Boss ROM - Neither of these have any instructions. Tha Boss ROM actually includes a download link, while AOSP Magic eschews the link in favor of a video review. The video review is nice, as it contains the first instructions I've seen so far, brief as they may be.
A few lines of description on your releases would really help the new people. Really, you'd have to be a fool to download these programs and flash/fry your phone without description or instruction! You're pushing away the more cautious people who might otherwise join in.
Netop said:
Hi guys,
I've been reading this forum for almost a month now (since I got my Epic), and I still haven't seen any description for a lot of the software you're using. I'm not an idiot here, I made a joeykrim exploit uninstaller of my own shortly after noobnl posted the one click exploit. Still, I'm not a mind reader. How do you guys even keep up with this?
ClockworkMod - The website describes it as, "An open source recovery image used by many phones". Not very helpful. There's a post on their forums asking what it does, with no response.
Andromeda - Apparently a ROM Manager with built in root. Not very helpful. Starting from the top, why would I need a ROM manager? Does this run on the phone? Why would I want a ROM manager on my phone? Doesn't this serve the same function as ClockworkMod?
AOSP Magic and Tha Boss ROM - Neither of these have any instructions. Tha Boss ROM actually includes a download link, while AOSP Magic eschews the link in favor of a video review. The video review is nice, as it contains the first instructions I've seen so far, brief as they may be.
A few lines of description on your releases would really help the new people. Really, you'd have to be a fool to download these programs and flash/fry your phone without description or instruction! You're pushing away the more cautious people who might otherwise join in.
Click to expand...
Click to collapse
clockwork rom manager is an app on your phone that requires root access, allows you to flash roms under the android OS and is nice and GUI (graphic user interface)
clockwork recovery is at the boot level, before the android OS loads, it's used as a minimal menu to do lower level functions such as flashing roms to your phone, clockwork rom manager uses this as it's backend for flashing roms.
androidmedia, boss rom and aosp magic are all roms (entire custom android OS packages) flashable though clockwork recovery
everything listed as a kernel is only a chunk of the OS that controls the hardware and such... they can overclock the device and improve battery etc. applications and favorites and other user data stuff is uneffected.
the weird names are just what the developers are naming their software. What you should be paying attention to are key terms like
ROM, KERNEL, RECOVERY those are the different parts that are being modified...
That being said.... for someone that researched for over a month, you don't seem to be quite getting it, also this doesn't need to be in developer forum, and all this is in the hundreds of WIKI's posted on other android devices.. also a quick google search would answer most of your questions you're having
Netop said:
ClockworkMod -
Andromeda -
AOSP Magic and Tha Boss ROM
Click to expand...
Click to collapse
ClockworkMod - makes a custom recovery, along with many other programs and apps, that makes flashing custom rom's and kernels much easier. Add Clockwork Recovery to your phone and you can load any custom rom or kernel you want by simply booting into recovery. Instructions to install it on your phone are in the OP (original post) of the clockwork recovery thread.
Andromeda - It is a group of custom programs noobnl has made. He made a custom kernel (this overclocks (makes faster) your cpu and undervolts (adds battery life)). His kernel also installs rom manager and super user to make make rooting more functional. Noobnl also has an andromeda rom that modifies touchwiz to be a little different with some different features. In both cases read the OP of the two threads and you will find easy installation instructions (using clockworkmod recovery) and a description of what they both do.
Aosp Magic and Tha Boss - These are both custom roms that in some way change how your phone looks and functions. Custom roms are all just ways to personalize your phone. For the most part they all install easily with clockwork recovery. Read the OP of any rom and it tells what they have done, what they do with each update, and how to install it.
Not trying to be mean or anything, but reading the OP pretty much always explains everything. I have only been doing this since they epic came out and have just learned by trying things out. It is very difficult to fully brick your phone. Most the time if you can't get your phone to work you can use Odin (see the thread for more info) to flash back to stock and start over.
Just my two cents but people who are pushed away isn't a bad thing. If they don't know what they are doing they don't need to be doing this. There are several terminology threads on this site...pushing them away means a lot less clutter in the dev threads and else where. Not that I'm saying they shouldn't be here at all, but read read read read....read....and then read some more. And if all else fails bash it with a hammer and turn it in on insurance.
Sent from my SPH-D700 using XDA App
See, its hard to really complain on this because some people are doing some cool stuff on their own effort and time, but I will agree with the OP on this. I agree that only a few lines of descriptions would not only help new users but cut a LOT of threads and posts from people interested but unsure of what do or what something is. And in fairness, it sounds pretty bad when u say that if people aren't that familiar with stuff they shouldn't try it. We don't all know everything and sometimes a little info goes a long way. But that's just my opinion.
Sent from my SPH-D700 using XDA App
Unfortunately if you can't search, read, and understand all the info that is posted you'll have only one option to customize your phone...Sprint ID(which will cost you $$). I've found that none of the processes, such as rooting or flashing kernels, are difficult to perform. In fact sometimes the amount of information already provided becomes confusing to some. I understand the issue devs have with the clutter in this section of the forum. Maybe mods can help by moving topics to the general section and maybe preserving the cleanliness of this section. On the other hand, why all the rage against people asking questions? If I'm not mistaken everyone isn't magically born with all the knowledge required to customize their phone. That's why there are forums like these to provide a community where people seeking knowledge can find it. Personally I find the forums for any piece of hardware from my Directv box to my Epic to be absolutely the most valuable "manual" I can have. Its nice to rely on actual intelligent users for information and not a low paid csr with a script on the other end of the phone.
zetterwing said:
Unfortunately if you can't search, read, and understand all the info that is posted you'll have only one option to customize your phone...Sprint ID(which will cost you $$). I've found that none of the processes, such as rooting or flashing kernels, are difficult to perform. In fact sometimes the amount of information already provided becomes confusing to some. I understand the issue devs have with the clutter in this section of the forum. Maybe mods can help by moving topics to the general section and maybe preserving the cleanliness of this section. On the other hand, why all the rage against people asking questions? If I'm not mistaken everyone isn't magically born with all the knowledge required to customize their phone. That's why there are forums like these to provide a community where people seeking knowledge can find it. Personally I find the forums for any piece of hardware from my Directv box to my Epic to be absolutely the most valuable "manual" I can have. Its nice to rely on actual intelligent users for information and not a low paid csr with a script on the other end of the phone.
Click to expand...
Click to collapse
no problem with the questions, it's just where it's being asked is the problem. People don't think their question will be answered if asked in the general section, or the thread that relates to their problem and decides... I'll just post in the dev section.. there's smart people in that forum!
I've seen it more than once, people don't want to search, or research... or read.. they want to ask a question and have someone answer it directly without having to dig back through posts that don't relate to the question they're asking. Like I said I seen it more than once and the mentality is easy to pick up on.
Don't worry I'm on your side. I've just seen some pretty rough treatment of someone asking a question...in this forum actually(not this thread). They were posting in the wrong place but there's a better way to direct someone to the right place than to berate them. That being said go to the Search and type in "root my phone" without quotes and THIS thread shows up higher in the list than one-click-root. Tends to throw people off the search function. I know it's a faulty way of searching but it's the way people do things. Many forums have problems with their search though. A google search for root Epic 4g has similar problems...the top results link to outdated information and the one click is halfway down the page.
People don't always read the rules of a forum either...it's just human nature. At least the people that make it here are finding the smartest people to answer their questions
Thread moved to General. Please stop flaming the OP.
is there one?
i just know cyanogen and i heard about "blacky´s rom" but could not find it via google.
thx vm
kws
You won't get an answer here.
You really should just Google it.
There is no list. There is no one collection of these MODS.
I don't know if you are referring to MODS, as those coders/hackers that MODify Android, or if you are looking for MODifications to android.
Either way, you are asking for one helluva long ass list if you think one exists.
There are literally thousands of MODifications you can do to an android device.
There literally hundreds of android MODifiers/coders/hackers/developers, etc.
yes indeed,
i ment MODifications of android. but not just modifications but roms.
i just wrote 'mods' because cyanogen call their product 'mod'.
and i did google it. especially 'blacky', about which i heard some time ago.
but i could not find anything. when i google 'android mod' 90% of the results
are about cyanogenmod. the rest is something totally different.
and i think if you would take just the notable (means with a certain amount
of developer activity) roms/mods, the list would not be too long.
but anyway, thanx. i will bite my way through.
have a nice one
kws
Suggestion. Put rom manager on your phone and play
Sent from my EVO with CM7 and honeybread
Compile a list yourself and post it?
It is clear that custom roms are new to you. I only recently flashed my first custom rom but I think I can be more helpful than some people are choosing to be.
I wouldnt get a rom from google. You dont really know its source and often have no one to contact about issues/suggestions. I think the safest option if to go to the subforum on this site that is specific for your phone. Then click on Android Development Forum. In there you will probably have threads for all the major roms such as CyanogenMod, Revolution, LeeDroid, CoreDroid. These are all being constantly improved and you can also report bugs to help future development. Best advantage is they usually have specific instructions for that rom.
Good luck!
I understand, after 2+ years, that ROM development and the forums for the EVO are gonna slow down. Devs are going to move on to other devices, but there is a really disturbing trend here that is irritating the hell out of me.
ROMs used to be released as Aplha's Beta's RC's, final, etc. You could look at the OP and see everything about the ROM. Devs took their time crafting something unique.
Now, I'm seeing these ROMS come out at a rapid pace and I'm not liking it for several reasons.
1) Poorly written OP's that don't even list the Android base version or the kernel, etc.
2) The same ROM with different names and the only real differences are a few 3rd party apps, or a slight theme change.
3) ROMs released as finals, with a ton of bugs. I'm not talking about FFC, Netflix, 4G bugs on ICS/JB ROMS; I'm talking about ROMS with no Wifi, for example. The majority use WiFi. Why the HELL would you release something where one of the most important aspects doesn't even work?? It's like not paying attention to details is suddenly OK
Settings that don't stick. Sounds that don't stick. Constant System Process Errors. These are pre-release errors, and I don't see them getting fixed, because it's become like a race to port every other ROM from every other device and tweak to boot up on the Evo, then letting it go.
I REALLY wish I could take the time and learn how to properly cook up my own ROM. My OCD of paying attention to details would probably make it great.
Hipkat thats the best thing ive heard in weeks,someone finally speaking out about the BS thats being posted now days and its like everyones in a race to see who can come out with the most borked roms,lol,like you said,they are all the same,except the apps and some themeing and half of them cant do that either,i'm sure this isnt meant to be a bashing session,its just getting rediculous with the drama some are causing and all the crappy ass roms being released,some guys do know what their doing,theres been 1 or 2 that i've put out that i shouldnt have,but come on guys at least take your time and try to do it right,only takes a little common sense and effort.If you havent noticed,over half the members and devs have left because of the BS,when i started doing roms,it was fun,nows its just a big joke,lol.
I dont care if anyone gets pissed about this and i'm sure they will,but oh well life goes on,you will eventually get over it.
It's definitely not a bashing, but a call for Devs to take a little more time and do it right
HipKat said:
It's definitely not a bashing, but a call for Devs to take a little more time and do it right
Click to expand...
Click to collapse
I don't Dev, Cook, Build, Port or whatever term is used so I have alot of respect for those that do. With that being said I would also state that I am in complete agreement with you and Diablo.
I look at damned near every topic started in the Dev forum just to see what is being made. I take weeks to look at a new ROM and follow the threads to see what comes of it (with the only exception being Mazda's new CAJB ROM. On that one I went with name recognition and am pleased that I did)
In regards to the mass influx of ROMs I'll say this: If you guys don't take the time to keep up with each item you produce, work on bugs, add new options, answer questions from the users then you'll soon find yourself out of favor. Your reputation here, just like in RL, is something of value. It takes very little to earn trust, respect and loyalty. Most people will always give you the benefit of the doubt. Do something to devalue that trust and it can be nearly impossible to regain.
I think some wisdom can be gleaned by the following quote:
jamieg71 said:
I've seen devs, chefs, hackers, w/e, that make statements like "I do this for myself and just choose to share" or things to that effect. I call BS. I won't speak for anyone else but myself when I say, I do this for the thrill of it, for the challenge, to learn, and to share. I'd be lying if I said I didn't care about d/l numbers or that seeing my thanks meter grow did not give me some juvenalalistic (is that a word?) thrill. The fact is, guys like me doing this stuff get off on it...
Click to expand...
Click to collapse
We know why you do it, and if you want to keep your junkies and not lose your rep, then make sure you take the time to Develop your craft and thereby make a better product for the masses...
Sorry for the rant
Well said, and nice quote from Jamie, who, btw, you notice took a lot of time with Reloaded
HipKat said:
Well said, and nice quote from Jamie, who, btw, you notice took a lot of time with Reloaded
Click to expand...
Click to collapse
...lol, 'nuff said!
I think everyone needs to remember the difference between Development and Port / Theme / Tweak / Mod. That simple labeling would be a start
Over in Evo LTE land, they have finally recognized this distinction by creating entirely separate forums for "HTC EVO 4G LTE Android Development" and "HTC EVO 4G LTE Original Android Development"
One is for tweaks or ports, and the other is for people who actually compile something.
I made a request for the same original dev section but got denied as our device is to old.
I agree that there are a ton of ports and not enough originality or bugs being fixed. What I would like to state us that the op is stating that a lot have some third party apps but that's like calling the kettle black. You yourself have a rerelease of a miui from where all you did was slap your team name in the thread. I believe the original thread still exists. I'm not calling you out at all but at the same time the work that goes into all these ports or mods or what not is a ton. I myself have my rom thread and some new stuff coming out but I don't call people out usually on their stuff unless its a pure kang(meaning an actual using of ur work with out permission) not a duplicate port.
Yeah some of the revs here could put a little more work in and for sure learn to organize their rom thread a whole hell of a lot better but at the same time who else do u see bringing the newest and best to a two year old device.
XDA Moderator
It's not that they have 3rd party apps, all ROMS do, it's that some ROMS are just the same ROM with a few different 3rd party apps, or a slight variation in theming, and I mean real slight, but tbh, my biggest beef was with the OP not even listing what kernel is in the ROM, or if it has A2SD or a way to get it working, or the version of Android it's based on, etc.
Add in bug reports that get ignored or the person posting the report gets demeaned for it.
Mostly, it's just the sloppiness that I see going on over the last few months. Too hasty to release something without really perfecting it first
HipKat said:
It's not that they have 3rd party apps, all ROMS do, it's that some ROMS are just the same ROM with a few different 3rd party apps, or a slight variation in theming, and I mean real slight, but tbh, my biggest beef was with the OP not even listing what kernel is in the ROM, or if it has A2SD or a way to get it working, or the version of Android it's based on, etc.
Add in bug reports that get ignored or the person posting the report gets demeaned for it.
Mostly, it's just the sloppiness that I see going on over the last few months. Too hasty to release something without really perfecting it first
Click to expand...
Click to collapse
I can agree with that there. sloppy op's without all the listings of what is added or taken out and what its running with a q & a section amoung other things.
I feel like we developers and porters alike should make a check list. Every time you want to post something, run through the list and then once everything is there, read again. If it seems like a business proposition (detailed, understandable, provocative and complete) then, that is the right moment to unleash it.
Thats exactly what i do,i make a list in notepad of what i want to do to the rom,then i go through and check it off as i go,wahla,i have a channelog,so to speak,then post it on the thread.Just like in my 4 Kornerz thread..... http://forum.xda-developers.com/showthread.php?t=1612933
Same thing I'm gonna do as I try and update this MIUI GB ROM
What's funny is that the main reason I always hated opening ROM threads is because I'm completely OCD and feel like the posts have to make perfect sense. I try for my thread to make a little bit of sense at least at this point. And I try to keep change logs, bug reports & FAQs up to date.
But then again, I only have one ROM thread in this device section.
----------------------
Current Device: HTC EVO 4G LTE | ROM: toasted-deck CM10 | Kernel: Stock
Kernel should be listed.
a2sd included/not included AND if a specific version is known to work/not work.
Gapps included/not included (you can usually tell from the size of the ROM, but still)
SuperSU vs. Superuser
Wifi and data working/not working
Boot animation audio (can lead to uncomfortable moments when flashing in restrooms, in bed, around family or in TSA security lines--- yes, all personal experiences)
Probably much more...
RootzWiki kinda sorta tried to standardize some of that in OP headers. Would be cool to see that concept expanded in a visually pleasing manner. But, I know people like sprucing up their OP to their liking. Example:
Source: https://github.com/s...mmc-ra-recovery
Mod Type: Recovery Difficulty: Moderate Mod Status: Kang Mod Base: Carrier:
Requires Root: Yes Apply In: Fastboot Optional: Themed Optional: Android Version:
I think ports are great. If the developer is planning on just bringing it over and leaving it alone I think that's fine, but they should be upfront and say "Hey, I did this. Probably won't do any more with it myself, but anyone is welcome to add to it. Otherwise, enjoy."
What I'd really like to see is the people who respond first after an OP + OP reserved do something with that slot besides planting their flag of happening to be online at the right time (e.g. "First. Looks cool!"). They could take the lead, especially for very active developers with many ROMs and threads, to follow that thread and maintain an updated ROM Cheat Sheet/Known Fixes post. How many times have you followed the development of a ROM and things like the new boot animation didn't make it into the next update because the developer forgot. Then people post, "Hey, what happened to the boot ani" five or six times. Then a nice person posts it on Dropbox. Then a few people say other things. Then people repeat the question. Then people point them to the Dropbox link two pages back. Repeat. Repeat. Probably wouldn't matter though since a lot of people never read the OP. They sure wouldn't read that. I'll shut up.
smelkus said:
Kernel should be listed.
a2sd included/not included AND if a specific version is known to work/not work.
Gapps included/not included (you can usually tell from the size of the ROM, but still)
SuperSU vs. Superuser
Wifi and data working/not working
Boot animation audio (can lead to uncomfortable moments when flashing in restrooms, in bed, around family or in TSA security lines--- yes, all personal experiences)
Probably much more...
RootzWiki kinda sorta tried to standardize some of that in OP headers. Would be cool to see that concept expanded in a visually pleasing manner. But, I know people like sprucing up their OP to their liking. Example:
Source: https://github.com/s...mmc-ra-recovery
Mod Type: Recovery Difficulty: Moderate Mod Status: Kang Mod Base: Carrier:
Requires Root: Yes Apply In: Fastboot Optional: Themed Optional: Android Version:
I think ports are great. If the developer is planning on just bringing it over and leaving it alone I think that's fine, but they should be upfront and say "Hey, I did this. Probably won't do any more with it myself, but anyone is welcome to add to it. Otherwise, enjoy."
What I'd really like to see is the people who respond first after an OP + OP reserved do something with that slot besides planting their flag of happening to be online at the right time (e.g. "First. Looks cool!"). They could take the lead, especially for very active developers with many ROMs and threads, to follow that thread and maintain an updated ROM Cheat Sheet/Known Fixes post. How many times have you followed the development of a ROM and things like the new boot animation didn't make it into the next update because the developer forgot. Then people post, "Hey, what happened to the boot ani" five or six times. Then a nice person posts it on Dropbox. Then a few people say other things. Then people repeat the question. Then people point them to the Dropbox link two pages back. Repeat. Repeat. Probably wouldn't matter though since a lot of people never read the OP. They sure wouldn't read that. I'll shut up.
Click to expand...
Click to collapse
LOL, you forgot 'Lather, Rinse...'
Who else clicked the link
While I agree with the OP 100%, I think at the end of the day there is NO rule that states that you need to do all that..... This is for FREE, and therefore we should be happy with we get on our EVO's nowadays..... I wish developers took their time to put a fully detail change log, bug list Q&A's section, but honestly if we don't like the way certain devs handle their threads, then just move on to the next Rom either way I don't develop, and I can figure out most stuff regarding a Rom by myself now, so I'm just thankful for all the roms out for the og EVO.
Edit: what I would like to know is what's going on with all the Rom teams flip flopping, what's up with that? Sorry to go off topic, lol.
Sent from my PC36100 using xda premium
Sorry, but while I appreciate the freeness of the work done and am grateful for it, there should still be enough info to identify exactly what you're getting into.
Perfect example. A lot of ICS/JB ROMS require the patched A2SD file. Good luck finding it. Why not add a link to the OP?? Same with GAPPS
And the date that it was released is much appreciated, although not as critical. The Android version if it's a Sense and/or GB ROM is definitely something that should be there, along with the kernel.
PHE-NOM said:
Edit: what I would like to know is what's going on with all the Rom teams flip flopping, what's up with that? Sorry to go off topic, lol.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Two teams merged. Some people have left teams. I myself left td to not look partial towards a certain group.
XDA Moderator
This rom is now available. I found it during a system-wide search on android file host. Its a new release. I have not tested it, but after testing the Xperia Z5 rom in an earlier post, I'd like to see someone else give this one a shot.
There's rom's out there guys, that we haven't seen on the boards. Lets find them, test them, and get them posted!! The moto community will be grateful! I'm assuming this xperia z5 rom is going to be a huge hit on here.
Once again, I'm new here, thus I can't post links yet. But go to android file host, search osprey and you'll find both the Xperia Z5 and the AOKP.
Those familiar with AOKP/AOSP will probably love this new rom!
Dude.. we're not going to flash a zip without any information.
I could just upload a zip with a script to hard brick your phone and name it Osprey Rom, Would you flash it?
HelpMeruth said:
Dude.. we're not going to flash a zip without any information.
I could just upload a zip with a script to hard brick your phone and name it Osprey Rom, Would you flash it?
Click to expand...
Click to collapse
Yes. I did.
Yes it works.
No, its not for me. Its too vanilla. Basically an AOSP with a few tricks. Its about a 315mb rom when packed. This is a good rom for someone looking to make a "custom" rom themselves using xposed, gravitybox, etc. Nothing more, nothing less.
So I answered your question, and honestly. Your turn:
If I made a nice thread, with a visually pleasing post, some github links, thanked squid for his kernel that I used, gave a few step by step instructions on how to install it, and a fancy little change log......... maybe a gif of a dancing baby. Would that'd be enough for you to click on it? Keep in mind, its the same file I just posted above.... but you're going to download it now that its 'described' and has 'screenshots'. LOL You're about a rom away from a total brick dude. I guess what I'm saying is, what do you look for when you install a new rom? If you're not testing it before you install it, reviewing its code, etc... then you're just going on the words of someone else. BE smart. Try before you buy.
Thank god that Alberto, vastal, boswejla, and flasssssshhhh are good guys and gals. You'd obviously click on anything that had a trusted OP backing it. Be smarter than that. And don't come in here speaking for other people. Its disrespectful to insert your opinion into the minds of others, representing yourself as a spokesman for a "Brick Union"......
If you don't want to try out the rom found, don't. I didn't build it. I'm not getting paid for it. I don't even know who designed it or who ported it.
I just know, that I tested it on my linux VM..... then my Moto G3..... it boots, it works, and I haven't found any security issues with it.
Stick to your 'safe' custom rom. I'll stick to mine. Just trying to expose people to more roms. Nothing more, nothing less.
Thank you for your time and thoughts. Every response keeps this thread visible, and allows more people to experience the things I have.
bubbyj said:
Yes. I did.
Yes it works.
No, its not for me. Its too vanilla. Basically an AOSP with a few tricks. Its about a 315mb rom when packed. This is a good rom for someone looking to make a "custom" rom themselves using xposed, gravitybox, etc. Nothing more, nothing less.
So I answered your question, and honestly. Your turn:
If I made a nice thread, with a visually pleasing post, some github links, thanked squid for his kernel that I used, gave a few step by step instructions on how to install it, and a fancy little change log......... maybe a gif of a dancing baby. Would that'd be enough for you to click on it? Keep in mind, its the same file I just posted above.... but you're going to download it now that its 'described' and has 'screenshots'. LOL You're about a rom away from a total brick dude. I guess what I'm saying is, what do you look for when you install a new rom? If you're not testing it before you install it, reviewing its code, etc... then you're just going on the words of someone else. BE smart. Try before you buy.
Thank god that Alberto, vastal, boswejla, and flasssssshhhh are good guys and gals. You'd obviously click on anything that had a trusted OP backing it. Be smarter than that. And don't come in here speaking for other people. Its disrespectful to insert your opinion into the minds of others, representing yourself as a spokesman for a "Brick Union"......
If you don't want to try out the rom found, don't. I didn't build it. I'm not getting paid for it. I don't even know who designed it or who ported it.
I just know, that I tested it on my linux VM..... then my Moto G3..... it boots, it works, and I haven't found any security issues with it.
Stick to your 'safe' custom rom. I'll stick to mine. Just trying to expose people to more roms. Nothing more, nothing less.
Thank you for your time and thoughts. Every response keeps this thread visible, and allows more people to experience the things I have.
Click to expand...
Click to collapse
Wow dude you got me there, i'm sorry man
bubbyj said:
Yes. I did.
Yes it works.
No, its not for me. Its too vanilla. Basically an AOSP with a few tricks. Its about a 315mb rom when packed.
Click to expand...
Click to collapse
You stated in your first post that you found it but had not tested it, so no, no one would want to test it from that. As for this post, I'm not sure what to make of that rambling, partly incoherent post.
Tel864,
At the moment I found it, I was testing the Xperia z5-g3 rom that I had found. A little later, I tested the AOKP that this thread is based upon. I apologize that I wrote my last post in a way that is difficult to understand for some people (you). But I'll try typing a little slower, for those who read a little slower.
So a brief recap for the reading impaired:
-Yes, I downloaded it.
-Yes, I tested it.
-No, I didn't really like it. Its a vanilla based rom, meant for customization by the end user using xposed and gravity box.
-It is a rather small build, about 315mb downloaded and about 900mb installed.
-I haven't found any rom breaking bugs, but again, I only tested it for about an hour before deciding it wasn't for me. But in all honesty, I knew it wasn't, as I had used AOKP and AOSP rom's in the past. I was merely testing it, so that those who are scared to do so -- would feel better about it.
Here's what I don't understand. Every week someone posts a new project, whether it be a kernel or rom. And every week, it is usually untested until they ask for volunteers. Sometimes the post will even go as far as saying that the it was developed without access to a moto g3, hence the developer themselves hadn't even tested it. Yet, with each new and untested project, person after person says "I'll test it!", "Sign me up!", "Ready when you are!!"
If testing a unknown rom isn't for you, then do us a favor... move on. Just curious though, what rom/kernel do you use? If you're running anything other than stock, then you took a chance when you installed it. The difference however, is that the OP made a 'pretty' and 'informative' initial post that caught your eye like a shiny object. If the same file that I mentioned in the original post, had specs, some graphics, and a few visually pleasing edits..... it wouldn't change anything about the file. It'd just change YOU, and YOUR mind.
So again, why do you trust ANYONE on here? Now... move on.
Interesting... I thought AOKP kind of folded a year or two ago, there haven't been any "official" builds since 2014. The Moto G is not listed as a supported device on their site, any generation of it, must be someones private port.
bubbyj said:
Tel864,
At the moment I found it, I was testing the Xperia z5-g3 rom that I had found. A little later, I tested the AOKP that this thread is based upon. I apologize that I wrote my last post in a way that is difficult to understand for some people (you). But I'll try typing a little slower, for those who read a little slower.
So a brief recap for the reading impaired:
-Yes, I downloaded it.
-Yes, I tested it.
-No, I didn't really like it. Its a vanilla based rom, meant for customization by the end user using xposed and gravity box.
-It is a rather small build, about 315mb downloaded and about 900mb installed.
-I haven't found any rom breaking bugs, but again, I only tested it for about an hour before deciding it wasn't for me. But in all honesty, I knew it wasn't, as I had used AOKP and AOSP rom's in the past. I was merely testing it, so that those who are scared to do so -- would feel better about it.
Here's what I don't understand. Every week someone posts a new project, whether it be a kernel or rom. And every week, it is usually untested until they ask for volunteers. Sometimes the post will even go as far as saying that the it was developed without access to a moto g3, hence the developer themselves hadn't even tested it. Yet, with each new and untested project, person after person says "I'll test it!", "Sign me up!", "Ready when you are!!"
If testing a unknown rom isn't for you, then do us a favor... move on. Just curious though, what rom/kernel do you use? If you're running anything other than stock, then you took a chance when you installed it. The difference however, is that the OP made a 'pretty' and 'informative' initial post that caught your eye like a shiny object. If the same file that I mentioned in the original post, had specs, some graphics, and a few visually pleasing edits..... it wouldn't change anything about the file. It'd just change YOU, and YOUR mind.
So again, why do you trust ANYONE on here? Now... move on.
Click to expand...
Click to collapse
I trust people with a high *thanks* rating, So if Squid or lost101 asks me to test something I don't expect that they want to brick my device. And please this is still Xda the place for the nice people .
I already said sorry for posting that hateful post, We can be friends.
I see you are really into testing new and exciting things, we need those people who will almost flash and test anything to make the experience for the end user as good as possible. Have a nice day and again sorry for the hate.
bubbyj said:
Yes. I did.
Yes it works.
No, its not for me. Its too vanilla. Basically an AOSP with a few tricks. Its about a 315mb rom when packed. This is a good rom for someone looking to make a "custom" rom themselves using xposed, gravitybox, etc. Nothing more, nothing less.
So I answered your question, and honestly. Your turn:
If I made a nice thread, with a visually pleasing post, some github links, thanked squid for his kernel that I used, gave a few step by step instructions on how to install it, and a fancy little change log......... maybe a gif of a dancing baby. Would that'd be enough for you to click on it? Keep in mind, its the same file I just posted above.... but you're going to download it now that its 'described' and has 'screenshots'. LOL You're about a rom away from a total brick dude. I guess what I'm saying is, what do you look for when you install a new rom? If you're not testing it before you install it, reviewing its code, etc... then you're just going on the words of someone else. BE smart. Try before you buy.
Thank god that Alberto, vastal, boswejla, and flasssssshhhh are good guys and gals. You'd obviously click on anything that had a trusted OP backing it. Be smarter than that. And don't come in here speaking for other people. Its disrespectful to insert your opinion into the minds of others, representing yourself as a spokesman for a "Brick Union"......
If you don't want to try out the rom found, don't. I didn't build it. I'm not getting paid for it. I don't even know who designed it or who ported it.
I just know, that I tested it on my linux VM..... then my Moto G3..... it boots, it works, and I haven't found any security issues with it.
Stick to your 'safe' custom rom. I'll stick to mine. Just trying to expose people to more roms. Nothing more, nothing less.
Thank you for your time and thoughts. Every response keeps this thread visible, and allows more people to experience the things I have.
Click to expand...
Click to collapse
Thanks for the tip
However its not booting on my xt1550 stuck @Moto logo
I flashed @squid2's kernel and it booted but my setup wizard kept fcing
So unable to use the ROM..
androidbaba said:
Thanks for the tip
However its not booting on my xt1550 stuck @Moto logo
I flashed @squid2's kernel and it booted but my setup wizard kept fcing
So unable to use the ROM..
Click to expand...
Click to collapse
Just delete setup wizard via twrp
I've opened this thread so that there can be a CLEAN thread for devs to discuss the development of a kernel mod to the Sprint userdebug firmware to allow a hybrid T-mo/Sprint ROM to be built that preserves T-Mo features such a Wi-Fi Calling and VoLTE.
If you are not a dev currently contributing to this particular effort, please refrain from posting in this thread and use the "ALL THINGS ROOT..." thread here for all other root related discussion.
See Post #2 for ORDER OF EVENTS, CURRENT STATUS AND REQUEST FOR HELP.
See Post #3 for a compiled summary of everything we know and have tried as of this moment.
Let me know if there is anything that you think I should add to this post that might help keep this process on track.
I believe this goal to be attainable but it will likely require some teamwork and collective imagination.
YOU CAN DO IT! :good:
Click to expand...
Click to collapse
ORDER OF EVENTS, CURRENT STATUS AND REQUEST FOR HELP:
1. T-Mo Note 7 ships with locked bootloader.
2. freeza manages to supply Sprint Note 7 users with a userdebug firmware that allows root access to be gained on the N930P
3. ethanscooter posts the following info in which he shares his experience that the N930P userdebug flashes normally to the N930T, allows boot and root:
Here's how you do it: Follow the EXACT SAME GUIDE FROM THE SPRINT NOTE 7 SECTION!
Click to expand...
Click to collapse
http://forum.xda-developers.com/spri...alaxy-t3447202
To get LTE to work again just add the T-Mobile APN (not that hard).
Also, you might want to freeze all the "Sprint OMADM" packages with titanium backup once you're rooted (will cause less of a hassle every time you boot. I understand the devs in the "all things root" thread are holding this from you because they want to fix WiFi calling but I think giving you root at all will tie you over for now. Also, I'm having problems downloading the gear VR apps with this so it's related to following this tutorial.
Thank you so much to the developers who made this possible for the Sprint note 7 and for everyone who brought this to the other variants (the T-Mobile note 7 was the easiest imo). It's a little funny to think that this whole time it was this easy and we could've been rooted all along. *If you really need the T-Mobile firmware rooted so you can enjoy wifi calling I've been working on something for a few hours but it's not ready.*
T-Mobile APN: https://bestmvno.com/apn-settings/t-...-apn-settings/
Click to expand...
Click to collapse
5. The loss of WI-Fi Calling and VoLTE as well as other T-Mo specific customizations (Visual Voicemail?) is identified as a major drawback of using the Sprint fw.Edit: Other issues as reported so far: Samsung Apps cannot be updated, any Bluetooth pairings that are made must be re-paired after every reboot 6. A T-Mobile engineering build is being sought to no avail as of yet. This would resolve the primary issue by allowing us to use a T-Mobile FW with the appropriate T-Mobile modifications for WiFi Calling and VoLTE. (Not sure yet what might be causing the issues with Samsung apps and Bluetooth)
7. In the absence of a Tmo eng boot, several devs are organizing to find a solution. The current idea is to dd a modded kernel after flashing the Sprint fw which would (hypothetically) remove the validation checks that prevent flashing modified images. Then build a deodexed T-Mobile build with the modded kernel and su included.
Progress has been somewhat limited up until now. Partially because most devs have been working quietly in their own silos and communicating ideas and knowledge has been a challenge with the previous threads becoming dominated by chatter rather than the facts as they have and are being discovered.
The other hindrance has been that many devs who are keen to work on this issue are without a device such as Rx8Driver and Chainfire.
ATTENTION:
ANYONE THAT IS NOT A DEVELOPER BUT IS LOOKING TO CONTRIBUTE TO THIS EFFORT, PLEASE DONATE TO THE TWO DEVS MENTIONED ABOVE SO THAT THEY CAN HAVE A DEVICE WITH WHICH TO WORK. ALSO, SINCE I KNOW YOU ARE ALL EAGERLY POURING OVER THESE THREADS, KEEP AN EYE OUT FOR OTHER DEVS INTERESTED IN HELPING THAT MAY NEED A DEVICE AND TRY TO HELP THEM GET THEIR HANDS ON ONE.
ANOTHER OTHER WAY TO CONTRIBUTE WOULD, OF COURSE, BE TESTING. BE WARNED THAT NO ONE HERE AT XDA ASSUMES ANY RESPONSIBILITY FOR ANY CODE THAT IS PROVIDED TO TESTERS OR USERS AND BRICKING YOUR DEVICE IS A VERY REAL POSSIBILITY.
THOSE INTERESTED IN TESTING, PLEASE START A SEPARATE THREAD IN DEV SO THAT GUINEA PIGS CAN ADD THEIR NAME TO THE LIST OF WILLING TESTERS. (PLEASE KEEP THAT THREAD SIMPLE AND TO THE POINT)
In Post #3, I will do my best to provide a straight-forward compilation of all we know and have tried as of this moment.
WHAT WE KNOW (OR AT LEAST THINK WE KNOW):
The following is the list of details that we currently know regarding the T-Mobile Samsung Galaxy Note 7 (SM-N930T) and its locked bootloader including concepts, ideas and loosely confirmed information:
FROM CHAINFIRE ON G+ (regarding SU challenges and some work-arounds):
New exploit protections
As isn't uncommon with Samsung, they've built-in some new (and arguably ineffective to actual exploits) protections directly to the kernel code, that cannot be turned off by just modifying the boot image ramdisk.
This time, they've decided to kernel panic in case a 'priviliged' process (uid or gid below or equal to 1000, so this includes root and system processes) creates another process that isn't stored in /system or rootfs. SuperSU itself does this, but so do a great many root apps. Any time this happens: immediate reboot.
I'm not going to elaborate why in my opinion this is a fairly useless protection exploit-wise, but needless to say it is fairly bothersome for the normal root user, which is probably a lot more relevant for the average reader here.
Unfortunately - unlike many of the security features developed by Google - this feature is not easily disabled by modifying initramfs (boot image ramdisk), and requires further trickery to bypass.
Maybe a better bypass is yet to by found, but for the time being, I have resorted to patching the check inside the kernel itself when the systemless SuperSU boot image is created. This prevents the user from needing a custom source-built kernel, but it's questionable how long this hex patch will work. The code that performs this patch is fairly trivial - it may keep working the rest of the Note7's lifetime, or stop working the next update.
In other words, this could end up being resource intensive to support, or not. We don't know yet. We have to wait and see what Samsung is going to do.
Bearer of bad news
We know S and Note development are generally strongly related, so we should assume to see the same 'protections' appear in the S7 sooner or later as well. This is probably the (ugly) way forward.
Workarounds
Aside from the binary/hex patch SuperSU employs (see common/hexpatch inside the ZIP), there are some more ways to get around this protection.
If you're compiling kernels from source, it seems that setting CONFIG_RKP_NS_PROT=n gets rid of these protections. You may want to disable other RKP and TIMA settings as well, but that is the one directly relating to this issue.
This protection also disables itself in recovery mode, so simply copying a boot image with these protections to the recovery partition and rebooting into recovery (which will then just launch Android) will work beautifully as well.
CF-Auto-Root
The test CFARs I have made so far for the Note7 have not worked, so since both TWRP and SuperSU ZIPs are already available for this device, I'm dropping CFAR development until I have a device in-hand.
Click to expand...
Click to collapse
FROM
STILL WORKING ON THIS - NEED TO TAKE A BREAK - FEEL FREE TO BEGIN USING THIS THREAD FOR DEV RELATED DISCUSSION ONLY
REMINDER: See above link to "ALLTHINGS ROOT..." thread for open discussion that is not directly related to solving this issue. Thanks!
Post #4
RESERVED
This is a spectacular thread with solid information and an accurate description of our intentions....i want to state that although i appreciate any efforts made that contribute to obtaining a development device I CANNOT IN GOOD FAITH MAKE ANY PROMISES OF RESULTS NOR CAN I SUPPLY A TIME FRAME SHOULD A DEVICE BECOME AVAILABLE. That said, in time I'll have the device no matter what (assuming i don't just buy an Intl F variant- although that's unlikely since $150 on the barrel head is much more palatable than $900 when i literally just had a baby 4 days ago... plus i work 50hrs a week at my regular job) so i don't want folks to think if they don't contribute I'll never get the device- in fact, honestly if I buy it myself there's even MORE likelihood it'll be a T variant- because i will...
Also, be aware the Chinese model is said to be sd820 as well, and has it's own chances of being unlocked, so when everyone's pitched in to buy myself or Chainfire a device then Samsung releases a Chinese Bootloader we can use that's unlocked and solve all our problems, i don't want a bunch of butt hurt fellow members angry with me because the necessity dried up before i could produce the intended Results. I think @freeza and a few other members who have known me around the forums these past few years will vouch that I'm a Stand Up Dude and truly intend to go as far as reverse engineering the T Bootloader to unlock it. Can I? Idk. Am i knowledgeable enough at this very moment to do it? Probably not. Can i still figure it out? I hope so. Will i brick the device? Good chance. Will i try my best and promise to research and learn whatever is necessary to make it happen? Absolutely.
Those are my terms. If you as an individual reading this don't 100% agree then keep your money in your wallet and wait until i can buy the device myself. That's as straight up as i can be. I'll make another promise. Should anyone donate but the total come up short of obtaining a device before i can on my own, i will leave all the donations in my PayPal and refund everyone's money. Only if enough is gained to buy a device will the money move from PayPal, and then it'll be one transaction to purchase the device using the account. If not enough is collected I'll refund everything that was donated...I'll also agree to prove with screenshots...
So again if you're uncomfortable then DO NOT SEND MONEY.
Thanks to all and i look forward to busting this whole Bootloader open! Or giving it one heck of a try if not!
Sent from my SM-N930F using Tapatalk
Thread moved to General
Thanks for starting something like this gentleman, but as with the bootloader thread, this is not actual development so it belongs in general. Carry on.