Ok so I picked up my Droid X about a month ago and haven't been able to put this thing down, I never thought about rooting it because it did everything I needed/wanted it to do, then one day I log into my car forum and all the OT guys are posting cool print screen's of their phones. I was intrigued, so I rooted my phone and have been trying to figure out a few things but I'm not really up on the terminology and/or logic behind doing certain things. I would greatly appreciate any help in regards to explaining the following:
1) Rooting - Takes off restrictions on the phone so that developer apps can be installed... Is there more to this or is that pretty much it?
2) Flashing - I see this term often but I'm not sure what it is exactly, I tried installing a theme once and the directions said to flash something somewhere and looked at it the same way my dog looks at me while I'm working out at home.. lol
3) ROM - !?
4) apk's - What are they, what do they do, and how do you install them!?
5) Installing themes - I'm thinking has to do with all of the above...
6) Locating and moving downloaded content...
7) How do all of these things tie together? I'm completely clueless as to what does what on the phone and would like to become as knowledgeable as I was when the iPhone first came out and I figured out how to jailbreak/unlock it...
As a reward for your time and effort I leave you Final Fantasy VII fan's with a cool wallpaper I found at work today.. Thanks for any/all input and again, your time is most appreciated!!
Initial GT3 said:
Ok so I picked up my Droid X about a month ago and haven't been able to put this thing down, I never thought about rooting it because it did everything I needed/wanted it to do, then one day I log into my car forum and all the OT guys are posting cool print screen's of their phones. I was intrigued, so I rooted my phone and have been trying to figure out a few things but I'm not really up on the terminology and/or logic behind doing certain things. I would greatly appreciate any help in regards to explaining the following:
1) Rooting - Takes off restrictions on the phone so that developer apps can be installed... Is there more to this or is that pretty much it?
2) Flashing - I see this term often but I'm not sure what it is exactly, I tried installing a theme once and the directions said to flash something somewhere and looked at it the same way my dog looks at me while I'm working out at home.. lol
3) ROM - !?
4) apk's - What are they, what do they do, and how do you install them!?
5) Installing themes - I'm thinking has to do with all of the above...
6) Locating and moving downloaded content...
7) How do all of these things tie together? I'm completely clueless as to what does what on the phone and would like to become as knowledgeable as I was when the iPhone first came out and I figured out how to jailbreak/unlock it...
As a reward for your time and effort I leave you Final Fantasy VII fan's with a cool wallpaper I found at work today.. Thanks for any/all input and again, your time is most appreciated!!
Click to expand...
Click to collapse
First off- that is a lot to bite off as an opener. lol. I have to get in a minute- plus I am a newb as well but here a couple of things...
1) You sound pretty on track. Root gives you access to more options with your phone. It also voids your warranty.
2) Flashing. A term used loosely. Normally it is used in conjunction with "flashing a rom". It simply means to install something (basically).
3) Rom. It is the image (not in the photo-graphical sense) that is embedded/burned on your phones hard drive with all the information of your operating system. For instance: you are on the stock 2.2 ota "rom". But you could "flash" the new "AOSP rom" that was just released. That means you would be removing the factory image that came on your phone and replacing it with a modified image. Theme's and .apk's -those are not "burned" into the phone. If you do a factory reset- those will be wiped. The rom image stays put. If you flash from 2.2 ota to AOSP and then did a factory reset- you would not return to the original state your phone came from Motorola bc that image is completely removed and replaced by the new image you flash. Instead you would return to a clean AOSP.
4) .apk's - .apk is simply the name of the file extension used for android applications. I came from Windows Mobile and they were called .cabs. So any app can be referred to as an .apk. You can download an apk from XDA, place it on your sdcard, tap the file, and i think you will be prompted with "do you want to install" (some where along those lines). There is a setting in the "Settings" that allows you to install 3rd party (non-market) .apk's.
5)Installing themes. This refers to modifying the images (and this time I do mean in the graphic sense) of certain .apk's and other whatchamajiggies. You can install a simple theme that just changes your lockscreen, or you can install a huge theme that changes almost every part of every image so the entire phone looks similar. Here is the tricky part about using themes- your phone has to be deodexed.
deodexed. When you get your phone all of the system files come with a few different parts to them. One of those parts is an odexed file. Apparently the theme building types do not like working with these files so they run this process called de-odexing in which all of the system files are somehow manipulated in a way where they no longer need their odex file. So you end up "de-odexed". There is a program called "xultimate 2.2" that enables regular folk like you and me to deodex our phones. I tried running it yesterday and it errored out on me. So I used another method that worked fine. There are some threads on here about deodexing- if you want themes you will have to do it.
6) locating and moving downloaded content. When you have root you can get Root Explorer from the market. I am sure there are other good file exploreres- but I can't speak to them- I use Root Explorer. As far as locating downloaded content- whenever I download something from my phone, it always (normally) goes to /sdcard/downloads. If it is not there, I guess you just do a search for it. If you want to move it- long press the item, copy, move.
And you will need to google "ADB" (android device bridge). Many of these activities will require the use of ADB. You plug in your phone through USB (make sure phone settings are set to "USB debugging") and... well there is just way to much on this one. Google this one and you will find a lot of stuff- or search it here on XDA
have a great weekend. got to go.
Not being stranger to ROM changing, after buying my Xperia Z3 Compact, I went straight for the bootloader unlock (following CM official wiki page). I did not backup my TA partition and therefore, my DRM keys are gone forever. Such is life. But I am not giving up...
I installed ResurrectionRemix (AOSP/CM based) and I am quite happy with it, but I thought it would be nice to have the original stock Sony camera functionality.
What I managed to do so far:
Mod the RR framework using this guide, which means:
- get /system/framework/framework.jar from your phone
- unpack classes.dex using your favorite archive tool
- decompile the classes.dex using Rom Tools (direct download link)
- overwrite the files with the ones from the linked guide
- compile it back to new classes.dex
- pack the modded classes.dex to the framework.jar
- copy the new framework.jar to /system
Install Sony Stock camera using this guide:
- flash the stock camera port
- flash panorama sweep fix
- flash face detection fix
Deactivate the standard CM camera apps
- including CameraWorkaround, Camera2, etc.
Clear data of all camera-related apps
- if you don't, the Sony Stock camera might crash, I checked logcat and found out it was because of SQLite DB version mismatch that the CM camera created and the Sony Stock camera couldn't use.
Then I found this thread:
[Z~Z5 Series][EXRxTHS]SONY DRM FUNCTION RESTORATION FOR UB DEVICE | Z3 lines support!
If what is claimed there really works, then the Sony proprietary image processing can be enabled even without the DRM keys. That basically means that the DRM keys are only used as verification, but the software performing the processing is indeed in the ROM.
The thread itself states that it is only for stock-based ROMs as AOSP/CM ROMs don't have the functionality in the first place. I might be wrong, but I believe that by modifying my framework I have imported some of these functionalities back into the phone.
If it was possible to port some parts, it should be possible to port more of them, including the image processing.
So I am starting this thread to track progress in this and to find the last piece of the puzzle - to bridge the gap between having Stock Camera framework and app on AOSP/CM ROM and the DRM patch, which probably patches the DRM-checking core to always return "keys are fine" even if they are missing,
I am interested in this as well, because I always prefer using AOSP than stock rom, be it on Sony device, Samsung, whatever. But lack of proper camera is keeping me away, mainly the reversed fish eye effect.
Have you experienced some crashes with that setup? I remember that people reported various crashes with that port.
I would help, but I have zero knowledge about coding and porting and everything associated with it unfortunately.
no crashes for me like this. but i have uninstalled most of the "fancy effects" apps in the bundle. so i got superauto, manual, livecast, some fx and stickers and thats about it
Hey, I'm also interessted in your work. How do you handle updates with this mod?
curlyboi said:
no crashes for me like this. but i have uninstalled most of the "fancy effects" apps in the bundle. so i got superauto, manual, livecast, some fx and stickers and thats about it
Click to expand...
Click to collapse
I don't need fancy stuff either, I would keep 4k video and Slow motion video out of all those and that's it. So I guess I could try some AOSP if it works on your side as you say
Some questions though. Do you think I can use zezadas' unlocked camera app with this port? It's just a matter of replacing apk only, nothing else.
And which version of RR do you use, based on CM13 or CM12.1?
It's RR based on 12.1.
And I don't plan on updating too often... Maybe once some very important fix comes out, but before that it's not necessary. I customize everything so every ROM reinstall is so much pain in the ass for me, hours going thru all the 200 apps and setting everything
Need HELP @ Note 3 ( SM-N9002 / SM-N9009 ) SIM2 Call Audio/Mic Routing & MagMa-NX ROM
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out
I think I figured something. Everytime I attempt to make a phone call on this, I get to choose from which sim card should I dial, #1 or #2 , but what I have noticed now is that I am being asked "SIM1" or "Slot2" ... SLOT 2 I thought? That may be the reason that audio routing doesnt work well for this... tried searching build.prop but this string is not there and I just dont know where to search for this string to get this fixed, anybody can chime in?
Thanks
Did you figure it out ? As i have the same problem with the same rom in addition that when i call anyone and he is on a call i don't get notified with " call waiting
Mr.Ultimate said:
Got my hands on this one beautiful piece of Samsung Galaxy Note3 SM-N9002 Dual-Sim, and it had this odd version of Chinese samsung rom on it, as it comes from factory, half apps installed that comes with it was in Chinese and had no play store etc and was on 4.xx android, so I went and did my research, found working TWRP, managed to install it OK, then tried few beautiful ROM versions and found MagMa-NX (note7 ported ROM) works wonderfully well, zero crashes etc etc and it also has kernel support for SM-N9002 during installation which I chose to use, all features work 100% and everything works ok, all but SIM#2 call audio.
I mean, I have signal on both sim cards simultaneously OK, I can make and receive calls and all would seem ok, but when dialed to or from SIM#2 there is no audio coming out from earpiece or loudspeaker and mic dont seem to activate as even if I try to record call which feels like muted for both caller and receiver ends, call audio recorder while recording does not pick up any sound trough phone microphones, so I think its something to do with settings in some file not done right or else I dont know what I could be doing wrong.
both sim cards worked 100% ok before ROM flash, but now I'm lost because I cant even flash back to old stock rom, and yes I have gathered original android 4.xx rom but it fails flashing via ODIN every time, so my best bet is on doing some DIY on current MagMa-NX note7 port rom... I wonder if there are any fellows who I could buy the paypal-beer for great help sorting me out on this DIY project? Please PM me or post here if you feel like you could collaborate in resolving this dilemma for me... would highly appreciate folks
I will keep an eye out
Click to expand...
Click to collapse
Which CSC did you choose?
I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!
Mr.Ultimate said:
I did not figure anything out guys... as I was trying to get this working, I tried every CSC option possible... none worked. Which should have been the one that's working for this models?
in fact Im thinking of selling this beauty of note3, its almost new... in case someone interested I have it... because I would love note7 port rom on this, and nothing else... PS I could live with it being just single-sim option, it works but not perfect as sim #2 is useless then... signal there and texts only works for it as described above...
at the moment its on stock adroid 5.0 and its all 100% ok and fine, flawless, but its boring!
Click to expand...
Click to collapse
Well, i know that mixer paths are different on single sim and dual sim phones.
Can you extract from stock rom the file "/system/etc/mixer_paths.xml" and overwrite the one in custom rom ?
I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?
Mr.Ultimate said:
I think I tried something similar if not exact with no success .. let me repeat the process just in case...
PS also, I will try and dump both versions of these files. Is there anything else I may need to dump from stock rom 5.0 rom?
Click to expand...
Click to collapse
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.
zlazaar said:
There are some specific binaries and libs, but i'm pretty sure magma rom already inject them during flash when you select n9002 as variant.
Dumping the CSC folder is a good idea too.
Click to expand...
Click to collapse
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks
Mr.Ultimate said:
cool, which is the csc folder to be exact? will there should there be any conflicts between 5.0 stock android and 6.0 in magma rom when doing CSC trick?
thanks
Click to expand...
Click to collapse
Path : /system/csc
Indeed, conflits may happen. But just dump it and let we examine it.
Ok here is what I managed to try, I backed up stock rom android 5.0 all working state mixer files from etc dir, then flashed magma rom again, backed up those same files for restoration to working state, replaced files with ones extracted while on 5.0 stock android, reboot device, no sound whatsoever, phone wont even buzz keypad dialtones or connect dial phonecalls just hangs. So I went and restored back original magmanx rom mixer files, reboot, but still no success... so now I have just finished restoring 5.0 again, will dump csc folder and share with you. will also need to charge my battery a bit because @ 30% cant expect much to happen when flashing magma nx...
Thanks for the help amigo!!!
Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856
Mr.Ultimate said:
Alright, tried merging csc from 5.0 to magmanx 6.0, no luck. then tried after this to merge mixer file from 5.0 to magmanx 6.0 , no luck, back at square1....
files attatched both versions... obviously something wasnt done right from looong time ago and had never been reported, been forgotten... in regards of 9002 users..
https://forum.xda-developers.com/attachment.php?attachmentid=4154927&stc=1&d=1495202856
Click to expand...
Click to collapse
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).
zlazaar said:
Indeed, the mixer_paths of TW6 is missing the whole part concerning "cp2" (second sim).
I'm not a reel dev but i tried to add missing parts from TW5.
Can you please try the attached mixer_paths on magma ? (don't touch csc).
Click to expand...
Click to collapse
amazing, will try in few mins
no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!
Mr.Ultimate said:
no success, exact same fail of global audio post merging files... any more ideas... ? really appreciate your effort man, really do!
Click to expand...
Click to collapse
Did you checked correct permissions before reboot ?
I'm afraid the problem is deeper than mixer paths.
I'll try to digg more.
I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway
Mr.Ultimate said:
I enable root explorer in third party file manage, grant permission, copy file from sd card to system/etc, prompt to overwrite -grant, overwrite complete, power off phone from power-button menu, power on, done. is this bad/incorrect procedure? magmanx has root from stock, when I navigate root dir I get access grant prompt, I grant it and then I can modify whatever.
please let me know what else I could do? maybe there are specific files I could look in to dump out of working 5.0 rom? Thanks!
or maybe just directory content filenames that could/would make sense by their name etc?
its weird, I think its something to do with the kernel itself... maybe Im wrong, but I dont think 9002/9008 kernels were ever made properly to be tested thus the errors... I cant even find any other kernels for 9002 other than included in magmanx and it aint working well anyway
Click to expand...
Click to collapse
The file "mixer_paths.xml" must have permission set to 0644 (like other files in /system/etc directory).
And try darklord Kernel.
6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go
Mr.Ultimate said:
6044 is as per read/write permissions for user enabled, as per this link http://permissions-calculator.org/decode/0644/ , I assume these permissions will auto set after moving replacing file do they not?
Where do I obtain the darklord kernel? I was pretty sure it comes with it... let me re-do the rom and take some snips as I go
Click to expand...
Click to collapse
Sorry i just noticed you already have darklord kernel.
And set permission like other files in this directory (if not already done by your file manager).