Related
I hate to make a thread on this but would like to get started soon with learning how to root roms and add the kernel for multitouch and tethering. This is more for my personal use since I just want a stock rom with all the root benefits like jf use to and theses are the questions I have.
1. Will I have to take the update.zip file and extract everything and modify it then resign and I'm done?
2. I read some info on adding busybox and root which seem easy but when I run the chmod command and such everything will be through adb and the files will be on my pc so do I just make sure its all in the right directory and file path?
3. Where are the wallpapers stored in builds along with animations I will be looking into the framwork/framework-res.apk later but still curious
4. The modified kernel for tethering and multitouch is located where along with the market.db file?
5. What is meta.inf and how easy is it to make the cpu 528mhz standard also not sure what BFS and ASOP are haven't been keeping up.
P.S. I would really appreciate some help on this and I don't mind reading if this information is somewhere else so please provide a link and as always gotta show love to those who started this like JF, Hakuro, Cyanogen, Drizzy, and many more like daproy and kornub did a lot of helping.
I hate to make a thread on this
Click to expand...
Click to collapse
You mean you hate starting threads in the correct place?
Thats a fine line here. Although it is a question, it is specifically a development question. Its not a which rom do i choose?
Although android is "open source" these people dont give a **** about people trying to learn how to develop. They will pull the google line or something.
yeah me 2
Trying 2 learn
Im a noob, so I can only answer two of thosew questions
1. Anytime you modify your update.zip you will have to resign before trying to flash it onyour device.
5b. BFS: Brain **** (simple) Scheduler, something to do with the priority of running proccesses or something http://en.wikipedia.org/wiki/Brain_Fuck_Scheduler. AOSP stands for Android Open Software Project, which i believe is just googles standard rom really (but I may be wrong)
I recommend you try out this rom though, kind of like JF but for Donut http://forum.xda-developers.com/showthread.php?t=538456
Very Sorry, double post
Thanks! I'm actually using that rom and its what has me so interested in this cause I hate having to flash another update.zip to get the full root benefits when JF just made everything available in one nice package but looks like I will just have to go through trial an error unless I get some more feedback cause switching between cyan 4.1.11.1 and JF1..51 is killing me and taking up space on my card.
With my little to no knowledge, replacing the boot.img and some files in system/bin with the ones provided in theofficial expansion pack should give you all that you need. With no extra apps.
yeah me 2
Yeah me too
This a simple and quick guide for everyone who wana make or just modify their own HTC DESIRE ROM's.(Rooted ones)
For example you downloaded a nice ROM from one of devs here, but they removed some application that you cant live without. Now you dont need to beg them to add those files back, simple add them your self and flash your rom.Missing APK's you can get simple by downloading any stock rom, than extract them and put them in your new ROM.
After you extracted files provided (c root recomended), you will see 2 maps
"Sign ROM" and "tools"
Signing ROM's:
After you modifed your ROM zip file, simple put it in "Sign ROM" map, and rename it to update.zip.Than run "Sign.bat" After the process is done you will get another zip called "update_signed.zip" which you can now put to your SD card and your ready for flashing. Note:JAVA SDK files are included, you only need to have normal java installed.
http://img99.imageshack.us/img99/2921/signedrom.jpg
Pushing recovery files from windows:
Now to flash your ROM you dont need linux anymore, simple enter recovery (Power button+back, than select recovery...), and than in the map "tools" run recovery-windows.bat. Than you will get standard screen where you can flash your roms, partition SD, clear data and so on..
NOTE: You need to have HTC Sync driver installed or your phone wont be detected (you can get them from HTC)
http://img213.imageshack.us/img213/1894/pushfiles.jpg
If you have any questions, suggestions or if i wrote something wrong i will be happy to answer/corect them.
http://hotfile.com/dl/43311449/92d9ee6/Desire_Tools.exe.html
http://www.megaupload.com/?d=JNI68MWZ
http://rapidshare.com/files/388849647/Desire_Tools.exe.html (Thanks pympster for link )
http://www.robertolsen.no/desire_tools.rar
(Thanks GeoTrail for link)
would this tool work for the HTC Legend aswell?
For signing roms yes, for pushing files not sure if Desire and legend use same files..
Ok this one is simple, but this is only how to add/delete several apps.
How about going little bit more deeper?
Well if you wana go deeper, you can download costom kernels with overclocks or low volatege and replace the ones in rom, or those circle battery mods or costom boot sounds and so on...Basicly your replacing/modifying original files. But this is just quick basic guide for basic stuff, let real ROM developing and costomizing to the developers who are good at it.
As far as hardware support goes is it the kernel that provides everything? Basically if I take an N1 rom (like cyanogen 5.0.6) and change to a desire kernel, is it likely to just work perfectly or are there other bits in the ROM that are likely to need changing?
Of course you can just use dsixda's Kitchen which is cross-platform and quite straightforward to use.
You just add the update.zip file you want to change, remove/add any apps you want and make any advanced changes you want too.
Select Build ROM and it'll create the new update.zip that you can flash to phone.
I've used it on my Desire without problem for adding/removing apps.
Well that kitchen is nice, but still..you need to downlaod virutal machine to make it run under windows or Cygwin tool than download JAVA SDK..setup lots of things.
My point of this thread was just vey basic and simple way to quickly add/remove/costomize files from ROM, without installling and downloading lots of tools, and quickly install it on Phone and test.
Sorry, I wasn't meaning to undermine your work. No doubt you've spent a lot of time creating this and trying to contribute to the community. It's far more than I can say for myself.
I was just pointing out there's something already out there, and more capable than this.
It's definitely good to see people helping out the members and this is definitely something useful
Everything is cool TheAshMan, and thanks for you link, im sure some enthusiastic people will try some advance things like that. But even my self im not big expert about Linux and phones, i do have great knowledge about windows and computers, but dont have much time for this area.
Screen shots on how to use this would help, I've come from cooking my own WinMo ROMs and wuld like to give this a try if possible
Also, as I use W7 x64 is it best to run the .bat files as an admin? Had issues using Windows methods in the past so have been using Linux to get rooted
I'm also using Windows 7 x64.
About running bat's as admin its not necessary unless you have some kind of UAC high settings, or running on some kind of limited user account. I never run this bats as admin and they work fine.
Basicly download some stock rom, or someones rom. And simple add or remove files inside rom.zip/system/app/
If you dont like facebook for example, just remove Facebook.apk and facebook.odex(if its present).
After your done with that, rename ROM to update.zip and put it in the folder
C:\Desire Tools\Sign ROM\ and excecute "Sign.bat" , and it will create signed rom with name update_signed.zip.
http://img99.imageshack.us/img99/2921/signedrom.jpg
This is just some base, im not gona explain you about ROM deodexing, framework, boot images kernels and stuff, because im not expert at this.
Now you can put that file to root of your SD card.
Now you can test it on your phone.
Shut down your phone. Turn it ON while holding back button.You will see Bootloader selected, press power button again. Than Recovery will appear, you can navigate down with volumen UP AND DOWN and select Recovery and press POWER button again to select it.Phone with Red triangle will appear on your phone. Now go in map C:\Desire Tools\tools and excecute "recovery-windows.bat"
http://img213.imageshack.us/img213/1894/pushfiles.jpg
And on your phone you will get that screen with green letters where you can select to 'Flash zip from sdcard' ,where your signed rom will appear.(You need to wipe data before from the same menu)
I hope i made some thing clearer im writing this from work so dont have much time
Right, got a ROM and added 2 .apk files to the /system/app folder and now got a signed_update.zip...is that it? They'll be on the device from the start?
Seems to simple to me!!
How can you add a new radio? Or change the version number in About phone>Software?
Yea thats it. About those other things..Google is your friend...
edit mate
when i flash it says:
E: Can't find update script
rom.zip/META-INF/COM/google/android/update-script
Did you touch that in ROM? If you didint, than you removed something that you shouldnt.
Can u also remove apps from rom that you don't like by this method.
-------------------------------------
Sent via the XDA Tapatalk App
Yea, thats the all point of everything i wrote here. Very simple way of very quickly removing apps that you dont want from the rom before flashing it.
Also, you need to watch out, and to a bit experementing. Because sometimes if you remove some crucial app, you will start getting random crashes of applications or random bugs. Allways make a copy of original rom.
For example if you remove HTC-IME.apk, you wont have any kind of keyboard in the rom. Making it un-usable
Somebody already asked how to add radio update, is it maybe included in Modaco r3 rom(the one without apps2sd and modaco additional stuff)?
Tnx for help
Hello there are rom custom for my sm-g350 pls ?
Izuna30 said:
Hello there are rom custom for my sm-g350 pls ?
Click to expand...
Click to collapse
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
ngoralph said:
1st this is i8260/i8262 section not sm g350
2nd this is dev section not Q&A
Click to expand...
Click to collapse
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
frost245 said:
Pretty sure this is q&a
Sent from my GT-I8262 using XDA Free mobile app
Click to expand...
Click to collapse
afaik it was moved as i have reported it
Gotta get this working!
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
AlexInHell said:
Hello everyone, I'm new to this forum, although I have spend a big amount of time here (before registering), reading through posts about customizing ROMs, etc.
First things first:
- I have a Samsung Galaxy Core Plus G350 (or G3500 whatever suites you), and I would like to customize it's stock ROM, no rooting involved. I did manage to customize, or I should say minimize, my stock ROM for my Samsung Galaxy Xcover 2 (S7710), rooted it, changed lot's of things, just to get rid off unwanted apps, services and maximize performance. And that worked out pretty well .
Being I'm a guy who likes things to be neat (I'll get to that in a sec ), and pretty much as close to factory build as it can be, I'm not trying to do anything flashy with my G350, just want to remove stupid apps and that's it.
When I said neat, I meant Odin flashing ROM neat. I prefer it to CWM Rom installing technique (although this is clean as well, one would have to have a memory card, memory card reader (or working USB drivers if one has to transfer files directly to the phone), CWM Recovery Firmware (no support for G350), and compatible Custom ROM...you get the picture, not much of a trouble, but a hassle if some of the components are missing....Odin flashing... clean and easy, anyone can use it.
My problem is:
After completing all modification, my system.img file appears with a lock, when I compile it. I'm not sure about the memory allocation, I did calculated it correctly ( i hope ) but that shouldn't be a problem, my main problem is the stupid lock on system.img file icon, before I compress everything to tar and checksum it. Ofc the flashing fails and my best guess its because of that lock in the icon, and Odin stops on system.img file. Does anyone know why is this happening, I didn't have any issues with Xcover's ROM packing, every time I finish with the modification in Xcover system.img file, unmount the file, and everything is fine. Even the flashing part.
I'm packing everything in Ubuntu 14.04 ...I am familiar with linux base systems but I ain't a wiz and flashing in Win 7.
Does anyone know the solution to this, I'm doing something wrong for sure, or I'm overlooking something, any help is very welcome.
Sorry for this extensive text and bad English (not my native language), I figured someone would appreciate some info.
Best regards.
Click to expand...
Click to collapse
As far as I know, the lock shows, that you don't have the write permission on this file
Sent from my SM-G350 using XDA-Developers mobile app
For those that want a rooted stock ROM, without having to use Kingoroot, here you go.
jy190_rooted.zip
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
I've made two harmless changes to stock that you can change after flashing:
Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
Default Timezone is America/Detroit instead of China/Shanghai (same reason as above)
Prerequisite: Probably you will want to get the JY1.90 ROM from Joying directly, and update your HU with it because Joying includes an updated MCU image. I am *not* including the MCU image here because one of you is going to flash it onto the wrong hardware and brick your HU. I am only providing the ROM image, just like Malaysk does.
1. To install, first extract dupdate.img from the zip.
2. Copy dupdate.img to the root directory of a USB stick or SD card
3. Enter recovery, flash. If coming from stock you can probably flash without clearing all. If coming from Malaysk you might want to clear all first.
Understand what you are doing. Read Malaysk's thread about flashing, and read all of his warnings, as they all apply here.
Thanks to Malaysk for his ROM and all of the other tweaks he's done. If you want something beyond stock, try his.
Thanks to Joying for making this unit, there is nothing else like it on the market. As long as continues to work, I'll continue to be very happy with it.
Thanks once more to Joying for being (so far) pretty friendly to the DIY/modding/hacking crowd. I've never seen a company so open with flashing and modding, and continuing to update their own firmware for their customers. It is nice to see, so let's not abuse it. Mod responsibly.
There won't be any additional support from me. This is a rooted stock ROM, that's it.
Edit 5-Nov-2016, some FAQ:
Unpacking and repacking a rockchip ROM
Adding root to the ROM
Make it easy on yourself: ROM kitchen by da_anton
it starts video playback on boot. its not your rom, its the original as well, but weird.
---------- Post added at 07:41 AM ---------- Previous post was at 07:28 AM ----------
What tool you use to unpack rom?
Hi!!! Thanks for your work I'm going to wipe my ROM (I think there's some garbage after deleting Kingoroot) and put your ROM into my unit.
Great work
wskelly said:
For those that want a rooted stock ROM, without having to use Kingoroot, here you go.
jy190_rooted.zip
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
I've made two harmless changes to stock that you can change after flashing:
Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
Default Timezone is America/Detroit instead of China/Shanghai (same reason as above)
Prerequisite: Probably you will want to get the JY1.90 ROM from Joying directly, and update your HU with it because Joying includes an updated MCU image. I am *not* including the MCU image here because one of you is going to flash it onto the wrong hardware and brick your HU. I am only providing the ROM image, just like Malaysk does.
1. To install, first extract dupdate.img from the zip.
2. Copy dupdate.img to the root directory of a USB stick or SD card
3. Enter recovery, flash. If coming from stock you can probably flash without clearing all. If coming from Malaysk you might want to clear all first.
Understand what you are doing. Read Malaysk's thread about flashing, and read all of his warnings, as they all apply here.
Thanks to Malaysk for his ROM and all of the other tweaks he's done. If you want something beyond stock, try his.
Thanks to Joying for making this unit, there is nothing else like it on the market. As long as continues to work, I'll continue to be very happy with it.
Thanks once more to Joying for being (so far) pretty friendly to the DIY/modding/hacking crowd. I've never seen a company so open with flashing and modding, and continuing to update their own firmware for their customers. It is nice to see, so let's not abuse it. Mod responsibly.
There won't be any additional support from me. This is a rooted stock ROM, that's it.
Click to expand...
Click to collapse
wskelly said:
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
Click to expand...
Click to collapse
Great idea and thanks for the work! Thought of that myself! Could you perhaps tell me how you made that ROM? How did you manage to extract the img file and put everything back together? Did you use imgRePackerRK? Thanks!
da_anton said:
Great idea and thanks for the work! Thought of that myself! Could you perhaps tell me how you made that ROM? How did you manage to extract the img file and put everything back together? Did you use imgRePackerRK? Thanks!
Click to expand...
Click to collapse
Yes, I used imgrepackerrk on Linux. After dumping the contents you are left with more img files. These are all block storage. In Linux, it is possible to mount these img files and manipulate their contents just like any block device.
Afterward, you can repack everything again with imgrepackerrk.
Sent from my Moto G using Tapatalk
wskelly said:
[*]Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
.
Click to expand...
Click to collapse
hey I also named my Joying that
This is great! If I hadn't install the Sept Joying image last weekend, I would have totally installed this. Thank so much!
One suggestion though, if you decide to make another one at some point, you might want to install the xposed framework (I did this via flashfire) and appsettings 1.13. I can provide a link to each, that are known good, as the 'regular' framework and App Settings 1.10 (from xposed directly) doesn't work. I know it's designed as 'stock' but at minimum the framework just makes sense, I think.
wskelly said:
Yes, I used imgrepackerrk on Linux. After dumping the contents you are left with more img files. These are all block storage. In Linux, it is possible to mount these img files and manipulate their contents just like any block device.
Afterward, you can repack everything again with imgrepackerrk.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Thanks! Great work! Got it working today and made my first ROM based on yours. I removed some apps which are just wasting RAM and I don't need.
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
da_anton said:
Thanks! Great work! Got it working today and made my first ROM based on yours. I removed some apps which are just wasting RAM and I don't need.
Click to expand...
Click to collapse
Awesome! Keep tinkering! This is how everyone gets started. ?
Sent from my Moto G using Tapatalk
Hi !, I'm not 100% sure but try to change radio reg at the Factory options.....
pinkpanther28 said:
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
Click to expand...
Click to collapse
Thank you for the work!
Question, how did you extract the img file. the typical utilities i use for android seem to be incompatible with this system image.
Found!
http://forum.xda-developers.com/showthread.php?t=2257331
Yes. Earlier post
mlkemac said:
Thank you for the work!
Question, how did you extract the img file. the typical utilities i use for android seem to be incompatible with this system image.
Found!
http://forum.xda-developers.com/showthread.php?t=2257331
Click to expand...
Click to collapse
See post #5.
@wskelly could you maybe tell me exactly what you did to include SuperSU in ROM? I would like to integrate it into the ROM builder scripts here https://github.com/da-anton/MTCD_ROM-cooking. Would be great!
da_anton said:
@wskelly could you maybe tell me exactly what you did to include SuperSU in ROM? I would like to integrate it into the ROM builder scripts here https://github.com/da-anton/MTCD_ROM-cooking. Would be great!
Click to expand...
Click to collapse
Yes, I kind of did already. If you look into the SuperSU thread here in Xda, you can get the latest version. Inside the flashable zip, there is a dir
META-INF/com/google/android
Then you'll find install-binary, which is actually a shell script. (this directory structure is the actually standard format for recovery-flashable zips)
In the shell script the author goes into great detail about what his where and with what permissions.
The big caveat for your efforts is that we have sdk 22 (5.1.1) and things are different depending on which version of Android you have (some Joying units are KitKat). The installation script handles every version of Android so far and this is all detailed by the author in the script.
Another warning: the installation script runs another binary tool that will "convert" wine of the binaries to "pie" executables. Because the ones I want are compiled for ARMv7, and I'm on Intel modding the ROM, I'm not sure if I can run that tool with confidence. So, I took the su binary files from Malaysk's ROM, which I know work. This is why SuperSU tells you that the binary is out of date right away. You must follow the chaos and chcon instructions in the installation script exactly. (I think malaysk is missing some of those steps because his rom would always fail to update su via the app)
So my recommendation is to look at the installation script, and follow the instructions in the comments section which are very detailed about what goes where. Except instead of using SuperSU installation files, you should take the files from my ROM. **You may try to use the files from SuperSU, but likely you will get a bootloop (because of the pie format issue), worth trying though. Also worth trying the pie conversion on Intel.
I'm on my phone so hopefully spellings and the path names aren't too messed up.
I'm curious if removing the recovery.img and bootloader.img if it will still flash. Flashing those two partitions every time is asking for trouble eventually.
Sent from my Moto G using Tapatalk
pinkpanther28 said:
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
Click to expand...
Click to collapse
Yea, this post is *completely* off topic and deserves its own thread. Maybe someone here will start a new thread for you.
Sent from my Moto G using Tapatalk
wskelly said:
So my recommendation is to look at the installation script, and follow the instructions in the comments section which are very detailed about what goes where. Except instead of using SuperSU installation files, you should take the files from my ROM. **You may try to use the files from SuperSU, but likely you will get a bootloop (because of the pie format issue), worth trying though. Also worth trying the pie conversion on Intel.
Click to expand...
Click to collapse
OK. I created a module in the MTCD ROM builder for that. How exactly did you set the links without chroot? Maybe you could have a look a my version and could tell me if anything is missing :angel:
https://github.com/da-anton/MTCD_ROM-cooking/blob/master/modules/install_supersu.sh
da_anton said:
OK. I created a module in the MTCD ROM builder for that. How exactly did you set the links without chroot? Maybe you could have a look a my version and could tell me if anything is missing :angel:
https://github.com/da-anton/MTCD_ROM-cooking/blob/master/modules/install_supersu.sh
Click to expand...
Click to collapse
Awesome script! I was way too lazy to do this but I wished I had it! ? I actually started to mod the SuperSU script to root the local ROM but I just got lazy.
To link without chrooting you can use the -f (force) option.
I am on my phone and didn't get to look at the whole script yet but you could just try to root stock and see if it works?
Nice job!
Sent from my Moto G using Tapatalk
wskelly said:
Awesome script! I was way too lazy to do this but I wished I had it! ? I actually started to mod the SuperSU script to root the local ROM but I just got lazy.
To link without chrooting you can use the -f (force) option.
I am on my phone and didn't get to look at the whole script yet but you could just try to root stock and see if it works?
Nice job!
Click to expand...
Click to collapse
Thanks! I already tried that and my unit is stuck in a boot loop now. Guess it's because I forgot to include the binary from Malaysk and used the official one instead will try the next days to fix my unit
Hi folks.
I'm new here.
It's my first post so please forgive me if there's something wrong.
Basically I want to know is, what type of knowledge do i need (programming language and other things) to work on root of android like build.prop and making custom roms and working on the custom recovery etc.
What do I need to learn to understand those things and work on them.
Thanks.
Kaksrocks said:
Hi folks.
I'm new here.
It's my first post so please forgive me if there's something wrong.
Basically I want to know is, what type of knowledge do i need (programming language and other things) to work on root of android like build.prop and making custom roms and working on the custom recovery etc.
What do I need to learn to understand those things and work on them.
Thanks.
Click to expand...
Click to collapse
Your question is not specific and I not sure exactly what information you requesting. For instance,
1 "root of android" ? Are you trying to root you're phone?
2. "build.prop"? Adding or modifying that can be done with an android app provided your device is already rooted. Ising ADB and fastboot may also be a possible.
3. " making custom roms" ? Does that mean installing or actually building a custom rom? Actually building a custom rom that is best left for advanced level developers. If, you mean installing a custun rom then generally speaking that is usually done in custom recovery by flashing a .zip file. Its very specific for each phone and carrier.
4. "working on custom recovery"? Depends on which custom recovery you have installed and what options are available. A YouTube search can provide some general information.
I am assuming you are interested in rooting you phone and unfair with all is necessary in order to do so. I suggest, searching for your specific model and carrier hear on XDA. For instence, I have a note 4, I search, "XDA Sprint Note 4".
Mr. JAVI said:
Your question is not specific and I not sure exactly what information you requesting. For instance,
1 "root of android" ? Are you trying to root you're phone?
2. "build.prop"? Adding or modifying that can be done with an android app provided your device is already rooted. Ising ADB and fastboot may also be a possible.
3. " making custom roms" ? Does that mean installing or actually building a custom rom? Actually building a custom rom that is best left for advanced level developers. If, you mean installing a custun rom then generally speaking that is usually done in custom recovery by flashing a .zip file. Its very specific for each phone and carrier.
4. "working on custom recovery"? Depends on which custom recovery you have installed and what options are available. A YouTube search can provide some general information.
I am assuming you are interested in rooting you phone and unfair with all is necessary in order to do so. I suggest, searching for your specific model and carrier hear on XDA. For instence, I have a note 4, I search, "XDA Sprint Note 4".
Click to expand...
Click to collapse
Well. First of all thanks for the reply.
I do have the knowledge on how to root the device and i have my device rooted.
I know how can i modify the build.prop file.
But i want to know how the tweaks are actually made to put them in build.prop file to get it into work. How that tweak is made.
How to know what actually should i edit and etc.
And for custom roms. I do actually want to know about how to actually make a custom rom. Even though if its a high level thing. I still want to know. So that i can start learning and get in that field.
I want to know how custom recovery is made. For ex how twrp was made. And i want to learn its functionality.
Thanks again for the reply.
Kaksrocks said:
Well. First of all thanks for the reply.
I do have the knowledge on how to root the device and i have my device rooted.
I know how can i modify the build.prop file.
But i want to know how the tweaks are actually made to put them in build.prop file to get it into work. How that tweak is made.
How to know what actually should i edit and etc.
And for custom roms. I do actually want to know about how to actually make a custom rom. Even though if its a high level thing. I still want to know. So that i can start learning and get in that field.
I want to know how custom recovery is made. For ex how twrp was made. And i want to learn its functionality.
Thanks again for the reply.
Click to expand...
Click to collapse
I
You welcome and I also Thank you for responding.
In regards to modification of build.props, I advise beginning with custom recovery and making a full back- up (all partitions). I have soft bricked my phone more that once by modifying build.pros and simply did a full wipe and restored my backup and up and running. Kernel Aduitor is an app that provides a Build prop Editor but there are stand alone app that are also available.
If your custom recovery is TWRP then Tipatch is an app that is worth looking into. Its available here on XDA or can be downloaded via Google Play Store.
Odex Roms vs Deodex Roms and what that means. I suggest Deodex if your plan on modifying and/or porting.
Also good to know the differences between kerels permissive vs enforcing.
Apps= ApkTool X, Apk Editor v1.3,(this is a lower version that offers a rebuild function while the updated version available from Google Play dose not) Md5 , and ZArchiver.
As far as how to make custom roms? Thats above my skill level. However, If you download a custom rom make a copy and rename it, then use a root file manager to extract it or ZArciver app and look threw the files of the rom. May help prove helpful in learning basic structure.
Keep in mind I am not a developer. Modified, porting, flashing, treaking I do often. For instance, Im tunning and od Note 4 on marshmallow 6.0.1 and have official Google Play Dark Theme.
If you have any questions
https://forum.xda-developers.com/android/themes/official-google-play-store-dark-theme-t3977061
Mr. JAVI said:
I
You welcome and I also Thank you for responding.
In regards to modification of build.props, I advise beginning with custom recovery and making a full back- up (all partitions). I have soft bricked my phone more that once by modifying build.pros and simply did a full wipe and restored my backup and up and running. Kernel Aduitor is an app that provides a Build prop Editor but there are stand alone app that are also available.
If your custom recovery is TWRP then Tipatch is an app that is worth looking into. Its available here on XDA or can be downloaded via Google Play Store.
Odex Roms vs Deodex Roms and what that means. I suggest Deodex if your plan on modifying and/or porting.
Also good to know the differences between kerels permissive vs enforcing.
Apps= ApkTool X, Apk Editor v1.3,(this is a lower version that offers a rebuild function while the updated version available from Google Play dose not) Md5 , and ZArchiver.
As far as how to make custom roms? Thats above my skill level. However, If you download a custom rom make a copy and rename it, then use a root file manager to extract it or ZArciver app and look threw the files of the rom. May help prove helpful in learning basic structure.
Keep in mind I am not a developer. Modified, porting, flashing, treaking I do often. For instance, Im tunning and od Note 4 on marshmallow 6.0.1 and have official Google Play Dark Theme.
If you have any questions
Click to expand...
Click to collapse
Great. Thanks for the information you provided.
You were pretty helpful.
So again thanks.