Hi, could anyone please help me by either post or upload their "default.prop" file located under root directory??
Model: i9100
Rom: Lite'ning Rom 5.0 based on XXKG6
Kernel: Ninphetamine-2.0.5
STORY:
I have accidentally deleted "default.prop" file, under root directory. (not /system)
Realising my mistake, I created a new file, named it "default.prop", hoping that the system will fill it in with lines it had.
Now all I have in the file are these;
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
I have never opened the file before to see what was in there. As I had no other Galaxy S2 to compare with, I wasn't sure if these lines were all the file originally contained. I have tried reflashing the entire rom, and also restoring previous NAND backup, but none of those seemed to return the "default.prop" file into its original state.
After frantic searching, I found that the original galaxy s had those lines as well;
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.am=android-samsung
ro.com.google.clientidbase.vs=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=2.1_r2
Source: http://forum.xda-developers.com/showthread.php?t=734151&page=2
Would Galaxy S2's default.prop also have those lines?
The first weird thing I noticed after deleting default.prop was that the market app stopped showing me a lot of apps under "Top Free" or "Top Paid". It is still like that after entering the above lines from original galaxy S..
Could anyone please upload or post what's in their default.prop, so that I can copy it into mine, or use as reference?
Thank you in advance, I'm dying of knowing the fact that my phone might be missing a critical file..
All mine has in it is:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Sent from my GT-I9100 using XDA Premium App
..then it seems like I have overreacted. The system seemed to have filled in all the lines back to original state, and im going to have to look elsewhere to solve the market problem.
Thank you very very much!! Thats all I needed
Sent from my GT-I9100 using XDA App
Related
Lets say I'm building/modifying a ROM. I remove all audio files and replace them with audio files of my choice. When editing the build.prop file, the following lines:
Code:
ro.config.ringtone=QuietlyBrilliant.mp3
ro.config.notification_sound=Zeta.mp3
ro.config.alarm_alert=NewDay.mp3
ro.config.cal_notification=Epsilon.mp3
ro.config.msg_notification=Gamma.mp3
I replace each one of the 'audiofile.mp3' with one I place in the correct directory. So those files listed above do not exist. When I flash the ROM, I look at the build.prop file and it's like I want it.
BUT, none of the sounds play when a call comes in, alarm goes off or text message receives. I actually have to manually set it once I'm in the ROM.
Any ideas?
They might have to be the exact same length as the old ones to work right
Sent from my ADR6425LVW using XDA
I got this from one of my sources.
This is the latest ICS build for Xperia Pro from EMMA - SE external testing software.
It's of use only for developers, as it's boot, system, etc packaged into one file (there is
info around on how to unpack it) and by default it can't be flashed on non-brown (not
developer) phones.
http://www.mediafire.com/?ni6smknsi68z4zy
http://www.mediafire.com/?zpd3q6dd660pfoa
http://www.mediafire.com/?4bg435kq40d22pf - Kernel & Ramdisk
Click to expand...
Click to collapse
PS: I do not want to disclose any details about the source.
Decrypted ftf file with complements from NorwayFun: http://monitor.lunet.ge/mk16i_xz_xz.ftf
update.zip with complements from eryen: http://www.multiupload.nl/NMN4WPMVO9
updat.zip & kernel with complements from Riyal:
http://108.166.90.15/.files/ICS3.img - Kernel
http://www.sendspace.com/file/rt9kau - ROM
* Refer Riyal's post on instructions to flash.
[HIGHLIGHT]PS 2: Be warned that this might not work, if not brick your phone.[/HIGHLIGHT]
ameer1234567890 said:
I got this from one of my sources.
PS: I do not want to disclose any details about the source.
Click to expand...
Click to collapse
Thanks for making it as a thread....I tried to search in google on how to unpack frimware files downloaded via emma....but was not able to find.....Can you please give the steps or share the link on how to unpack firmware files downloaded via emma
naveen88 said:
Thanks for making it as a thread....I tried to search in google on how to unpack frimware files downloaded via emma....but was not able to find.....Can you please give the steps or share the link on how to unpack firmware files downloaded via emma
Click to expand...
Click to collapse
I am working on it ATM. I shall post here one done!
PS: Be warned that this might not work, if not brick your phone.
This should work with EMMA.
Ill tell u a way to Decrypt the file Using Flash Tool.
1. Extract the file from zip archive to a new folder
2. Copy the Newly created folder to FLASHTOOL folder
3. Open Flashtool.exe, ==> Advance ==> Decrypt Files.
4. Select the Folder that contains the ICS file..
5. Then Move the File to " FILES TO CONVERT " pane.
6. Then Click Ok, It will take some time to Decrypt.
Then You can see extracted sin files there in same folder u copied before.
But you can not extract those sin files at the moment. You can try...
Anyways if i find anything, ill share with u..
Note : I'm not responsible for any damage to your device. use at your own risk.
Thanks for this! I'll see later if I could get all the libraries I needed from this. If yes then expect an ICS version of ultima in probably a week or two. I just need some specific libs for pro and drivers also
ftf file added!
The following files are missing in the ftf file I guess which are needed for flashing successfully:-
a)kernel.sin
b)adsp.sin
c)amss.sin
d)fota0.sin
e)fota1.sin
f)cache.sin
g)apps_log.sin
I had even tried to add these missing files and flashed from official ics ftf for Xperia Neo V as both are identical, but it doesn't work. Had got some critical security error via flash tool.
Is there any other way to extract sin files apart from SIN2IMG as it doesn't work?
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Riyal said:
Thanks for this! I'll see later if I could get all the libraries I needed from this. If yes then expect an ICS version of ultima in probably a week or two. I just need some specific libs for pro and drivers also
Click to expand...
Click to collapse
Good, I guess by that time official ICS firmware would be out for Xperia Pro. Then it would be double fun
---------- Post added at 05:20 PM ---------- Previous post was at 04:58 PM ----------
Guys I guess I struck gold
Hopefully will be posting some good news in few hours for all fellow xperia pro users
anyone tried this?
bye
28spawn said:
anyone tried this?
bye
Click to expand...
Click to collapse
it will not work. sin file headers are corrupt or encrypted.
##### Merging of the /util/data/semc_kernel_time_stamp.prop file #####
ro.build.date=Tue Apr 24 11:57:09 2012
ro.build.date.utc=1335261429
ro.build.user=BuildUser
ro.build.host=BuildHost
##### Final patch of properties #####
ro.build.product=MK16i
ro.build.description=MK16i-userdebug 4.0.4 4.1.B.0.431 UL5_3w test-keys
ro.product.brand=SEMC
ro.product.name=MK16i_1250-3710
ro.product.device=MK16i
ro.build.tags=release-keys
ro.build.fingerprint=SEMC/MK16i_1250-3710/MK16i:4.0.4/4.1.B.0.431/UL5_3w:userdebug/release-keys
######################## Customized property values #########################
ro.semc.version.cust=1250-3710
ro.semc.version.cust_revision=R2I
ro.semc.enable.fast_dormancy=true
ro.com.google.clientidbase.am=android-h3g-{country}
ro.com.google.clientidbase.ms=android-h3g-{country}
ro.com.google.clientidbase.vs=android-h3g-{country}
ro.net.data_tmpfailures=26,29,30,31,34
ro.gsm.data_retry_config=20000:5000,20000:5000,20000:5000,40000:5000,80000:5000,160000:5000
ro.semc.ecclist.num=1
ro.semc.ecclist.type.0=police
ro.semc.ecclist.number.0=999
ro.ril.mtu_size=1500
ro.network.auto_selection_only=true
ril.uus.support=true
ro.settings.apn.lock=3
ro.telephony.no_emg_calls_only=true
#########################################################################
ro.config.ringtone=sony_ericsson.ogg
ro.config.notification_sound=notification.ogg
ro.config.alarm_alert=alarm.ogg
ro.semc.content.number=PA6
################# Updating of the SW Version #################
ro.semc.version.fs_revision=4.1.B.0.431
ro.build.id=4.1.B.0.431
ro.build.display.id=4.1.B.0.431
##### Values from product package metadata #####
ro.semc.product.model=MK16i
ro.semc.ms_type_id=AAD-3880110-BV
ro.semc.version.fs=HUTCH-i
ro.semc.product.name=Xperia pro
ro.semc.product.device=MK16
ro.product.model=MK16i
# begin build properties
# autogenerated by buildinfo.sh
ro.build.version.incremental=UL5_3w
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.type=userdebug
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony Ericsson
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
ro.build.characteristics=default
# end build properties
#
# system.prop for iyokan
#
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
DEVICE_PROVISIONED=1
wifi.interface = wlan0
ro.semc.wifi.hostapd=1
persist.ro.ril.sms_sync_sending=1
ro.use_data_netmgrd=true
# Notify the system that the RIL only signals once
ro.telephony.call_ring.multiple=false
ro.semc.timescape_keys=Sony_Ericsson_Xperia
# Disable strict mode checking
persist.android.strictmode=0
ro.semc.sols.product-code=88
ro.semc.sols.company-code=5
# Constant values for Battery test in Service menu
ro.semc.batt.capacity=1500
ro.semc.batt.test.z_threshold=50
ro.semc.batt.test.min_level=70
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
#Default values/Locales for the hiding languages feature
ro.product.locale.excluded=ar_EG ar_IL fa_IR iw_IL
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=framework/SemcGenericUxpRes.apk
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r1
ro.com.google.clientidbase=android-sonyericsson
drm.service.enabled=true
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.semc.xloud.supported=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
ro.sf.lcd_density=240
ro.usb.pid_suffix=15A
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.drm.active.num=4
ro.drm.active.0=semc,1
ro.drm.active.1=cmla,0
ro.drm.active.2=viaccess,0
ro.drm.active.3=marlin,1
Click to expand...
Click to collapse
update.zip uploading.
eryen said:
update.zip uploading.
Click to expand...
Click to collapse
If its ics for xperia pro, then you are awesome man
can't wait to try it now........
Hope boot.img is also there in update.zip
naveen88 said:
If its ics for xperia pro, then you are awesome man
can't wait to try it now........
Hope boot.img is also there in update.zip
Click to expand...
Click to collapse
There is no kernel in original file. Sorry.
Flashtool extracted these files only,
1. amss_fs_iyokan_S1-SW-TEST-3F3C-0001-S1-PARTITION.sin
2. simlock.ta
3. system_S1-SW-TEST-3F3C-0001-S1-PARTITION-WITH-SPARE.sin
4. userdata_S1-SW-TEST-3F3C-0001-S1-PARTITION-WITH-SPARE.sin
All these origins for filesystem.
I will test system partition with my Arc.
---------- Post added 15th May 2012 at 12:18 AM ---------- Previous post was 14th May 2012 at 11:59 PM ----------
No kernel for release.
MK16i-userdebug-4.1.B.0.431.zip
http://www.multiupload.nl/NMN4WPMVO9
eryen said:
There is no kernel in original file. Sorry.
Flashtool extracted these files only,
1. amss_fs_iyokan_S1-SW-TEST-3F3C-0001-S1-PARTITION.sin
2. simlock.ta
3. system_S1-SW-TEST-3F3C-0001-S1-PARTITION-WITH-SPARE.sin
4. userdata_S1-SW-TEST-3F3C-0001-S1-PARTITION-WITH-SPARE.sin
All these origins for filesystem.
I will test system partition with my Arc.
---------- Post added 15th May 2012 at 12:18 AM ---------- Previous post was 14th May 2012 at 11:59 PM ----------
No kernel for release.
MK16i-userdebug-4.1.B.0.431.zip
http://www.multiupload.nl/NMN4WPMVO9
Click to expand...
Click to collapse
Are only the sin files included in the zip file?
From where you got that build properties?
naveen88 said:
Are only the sin files included in the zip file?
From where you got that build properties?
Click to expand...
Click to collapse
System.sin partition extracted to flash-able zip file.
Info belongs to build.prop file.
Ok, Won't arc's kernel or neo v's kernel work for xperia pro as the platform is same?
Btw...if any developers want direct download link for the zip file posted by eryen, then p.m me for the link
Interesting to note that this is the Android 4.04 release!
Isn't it great having all those Neo V, Ray and Arc S users acting as beta-testers for us with the power of the SEX-Pro!
A direct link of the zip would be good for me I already ported Xperia ICS kernel to pro. If I'll be releasing a stock one then I could release it in no time. If I encorporate my mods then this would take more than a week
Now my only problem is a freaking ramdisk for pro ICS
If I get hold of the extracted system files of pro ICS probably I could port the ramdisk from arc S to Pro
paul5425 said:
Isn't it great having all those Neo V, Ray and Arc S users acting as beta-testers for us with the power of the SEX-Pro!
Click to expand...
Click to collapse
That's a great thought.
@Riyal and Ameer
Direct download link sent via pm. Please check and confirm.
@Riyal
Please release a stock one first so that we can test it and report bugs if any. And then you can work on including the mods.
Just a thought, If you can work on FXP120, may be porting camera(fixing the video recording and front camera issue) and music app to FXP 120 then it would be just awesome.
Hi everyone
After seeing all the beautiful creations by wonderful ROMs like MiniCM10, JBMP, GingerSony and much more for X10 Mini and Pro, you might wanted to know how to make your own unique ROM.
So, I am going to tell how to make your own customized ROMs
(It is not about building a ROM from source but modifing a prebuilt ROM)
So, what are we waiting for Let's start!
CONTENTS
1. Setting Up
2. Unpack and Modifying /System (App, Lib, Media)
3. Editing Build.prop
4. Modifing /Meta-Inf
5. Additional Tweaks
6. Repack, Rename and Release
Step 1 Setting Up
1. Files you need:
- Base ROM (Choose a stable one)(MiniCM6, 7, 9, 10, SlimROMs+ are the best choices for modification!)
- 7Zip or Winzip or anything that has function to unzip
- Notepad++
- Your thinking about what the ROM should be like
- Patience
OK. Let's move up to Step 2 and let's start the real work!
Step 2 Unpacking the Base ROM and Modifying /System Folder
1. Unzip your Base ROM using 7zip, Winzip or whatever.
2. After unzipping, you will see two folders inside the folder. One is META-INF, and another is System.
2-1. Go inside the /System folder.
3. You will see many folders/files which usually are
addon.d
apps
bin
etc
fonts
frameworks
lib
media
usr
vendor
xbin
build.prop
and we are going to focus on apps, lib and media folder on this step.
4. Browse to /app folder. /app folder contains .apk files of apps in your ROM. Delete apps you do not need and add .apk files of apps what you want to add.
5. Browse to /lib folder. /lib folder contains necessary files for Android to run. Which means, without lib files, you will not be able to run your ROM as well as apps. Add libs for your added apps if necessary (Not all apps need it) and DO NOT DELETE ANY OF PRE-INSTALLED FILES IN THE /LIB FOLDER!
6. Browse to /media folder. /media folder contains ringtones, bootanimations and more.
6-1. Browse to /media/audio, and you will find 4 folders, alarms, notifications, ringtones, and ui. Go ahead and delete songs you do not like and add your favorite songs for alarms, notifications, ringtones folder.
6-2. Back to /media folder, you will find Bootanimation.zip If you want to change your bootanimation as well, see [TUTORIAL] How to make and install android bootanimations.
We are pretty done for that three folders. So, let's continue onto editing build.prop!
Step 3 Editing Build.prop
There is build.prop in your system, and we will modify that file.
You have to have Notepad++ to open it.
1. Open build.prop with Notepad++.
This is build.prop from my SlimROMs+ R3:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=Slim ROMs+ CM10 Revised3 for Robyn
ro.build.display.id=Slim ROMs+ CM10 Revised3 for Robyn
ro.build.version.incremental=eng.pongnamu.20130317.121841
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=March 23, 2013
ro.build.date.utc=1363289271
ro.build.type=user
ro.build.user=pongnamu
ro.build.host=pongnamu
ro.build.tags=test-keys
ro.product.model=E10i
ro.product.brand=SEMC
ro.product.name=LT30p_1269-0608
ro.product.device=robyn
ro.product.board=robyn
ro.product.cpu.abi=armeabi-v6l
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony Ericsson
ro.wifi.channels=
ro.board.platform=msm7x27
# ro.build.product is obsolete; use ro.product.device
ro.build.product=robyn
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=LT30p-user 4.0.4 7.0.A.3.195 PPP_xw test-keys
ro.build.fingerprint=Sony/LT30p_1269-0608/LT30p:4.0.4/7.0.A.3.195/PPP_xw:user/release-keys
ro.build.characteristics=default
ro.cm.device=robyn
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.sf.lcd_density=120
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=Slim ROMs+ CM10 Revised3 for Robyn
ro.modversion=Slim ROMs+ CM10 Revised3 for Robyn
ro.min.kernel.version=2.6.32.60-nAa
ro.min.kernel.revision=05
persist.sys.themeId=CrystalMiniCM10
persist.sys.themePackageName=com.darkdog.theme.crystalminicm10
ro.media.dec.jpeg.memcap=10000000
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d/dev/smd0
ro.ril.hep=1
ro.ril.hsdpa.category=10
ro.ril.enable.dtm=1
ro.ril.enable.3g.prefix=1
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hsupa.category=6
ro.ril.disable.power.collapse=1
ro.telephony.ril_class=SemcRIL
wifi.interface=wlan0
wifi.softap.interface=wlan0
wifi.softapconcurrent.interface=wlan0
wifi.supplicant_scan_interval=45
ro.ril.def.agps.mode=2
ro.ril.def.agps.feature=1
persist.sys.use_16bpp_alpha=1
persist.sys.use_dithering=2
persist.sys.force_hw_ui=true
ro.telephony.default_network=0
ro.telephony.call_ring.delay=1000
ro.telephony.call_ring.multiple=false
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.ril.enable.a52=1
ro.ril.enable.a53=1
ro.telephony.ril.v3=icccardstatus,skipbrokendatacall,signalstrength,datacall
ro.telephony.ril_skip_locked=true
ro.media.enc.file.format=3gp,mp4
ro.media.enc.vid.codec=m4v,h263
ro.media.enc.vid.h263.width=176,640
ro.media.enc.vid.h263.height=144,480
ro.media.enc.vid.h263.bps=64000,1600000
ro.media.enc.vid.h263.fps=1,30
ro.media.enc.vid.m4v.width=176,640
ro.media.enc.vid.m4v.height=144,480
ro.media.enc.vid.m4v.bps=64000,1600000
ro.media.enc.vid.m4v.fps=1,30
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
settings.display.autobacklight=1
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
windowsmgr.max_events_per_sec=150
debug.camcorder.disablemeta=1
dalvik.vm.dexopt-flags=m=y
dalvik.vm.checkjni=0
dalvik.vm.dexopt-data-only=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.execution-mode=int:jit
dalvik.vm.verify_bytecode=false
dalvik.vm.heapsize=32m
debug.sf.hw=1
debug.composition.type=mdp
debug.gr.numframebuffers=3
ro.max.fling_velocity=4000
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
hwui.render_dirty_regions=false
hwui.disable_vsync=true
debug.mdpcomp.logs=0
debug.sf.no_hw_vsync=1
hwui.print_config=choice
debug.enabletr=false
debug.hwui.render_dirty_regions=false
debug.hwui.disable_vsync=true
com.qc.hardware=true
persist.service.zram=1
ro.zram.default=18
persist.sys.usb.config=mtp,adb
persist.service.adb.enable=1
ro.opengles.version=131072
ro.product.locale.language=en
ro.product.locale.region=US
persist.ro.ril.sms_sync_sending=1
persist.android.strictmode=0
debug.performance.tuning=1
video.accelerate.hw=1
pm.sleep_mode=1
persist.pmem.camera=4000000
ro.config.ringtone=InsertCoin.ogg
ro.config.notification_sound=Helium.ogg
ro.config.alarm_alert=Cesium.ogg
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
2. We are going to change lines with orange color.
Above lines explained:
ro.build.id= Write your ROM name here
ro.build.display.id= Write your ROM name here (It will be displayed in Settings>About Phone)
ro.build.version.incremental= Keep this basic principle: eng.YOURNAME.YYYYMMDD .HHMMSS (Year, Month, Date, Hour, Minute, Second)
ro.build.date= Write when you build the version
ro.build.user= Write your name
ro.build.host= Write your name
ro.cm.version= Write your ROM name here (Example: SlimROMs+, MiniCM10 etc)
ro.modversion= Write your ROM name here
persist.sys.themeId= Write your theme chooser theme you included in the /app folder
persist.sys.themePackageName= Write the package name of the theme you included in your ROM
ro.config.ringtone= Write your ROM's default ringtone
ro.config.notification_sound= Write your ROM's default notification sound
ro.config.alarm_alert= Write your ROM's basic Write your ROM's default alarm
3. Add tweaks to it. Search for tweaks in XDA, follow their guide on how to add it and do it.
We are done editing build.prop! It was not hard, was it? Lets continue onto modifying /Meta-Inf on the next post!
Step 4
step5
step6
+1
Re: [GUIDE][WIP] How To Make (or Cook) Your Own Custom ROM | Easy as 1.2.3
Hey where is the steps??? Please give the steps...
Sent from my E10i using xda app-developers app
LOL Renz. give him time to write
This thread is a great idear. i hope a lot of newbies will play with the guide and end up becomming the coolest devs around. and make their own ROM too
Emperor.dk said:
LOL Renz. give him time to write
This thread is a great idear. i hope a lot of newbies will play with the guide and end up becomming the coolest devs around. and make their own ROM too
Click to expand...
Click to collapse
sorry...
Re: [GUIDE][WIP] How To Make (or Cook) Your Own Custom ROM | Easy as 1.2.3
Renz29 said:
sorry...
Click to expand...
Click to collapse
No need to be sorry I will complete the guide soon.
Sent From X10Mini Running SlimROMs+ R3 Final
Thanks pongnamu I cant w8 please complete your Guide
tnx
erfandl said:
Thanks pongnamu I cant w8 please complete your Guide
tnx
Click to expand...
Click to collapse
thank you pongy
:laugh:
Re: [GUIDE][WIP] How To Make (or Cook) Your Own Custom ROM | Easy as 1.2.3
=D
☜ Enviado desde mi u20a ☞
pongnamu thank you, this is perfect! very well explained!
Emperor.dk said:
LOL Renz. give him time to write
This thread is a great idear. i hope a lot of newbies will play with the guide and end up becomming the coolest devs around. and make their own ROM too
Click to expand...
Click to collapse
You are absolutely right bro, this'll give many the chance to become devs.
Keep op the work, @pongnamu !!!
Sent from my U20i using xda app-developers app
Thanks pongnamu... ends soon please
Cool
Cool, working on it now
I hope we will soon have a sequel, because the subject is really perfect!
adb remount is not permitted
after reading about it i heard you can modify the kernel (default.prop) to fix this error?
i have done so and i would like to know if compiling annd flashing the modified kernel will work, and are there any chances of bricking?
BEFORE EDITING
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
AFTER
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
persist.service.adb.enable=0
"persist.service.adb.enable=0" this line was not there, so will adding it affect it?
i have uploaded the kernel without the modifications applied at the bottom of this post (stock samsung gti-9300 4.1.2 XXEMH1)
KERNEL HERE
Thanks in advance!
Hello friends,
I have an Android 5.1.1 device and my question is the following:
I just finished editing/optimizing the build.prop file (located in /System) and was wondering if this is also possible with the default.prop file (located in the beginning of the root folder ''RootFS'') ?
Codes in them are often the same / very similar.
It is about these codes that I had put in the Build.prop and also want to put in default.prop:
#Disable Android Logging
debugtool.anrhistory=0
profiler.debugmonitor=false
profiler.launch=false
profiler.hung.dumpdobugreport=false
# Disables data sent and logging
ro.config.nocheckin=1
profiler.force_disable_err_rpt=1
profiler.force_disable_ulog=1
Of course, I thank you all in advance for your time and effort.
You need to modify your boot.img with mkbootimg or other kernel tools. This file, default.prop, is inside of ramdisk, inside of boot.img file ... and you need to extract from there to modify and after flash on your device. I found on google and on xda many "how to".
Sorry for my bad english.