Has anyone with root successfully edited their build.prop? I've tried adding some tweaks with several editors but the changed build.prop will not save, I get an error or app crash when I try.
OK, got it to work through Flashtool.
jeriku said:
Has anyone with root successfully edited their build.prop? I've tried adding some tweaks with several editors but the changed build.prop will not save, I get an error or app crash when I try.
Click to expand...
Click to collapse
I have no issues using root explorer. should be in r/w mode.
How are you editing it.
ganeshbiyer said:
I have no issues using root explorer. should be in r/w mode.
How are you editing it.
Click to expand...
Click to collapse
I tried through ES File Explorer and Rom Toolbox, but kept getting errors. I finally was able to edit and save using Flashtool. Is there a setting in ES or RT that I hit so I can edit this?
jeriku said:
I tried through ES File Explorer and Rom Toolbox, but kept getting errors. I finally was able to edit and save using Flashtool. Is there a setting in ES or RT that I hit so I can edit this?
Click to expand...
Click to collapse
I don't know about es explorer.
Thru rom tool box, I changed one setting and saved, no problems there.
Check if rom toolbox has been granted super user privileges.
Check in the Super user app.
ganeshbiyer said:
I don't know about es explorer.
Thru rom tool box, I changed one setting and saved, no problems there.
Check if rom toolbox has been granted super user privileges.
Check in the Super user app.
Click to expand...
Click to collapse
Yes it does. Maybe because it's the free version?
Sent from Rooted LT28at with ICS.
Can someone with the .111 baseband and Root/ICS tell me what your value for:
ro.settings.apn.lock
in the build.prop is?
Also what your value for:
persist.sys.timezone
Mine is set to Aisa/Hong_Kong, but I'm thinking mine should be something for the US.
My ro.settings.apn.lock settings are in characters, so I don't know what it says.
I have the same settings as you for persist.sys.timezone.
Sent from my LT28h using xda premium
jeriku said:
Can someone with the .111 baseband and Root/ICS tell me what your value for:
ro.settings.apn.lock
in the build.prop is?
Also what your value for:
persist.sys.timezone
Mine is set to Aisa/Hong_Kong, but I'm thinking mine should be something for the US.
Click to expand...
Click to collapse
JaredP said:
My ro.settings.apn.lock settings are in characters, so I don't know what it says.
I have the same settings as you for persist.sys.timezone.
Sent from my LT28h using xda premium
Click to expand...
Click to collapse
OK, well how about someone with the .257 ATT baseband?
jeriku said:
OK, got it to work through Flashtool.
Click to expand...
Click to collapse
Can you explain how you did using flashtool? I assume no-root required?
Anyone still bone stock that can pull their build.prop file? I should have done all this before my upgrade/root, but I just wanna look and compare what I have -vs- what I had.
The bad thing is we really don't have much a way to root a Gingerbread. I can try in a day or 2.
popfan said:
The bad thing is we really don't have much a way to root a Gingerbread. I can try in a day or 2.
Click to expand...
Click to collapse
I think you should be able to read the build.prop without root. You just can't edit it.
Sent from my LT26i using xda premium
tribalartgod said:
Anyone still bone stock that can pull their build.prop file? I should have done all this before my upgrade/root, but I just wanna look and compare what I have -vs- what I had.
Click to expand...
Click to collapse
I can get it to you.
Sent from my LT28at
KEB64 said:
I can get it to you.
Sent from my LT28at
Click to expand...
Click to collapse
Got it! It was the first message of the two that you sent that was successful for me, so thanks.
Now the LTE lock question... This line... I want to change that value, so I'm not locked to LTE... But I need to know what to change it to? FALSE? 0? Leave it blank?
Code:
ro.settings.apn.lock=AT&T PTA
Any help on this is greatly appreciated. I am also gonna toy around with some of the settings I am familiar with changing. But this one in particular, I'm just unsure of the value to use to remove the LTE lock.
tribalartgod said:
Got it! It was the first message of the two that you sent that was successful for me, so thanks.
Now the LTE lock question... This line... I want to change that value, so I'm not locked to LTE... But I need to know what to change it to? FALSE? 0? Leave it blank?
Code:
ro.settings.apn.lock=AT&T PTA
Any help on this is greatly appreciated. I am also gonna toy around with some of the settings I am familiar with changing. But this one in particular, I'm just unsure of the value to use to remove the LTE lock.
Click to expand...
Click to collapse
Would you be able to post the file here? Or even better, since you seem to know what you're doing, could you post the changes to be done with the file? So far I've read only about changing every reference of LT28h to LT26i to be able to use the PS store and games.
josemald said:
Would you be able to post the file here? Or even better, since you seem to know what you're doing, could you post the changes to be done with the file? So far I've read only about changing every reference of LT28h to LT26i to be able to use the PS store and games.
Click to expand...
Click to collapse
I only know as much as I have learned... Which really isn't a whole lot compared to most. :-/ My thing...I'm just not afraid to try stuff. LOL.
Would you like me to post the file I was sent anyways? It's a Gingerbread Stock build.prop file...
I intend on comparing both files (Stock and Rooted) to see where the differences are between the two, and then play with settings from there. The issue with messing witha build.prop... Is sometimes things work better...Sometimes it breaks stuff... Once I am able to compare and go from there, I'd be happy to share my finding though... Especially if I find something that helps.
Yea, if you can post it would be nice so some of can do the same thing.
---------- Post added at 11:05 AM ---------- Previous post was at 11:01 AM ----------
tribalartgod said:
Got it! It was the first message of the two that you sent that was successful for me, so thanks.
Now the LTE lock question... This line... I want to change that value, so I'm not locked to LTE... But I need to know what to change it to? FALSE? 0? Leave it blank?
Code:
ro.settings.apn.lock=AT&T PTA
Any help on this is greatly appreciated. I am also gonna toy around with some of the settings I am familiar with changing. But this one in particular, I'm just unsure of the value to use to remove the LTE lock.
Click to expand...
Click to collapse
I am not sure that the apn.lock mean that you are locked to LTE or not. I think it is referring to the APN that the phone should be using.
tribalartgod said:
I only know as much as I have learned... Which really isn't a whole lot compared to most. :-/ My thing...I'm just not afraid to try stuff. LOL.
Would you like me to post the file I was sent anyways? It's a Gingerbread Stock build.prop file...
I intend on comparing both files (Stock and Rooted) to see where the differences are between the two, and then play with settings from there. The issue with messing witha build.prop... Is sometimes things work better...Sometimes it breaks stuff... Once I am able to compare and go from there, I'd be happy to share my finding though... Especially if I find something that helps.
Click to expand...
Click to collapse
That's my thing more or less with computers, because with a PC the almost worst case scenario is having to format the HD from a Windows DVD and reinstall everything. On the other hand, a cell phone can be turned into a paperweight much more easily, so I go a lot more cautiously.
But yes, please post the file, things like the APN or the persistent time should be changeable without bricking the phone, so worst case I'd just undo the changes (not so much for APN, since in the rooted ICS it's written in Chinese). I used to play around a bit with the Windows Mobile registry, seems like this file serves a similar role in Android.
tribalartgod said:
Anyone still bone stock that can pull their build.prop file? I should have done all this before my upgrade/root, but I just wanna look and compare what I have -vs- what I had.
Click to expand...
Click to collapse
You know you can open an ftf like a zip file using 7zip and then use Flashtool to dump the data from the system.sin. Use ext2explorer then on the ext4 file that you get after dumping the system.sin data and that will allow you to browse and copy files from the system folder. This way you can get files/folders from rom firmware without having to have it on your phone.
Stock AT&T build.prop attached in zip file.
##### Merging of the /util/data/semc_kernel_time_stamp.prop file #####
ro.build.date=Wed Apr 18 11:20:38 2012
ro.build.date.utc=1334719238
ro.build.user=BuildUser
ro.build.host=BuildHost
##### Final patch of properties #####
ro.build.product=LT28at
ro.build.description=LT28at-user 2.3.7 6.0.C.1.257 _nr_zw test-keys
ro.product.brand=SEMC
ro.product.name=LT28at_1255-7823
ro.product.device=LT28at
ro.build.tags=release-keys
ro.build.fingerprint=SEMC/LT28at_1255-7823/LT28at:2.3.7/6.0.C.1.257/_nr_zw:user/release-keys
######################## Customized property values #########################
ro.semc.version.cust=1255-7823
ro.semc.version.cust_revision=R53E
ro.semc.enable.fast_dormancy=true
ro.semc.rem-roam-icon=2
persist.cust.tel.eons=1
persist.cust.tel.adapt=1
ro.com.google.clientidbase.am=android-att-us
ro.com.google.clientidbase.gmm=android-sonyericsson
ro.com.google.clientidbase.ms=android-att-us
ro.com.google.clientidbase.yt=android-sonyericsson
ro.config.ringtone=AT&T_PlayOn.ogg
ro.config.notification_sound=Pixie_Dust.ogg
ro.network.auto_selection_only=false
ro.operator.displayUnicodeName=true
ro.settings.apn.lock=AT&T PTA
ro.network.signalbar=5
ro.semc.facebook_inside=true
ro.semc.att.deviceid=1
cust.att.carriername=true
ro.roaming.extended=true
ro.roaming.mcc_list=310,311,312,313,314,315,316
ro.roaming.extended_rule=0
ro.roaming.excluded_plmn_list=310110,310140,310400,310470,311170
ro.tether.entitlement.enable=1
persist.data_netmgrd_mtu=1500
ro.PDP_CONNECTION_POOL_SIZE=3
ro.nfc.se.default=SIM
ro.nfc.se.sim.enable=true
ro.statusbar.4G-show-umts-hspa=true
#########################################################################
ro.config.alarm_alert=alarm.ogg
ro.semc.content.number=PA2
################# Updating of the SW Version #################
ro.semc.version.fs_revision=6.0.C.1.257
ro.build.id=6.0.C.1.257
ro.build.display.id=6.0.C.1.257
##### Values from product package metadata #####
ro.semc.product.model=LT28at
ro.semc.ms_type_id=AAL-8880001-BV
ro.semc.version.fs=ATT
ro.semc.product.name=LT28at
ro.semc.product.device=LT28
ro.product.model=LT28at
# begin build properties
# autogenerated by buildinfo.sh
ro.build.version.incremental=_nr_zw
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.type=user
ro.product.board=MSM8660_SURF
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=US
ro.wifi.channels=
ro.board.platform=msm8660
# ro.build.product is obsolete; use ro.product.device
# Do not try to parse ro.build.description or .fingerprint
# end build properties
#
# system.prop for surf
#
# Notify the system that the RIL only signals once
ro.telephony.call_ring.multiple=false
rild.libpath=/system/lib/libril-qc-qmi-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=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
#
# system props for the cne module
#
persist.cne.UseCne=false
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.be.ge.sqi.min=0
persist.cne.be.ge.sqi.max=100
persist.cne.be.umts.sqi.min=0
persist.cne.be.umts.sqi.max=100
persist.cne.be.hspa.sqi.min=0
persist.cne.be.hspa.sqi.max=100
persist.cne.be.1x.sqi.min=0
persist.cne.be.1x.sqi.max=100
persist.cne.be.do.sqi.min=0
persist.cne.be.do.sqi.max=100
persist.cne.be.wlan.sqi.min=0
persist.cne.be.wlan.sqi.max=100
ro.hdmi.enable=true
lpa.decode=false
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=11
#system props for time-services
persist.timed.enable=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072
# NFC
ro.nfc.port=I2C
ro.nfc.on.default=false
ro.nfc.se.smx.enable=false
# System props for SOLS
ro.semc.sols.product-code=101
ro.semc.sols.company-code=5
# system props 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
# prop to indicate what kind of external memory the product have.
ro.semc.product.user_storage=emmc_sdcard
ro.build.characteristics=default
# Override timer on how long to wait before switching
# back to a radio's default network
# 600000 = 10 minutes
android.telephony.apn-restore=600000
# For AT&T, use first PNN Record to display correct network name
config_use_firstPnnRecord=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.product-res-path=framework/SemcGenericUxpRes.apk
ro.com.google.gmsversion=2.3_r10
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-sonyericsson
ro.sf.lcd_density=320
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
ro.com.google.clientidbase=android-sonyericsson
ro.sf.lcd_density=320
dalvik.vm.heapsize=32m
ro.sf.lcd_density=320
dalvik.vm.heapsize=48m
ro.semc.xloud.default_setting=false
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.drm.active.num=1
ro.drm.active.0=marlin,1
ro.service.swiqi.supported=true
persist.service.swiqi.enable=1
Click to expand...
Click to collapse
Related
This is the latest Froyo 2.2 release for North-America(Canada), the firmware is re-packaged to a 3 files' firmware so it can be flashed with or with pit and re-partition.
Firmware: I9000MUGKC1
PDA: UGKC1
MODEM: UGKC1
CSC: MultiCSC (BMC, BWA, VMC)
No bootloaders, Multiupload Link: Download (145.2 MB) (Double-click to extract)
With bootloaders, Multiupload Link: Download (145.4 MB) (Double-click to extract)
Note: Flash as PDA only with no pit and no re-partition. Flash at your own risk!)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FROYO
ro.build.display.id=FROYO.UGKC1
ro.build.version.incremental=UGKC1
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=2011. 03. 04. (금) 16:07:58 KST
ro.build.date.utc=1299222478
ro.build.type=user
ro.build.user=shout.lee
ro.build.host=SEP-09
ro.build.tags=release-keys
ro.product.model=GT-I9000M
ro.product.brand=samsung
ro.product.name=GT-I9000M
ro.product.device=GT-I9000M
ro.product.board=GT-I9000M
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=CA
ro.wifi.channels=
ro.board.platform=s5pc110
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-I9000M
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-I9000M-user 2.2 FROYO UGKC1 release-keys
ro.build.fingerprint=samsung/GT-I9000M/GT-I9000M/GT-I9000M:2.2/FROYO/UGKC1:user/release-keys
# Samsung Specific Properties
ro.build.PDA=I9000UGKC1
ro.build.hidden_ver=I9000UGKC1
ro.build.changelist=928457
ro.tether.denied=false
# end build properties
#
# system.prop for smdkc110
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version=131072
persist.sys.timezone=America/Toronto
#
# ADDITIONAL_BUILD_PROPERTIES
#
windowsmgr.max_events_per_sec=55
keyinputqueue.use_finger_id=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
keyguard.no_require_sim=true
ro.config.ringtone=01_Samsung_tune.ogg
ro.config.notification_sound=20_Cloud.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.opengles.version=131072
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Good luck and have fun
Thanks Ramad!
Sent from my GT-I9000 using XDA Premium App
Thanks. Nice to have all the parts seperate.
I also have the original TAR file from kies, which also include the SBL.
Is it the same thing?
zorxd said:
I also have the original TAR file from kies, which also include the SBL.
Is it the same thing?
Click to expand...
Click to collapse
This package does not include Sbl.bin, my opinion is if Download Mode works then don't re-flash it unless you have to.
Ok Downloading
[Ramad] said:
This package does not include Sbl.bin, my opinion is if Download Mode works then don't re-flash it unless you have to.
Click to expand...
Click to collapse
Well if the sbl.bin included in KC1 is newer I would prefer to flash it too. Kies flash it anyways, and I will probably upgrade with kies.
zorxd said:
Well if the sbl.bin included in KC1 is newer I would prefer to flash it too.
Click to expand...
Click to collapse
I concur. It would be great if we can get the secondary bootloader also
Well as I said I have it. I can upload the original tar file from kies if some people are interested.
The firmware with Sbl.bin is added, flash at your own risk, I'm not responsible if you brick your phone.
Hello Guys,
I have the GT-I9000M and I recently upgrated my firmware to this version FROYO.UGKC1. I am getting the error message "Warning Camera Failed" everytime i launch the camera app so now I am looking to root my device to fix this. I found many different solutions but they all require for the device to be rooted. I tried rooting my device with the z4root app but it did not work and i am guessing it is because of my firmware version. I am new to rooting but I have read a lot of article about this since then. Can somebody please help me root my device or just find a solution to the camera issue? It would be really appreciated. Thank you!
Use SuperOneClick Root.. works great...
http://forum.xda-developers.com/showthread.php?t=803682
Im coming from miui so do i flash the 3 file with pit and repartition?
Jason123420 said:
Im coming from miui so do i flash the 3 file with pit and repartition?
Click to expand...
Click to collapse
Yes please.
[Ramad] said:
Yes please.
Click to expand...
Click to collapse
Yes please? I take it that means with pit and repartition?
Sent from my GT-I9000 using XDA Premium App
Jason123420 said:
Yes please? I take it that means with pit and repartition?
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Yes, please use pit and re-partition.
Your questions was if you should use pit and re-partition, answering by Yes and adding 'please' does not make it 'No'.
xpirozx said:
Use SuperOneClick Root.. works great...
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Thank you so much! Worked fine for me. I rooted my phone, replaced my camera firmware files and everything works fine now.
[Ramad] said:
Yes, please use pit and re-partition.
Your questions was if you should use pit and re-partition, answering by Yes and adding 'please' does not make it 'No'.
Click to expand...
Click to collapse
Thanks
Sent from my GT-I9000 using XDA Premium App
Hi folks.
Do you know if this firmware has Brazilian Portuguese language and swype ?
If not, can you tell me the latest firmware for I9000, not I9000B that hast it ?
Thanks a lot.
I think most, if not all Euro ROMs have Portuguese, but from Portugal. These ROMs are the most popular here on XDA. Asian ROMs are popular too.
If you really want Brazilian Portuguese, I think you have no choice but sticking to official i9000B ROMs.
This one is a Canadian ROM and if I remember it has only English and French. Quite a few Swype language but I don't remember seeing anything about Brazil.
Thanks to kc_NOTREALLY for the leak.
Its odex with full root and busybox has been added. no modem YOU WILL LOOSE RECOVERY. until someone makes it available for v FB17.
Download: > SPH-D710-user 4.0.3 IML74K FB17 release-keys (wont let me add link see attach txt
[/URL]
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.FB17
ro.build.version.incremental=FB17
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Sat Feb 18 00:38:45 KST 2012
ro.build.date.utc=1329493125
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-29
ro.build.tags=release-keys
ro.product.model=SPH-D710
ro.product.brand=samsung
ro.product.name=SPH-D710
ro.product.device=SPH-D710
ro.product.board=SPH-D710
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SPH-D710
ro.tether.denied=false
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SPH-D710-user 4.0.3 IML74K FB17 release-keys
ro.build.fingerprint=samsung/SPH-D710/SPH-D710:4.0.3/IML74K/FB17:user/release-keys
ro.build.characteristics=phone
# Samsung Specific Properties
ro.build.PDA=SPH-D710.FB17
ro.build.hidden_ver=SPH-D710.FB17
ro.build.changelist=159611
# end build properties
#
# system.prop for smdk4210
#
rild.libpath=/system/lib/libsec-ril40.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
# USB HUB default setting
persist.service.usb.hubport=4
#wlan.driver.apmode "unloaded"
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
ro.sf.lcd_density=240
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=128m
ro.wimax.interface=uwbr0
ro.secdirenc=true
ro.secsddecryption=true
ro.secfulldirenc=true
keyguard.no_require_sim=true
dev.sfbootcomplete=0
dev.powersave_fps=0
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0.3_r0
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
http://hotfile.com/dl/147029833/e0e75ee/signed_SPH-D710.FB17_IML74K.FB17.4.0.3.zip.html
Sent from my SPH-D710 using xda premium
Not able to open it in my browser. Nice though :
Sent from my SPH-D710 using xda premium
hijacking?
why not just download it directly from my host? no dealing with hotfile's slow speeds and wait times :/
EDIT:
whoops learned my lesson down below XD
I'm currently on the latest stock update. No root.
Can I just put this on my SD card and do that update.zip thing? Or do I need to use that weird program. Still new to this. Got my Epic Touch less than 2weeeks ago (in white <3)
shabbypenguin said:
why not just download it directly from my host? no dealing with hotfile's slow speeds and wait times :/
Click to expand...
Click to collapse
maybe this one is pre-rooted shabby..
bubur_bewok said:
maybe this one is pre-rooted shabby..
Click to expand...
Click to collapse
ah right you are!
sorry bout taht my eyes are very blurry. i need to go get me some sleep
What's different from shabbys
Sent from my SPH-D710 using Tapatalk
Will of fire said:
What's different from shabbys
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
i wanna know too
this one is pre rooted ? says it in the op
but shabbys is pre rooted as well
internetaffairs said:
but shabbys is pre rooted as well
Click to expand...
Click to collapse
only shabbys o9 is rooted. he is talking about fb17. downloading now!
he says his FB17 is pre rooted
http://forums.acsyndicate.net/showthread.php?4963-Stock-Flashable-FB17-ICS
is there a difference between that rom and this one?
Anyways, this rom boots fine
so i guess everything but GPS works.
Sent from my SPH-D710 using Tapatalk
internetaffairs said:
he says his FB17 is pre rooted
http://forums.acsyndicate.net/showthread.php?4963-Stock-Flashable-FB17-ICS
is there a difference between that rom and this one?
Click to expand...
Click to collapse
Sorry about that. I read the thread when it first hit. The non rooted tar
Also when you check superuser in this one you can't update it. It says vnull and that damn keyboard error is back until you disable samsung keyboard as primary
Sent from my bad a$$ SAMSUNG GALAXY S|| EPIC TOUCH 4G using xda premium app.
flashed this..dont have su..wifi/3g/4g doesnt work. cant add accounts
Everyone grab the one from shabby over in acs forums. Its cwm flashable and has root
Sent from my bad a$$ SAMSUNG GALAXY S|| EPIC TOUCH 4G using xda premium app.
twoeleven99 said:
flashed this..dont have su..wifi/3g/4g doesnt work. cant add accounts
Click to expand...
Click to collapse
It does have su permissions...just no wifi/3g/4g...basically no way to get online. Thus su permissions is pointless. Also the rooted flashable one over at acs doesn't boot up at all. Guess we gotta wait until morning for a working rooted version lol
Hello
Anyone can upload a unmodified stock build.prop file from Samsung Galaxy Nexus Yakjuzs ICL53F 4.0.2?
The file is under /system
You can access the file by using Root Browser.
I need it to update my phone from 4.0.2 to 4.0.4.
Thank you
antchee said:
Hello
Anyone can upload a unmodified stock build.prop file from Samsung Galaxy Nexus Yakjuzs ICL53F 4.0.2?
The file is under /system
You can access the file by using Root Browser.
I need it to update my phone from 4.0.2 to 4.0.4.
Thank you
Click to expand...
Click to collapse
use YAKJUXW ICL53F..i9250xwkl2 build.prop and edit the device information to Yakjuzs..
manumanfred said:
use YAKJUXW ICL53F..i9250xwkl2 build.prop and edit the device information to Yakjuzs..
Click to expand...
Click to collapse
Or download the stock ROM and pull the build.prop from it.
manumanfred said:
use YAKJUXW ICL53F..i9250xwkl2 build.prop and edit the device information to Yakjuzs..
Click to expand...
Click to collapse
How is he going to know what to change? If he knew that, he prob wouldn't be asking for the file.
JaiaV said:
Or download the stock ROM and pull the build.prop from it.
Click to expand...
Click to collapse
Where is a stock yakjuzs ICL53F ROM?
Sent from my Galaxy Nexus using Tapatalk 2
manumanfred said:
use YAKJUXW ICL53F..i9250xwkl2 build.prop and edit the device information to Yakjuzs..
Click to expand...
Click to collapse
I have already tried that, it failed.
If the build.prop file been edited, update will failed.
Because I have changed the DPI before, and have changed it back,
now any update will fail.
If someone create a backup of the ROM using CWM it will help.
JaiaV said:
Or download the stock ROM and pull the build.prop from it.
Click to expand...
Click to collapse
There is no stock ROM for 4.0.2 Yakjuzs.
The build.prop file cannot be edited.
If it has been edited, any update to the phone will failed.
Now my phone will stay on 4.0.2 until I flashed ot with Yakju.
But my phone has to be running Yakjuzs as other builds do not have the Samsung Chinese input.
And if I flashed my phone, my warranty will be voided .
antchee said:
The build.prop file cannot be edited.
If it has been edited, any update to the phone will failed.
Now my phone will stay on 4.0.2 until I flashed ot with Yakju.
But my phone has to be running Yakjuzs as other builds do not have the Samsung Chinese input.
And if I flashed my phone, my warranty will be voided .
Click to expand...
Click to collapse
If I am not mistaken, takju JRN84D has Chinese input.
As for your warranty, if you do a backup of you yakjzs build, you can always restore it. Besides, I have never heard of Samsung refusing warranty service because of yakju or takju being used...
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
How is he going to know what to change? If he knew that, he prob wouldn't be asking for the file.
Where is a stock yakjuzs ICL53F ROM?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
How he's going to change:
Yakjuzs is not Yakjuwx but if editing the device information in build .prop for Yakjuzs device it might work, just device name needs modifying, other texts should be really similar in all GSM GNex 4.0.2 ROMs..
(it's easy, but might not work if something is badly edited..)
manumanfred said:
How he's going to change:
Yakjuzs is not Yakjuwx but if editing the device information in build .prop for Yakjuzs device it might work, just device name needs modifying, other texts should be really similar in all GSM GNex 4.0.2 ROMs..
(it's easy, but might not work if something is badly edited..)
Click to expand...
Click to collapse
Build.prop files are not similar enough across different builds to just change "yakjuxw" to "yakjuzs" where ever it appears.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Build.prop files are not similar enough across different builds to just change "yakjuxw" to "yakjuzs" where ever it appears.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
example:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ICL53F
ro.build.display.id=ICL53F
ro.build.version.incremental=235179
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.2
ro.build.date=Thu Dec 8 01:24:15 UTC 2011
ro.build.date.utc=1323307455
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs3.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.product.name=yakju
ro.product.device=maguro
ro.product.board=tuna
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=maguro
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=yakju-user 4.0.2 ICL53F 235179 release-keys
ro.build.fingerprint=google/yakju/maguro:4.0.2/ICL53F/235179:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
#
# system.prop for maguro
#
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
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.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
drm.service.enabled=true
camera.flash_off=0
ro.com.google.mcc_fallback=262
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
To ---->
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=ICL53F
ro.build.display.id=ICL53F
ro.build.version.incremental=235179
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.2
ro.build.date=Thu Dec 8 01:24:15 UTC 2011
ro.build.date.utc=1323307455
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs3.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Galaxy Nexus
ro.product.brand=google
ro.product.name=yakjuzs
ro.product.device=maguro
ro.product.board=tuna
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=maguro
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=yakjuzs-user 4.0.2 ICL53F 235179 release-keys
ro.build.fingerprint=google/yakjuzs/maguro:4.0.2/ICL53F/235179:user/release-keys
ro.build.characteristics=nosdcard
# end build properties
#
# system.prop for maguro
#
rild.libpath=/vendor/lib/libsec-ril.so
rild.libargs=-d /dev/ttys0
telephony.lteOnCdmaDevice=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.sf.lcd_density=320
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.config.ringtone=Girtab.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
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.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
keyguard.no_require_sim=true
drm.service.enabled=true
camera.flash_off=0
ro.com.google.mcc_fallback=262
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
if you check Yakjuxw build.prop (stock 4.0.2) it is same, only the device information is different..
EDIT: also if the build is not only ICL53F and it is icl53f.i9250#### then you have to add it to build.prop too..
UTC time text and other maybe not needed to edit because it should still update 4.0.2 if it has the system/etc/updatecmds folder ...?
manumanfred said:
example:
if you check Yakjuxw build.prop (stock 4.0.2) it is same, only the device information is different..
EDIT: also if the build is not only ICL53F and it is icl53f.i9250#### then you have to add it to build.prop too..
UTC time text and other maybe not needed to edit because it should still update 4.0.2 if it has the system/etc/updatecmds folder ...?
Click to expand...
Click to collapse
Not sure what build.prop files you are looking at, but I just looked at yakju 4.0.4 and yakjukr 4.0.4, and there are many differences. See the attachments... And although I don't have yakjuzs or yakjuxw build.prop files handy, I am confident that it applies to those as well...
You cannot just make a few changes without knowing what goes in the fields.
efrant said:
Not sure what build.prop files you are looking at, but I just looked at yakju 4.0.4 and yakjukr 4.0.4, and there are many differences. See the attachments... And although I don't have yakjuzs or yakjuxw build.prop files handy, I am confident that it applies to those as well...
You cannot just make a few changes without knowing what goes in the fields.
Click to expand...
Click to collapse
on those build.prop:s is not really much difference..
but whatever...
I don't think that there is many users with yakjuzs so I don't have yakjuzs build.prop but i know it it is GSM Galaxy Nexus and yakju/yakjuxw/other buil build.prop file (ICL53F) can be edited for yakjuzs which still works and then it should let to update it whatever does the build.prop look like the stock yakjuzs build.prop, only the device information matters if want to flash update, but I'm not pretty sure can it flash the OTA update then, it should let flash it because it overwrites the build.prop to the newer build.prop.. ?
I'm not really Android expert but I've edited build.prop file on ZTE Blade, Samsung Jet (JetDroid), and on Gnex many times and still should have to let update GNex if the build.prop doesn't look 100% same as it have to be..
and my English is not so good, so I don't know did you understood what I wrote..
manumanfred said:
on those build.prop:s is not really much difference..
but whatever...
I don't think that there is many users with yakjuzs so I don't have yakjuzs build.prop but i know it it is GSM Galaxy Nexus and yakju/yakjuxw/other buil build.prop file (ICL53F) can be edited for yakjuzs which still works and then it should let to update it whatever does the build.prop look like the stock yakjuzs build.prop, only the device information matters if want to flash update, but I'm not pretty sure can it flash the OTA update then, it should let flash it because it overwrites the build.prop to the newer build.prop.. ?
I'm not really Android expert but I've edited build.prop file on ZTE Blade, Samsung Jet (JetDroid), and on Gnex many times and still should have to let update GNex if the build.prop doesn't look 100% same as it have to be..
and my English is not so good, so I don't know did you understood what I wrote..
Click to expand...
Click to collapse
Not much difference? Are you joking? They are completely different.
And I can tell you the an update will NOT work if the build.prop file is not EXACTLY the same. The updater-script file checks the MD5 hash of the build.prop. It it does not match, the update will fail.
efrant said:
Not much difference? Are you joking? They are completely different.
And I can tell you the an update will NOT work if the build.prop file is not EXACTLY the same. The updater-script file checks the MD5 hash of the build.prop. It it does not match, the update will fail.
Click to expand...
Click to collapse
Okay!..
One yakjuzs buildprob coming. I have it, just give me couple of hours and I'll post it.
One question though. What changes the values in build prop? Beside changing dpi.
efrant said:
If I am not mistaken, takju JRN84D has Chinese input.
As for your warranty, if you do a backup of you yakjzs build, you can always restore it. Besides, I have never heard of Samsung refusing warranty service because of yakju or takju being used...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Flashing the phone will void the warranty in HK.
I read a lot of posts (Chinese websites) that people got the warranty voided becuase of flashing their Samsung phones.
I found someone have uploaded a 4.0.4 Yakjuzs CWM backup image, if I can't the build.prop file for 4.0.2, I will restore my phone using the backup image.
Emhalwis said:
One yakjuzs buildprob coming. I have it, just give me couple of hours and I'll post it.
One question though. What changes the values in build prop? Beside changing dpi.
Click to expand...
Click to collapse
All I have changed was the DPI, I changed it back and now I can't update to 4.0.4.
I can't wait for your build.prop file. Just make sure it is from 4.0.2 Yakjuzs (GMS) and the file must be unedited/untouched.
You are my only hope!!
now, what are you willing to give in return, since i had to charge my phone, backup my rom, restore my backup then restore my rom again?
kidding, here is your file, good luck updating.
Emhalwis said:
now, what are you willing to give in return, since i had to charge my phone, backup my rom, restore my backup then restore my rom again?
Click to expand...
Click to collapse
Why did you have to do that????
You could have just extracted the one file from your backup without restoring the whole backup...
WARNING:
This contains bootloaders, is for the AT&T Captivate Glide only, will wipe your internal sdcard... Flash at your own risk! No one but you can be held responsible for your actions.
Thanks to Roeni for taking the plunge as the first to flash!
How to Root:
Flash CWM or TWRP with odin, boot into recovery and flash a SuperUser zip.
Download:
http://www.gigashare.in/40e09
MD5: E04C404651BB7E0ED3BF0CD65C24BC9A
Other info:
This is considered beta software until it is officially pushed out by AT&T/Samsung. Leaks do NOT come with changelogs, so don't ask, no one knows. I won't be providing any other versions of this leak, use the oneclick exe or wait for someone else to build a cwm/twrp flashable.
FLAMING or TROLLING:
The thread will be closed and links deleted.
Build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=IMM76D
ro.build.version.incremental=UCLG9
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Fri Jul 27 23:37:33 KST 2012
ro.build.date.utc=1343399853
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-121
ro.build.tags=release-keys
ro.product.model=SGH-I927
ro.product.brand=samsung
ro.product.name=SGH-I927
ro.product.device=SGH-I927
ro.product.board=SGH-I927
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=I927UCLG9
ro.build.hidden_ver=I927UCLG9
ro.build.changelist=970642
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=SGH-I927
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SGH-I927-user 4.0.4 IMM76D UCLG9 release-keys
ro.build.fingerprint=samsung/SGH-I927/SGH-I927:4.0.4/IMM76D/UCLG9:user/release-keys
ro.build.characteristics=default
# end build properties
dalvik.vm.heapsize=64m
ro.opengles.version = 131072
wifi.interface=wlan0
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
#rild.libpath=/system/lib/libril-icera.so
#rild.libargs=-e wwan0
persist.sys.storage_preload=1
#ril.fastdormancy_to=50
# Icera fild
#modem.fild.rootdir=/data/rfs
#modem.fild.blocksize=65528
#modem.fild.baudrate=3500000
#modem.fild.hif=0
#modem.fild.coredump=enabled
#modem.fild.coredumpdir=/data/rfs/data/debug
#modem.powercontrol=disabled
#modem.power.device=/sys/class/gpio/gpio169/value,0,1
#ro.ril.devicename=/dev/ttyACM1
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-att-us
ro.com.google.clientidbase.am=android-att-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.error.receiver.default=com.samsung.receiver.error
ro.monkey=0
ro.com.google.gmsversion=4.0_r3
ro.config.ringtone=ATT_Firefly.ogg
ro.config.notification_sound=S_Sherbet_Default_message.ogg
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.kernel.qemu=0
ro.secdirenc=true
ro.secsddecryption=true
ro.secfulldirenc=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Nice. Darn on vacation an cant flash on my glide but directing dman right away...
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
Will post a superuser zip tonight.
DO NOT FLASH YET IF YOU NEED ROOT!
I really want to try it, but i am affraid of bricking my device!
I'm literally on the other side of the world right now and cannot afford to take the risk. And I've got the Rogers' version, so it might backfire if it does some kind of strict device ID checking(even if there is no hardware difference!).
I can say the download seems legit/safe. No viruses and when you run it you get an Odin-like interface! So excited, wish I could take the plunge...!
HELL YEAH!
Tested working so far:
- GSM Network (Germany)
- Edge
- Wifi
- Camera
- Audio
See this thread for a full list of the things i've tested so far: http://forum.xda-developers.com/showpost.php?p=30184848&postcount=17
Roeni said:
https://www.dropbox.com/s/z1re33jg5of55fs/2012-08-14%2000.25.28.jpg
HELL YEAH!
Click to expand...
Click to collapse
Thanks for the image! I will put it in the op!
Is it running smooth?
designgears said:
Thanks for the image! I will put it in the op!
Is it running smooth?
Click to expand...
Click to collapse
So far there are no issues.
I'm connected to my wifi, downloaded some updates from play store, successfully sent an sms. for some other tests see my post above.
---
...a LOT of Blot is installed xD
Excellent, looking forward to installing this tonight.
I'm about to try. Thank you!
The only thing holding me back is lack of root. I can't wait.
antharr said:
The only thing holding me back is lack of root. I can't wait.
Click to expand...
Click to collapse
lack of root?
just flash cwm recovery with odin and flash the ICS superuser zip.
designgears said:
lack of root?
just flash cwm recovery with odin and flash the ICS superuser zip.
Click to expand...
Click to collapse
Sorry. I was under the impression that this was leaked and stock. Thank you for providing this. You sir......are awesome!
It boots on i927r (Rogers) and everything seems to be working properly!
Just a question for those who have flashed
Is it touchwiz 4 or UX ( the tw that comes on the gsiii?)
Hopefully this is all dman needs to get stock aosp... or better yet my favorite on my gsiii aokp
Sent from my SGH-I747 using xda premium
designgears said:
lack of root?
just flash cwm recovery with odin and flash the ICS superuser zip.
Click to expand...
Click to collapse
Where can i find this superuser.zip?
Aquethys said:
Just a question for those who have flashed
Is it touchwiz 4 or UX ( the tw that comes on the gsiii?)
Hopefully this is all dman needs to get stock aosp... or better yet my favorite on my gsiii aokp
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Settings -> Applications says: TwLauncher Version 4.0.4-UCLG9
Did you mean this?
Gab1288 said:
Where can i find this superuser.zip?
Click to expand...
Click to collapse
I Second This!
superuser zip
Worked on my galaxy s 3...should work on you guys. If not Google is your friend. If it does work OP feel free to add it
MAKE A NANDROID Backup!
By the by, can someone pull the proprietary files so dman can finish aosp ICS?
Feel free to hit thanks
Sent from my SGH-I747 using xda premium
Aquethys said:
superuser zip
Worked on my galaxy s 3...should work on you guys. If not Google is your friend. If it does work OP feel free to add it
MAKE A NANDROID Backup!
By the by, can someone pull the proprietary files so dman can finish aosp ICS?
Feel free to hit thanks
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
How do i extract them?
If it helps, I could flash this leak, and then make a back-up using CWM and provide it somehow? Could the drivers be pulled from that? Just let me know!
-> Text follows tommorrow <-
Downloadlink:
https://twrp.me/devices/sonyxperiaz1.html
Sent from my mint using XDA Free mobile app
woooow
SdtBarbarossa said:
-> Text follows tommorrow <-
Downloadlink:
https://twrp.me/devices/sonyxperiaz1.html
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
This build does not work on my Z1. I removed TWRP from my boot.img, then put your image in Fota (dd et all), but it never starts. I then erased recovery and installed your image the classic way: fastboot flash recovery recovery.img with the same result.
On the other hand, when I took recovery.img from my rom and put it in FOTA, it worked fine. Did you build your image with all the required flags? The only ones who do it properly are Slimrom guys. You might want to take a look at their device_sony_rhine-common as well as twrp.stub for proper flags...
optimumpro said:
This build does not work on my Z1. I removed TWRP from my boot.img, then put your image in Fota (dd et all), but it never starts. I then erased recovery and installed your image the classic way: fastboot flash recovery recovery.img with the same result.
On the other hand, when I took recovery.img from my rom and put it in FOTA, it worked fine. Did you build your image with all the required flags? The only ones who do it properly are Slimrom guys. You might want to take a look at their device_sony_rhine-common as well as twrp.stub for proper flags...
Click to expand...
Click to collapse
That sounds mysterical... Because a main tester had confirmed this to work as a fotakernel recovery... Can you test again?
Sent from my mint using XDA Free mobile app
SdtBarbarossa said:
That sounds mysterical... Because a main tester had confirmed this to work as a fotakernel recovery... Can you test again?
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
Not working. It flashes fine, but is not starting.
Works fine on my Z1..
Only brightness settings not working but I don't need them anyway
What's new in this build?
mateo1111 said:
Works fine on my Z1..
Only brightness settings not working but I don't need them anyway
Click to expand...
Click to collapse
OK. It only works on latest boodloaders and it does not work on original ones. TWRP with working brightness is available...
optimumpro said:
OK. It only works on latest boodloaders and it does not work on original ones. TWRP with working brightness is available...
Click to expand...
Click to collapse
Ok thx for information
The brightness stuff i fix soon...
Whats the different? Not much ... Its simply the official one from twrp and it will be automatically updated...
Hawkeyexp will soon be the maintainer
Sent from my mint using XDA Free mobile app
SdtBarbarossa said:
Ok thx for information
The brightness stuff i fix soon...
Whats the different? Not much ... Its simply the official one from twrp and it will be automatically updated...
Hawkeyexp will soon be the maintainer
Sent from my mint using XDA Free mobile app
Click to expand...
Click to collapse
Any hope for adding official support for Amami (Z1c)?
They are very similar after all, shouldn't be too much work afaik
o-l-a-v said:
Any hope for adding official support for Amami (Z1c)?
They are very similar after all, shouldn't be too much work afaik
Click to expand...
Click to collapse
im VERRY bussy atm with the whole new stuff for XL XT and cm13... is there no ither dev that can handle it,? if not tell me...
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
im VERRY bussy atm with the whole new stuff for XL XT and cm13... is there no ither dev that can handle it,? if not tell me...
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Hey!
So sadly there is still no official Amami TWRP. Here is a edited version of the honami recovery which seems to work well. THe author also shows the changes he applied. Can you apply those changes in order to get official builds?
http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-3-0-0-0-amami-t3310794
Here the changes:
Verbato said:
For the curious ones, default.prop:
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.zygote=zygote32
rild.libpath=/system/vendor/lib/libril-qc-qmi-1.so
persist.sys.usb.config=mtp,adb
dalvik.vm.dex2oat-Xms=64m
dalvik.vm.dex2oat-Xmx=512m
dalvik.vm.image-dex2oat-Xms=64m
dalvik.vm.image-dex2oat-Xmx=64m
ro.dalvik.vm.native.bridge=0
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=14.4.A.0.157
ro.build.display.id=14.4.A.0.157
ro.build.version.incremental=Yv__jQ
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=4.4.4
ro.build.date=Fri Feb 5 19:51:36 EST 2016
ro.build.date.utc=1454719896
ro.build.type=eng
ro.build.user=jenkins
ro.build.host=build
ro.build.tags=test-keys
ro.build.flavor=cm_amami-eng
ro.product.brand=Sony
ro.product.name=D5503
ro.product.board=MSM8974
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8974
# ro.build.product is obsolete; use ro.product.device
ro.build.product=amami
ro.product.model=Xperia Z1C
ro.product.device=amami
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=D5503-user 4.4.4 14.4.A.0.157 Yv__jQ release-keys
ro.build.fingerprint=Sony/D5503/D5503:4.4.4/14.4.A.0.157/Yv__jQ:user/release-keys
ro.build.characteristics=default
ro.cm.device=amami
# end build properties
#
# from device/sony/amami/system.prop
#
# Graphics
ro.sf.lcd_density=320
# USB path
ro.usb.pid_suffix=1A7
ro.use_data_netmgrd=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
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.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
persist.sys.dun.override=0
media.sf.omx-plugin=libffmpeg_omx.so
media.sf.extractor-plugin=libffmpeg_extractor.so
persist.sys.root_access=0
ro.cm.version=12.1-20160206-UNOFFICIAL-amami
ro.cm.releasetype=UNOFFICIAL
ro.modversion=12.1-20160206-UNOFFICIAL-amami
ro.cmlegal.url=https://cyngn.com/legal/privacy-policy
persist.sys.recovery_update=false
ro.cm.display.version=12.1-20160206-UNOFFICIAL-amami
ro.cm.build.version.plat.sdk=2
ro.cm.build.version.plat.rev=0
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Helium.ogg
ro.config.ringtone=Orion.ogg
ro.carrier=unknown
camera2.portability.force_api=1
sys.io.scheduler=bfq
ro.telephony.default_network=9
telephony.lteOnCdmaDevice=0
telephony.lteOnGsmDevice=1
persist.radio.apm_sim_not_pwdn=1
persist.radio.add_power_save=1
persist.radio.oem_socket=true
persist.radio.data_no_toggle=1
persist.radio.calls.on.ims=0
ro.telephony.call_ring.multiple=0
ro.qualcomm.perf.cores_online=2
ro.vendor.extension_library=libqti-perfd-client.so
ro.telephony.ril_class=SonyRIL
persist.sys.isUsbOtgEnabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
persist.hwc.mdpcomp.enable=true
ro.opengles.version=196608
wlan.driver.ath=0
audio.offload.buffer.size.kb=32
audio.offload.gapless.enabled=false
audio.offload.multiple.enabled=false
audio.offload.pcm.enable=enable
av.offload.enable=enable
av.streaming.offload.enable=enable
media.aac_51_output_enabled=true
ro.qc.sdk.audio.fluencetype=none
persist.audio.dualmic.config=endfire
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true
ro.qualcomm.sensors.qmd=true
debug.qualcomm.sns.hal=w
ro.qc.sdk.sensors.gestures=false
ro.qc.sensors.max_accel_rate=false
ro.qc.sensors.max_gyro_rate=false
ro.qc.sensors.max_mag_rate=false
ro.qc.sensors.smgr_mag_cal_en=true
ro.qualcomm.sensors.pedometer=false
ro.qc.sensors.step_counter=true
ro.qc.sensors.step_detector=true
ro.qualcomm.sensors.pam=false
ro.qualcomm.sensors.scrn_ortn=false
ro.qualcomm.sensors.georv=true
ro.qualcomm.sensors.smd=sony
ro.qualcomm.bt.hci_transport=smd
persist.gps.qc_nlp_in_use=0
ro.gps.agps_provider=1
ro.qc.sdk.izat.premium_enabled=1
ro.qc.sdk.izat.service_mask=0x0
persist.demo.hdmirotationlock=false
debug.mdpcomp.logs=0
persist.timed.enable=true
ro.input.noresample=1
persist.debug.wfd.enable=1
persist.sys.wfd.virtual=0
ro.hwui.texture_cache_size=72
ro.hwui.layer_cache_size=48
ro.hwui.r_buffer_cache_size=8
ro.hwui.path_cache_size=32
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=6
ro.hwui.texture_cache_flushrate=0.4
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=192m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.features=div
ro.kernel.android.checkjni=1
dalvik.vm.image-dex2oat-filter=verify-none
dalvik.vm.dex2oat-filter=interpret-only
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
It would be great if this is enough to get official Amami!
Thank you very much
[GER]Roxxor said:
Hey!
So sadly there is still no official Amami TWRP. Here is a edited version of the honami recovery which seems to work well. THe author also shows the changes he applied. Can you apply those changes in order to get official builds?
http://forum.xda-developers.com/sony-xperia-z1-compact/general/fota-twrp-3-0-0-0-amami-t3310794
Here the changes:
It would be great if this is enough to get official Amami!
Thank you very much
Click to expand...
Click to collapse
nope thats NOT enought for official support .... you need a mainatiner ... someone who can build FROM SOURCE... if you know someone that want to make it he can pm me and i will explain everything to him
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
nope thats NOT enought for official support .... you need a mainatiner ... someone who can build FROM SOURCE... if you know someone that want to make it he can pm me and i will explain everything to him
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
I would certainly be interested.
2 Problems:
1. Last time I built was Android 2.3 (some time ago )
2. I can write bash scripts. That’s about it.
But as Amami is very close to Honami, I guess not that much coding would be needed.
Is it enough for a maintainer to build and test new versions and in case of bugs report them, or is coding required?
[GER]Roxxor said:
I would certainly be interested.
2 Problems:
1. Last time I built was Android 2.3 (some time ago )
2. I can write bash scripts. That’s about it.
But as Amami is very close to Honami, I guess not that much coding would be needed.
Is it enough for a maintainer to build and test new versions and in case of bugs report them, or is coding required?
Click to expand...
Click to collapse
coding is required aswell... if something dont work you will need to fix it
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
coding is required aswell... if something dont work you will need to fix it
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
Ok. So I guess I will just for fun try to build it for myself.
I can stick to this guide, right? http://forum.xda-developers.com/showthread.php?t=1943625
Could you share your manifest for honami maybe? That would save me from a lot trial & error...
Thank you
[GER]Roxxor said:
Ok. So I guess I will just for fun try to build it for myself.
I can stick to this guide, right? http://forum.xda-developers.com/showthread.php?t=1943625
Could you share your manifest for honami maybe? That would save me from a lot trial & error...
Thank you
Click to expand...
Click to collapse
i have no special manifest (dont have the tree on.my pc... only on twrp server)
you simply need a full cm12.1 OR cm13 OR Omnirom tree
Sent from my Xperia T using XDA Free mobile app
I have installed XZDual recovery. It has TWRP 2.8.7. I wanted to install Twrp 3.0.0. So i downloaded the image officiall twrp 3.0.0 image for my device (Xperia Z1 5.1.1) and flashed it with recovery. After that when turning on the device it only vibrates. No display.
Why is that
ytheekshana said:
I have installed XZDual recovery. It has TWRP 2.8.7. I wanted to install Twrp 3.0.0. So i downloaded the image officiall twrp 3.0.0 image for my device (Xperia Z1 5.1.1) and flashed it with recovery. After that when turning on the device it only vibrates. No display.
Why is that
Click to expand...
Click to collapse
because you flashed it on boot i guess.... newbie mistake... flash your old kernel ....
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
because you flashed it on boot i guess.... newbie mistake... flash your old kernel ....
Click to expand...
Click to collapse
When installing the image, I selected the partition as Kernel.
Please Describe a way step by step. I am quite new to this. Now my device is normal with XZDual recovery. How do I install TWRP 3.0