I'm due for an upgrade here real soon. Like tomorrow.
I currently own an Eris, and of course have it rooted, custom recovery, blah blah... Anyway, I can certainly survive with only root, as the only reason I used custom ROMs was to improve the garbage stock performance on the thing. So, after doing a few searches of the DX forum, I've found only a couple mentions of Metamorph, which I use extensively in theming my phone, mostly framework-res.apk.
So my question then, is what is the issue with modifying the framework on the Moto? I've seen that most people are just pushing modified .apks through ADB or flashing .zip. Is there a real danger in modifying the .png files and pushing them with Metamorph, or is this just general paranoia about the security of the phone in general? Obviously it's not a signature issue, or you wouldn't be able to boot after pushing the modified .apk
As far as I'm concerned, this is the only thing that has me leaning towards the Incredible right now, despite it's inferior hardware.
Any thoughts/suggestions/explanations would be greatly appreciated.
I wouldn't consider the Inc to have inferior hardware. I can say in my personal usage, it may have even had BETTER preformance... it's OS feels much more prefected. 2.2 may fix that though.
Either way, I've never heard of this fear you speak of. This may have been present before the custom recovery though? Back when you had to sbf if you messed up?
Related
Sorry if this has been asked before, but I did search and found nothing:
I had an Inc. before, and traded to the X for the screen, and physical buttons which I like.
However, as we all know the X blows in comparison to the Inc. in terms of development; so I have to ask since I'm trying to decide what to do:
1) Is the kernel responsible for preventing us from things like notification toggles, notification recent apps, etc... ?
2) When Gingerbread/Ice Cream comes out, are we pretty much at moto's will w/o being able to modify the kernel?
3) What are the chances of seeing CM6 on the X specifically? I'd love to see it, but am no longer hopeful I guess
4) I saw that ccvp (or something like that) was able to hijack moto's init. Is this pretty much dead, or is there still work for it?
I don't really care that birdman stopped dev work on the X (he was responsible for a lot, i know) but will tear if more devs switch to other phones.
Any Ideas?
Again, sorry if all this was already covered.
P.S. I have programming, and Java experience so I WAS thinking to start trying to do some sort of cracking on this myself, but too afraid to brick my only phone
dreamersipaq said:
Sorry if this has been asked before, but I did search and found nothing:
I had an Inc. before, and traded to the X for the screen, and physical buttons which I like.
However, as we all know the X blows in comparison to the Inc. in terms of development; so I have to ask since I'm trying to decide what to do:
1) Is the kernel responsible for preventing us from things like notification toggles, notification recent apps, etc... ?
2) When Gingerbread/Ice Cream comes out, are we pretty much at moto's will w/o being able to modify the kernel?
3) What are the chances of seeing CM6 on the X specifically? I'd love to see it, but am no longer hopeful I guess
4) I saw that ccvp (or something like that) was able to hijack moto's init. Is this pretty much dead, or is there still work for it?
I don't really care that birdman stopped dev work on the X (he was responsible for a lot, i know) but will tear if more devs switch to other phones.
Any Ideas?
Again, sorry if all this was already covered.
P.S. I have programming, and Java experience so I WAS thinking to start trying to do some sort of cracking on this myself, but too afraid to brick my only phone
Click to expand...
Click to collapse
The inability to boot a custom kernel is the one and only roadblock to full custom ROMs like Cyanogenmod. And while I would never say 'never', I would not count on a hack showing up soon. Just go check in on the Milestone people (same bootloader)
Having said that, I would encourage you to go look at what's being done in the dev subforum. Roms like Tranquility, Apex, Zapx and the early Rubix roms are very solid, but removing much of the blur stuff.
Most recently, Fission & Rubix 1.0 are building just about the entire base from AOSP, using almost none of the motorola blur overhead.
Also, hacks have been recently released to overclock the processor.
All in All,there are certainly some limitations imposed by the kernel situation, but there is also still quite a bit happening.
I'd also like to add that it is virtually impossible to truly brick the DX now since the official OTA 2.2 SBF has been leaked.
The only thing we don't have on the DX is custom kernels. However, with all we do have at our disposal, I don't really care at all. I can fully theme, overclock, use all the root apps, etc...
I don't know whether or not the DX will get Gingerbread. It certainly is a possibility. However, I will be upgrading to the newer device designed for Gingerbread. When I say this, I mean a phone that's display can do 1024 by 720 resolution. Also, many of the top-end upcoming phones are going to have autostereoscopic 3D displays. Did I mention that many Gingerbread phones will have dual-core CPUs and GPUs with graphics which rival the PS3 and xBox 360? Well, they will
Remember, Verizon is going to probably do the same thing they did with the DX. They will let people get the 2-year account renewal price for the best upcoming phone even if you just renewed your 2-year contract this year. If someone renewed their contract with the DX and got it for $199, they will be able to do the same thing in December/January with the top-end Gingerbread phone most likely for $199 too
Im just curious if anyone can give me any insite on how you like modding the dx? I'm from t-mobile "my touch slide" and I love modding and stuff. I've done light research and it seems there is not much offered for this phone. Could anyone explain that to me for a reason? Anyone give me any insite about this phone?
I just ordered a new plan with verizon and I can always send the phone back but it looks soooo sweet with all of the features but I'm more a guy that likes to change his phone. thanks for any help
Look around that is what this forum is for. Start here http://forum.xda-developers.com/forumdisplay.php?f=691, that is all custom stuff for the phone. You will so much if you just start looking and reading. Many of the questions you have will have already been answered. I have only have my phone a few weeks and have already tried alot of stuff. Have fun.
Simple explanation - the Droid X (along with Droid 2, Pro, and 2 Global) have a locked bootloader. Because of this, we can't install custom kernals. Therefore we are stuck using Motorola's Blur kernal. Hopefully the bootloader will be cracked soon, then we can see ROMs such as Cyanogen Mod come to be.
But just because we don't have a cracked bootloader doesn't mean we can't have fun. We're still rooted, and we can install roms, we can overclock (although not as good as if we had custom kernels), dozens of themes, etc.
rooted vs unlock bootloader
Since the question is already set.
Can someone explain if I'm right or wrong?
I think that someone had unlocked the "bootloader"
but with the new Motorola official update froyo 2.2.1
I believe it is locked again the Bootloader.
So maybe I totally misunderstand it but changing the Kernel only make some kind of performance improvement (sometimes this improvements are only notice for the expert people, not to regular people who don't get his phone to the extreme of performance).
So if it is actually "rooted" the DroidX, it means that I can only change themes and put&take off some apps and that is, or what else?
I guess time ago I used the sentence "Flash a ROM" when I actually replace/change the system file or kernel, and use the word Theme/Mod when only change some UI and apps, so to "Rooted" is not as flashing a ROM?
I'm correct or something more deep is missing in my idea??
Sorry but everybody start being a noob (in Android) before get the knowledge.
Thanks in advance Sa6r0s0 :thumbright:
I for one like MotoBlur, it looks and feels great and is appealing and easy to use. I love the enhancements included in BlurHome2, and I'd love to see it on the Droid X.
Now, my Android "developing" hasn't gone farther than theming, so I don't even know where to start if I wanted to port this over.
My question is, is this even possible? If so, how would I go about doing so?
As far as I've heard (I'm no developer) this isn't feasible because of the elements of the blur framework that need to be in place...that also can't be ported without causing the phone not to boot.
This MAY have potential in 2nd-init, however?
I've no idea.
Jubakuba said:
As far as I've heard (I'm no developer) this isn't feasible because of the elements of the blur framework that need to be in place...that also can't be ported without causing the phone not to boot.
This MAY have potential in 2nd-init, however?
I've no idea.
Click to expand...
Click to collapse
Well I've heard the same thing. I figured it'd be easier to do this on a Droid X (rather that a non-moto phone) due to Blur already being present. BlurHome2 depends on updated frameworks found in newer Droids, so when/if I get this started, I'll have to start porting the newer frameworks to the DX (which may not even be possible).
Only one way to try
It is possible (although 2nd init would have to be used), but would be very difficult as the code for Blur isn't open source.
Sent from my DROIDX using XDA App
shobon said:
I for one like MotoBlur, it looks and feels great and is appealing and easy to use. I love the enhancements included in BlurHome2, and I'd love to see it on the Droid X.
Now, my Android "developing" hasn't gone farther than theming, so I don't even know where to start if I wanted to port this over.
My question is, is this even possible? If so, how would I go about doing so?
Click to expand...
Click to collapse
You have to go to the droid x 605 update deodexed and apply the droid 3 theme then you put the lib files for BlurHome2.apk to /system/lib after that you change the permissions of them, then you put the BlurHome2.apk to /system/app/BlurHome2.apk and change the permissions to rw-r-r- and if you want you can put the new blurcamera into the system
Hey guys, just a quick question. Please please excuse me for I am definitely a noob, but I've done some research about rooting and what it offers yet I still don't know how to use it. It feels much like learning how to drive a stick... understanding in theory, but difficult in application until practice. My note 3 is rooted, but I still have no idea what and how much I can do from here. Not to mention, while I'm doing research and trying to educate myself, there are some names and terms I do not understand. Anyway, let me just write some of the questions I have in a list:
1) Cyanogenmod. Is it available for verizon note 3 running 4.3? I keep getting search results that there are while the cyanogenmod website itself doesn't offer it? I also got a Nexus 7 to try to expand my knowledge in this field, and it does have cyanogenmod installed. Now, to my understanding, it runs side by side with the Android OS while it basically strips the device's bloatware, giving you the pure, simple, raw experience of Android OS. If I were to install cyanogenmod to the note 3, how would it affect the camera functions and the s pen functions? The reason why I ask about the camera is because using my Nexus's camera and looking at some youtube videos of note 2's with cyanogenmod, it seems like it would actually be a downgrade from the note 3's stock camera. And as far as the S pen goes, I've realized that I would lose the action notes, s notes, and sketchbook for galaxy apps, wouldn't I? How could I go around that?
2) Flashing ROMS. What exactly does this do? All I can find is that it allows me to customize my phone, but I don't seem to understand to what extent.
3) Kernels. What are these?
Lol, so sorry for such basic questions. But I would really really appreciate your patience and information!
CyanogenMod is unofficially available for the Note 3. Not everything works. CyanogenMod is a ROM that changes the software on the phone. It's a more customized version of Android, and very close to "stock". If you use CyanogenMod however, you will lose your S-Pen and it's features, along with all of the other TouchWiz features of the phone (gestures, split screen, etc.). The S-pen will act as a basic mouse pointer. CyanogenMod is not pure AOSP, it's quite far from it. It's similar, but very different from a pure Google experience. It's really a beast of it's own in my opinion, and is now a stand alone company that will seek to profit off of the ROM (likely by coming standard on some devices). That's not to say it isn't good, I run it on most of my other devices but on the Note 3, without the S-Pen it's just a big phone.
ROM's are customized versions of Android typically created by a developer or group of developers. The features of each ROM will change. A 4.3 TouchWiz rom might remove all of the carrier bloat (applications not likely used, but run in the background and offer little no actual use to anyone). They'll also provide enhancements and tweaks that make life a little easier like a quick-access flashlight tied to your volume up button, or the ability to remove certain icons from the notification panel, a batter percentage indicator in the notification panel, removing the exchange security permissions, or just general speed improvements over the factory settings. There are many advantages to a ROM and once you use them you'll likely never go back to stock. The ROM features are typically listed in the ROM's topic.
There are many ROM's out there for many different devices, so make sure you only install one that is made for your phone. You'll also hear about AOSP ROM's, these are stock or close-to-stock versions of Android, typically found on Nexus devices. The way Google intended Android to be used.
Android uses a Linux Kernal. It's a customized version of Linux. It's the base operating system behind Android. Similar to ROM's, different kernals can offer different levels of customization, however they won't be as prevalent as a ROM since they deal more with the core of the operating system. The Kernal will manage the drivers for all the different components of the phone, like your radios (how you receive a phone signal), your sensors, camera, CPU, etc. Be especially careful when changing Kernals, it can drastically affect your phone, and possibly permanently.
I'll put in the caveat that this is my understanding, and may not be 100% accurate. People are welcome to correct my mistakes and misunderstandings I may have =)
I hope you find it helpful!
Thank you for your response and information!
Okay, so I guess Cyanogenmod for the Note 3 is not an option for me since I enjoy using my S pen (I mean, why else would I have gotten the phone in the first place haha)
Could you direct me to some useful ROMs or recommend me some? The thing is, I had the Motorola Droid as my first smartphone and never really got into rooting or anything, and when I got the iPhone 4s, that's when I started learning about jailbreaking and got pretty good at it too. Now that I'm back to Android and learning about root, I've realized just how.. simple and basic jailbreaking is compared to rooting. So, would these ROMs be similar to tweaks you can get from the Cydia store in, let's say, behavior of the phone?
I don't think I would want to mess with kernels for a long while either, not until I get more acquainted with rooting in general.
ch0i said:
Thank you for your response and information!
Okay, so I guess Cyanogenmod for the Note 3 is not an option for me since I enjoy using my S pen (I mean, why else would I have gotten the phone in the first place haha)
Could you direct me to some useful ROMs or recommend me some? The thing is, I had the Motorola Droid as my first smartphone and never really got into rooting or anything, and when I got the iPhone 4s, that's when I started learning about jailbreaking and got pretty good at it too. Now that I'm back to Android and learning about root, I've realized just how.. simple and basic jailbreaking is compared to rooting. So, would these ROMs be similar to tweaks you can get from the Cydia store in, let's say, behavior of the phone?
I don't think I would want to mess with kernels for a long while either, not until I get more acquainted with rooting in general.
Click to expand...
Click to collapse
Well first thing you need is safestrap so you can actually flash a ROM link here
This allows you to create limited size slots to flash a ROM to without effecting the stock ROM. There is a way around the size limitation of the slots, but I wouldn't worry about that yet. Just get a feel for it first before you risk bricking.
As for a ROM, head on over to the android development section and pick one. They all have great descriptions of what they have and what they don't. Personally I run hyperdrive and it makes a great daily driver. Still has enough of the original Samsung stuff to look like a Note 3 but allows you to tweak it much further. There are plenty others, and that's the beauty of safestrap, flash to your heart a content until you find one you like.
Kernals aren't something to worry about yet because the boot loader is still locked, limiting our ability to flash a kernal or a custom recovery at that. Unless something has changed that is... Has it? Did it get unlocked while I was asleep.
I you ever get stuck, search then ask. You might also want to read about ODIN here. since you're already rooted some of this doesn't pertain to you, but is still a good read as ODIN will help you recover from some problems.
Hope that helped.
blksprk said:
Well first thing you need is safestrap so you can actually flash a ROM link here
This allows you to create limited size slots to flash a ROM to without effecting the stock ROM. There is a way around the size limitation of the slots, but I wouldn't worry about that yet. Just get a feel for it first before you risk bricking.
As for a ROM, head on over to the android development section and pick one. They all have great descriptions of what they have and what they don't. Personally I run hyperdrive and it makes a great daily driver. Still has enough of the original Samsung stuff to look like a Note 3 but allows you to tweak it much further. There are plenty others, and that's the beauty of safestrap, flash to your heart a content until you find one you like.
Kernals aren't something to worry about yet because the boot loader is still locked, limiting our ability to flash a kernal or a custom recovery at that. Unless something has changed that is... Has it? Did it get unlocked while I was asleep.
I you ever get stuck, search then ask. You might also want to read about ODIN here. since you're already rooted some of this doesn't pertain to you, but is still a good read as ODIN will help you recover from some problems.
Hope that helped.
Click to expand...
Click to collapse
It did! Thank you very much!
ch0i said:
It did! Thank you very much!
Click to expand...
Click to collapse
The only option with Safestrap and therefore on newer Verizon Note 3's is a ROM based on stock, so Cyanogenmod isn't an option at all.
I would consider Hyperdrive. Enhanced app windowing options, Xposed framework to get rid of earphone hearing damage warning and never ending reminder about how to clear default apps and tons of little customizations. Getting rid of boot sound is reason enough for me.
Other things on your checklist whether you get a custom ROM or not is Adaware, which you can download on xda to block ads. Need Titanium Backup to back up apps with data, something you can't do without root and very useful when switching ROMs or phones. Lots of other useful tools like Root Explorer on Google Play. If you stick with your stock ROM, do the mod to allow free tethering for Wi-Fi.
Since you like your S Pen, you need Pen Window Manager, available on Play to choose for yourself which apps can run in a pen window. That was one of the big reasons I wanted to root this phone.
By the way, once you find a ROM you like, it's best to nandroid back it up, backup the stock ROM for safety, then restore your custom ROM to the Safestrap stock slot. The ROM 1-4 slots have limited storage so not great long term solution if you have a lot of apps, etc.
Sent from my SM-N900V using Tapatalk
Hey all,
First off let me just say great work to everyone involved with rooting this now "ancient" phone, especially klabit87 and jrkruse. Additionally, I do not mean to be ungrateful with this post, nor suggest that rooting a phone is easy, especially one with a locked bootloader, or that the users here are entitled to such a feature.
With that out of the way....
I haven't looked into rooting this phone EVER until now. Haven't even peaked at XDA or Googled anything, I didn't even know it was possible until yesterday. I've re-ROMed all my previous phones but was actually satisfied with the stock S7 experience other than a Launcher swap and dealing with the always laggy Google maps. Well recently I got a new car and got fed up with the obnoxious list/action limit that Android Auto has as the voice search can be quite unreliable, the letter search is somewhat bugged on the media player I use, and in the end all it does is encourage people to just use their phone to change songs/settings and send messages, thereby completely failing at its goal of being safer. So, I really wanted to get Xposed installed to use the module that makes AA a lot more usable; however, now that I've looked back into the scene a bit, I'm not so sure I want to move forward.
To preface my question: Every Android device I've had before was essentially either rootable or not and ultimately banked on a security exploit that was eventually found. There were never really any concerns about major issues unless you were changing ROMs, kernels, or testing major CPU behavior changes. Just rooting itself was almost always issue free other than a small bug or two or the need to reapply at reboot.
From what I gather, it seems to me that they only way currently to gain root privileges on this device is to install this ENG kernel that's talked about in a lot of more recent posts. Is it truly the case that someone had to write a kernel from scratch that was pre-rooted and as of right now there is no way to root the device as it is stock? Is it that the only known exploit is how to flash another kernel, and the stock kernel is still locked up tight? It sucks that the current root seems so unstable/slow. I know there are a plethora of fixes but there really is no one major fix (other than potentially reflashing the stock bootloader that for some reason seems to work), and its a matter of installing a boat load of CPU and resource management tweaks and even then the performance/battery life isn't quite stock. Additionally it seems like its definitely a YMMV kind of thing as some users seem to still have significant battery drain or slowness/heat even after trying tons of fixes.
Since I am just now getting familiar with the "homebrew" the phone I've had for 3+ years and know nothing about the work that's been done, I genuinely just want to know the technical implications that got in the way of a cleaner root and why the current root method is stuck as sort of a work-around so to speak. The people that manage these breakthroughs rarely post about the process they went through unless its pertinent to a guide on how to root, so I was just curious why the root for this device is in the current state it is.
I would really like to root my Edge so I can be done with the AA nonsense but after just getting a new battery put in I really don't want to go through ****ty battery life again haha.
Thanks to all who weigh in.
Verizon requires most if not all manufacturers to lock the bootloaders. This is also Samsung choice as well. The T-mobile S7/edge and newer have locked bootloaders as well. Difference is T-mobile leaves it up to the OEMs whether they want to lock it or not. With some U.S. businesses and enterprises using Samsung Galaxy devices. They focus on being "enterprise ready" which makes sense from a business standpoint.
Believe it or not, Samsung used to be developer friendly when the S II came out. They even gave away Galaxy S2 devices to some XDA devs.
So, if you want a Samsung device with an unlock able bootloader. Get one that has an Exynos SoC or the Chinese Snapdragon variant.