[REF] Build prop terminology [INFO] - HTC Pico (Explorer)

Hello again fellow members ! I bring you yet another thread for reference thread ( read BORING ) , for our tiny community , here at xda-developers.com.
This is a reference thread about the build.prop that is found in our phones.
First up is the disclaimer :
Code:
#include<disclaimer.h>
$ Whatever you will be doing here is through root !
$ So whatever happens to your phone before or after editing something is purely your mistake.
$ If you blame me, I will blame you for not reading this.
What is the build.prop ?
> Build properties or build.prop is a file in your android system that maintains certain parameters on your phone in order for your phone to run.
> These properties are device specific and can change depending upon the various specifications of the device and also includes some system properties i.e. some properties that have to be defined in the build prop for a particular software ( Read ROM ) to run on it.
Click to expand...
Click to collapse
Where is this build.prop of yours located ?
> The build.prop of any ROM of our phone is located at
Code:
/system/build.prop
To access it via phone :
Download and install a root browser.
Allow it root access. (Obviously)
If you start up " /sdcard/ " then navigate UP to the root of your phone.
Go to /system folder.
Note 1: You can edit it using a text editor. ( Most root browsers have this feature ).
Note 2: There are a few apps that can be used to edit build.prop. Check out the playstore.
Click to expand...
Click to collapse
Now , time for the terminologies.
I will split the build prop into 2 sections :
Standard build properties
Additional build properties
Here is a reference View attachment build.prop.txt. You can keep referring to it while you are reading this guide/tutorial.
Standard build properties
So the normal build properties start with:
Code:
# begin build properties
# autogenerated by buildinfo.sh
This mentions that the build prop is built by build info shell script during the compilation of the ROM.
Code:
ro.build.id=JZO54K
ro.build.display.id=cm_pico-userdebug 4.1.2 JZO54K eng.sakindia123.20121117.161006 test-keys
ro.build.version.incremental=eng.sakindia123.20121117.161006
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Sat Nov 17 16:10:21 GMT 2012
ro.build.date.utc=1353168621
ro.build.type=userdebug
ro.build.user=sakindia123
ro.build.host=build1
ro.build.tags=test-keys
1) First up the build id (Here JZO54K) is the build id for the version number for Jellybean 4.1.2.
2) It is the version of the ROM which appears in the about phone. This is a cm10 build by sakindia123.
3) This is the software development kit version which is needed and used for building the ROM.
4) 3's codename.
5) This is the android version of the ROM.
6) This is the time and date of when the ROM and Kernel were built together. (ROM only).
7) More details on the kernel.
8) Read 7.
9) Userdebug ROMs has usb debugging set to 0 and eng are for general release.
10) Name of the person building the ROM & kernel.
11) -
12) Test keys suggests that the ROM is not an official version of the ROM. Release keys are for official releases.
Code:
ro.product.model=HTC Explorer A310e
ro.product.brand=htc_europe
ro.product.name=pico
ro.product.device=pico
ro.product.board=pico
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x27a
# ro.build.product is obsolete; use ro.product.device
ro.build.product=pico
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cm_pico-userdebug 4.1.2 JZO54K eng.sakindia123.20121117.161006 test-keys
ro.build.fingerprint=htc_europe/htc_pico/pico:2.3.5/GRJ90/207463.1:user/release-keys
ro.build.characteristics=default
ro.cm.device=pico
# end build properties
#
This part of the build prop shows the information about our phone and not the build of the ROM of our phone.
1) Model of our device
2) Brand of device. ( In some case carrier ) for which the android version has been made for.
3) Name is an alternative ( codename ) of the device during its development. For Explorer its pico, for Nexus 7 : grouper for Nexus 4 : mako for SG Ace its cooper etc.
4) -
5) -
6) It is the first instruction set (CPU + ABI convention type) of the code. Ours is an arm type arch cpu and abi version 7a )
7) It is the second instruction set type. ( like 6)
8) Name of manufacturer.
9) Language of the software ( read ROM)
10) Region of operation of software.
11) -
12) Name of board on which software has been built.
13) -
14 , 15 and 16. IMP: Never attempt to modify this value ! This can lead to bootloop (possibly hard brick) of your phone. This is the unique fingerprint of the software of your phone.
Now time for the system properties ! .
RIL properties:
What is RIL ?
A Radio Interface Layer (RIL) is a layer in an operating system which provides an interface to the hardware's radio and modem on e.g. a mobile phone.
Code:
rild.libpath=/system/lib/libhtc_ril.so
rild.libargs=-d /dev/smd0
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
ril.subscription.types=NV,RUIM
ro.baseband.arch = msm
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-Dutch=112
ro.ril.ecc.HTC-SPA=112, 911,112, 911
ro.ril.ecc.HTC-FRA=112,911
ro.ril.ecc.HTC-ITA=112,911
ro.ril.ecc.HTC-EastEurope=112
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.hsdpa.category=8
ro.ril.hsxpa=1
ro.ril.fast.dormancy.rule=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411,23420,27202
ro.ril.enable.managed.roaming=1
ro.ril.gprsclass=10
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
ro.telephony.ril.v3=signalstrength,singlepdp,skipbrokendatacall
ro.ril.htcmaskw1.bitmask = 4294967295
ro.ril.htcmaskw1 = 14449
ro.ril.update.acoustic.table = 1
ro.ril.avoid.pdp.overlap = 1
ro.telephony.default_network = 0
1,2, and 3) : These are basically the links between your phones hardware and software , i.e. it tells your phone where to find the libs for RIL and also detects whether you have any arguments in place of the operation of your libs to provide to the vendor.
4) -*-
5) Architecture of baseband radio.
6,7,8,9,10,11,12) Syntax :
Code:
ro.ril.ecc.HTC-xxx=nnn,nnn,nnn
These are basically the emergency call numbers(codes) for your phone. Its different according to your region. ( here xxx ) . The numbers can be 911 , 101,100 etc etc ( here nnn)
13,14,15,16) Something to do with GPRS, AFAIK.
17) HSDPA category : High speed downlink packet access category. ( 8 == 7.2 mbit/s )
18) HSXPA : High speed ( type ) packet . ( values 1- HSDPA 2-HSDPA/HSUPA ( High speed uplink packet access )
19) Something to do with 3G.
20) -*-
21) Ability of enabling data roaming.
22) Class of GPRS network that needs to be routed to phone.
23) No sim emergency call codes list
24) -*-
25) This is somehow related to mobile data and its stablility. ( adding skipbrokendatacall adds stability ).
26) -*-
27) -*-
28) Related to ril audio.
29) -*-
30) Default type of data connection.
Code:
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval=180
wifi.interface=eth0
wifi.softap.interface=eth0
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
# View configuration for QVGA
view.fading_edge_length = 8
view.touch_slop = 15
view.minimum_fling_velocity = 25
view.scroll_friction = 0.008
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# For no auto focus devices
ro.workaround.noautofocus = 1
# Increase SKIA decode memory capability for progressive jpg file
ro.media.dec.jpeg.memcap = 20000000
# For QC perf binary hooks
# src:vendor/qcom/proprietary/android-perf/release/lib/<CPU arch>/libqc-opt.so
ro.vendor.extension_library=/system/lib/libqc-opt.so
Please read the hashed out lines : It is selfexplanatory.
Code:
# Misc.
DEVICE_PROVISIONED=1
htc.audio.alc.enable = 1
htc.audio.swalt.enable = 1
dalvik.vm.heapsize=48m
ro.opengles.version = 131072
debug.composition.7x27A.type=mdp
media.stagefright.enable-player=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
ro.staticwallpaper.pixelformat=RGB_565
ro.max.fling_velocity=4000
httplive.enable.discontinuity=true
dev.pm.dyn_samplingrate=1
dev.pm.dyn_sample_period=700000
com.qc.hardware=true
com.qc.hdmi_out=false
debug.camcorder.disablemeta=0
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.enabletr=false
debug.sf.hw=1
ro.media.enc.jpeg.quality=100
ro.setupwizard.mode=OPTIONAL
hwui.print_config=choice
hwui.disable_vsync=true
ro.setupwizard.enable_bypass=1
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.config.sync=yes
ro.phone_storage=0
ro.hw_plat=7x27a
#Hwui
hwui.use.blacklist=true
1) There is a provision.apk in system/app requires this line.
2,3) Enabling certain audio libs.
4) Least amount of RAM that can be given to any application to run.
5) OpenGL 2.x.x
6) this is actually the software composition method. CAF suggests mdp for msm7x27a boards
7,8,9,10,11,12) media.stagefright is nothing but the type of media framework that is being supported and its various properties are in the build.prop. ( type of media playback : local media as well as online streaming like 3gp mpeg mp4 etc etc ).
13) It is the pixel format of RGB 565 with a constant value of 4
14) Something to do with app + data cache.
15) Self explanatory
16) Some thing with surface flinger hardware, aka our gpu.( probably framerate)
17) HTML Related.
18,19) Probably sampling rate of all media. ( Sound , picture quality etc etc . )
20) Something to do with the processes of above names.
21,22,23,24)-*-
25) debug surface flinger hardware. One of the best known tweaks , i.e. GPU Hardware acceleration.
26) Encoding media quality (jpeg)
27) Setupwizard ( google or otherwise ) enabling
28,29) Related to Hardware acceleration settings. (?)
30) By pass setup wizard.
31,32) Media decoding of audio and video of wma and wmv formats respectively.
33) Sync enabled at bootup.
34) something to do with phone storage. ( probably install location .. not sure)
35) hardware platform. msm7x27a.
36) Something to do with hwui. (?)
Next post for additional build properties. !
The points with " -*- " are unknown properties to me.. Please mention them if you know what they mean.
The points with " -- " are points that are either too obvious or are repeated.
All corrections are welcome. I know this post has many mistakes , please feel free to correct them. A huge shout out to sakindia123 for correcting my mistakes. Thanks mate. This is supposed to be a sort of database of information. Please do your bit and contribute !

I will reserve this one. for one more update.

very usefull post...thanks bro

Useful thread
@OP
Can I add ur thread to my guides threads??
Sent from my HTC Explorer A310e using xda premium

Hpsgill said:
Useful thread
@OP
Can I add ur thread to my guides threads??
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
Sure bro go ahead.

Useful thread..
Just one question ~14,15,16...do not attempt to change?
Really hard brick? How?
Or just a joke
And it would be better, if the numbers were also in build.pros codes
『Moved by touch™』 ?
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E

ptcpayme said:
Useful thread..
Just one question ~14,15,16...do not attempt to change?
Really hard brick? How?
Or just a joke
And it would be better, if the numbers were also in build.pros codes
『Moved by touch™』 ?
LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E
Click to expand...
Click to collapse
That was meant for trolling . . Will add the numbering.. when I get sometime. Just need sometime

my phone has stopped working on google servince what should i do

Related

What Version is this Xoom? Brazilian?

This came from a brazilian store...
I flashed a mod that replaced my framework-res.apk, but now I can't find the original one (my bad not to backup)
from the build.prop: (it says H.6.2-21)
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=H.6.2-21
ro.build.display.id=H.6.2-21.1300904098
ro.build.version.incremental=1300904098
ro.build.version.sdk=11
ro.build.version.codename=REL
ro.build.version.release=3.0.1
ro.build.date=Wed Mar 23 12:18:06 CDT 2011
ro.build.date.utc=1300900686
ro.build.type=user
ro.build.user=a22916
ro.build.host=il93lnxdroid47
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=MZ604
ro.product.brand=MOTO
ro.product.name=PORTLA
ro.product.device=wifi_hubble
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=wifi_hubble
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=wifi_hubble-user 3.0.1 H.6.2-21 1300904098 ota-rel-keys,release-keys
ro.build.fingerprint=MOTO/PORTLA/wifi_hubble:3.0.1/H.6.2-21/1300904098:user/ota-rel-keys,release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
# RIL and telephony related settings
rild.libargs=-d /dev/chnlat10
rild.libpath=/system/lib/libmoto_ril.so
persist.ril.mux.ttydevice=/dev/usb/tty2-1:1.2
persist.ril.mux.noofchannels=8
persist.ril.modem.mode=1
persist.ril.modem.ttydevice=/dev/usb/tty2-1:1.4
ro.telephony.default_network=4
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.version.full=Blur_Version.6.2.21.MZ604.Brasil.en.BR
ro.mot.setuptype=2
ro.config.ringtone=Sceptrum.ogg
ro.config.notification_sound=Cobalt.ogg
ro.config.alarm_alert=Cesium.ogg
keyguard.no_require_sim=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=3.0_r4
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.ms=android-motorola
Does any one have the same version????
Config ... About Tablet ... Version Number (last item) says "H.6.2-21.1300904098"
Yeah, it's Brazilian. Look at the build number und additional build properties. Have you tried flashing the us mz604 framework-res.apk? You should be able to fastboot flash the boot.img and system.img to the us wifi images and be fine.
Sent from my Xoom using Tapatalk
So I have 2 questions...
1) Can I use the canadian one??? as it have the brazilian portuguese translation??
2) How can I make a system.img and boot.img from my xoom, just in case something goes wrong so I can restore to as it is now?
The US framework-res.apk give me lots of FC
I have two framework-res.apk that works, both seens canadian, but I'm not sure... one, kinda works, but have some glitches the other have no glitches, but the market stops working
I'm afraid US or Canadian system.img & boot.img will not work... do I have reson to be afraid?
judison said:
2) How can I make a system.img and boot.img from my xoom, just in case something goes wrong so I can restore to as it is now?
Click to expand...
Click to collapse
Yes, in Clockwork Mod Recovery do a nandroid backup.
judison said:
I'm afraid US or Canadian system.img & boot.img will not work... do I have reson to be afraid?
Click to expand...
Click to collapse
The have been reports that the us image works on canadian MZ604s, so try it after making a nandroid backup.
I have flashed the canadian system.img & boot.img
It worked
(after that, I re-rooted it)
now I'm thinking about flashing the US Wifi Image, because most MODs are based on it...
but I will lose the brazilian portuguese translation, right?

[Q] CM10.1 AOSP 4.2.2 Jellybean Wifi region code lost after reboot / no channel 13 ?

This post should go into the "CyanogenMod 10.1 Jellybean 4.2.2 - KANG" thread (http://forum.xda-developers.com/showthread.php?t=2115520) but unfortunately I do not have enough "status" to post there.
I have noticed that the The advanced WIFI setting "Wi-Fi Region code" does not survives reboots, this would prevent my phone (HTC Sensation) from using channel 13.
It is my understanding that the following must be present in the phone to enable wifi channel 13:
In build.prop:
Code:
ro.product.locale.region=UK
ro.wifi.channels=13
In /data/data/com.android.providers.settings/databases/settings.db (secure table):
Code:
wifi_country_code UK
wifi_num_allowed_channels 13
However even after selecting "Europe" in the wifi advanced settings, this is what I have:
In build.prop:
Code:
ro.product.locale.region=US
ro.wifi.channels=
There are no wifi_country_code / wifi_num_allowed_channels in the secure table in /data/data/com.android.providers.settings/databases/settings.db:
Code:
[email protected]:/system # sqlite3 /data/data/com.android.providers.settings/databases/settings.db "SELECT * FROM secure WHERE name LIKE '%wifi%';"
gs.db "SELECT * FROM secure WHERE name LIKE '%wifi%';" <
2|wifi_watchdog_watch_list|GoogleGuest
I was wondering if this is a bug relates to Albinoman's work, or if it is something common to all Cyanogenmod 10.1 based ROMs.
Could the moderators please move this message in the appropriate thread?
Thank you.

[DUMP][4.4.2] - I535VRUDNE1-Dump / Dev Discussion ONLY!

First of all if you are NOT a developer please do not post in this thread. This will be the one and only time I am stringent in my request. If you want to thank me or anyone who works on this project then just hit the Thanks button.
Also, Developer is just a title given by XDA. There are many developers out there without the XDA anointed title. If you are one then please feel fee to join the discussion if can contribute anything of value!
Here is how I got this dump...
I built an unmodified Stock NC1 ROM from Odin TAR. I then applied patch from hre: [Update Zip] Kitkat 4.4 update.
I removed all the SBL's and the aboot from the patch as well as neutered the stock recovery image so they would not flash to the device
Dump will not boot. We (Beanstown106, Open1Your1Eyes1, Invlisiblek) think it may be firmware / kernel related as I tried on a MF1 based device with unlocked bootloader.
Here is the Build.Prop pulled while in reccovery
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=KOT49H
ro.build.display.id=KOT49H.I535VRUDNE1
ro.build.version.incremental=I535VRUDNE1
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.date=Tue May 20 00:16:48 KST 2014
ro.build.date.utc=1400512608
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD5809
ro.build.tags=release-keys
ro.product.model=SCH-I535
ro.product.brand=Verizon
ro.product.name=d2vzw
ro.product.device=d2vzw
ro.product.board=MSM8960
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=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=d2vzw
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=d2vzw-user 4.4.2 KOT49H I535VRUDNE1 release-keys
ro.build.fingerprint=Verizon/d2vzw/d2vzw:4.4.2/KOT49H/I535VRUDNE1:user/release-keys
ro.build.characteristics=verizon
# Samsung Specific Properties
ro.build.PDA=I535VRUDNE1
ro.build.hidden_ver=I535VRUDNE1
ro.build.changelist=1542239
ro.product_ship=true
ro.chipname=MSM8960
persist.sys.storage_preload=1
ro.build.knox.container=
# end build properties
#
# from device/samsung/d2vzw/system.prop
#
#
# system.prop for surf
#
# Evolution RIL (8xxx)
rild.libpath=/system/lib/libsec-ril.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
debug.egl.hw=1
debug.composition.type=dyn
persist.hwc.mdpcomp.enable=true
debug.compbypass.enable=1
debug.hwui.render_dirty_regions=true
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
debug.mdpcomp.maxlayer=3
#
# system props for the cne module
#
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.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=0
#
# System prop for Tvout/HDMI
#
persist.sys.camera.connect=0
persist.sys.videomode=0
ro.hdmi.enable=true
lpa.decode=true
lpa.use-stagefright=true
audio.offload.disable=1
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
#
# system props for call volume steps
#
ro.config.vc_call_vol_steps=7
# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
#
# system property for Bluetooth Handsfree Profile version
#
ro.bluetooth.hfp.ver=1.6
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0
#system prop for switching gps driver to qmi
persist.gps.qmienabled=true
# System property for cabl
ro.qualcomm.cabl=1
#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true
#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048
#
# Supports warmboot capabilities
#
ro.warmboot.capability=1
ro.sf.lcd_density=320
# System property for Default touch key light duration - commented out since default is 1500
#ro.button_key_light=6000
# System property for HDMI/WFD
persist.sys.camera.connect=0
persist.sys.camera.transform=0
persist.sys.videomode=0
# Use CDMALTE Phone
telephony.lteOnCdmaDevice=1
# Enable time services daemon
persist.timed.enable=true
# Keep SIM state on LPM mode
persist.radio.apm_sim_not_pwdn=1
# Don't wait the card state for RADIO POWER request
persist.radio.no_wait_for_card=1
# For sys info indication
persist.radio.add_power_save=1
# Snapshot Setting
persist.radio.snapshot_enabled=1
persist.radio.snapshot_timer=22
# Control EONS (true = EONS enabled, false = EONS disabled)
persist.eons.enabled=false
# Data modules
ro.use_data_netmgrd=false
# Use CP SE13 Table
persist.radio.use_se_table_only=1
# Default ECCList
ro.ril.ecclist=911,#911,*911
# Support Global Mode (Global Mode project)
ro.config.multimode_cdma=1
ro.telephony.default_network=10
# Restore delay of the default network - 30 mins (VZW)
android.telephony.apn-restore=1800000
# Restore delay of VZW Apps APN - 1 min (VZW)
vzw.telephony.appsapn-restore=60000
# Use data service state for signal display (Except SPR / USC / BST / VMU / CRI CS devices. PS ONLY devices use this property)
ro.config.combined_signal=true
# Retry Timer (VZW)
ro.gsm.data_retry_config=max_retries=infinite,5000,5000,60000,120000,480000,900000
# system property for vmware hypervisor running
vmware.hypervisor.running=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.vendor.extension_library=/vendor/lib/libqc-opt.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=1m
dalvik.vm.heapmaxfree=4m
ro.build.scafe=americano
ro.build.scafe.syrup=sugar
ro.build.scafe.size=short
ro.hdcp2.rx=tz
ro.sec.fle.encryption=true
ro.secwvk=144
ro.securestorage.knox=true
ro.monkey=0
ro.config.ringtone=Verizon_Airwaves_1.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Over_the_horizon_Acoustic.ogg
ro.error.receiver.default=com.samsung.receiver.error
ro.setupwizard.mode=OPTIONAL
ro.com.google.apphider=off
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-verizon
ro.com.google.clientidbase.am=android-verizon
ro.com.google.clientidbase.yt=android-verizon
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.4.2_r2
ro.HorizontalVVM=true
persist.sys.dalvik.vm.lib=libdvm.so
ro.kernel.qemu=0
ro.build.selinux=1
ro.config.knox=v30
ro.config.tima=1
ro.config.timaversion=2.0
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
ro.qc.sdk.izat.service_mask=0x0
persist.gps.qc_nlp_in_use=1
ro.gps.agps_provider=1
You can download the dump (/system and boot.img) from HERE: http://goo.im/devs/scrosler/vzw-sgs3//I535VRUDNE1-Dump.7z
If you can help figure out the non boot then great! Join in.
Once again this is for people that want to contribute to the development of 4.4.2 on UNLOCKED devices.
Please no Thank you Posts, no ETA Posts, etc....
I just want to get this ***** running!
-Scott
Here are my findings thus far (not encouraging)
1. With stock Kernel it just flashes Samsung image then goes totally black.
2. With a ML1 Compiled Kernel it flashes Samsung image then goes to the SGS3 logo and goes no further.
3. Tried a Sprint Kernel and results were same as data point 1.
I wouldn't dare flash the SBL chain, but I can't help but wonder if the RPM/TZ partitions are safe or even work. Wasn't there a case a few months ago where updating firmware was being enforced for newer d2vzw/d2lte builds since things were unstable otherwise?
Btw, GPL request for I535VRUDNE1/I535OYUDNE1 kernel and wifi source submitted. I don't expect it to help much if Sprint isn't booting, but somebody needs to keep Samsung compliant.
They always forget with Verizon. Quite stunning given how quickly they upload Sprint source, usually before OTA.
Have you talked to cnexus? I remember on the sprint side with the nd8 update there were issues regarding the firmware. Users there had to jump through hoops to update firmware before flashing any custom nd8 roms...
Sent from my SCH-I535 using xda premium
Macrodroid said:
Have you talked to cnexus? I remember on the sprint side with the nd8 update there were issues regarding the firmware. Users there had to jump through hoops to update firmware before flashing any custom nd8 roms...
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
agree with you Macrodroid, early I got an idea to replace the ramdisk of stock 4.3 with 4.4.2(sprint) and 4.1(verizon) ramdisk by modify safestrap!
ended with no boot stuck on black screen, updated to 4.4.2 and sprint 4.4.2 booted in safestrap slot.
I think the old bootchain not compatable with kitkat.
will test the dumb later, @scrosler you can test the sprint ND8 rom it booted with safestrap.
screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
We don't want to use SafeStrap even if unlocked devices can make use of it. Besides, you already have the latest firmware and bootloaders.
If we can manage it, we'd like a native boot with an unlocked bootchain.
I found the USC KitKat D3 Kernel source. Going to try that!
That did nothing.
They need to release the source code, plain and simple. That will be a tremendous help
LLStarks said:
We don't want to use SafeStrap even if unlocked devices can make use of it. Besides, you already have the latest firmware and bootloaders.
If we can manage it, we'd like a native boot with an unlocked bootchain.
Click to expand...
Click to collapse
Yes but you need bootable rom on locked device to make sure your tests not gone with the winds.
mohammad.afaneh said:
Yes but you need bootable rom on locked device to make sure your tests not gone with the winds.
Click to expand...
Click to collapse
I know this will worked on locked devices. The goal is to get it to work on Unlocked devices.
If updated to a locked device I could have a ROM out in 15 minutes. I like the challenge of the unlocked device.
Moved to Android Development.
Have you tried either of these combinations?
1) 4.3 source kernel (with source built DTB) and 4.4 ramdisk?
2) Extracted zImage with 4.3 ramdisk?
You might be able to generate new dtb using Sprint or USCC kk source.
Any access into adb, even if you move it up in init?
garwynn said:
Moved to Android Development.
Have you tried either of these combinations?
1) 4.3 source kernel (with source built DTB) and 4.4 ramdisk?
2) Extracted zImage with 4.3 ramdisk?
You might be able to generate new dtb using Sprint or USCC kk source.
Any access into adb, even if you move it up in init?
Click to expand...
Click to collapse
Hmmm... Number 2 seems like a good idea!
Gonna give that a spin tonight.
scrosler said:
That did nothing.
They need to release the source code, plain and simple. That will be a tremendous help
Click to expand...
Click to collapse
try this out https://www.dropbox.com/s/e8jilbv0ii9ngb3/d2-3.4.zip
its not flashable but throw it in any kernel
I found the vzw flags in the sprint kernel drop, so I chopped up a m2_vzw defconfig and compiled a vzw kernel from sprint source
edit - If somebody that is stock rooted on 4.4.2 can pull config.gz from /proc we can get the official m2_vzw config from there which would allow us to compile that with sprint source (which is the same as vzw, but if there is a more up to date like maybe USC, we can use it)
zachf714 said:
try this out https://www.dropbox.com/s/e8jilbv0ii9ngb3/d2-3.4.zip
its not flashable but throw it in any kernel
I found the vzw flags in the sprint kernel drop, so I chopped up a m2_vzw defconfig and compiled a vzw kernel from sprint source
edit - If somebody that is stock rooted on 4.4.2 can pull config.gz from /proc we can get the official m2_vzw config from there which would allow us to compile that with sprint source (which is the same as vzw, but if there is a more up to date like maybe USC, we can use it)
Click to expand...
Click to collapse
I'll try that tonight as well but I do believe you can not longer get config.gz from /rpoc. I thought that changed on later Android 4.3+ builds. Certainly could be wrong on that.
scrosler said:
I'll try that tonight as well but I do believe you can not longer get config.gz from /rpoc. I thought that changed on later Android 4.3+ builds. Certainly could be wrong on that.
Click to expand...
Click to collapse
OK cool, I know I can still pull it on my phone on AOKP 4.4.4 but touchwiz could be a completely different beast being that AOSP based code is more open security wise
zachf714 said:
OK cool, I know I can still pull it on my phone on AOKP 4.4.4 but touchwiz could be a completely different beast being that AOSP based code is more open security wise
Click to expand...
Click to collapse
Yeah, On pure AOSP or Nexus devices its done differently...
Here is one example: http://forum.xda-developers.com/showpost.php?p=43930020&postcount=46
I will still try to poke around. If I can at least get ADB its a start!
scrosler said:
Yeah, On pure AOSP or Nexus devices its done differently...
Here is one example: http://forum.xda-developers.com/showpost.php?p=43930020&postcount=46
I will still try to poke around. If I can at least get ADB its a start!
Click to expand...
Click to collapse
Im going to see what I can do with the kernel, nate told me he saw a Cert.pem file in the ramdisk which is different from 4.3 but that could just have do with 3.4.x kernel base. It is redicilous that we are almost a week in and Samsung has yet to meet GPL compliance
I found where the certificate is being loaded in init
zachf714 said:
I found where the certificate is being loaded in init
Click to expand...
Click to collapse
Interesting. I would then have to assume the certs have changed? And the theory of using old ram disk may possibly be affective because its looking for old certs and not new? Or maybe just try swapping init binary?
I was also wondering if grabbing the newest hlos-bin (as I have seen sel linux stuff in there as well (its just a zip file)) would help at all. Meaning having matching RamDisk and HLOS (radio).
What do you think?
Im still stuck at work so I cannot try anything.
scrosler said:
Interesting. I would then have to assume the certs have changed? And the theory of using old ram disk may possibly be affective because its looking for old certs and not new? Or maybe just try swapping init binary?
I was also wondering if grabbing the newest hlos-bin (as I have seen sel linux stuff in there as well (its just a zip file)) would help at all. Meaning having matching RamDisk and HLOS (radio).
What do you think?
Im still stuck at work so I cannot try anything.
Click to expand...
Click to collapse
That might work, but we would need to update the init.*.sh sctipts to load the new ril blobs and maybe also to load the 3.4.x kernel. I need to get the NC1 ramdisk down locally and look at it. I was thinking maybe setting selinux to permissive or just disabling it could maybe be worth a shot but thats just a shot in the dark.
edit - here is a boot.img with the old init in it

[Q]Help & Assistance needed [Laime L2+]

Hi, I have a Laime L2+ MTK6589T Quad core 4.0.3, can't boot in to fastboot, can only reach recovery mode, as it keeps bootlooping, it loads to the boot screen say "Laime" and that's it, which leads me to think a corrupt boot, went ahead and wiped the cached etc. , is there an "update.zip" I can get from somewhere or I'm willing to make it myself as tbh i've had enough of my phones turning in to expensive paperweights
Also when I got the phone it didn't include any form of OTA firmware upgrading & there was no play store, if there's any way to include this that would be helpful.
Sorry for being a pain in the arse and asking so much for a first post :silly:
Anyone???
TheOMFG said:
Anyone???
Click to expand...
Click to collapse
www.needrom.com/download/laime-l2-sc8825-2/
1. download rom
2. download upgrade file
3. go into upgrade application
4. select pac file
Start!
@TheOMFG
techrefresh said:
wwwneedromcom/download/laime-l2-sc8825-2/
1. download rom
2. download upgrade file
3. go into upgrade application
4. select pac file
Start!
@TheOMFG
Click to expand...
Click to collapse
The phone does not boot in to fastboot mode, only recovery is there any way I can apply the rom as an update in recovery mode?, if so do need to compile a zip from what the "Upgrade application" downloaded???
I put the .pac file in and my phone never restarted and by the looks of it, no files were flashed to my device so I pulled all the files from the temp folder that it downloads to, here's what I've got:
boot.img
cache.img
DSP_DM_G2.bin
fdl1.bin
fdl2.bin
laime.bmp
nvitem.bin
recovery.img
SC8800G_sc8825_modem_vlx_6825.bin
SC8825.xml
system_2.img
u-boot.bin
u-boot-spl-16k.bin
userdata.img
vmjaluna_6825.image
WVGA_logo_256_t6_guangxin_180.bmp(1)
Where do I go from here?
????
http://specdevice.com/showspec.php?id=a7cb-ae42-ce49-2af60033c587
KERNEL: Linux version 3.0.8 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Wed Aug 13 11:51:42 CST 2014
CODENAME: REL
Mainboard: sp8825c2
BRAND: L200
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: s9_1602
DISPLAY: T6GUANGXIN1602_4.3L035_CN_140813
FINGERPRINT: T6_6825C_SC2330B_GUANGXIN_4.3_L035_CN_16+2_RC_140813
HARDWARE: sc8825
ID: IML74K
TAGS: test-keys
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.version.incremental=140
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.date=Wed Aug 13 11:49:03 CST 2014
ro.build.date.utc=1407901743
ro.build.type=user
ro.build.user=jenkins
ro.build.host=relserver1
ro.build.tags=test-keys
ro.build.version.release=4.0.3
ro.product.model=L200
ro.product.brand=L200
ro.product.name=s9_1602
ro.product.device=s9_1602
ro.product.board=sp8825c2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=L200
ro.wifi.channels=
ro.board.platform=sc8825
# ro.build.product is obsolete; use ro.product.device
ro.build.product=s9_1602
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=s9_1602-user 4.0.3 IML74K 140 test-keys
ro.build.characteristics=default
#-----below add or modified by revo begin------------
ro.product.locale.language=zh
ro.product.locale.region=CN
persist.sys.language=zh
persist.sys.country=CN
ro.macro.pro=t6_1602-guangxin
ro.macro.subpro=t6_1602-guangxin-4.3_l035
ro.device.support.gps=1
ro.device.support.gsensor=true
ro.device.support.psensor=false
ro.device.support.lsensor=false
ro.device.support.msensor=false
ro.device.support.bt=true
ro.device.support.wifi=true
ro.device.support.uplmn=false
ro.device.flashlight=true
ro.device.single_camera=false
ro.sf.hwrotation=0
ro.build.display.id=T6GUANGXIN1602_4.3L035_CN_140813
ro.build.fingerprint=T6_6825C_SC2330B_GUANGXIN_4.3_L035_CN_16+2_RC_140813
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.config.ringtone0=Backroad.ogg
ro.config.ringtone1=Backroad.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=
ro.macro.music_light_style=true
ro.macro.single_signal=yes
universe_ui_support_revo=true
ro.lockscreen.android42=false
ro.lockscreen.four.point=true
ro.macro.androidlogo.jellybean=yes
ro.macro.incall_touch_lock=yes
ro.macro.InCallScreenOffTime=
ro.macro.focus=true
ro.macro.auto_time_zone=no
ro.macro.connectdata=no
ro.macro.default_inputmethod=baidu
ro.macro.is24hour=yes
ro.macro.ip_dail=yes
ro.macro.screen_brightness=b_80
ro.macro.volume_music=d_12
ro.macro.volume_ring_notifi=d_7
ro.macro.volume_alarm=d_5
ro.macro.volume_fm=d_15
ro.macro.screen_timeout=lvl_1
ro.macro.install_no_market=true
ro.macro.font_size=Normal
ro.macro.boot_ani_choose=no
ro.email.default.signature=
ro.macro.status_bar_bg=transparent
ro.macro.status_bar_bg2=part_transparent
ro.macro.status_bar_bg3=
ro.macro.baseband_mtk_type=MTK6589T
ro.macro.baseband_mtk_number=quad_core
ro.macro.showcpuwithbb=
ro.macro.android_version=4.2.1JOP40D
ro.macro.kernel_version=3.4.35-g1f428cc
ro.macro.lockscrn_no_statusbar=yes
persist.sys.timezone=Asia/Shanghai
ro.macro.fake_romsize=
ro.macro.increase_ram=
ro.macro.vibrate_on=yes
ro.macro.accele_rotation=false
dailpad_search_list_custram=
ro.macro.camera_fullscreen=
ro.macro.dtmf_volume=40
ro.macro.custom_logo=
ro.macro.cycle_slip=
ro.macro.simcardnumber=
ro.macro.shutdownanim=
ro.macro.wifi_tether_ssid=
ro.macro.audio_profile=
ro.macro.hide_qsb_bar=yes
ro.macro.haptic_feedback=
ro.macro.native_launcher=
ro.macro.dtmf_tone=
ro.revo.testcase_alert=true
ro.revo.testalert_code=true
ro.revo.dcaf_orientation=false
device.support.dccaf=0
device.support.dvcaf=0
ro.macro.not_show_focustip=
ro.revo.gs_replace_ps=true
ro.revo.gs_replace_ps_value=
ro.revo.call_connection_notify=
ro.revo.exchange.notification=
ro.revo.fakedisplaysize=
ro.revo.useoneincomingsrc=
scroll_quick_switch=
ro.contacts.showstarredonly=
ro.revo.ori_incallscreen=true
ro.macro.statusbar_add_font=
ro.macro.wifi_policy=0
ro.revo.android_calc_style=
ro.revo.homepage=
###---3rd party func property
ro.macro.lqplay_lock=
ro.macro.yl_lock=
ro.sky.browser.support=true
ro.macro.cooee_lock=no
ro.macro.ouxin_switch=
ro.macro.all_apps_button_pos=
ro.macro.ibingo_lock=
ro.macro.yllg_lock=
ro.macro.ringcool=
ro.revo.mcetools=
#-----add or modified by revo end-----------
ro.macro.fake_new_function=
ro.macro.fake_score=
ro.macro.fake_resolution=
ro.macro.fake_camera=
ro.macro.fake_cpu=
ro.macro.fake_cpu_hz=
ro.macro.fake_gpu=
ro.macro.fake_rom=
ro.macro.fake_ram=
ro.macro.fake_pixel=
ro.mocro.single_simcard=
ro.macro.pro_sub=
ro.macro.fake_cpu_model=MTK6589
ro.macro.fake_android_version=
ro.macro.fake_dpi=
ro.macro.fake_freq=
ro.macro.google_ui=
ro.macro.vibrate_last=
ro.macro.vibrate_sleep=
ro.revo.sound_save_path=
ro.revo.sales=
ro.revo.sales_number=
ro.revo.add.reboot.menu=
ro.macro.display_battery=
ro.com.android.dateformat=MM-dd-yyyy
ro.macro.own_wallpaper_lock=
ro.revo.power_save=false
ro.macro.close.dc.sound=no
ro.device.support.vt=0
ro.revo.uui_incallscreen=
ro.macro.sync_wallpaper=
persist.sys.salescount=
persist.sys.sales_num=
persist.sys.sales_time=
ro.macro.yingmai_googleui=
ro.macro.yingmai_zen=
ro.macro.mms_signature=
ro.macro.tracker=
persist.sys.trackerstatus=
persist.sys.trackernum=
persist.sys.trackerpass=
persist.sys.trackerimsi=
ro.macro.statusbardata_mkt=
ro.browser.fontsize=
ro.macro.simcardnozero=
# end build properties
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.gpu=mali
ro.opengles.version=131072
ro.device.support.mmc=1
hwui.render_dirty_regions=false
ro.hwui.text_cache_width=2048
persist.ttydev=ttyVUART0
#if our product support cmcc feature, then set the value true, else do nothing
ro.wifi.support.cmcc=true
#our sp6825c1 product supports Trout chip
ro.wifi.chip.vender=trout
# Can not install packages if the data space has used more than the following ratio value
ro.datastorage.threshold=85
#if out product surport trout chip, we set this
ro.fm.chip.vendor=trout
#if out product surport trout chip, we set this to support hci rset to power off
ro.bt.trout=true
ro.device.support.vt=0
#if our product support single link version
ro.system.property.singleconn=true
ro.product.hardware=sp8825C2_V1.0.0
#true default, false if bt/wifi should not coexist.
ro.btwifi.coexist=true
#if out product support fastboot feature, set as true
persist.sys.support.fastboot=false
# modify for AMS kill background process
ro.support.amskill=true
#if our product not support bt wifisoftap coexist
ro.btwifisoftap.coexist=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
lmk.autocalc=false
ksm.support=false
zram.support=true
zram_for_android.enable=true
persist.sys.service.delay=false
persist.sys.lowmem=16
ro.build.product.lowmem=1
persist.blcr.enable=0
ro.callfirewall.disabled=true
persist.msms.phone_count=2
persist.msms.phone_default=0
persist.sys.lowcost=true
persist.sys.sprd.modemreset=1
persist.sys.kdump.enable=0
dalvik.vm.heapstartsize=3m
dalvik.vm.heapsize=64m
dalvik.vm.heapgrowthlimit=48m
ro.config.ringtone=BeatPlucker.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.logappslow=0
ro.floatkey.show=false
persist.sys.kb.auto=1
device.support.face.smile=0
device.support.pano=0
have you already tried factory reset in cwm and clear cashe/data/dalvik cache? try deleting and reseting everything posible. This might remake partitions and reflash some files that maybe have somehow gone wrong and causing bootloop. Also sometimes apps or combinations of apps can make the phone bootloop. Then wiping dalvik cache can help or factory reset can delete the non-system apps that caused it. Either way, it's worth trying it.
If this didn't fix the problem, try to find somthing with a working laime l2+ and ask him to make an backup in cwm and sent his files to you. You should have a file named "clockworkmod" on your sd-card, check if there's a file named "backup" (if there isn't, just make it), and place the backup file inside this folder. The backup file should be name somthing like "2015-04-24.18.03.57" so just a date, and contain some files like boot.img, .android_secure.vfat, cache.ext4.tar, data.ext4.tar and so on. Then go into recovery and restore this backup.
That's the best I can do for you as I don't know a lot about pushing rom's with pc, don't have a laime l2+ myself and don't know anyone who have one.
Pleas hit thanks, as I took the time to try to help you

[GUIDE] Huawei Y5C | Y541-U02 | Honor Bee : Stock ROMs, ROM Dumping, Root & Flashing

[GUIDE] Huawei Y5C | Y541-U02 | Honor Bee : Stock ROMs, ROM Dumping, Root & Flashing
Disclaimer
Upon following this guide, you may or may not achieve same results with others. I am not held responsible for anything unexpected that may happen to your device. Do your research first regarding the areas you do not quite understand. Follow at your own risk.​
Prerequisites
Spreadtrum Flash Tool R4.0.0001 (PAC Flashing) or Flashfire (Zip flashing)
SPRD USB Driver (needed for PAC Flashing)
Male to Micro USB Cable (needed for PAC Flashing)
7-Zip
Root with SuperSU (just below, needed for first time Zip flashing)
Packet (*.pac) or Zip ROM (found below)
Rooting
Install and gain root through KingRoot android application.
Restart your phone. (I've encountered a sudden reboot when doing the steps below without this)
Replace KingRoot with SupeSU through this script.
Once the archive is downloaded, extract it. There will be a folder named root where you extract it.
Download and open Terminal Emulator.
Change directory to the root folder that was extracted:
Code:
cd /path/to/root
Then ask for root permissions:
Code:
su
Now run the first script:
Code:
sh level1.sh
Run the second script:
Code:
sh level2.sh
Leave the terminal running and open KingRoot.
Press the button at the upper right corner, and choose general settings.
Scroll down and press uninstall.
Uncheck backup and press OK.
After KingRoot has finished uninstalling, go ahead and uninstall Purify as well.
Go back to the terminal and run the third, last script:
Code:
sh level3.sh
Again leaving the terminal running, install SuperSU and open it.
Let it update the root binary through Normal method, and restart.
Notes:
Currently SuperSU's prompt for applications asking for root permissions does not work, but, changing the setting to "grant" will. Just return it to "deny" afterwards, for security. That's the workaround for now.
Dumping
Before doing anything to your device, it is advised to create a ROM dump/backup beforehand. Also make sure you have a lot of free space on your internal storage.​
Open up terminal and gain root permissions:
Code:
su
Then get the partition details:
Code:
ls -al /dev/block/platform/sprd-sdhci.3/by-name
Dump each partition (X) with its name (Y):
Code:
dd =if/dev/block/mmcblk0pX of=/sdcard/Y.img
Do not forget to dump the two bootloaders:
Code:
dd =if/dev/block/mmcblk0boot0 of=/sdcard/splloader.img
Code:
dd =if/dev/block/mmcblk0boot1 of=/sdcard/uboot.img
Flashing
PAC
Extract all the downloaded archives and install the driver (either 32install for 32/86bit or 64install for 64bit OS).
Open the flash tool by double clicking the executable named "ResearchDownload".
Once the flash tool opens, click the single gear button at the top left.
Find and open the PAC ROM.
Press the play button.
Power down the device, hold the volume down button and plug it into the PC.
The flash tool will then recognize the device and start downloading binaries to it.
Once the progress column shows "PASSED", the binary download is finished and the device can now be safely unplugged.
Remove the battery, reinsert, and power the device.
Zip
Gain root if not already done so.
Open Flashfire. (press agree and the other one is up to the user)
Press the red circular button with a plus sign ( + ) on the bottom right, and choose Flash ZIP or OTA.
Find and open the downloaded Zip ROM.
There will be a pop-up for a few settings, leave it as is and press the check icon at the upper right.
Now when the pop-up closes, swipe down and press the Flash button with a lighting icon.
Press OK, and let it flash.
The device will reboot once flashing is finished.
Unbrick Stock PAC ROM
Y541-U02V100R001C567B116
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HUAWEIY541-U02
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.version.security_patch=2016-03-01
ro.build.version.base_os=
ro.build.date=Mon May 23 22:44:32 CST 2016
ro.build.date.utc=1464014672
ro.build.type=user
ro.build.user=
ro.build.host=a7fcf16085c3
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=HUAWEI Y541-U02
ro.product.brand=HUAWEI
ro.product.name=Y541-U02
ro.product.device=HWY541-U
ro.product.board=Y541-U02
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HUAWEI
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=sc8830
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Y541-U02
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=Y541-U02-user 4.4.2 HUAWEIY541-U02 135 ota-rel-keys,release-keys
ro.build.fingerprint=HUAWEI/Y541-U02/HWY541-U:4.4.2/HUAWEIY541-U02/C567B116:user/ota-rel-keys,release-keys
ro.build.characteristics=default
ro.zygote.disable_gl_preload=false
# end build properties
#
# from device/ontim/Y541-U02/system.prop
#
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.opengles.version=131072
ro.product.hardware=SP7731GEA_V1.0.0
debug.hwui.render_dirty_regions=false
ro.config.hw_showSimName=true
ro.config.hw_hideSimIcon=false
ro.config.coop_stk1comp=com.android.stk1;com.android.stk1.StkLauncherActivity
# Bluetooth OPP low speed for save power
debug.bt.lowspeed=false
persist.ttydev=ttyVUART0
# delay for ConnectivityChange broadcast (ms)
conn.connectivity_change_delay = 0
ro.product.partitionpath=/dev/block/platform/sprd-sdhci.3/by-name/
# Default ecclist
ro.ril.ecclist=112,911,#911,*911
persist.modem.w.enable=1
persist.modem.w.nvp=w
ro.modem.w.dev=/dev/cpw
ro.modem.w.tty=/dev/stty_w
ro.modem.w.eth=seth_w
ro.modem.w.snd=1
ro.modem.w.diag=/dev/slog_w
ro.modem.w.loop=/dev/spipe_w0
ro.modem.w.nv=/dev/spipe_w1
ro.modem.w.assert=/dev/spipe_w2
ro.modem.w.vbc=/dev/spipe_w6
ro.modem.w.id=0
ro.modem.w.fixnv_size=0x40000
ro.modem.w.runnv_size=0x60000
persist.sys.engpc.disable=0
ro.modem.wcn.enable=0
ro.modem.wcn.dev=/dev/cpwcn
ro.modem.wcn.tty=/deiv/stty_wcn
ro.modem.wcn.diag=/dev/slog_wcn
ro.modem.wcn.assert=/dev/spipe_wcn2
ro.modem.wcn.id=1
ro.modem.wcn.count=1
camera.disable_zsl_mode=1
ro.digital.fm.support=1
ro.config.ksm.support=true
#supprot storage path change
ro.storagepath.change.support=true
#supprot quickcamera
ro.quickcamera.support=true
#zram config
ro.config.zram.support=true
ro.board_ram_size=mid
# SPRD: add low cost low memory @{
ro.config.low_ram=true
# @}
#if our product not support drm,set as false
drm.service.enabled=true
# hotspot development
ro.hotspot.enabled=1
# this product does not support bt and softap coexist
ro.btwifisoftap.coexist=true
# SPRD: add support hwrotation
ro.sf.hwrotation=0
#SPRD: add support follow sim system config
persist.support.fssc=1
#SPRD: add for cphs
persist.support.oplpnn=true
persist.support.cphsfirst=false
#SPRD: add support virtualnet
persist.support.virtualnet=true
#ontim:add support huawei wlan setting
persist.huawei.wifi.setting=true
#SPRD: add support encrypt
ro.encrypt.devices.support=0
#SPRD: add support vt
persist.sys.support.vt=false
#SPRD: delete baseband version
ro.show.basebandversion=false
#SPRD: mccmnc config path
ro.mccmnc.info.path=/globalinfo/
#for app can install on sd and primary is internal
ro.storage.installonsd=true
# Audio Dump Information for HAL
audio.dump.show.switch=0
hw-k3-burst-supported=1
# adapter for HuaWei PIN(keyguard apk) added by liulibo
ro.config.is_sprd=true
#avoid gallery function:chang voice pic to video.
ro.config.hw_trans_voiceimage=false
#avoid gallery map function
ro.config.support_gallery_map=false
#wifi_country
ro.config.custCountryEnable=ir,sd,sy,kr
# SPRD: DC lowpower
sys.dc.lowpower=true
ro.systemui.flashlight.timeout=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.version.incremental=C567B116
ro.product.sw.internal.version=Y541-U02V100R001C567B116_user_30323_160523.223910
ro.product.sw.external.version=Y541-U02V100R001C567B116
ro.build.cust.id=Y541-U02V100R001C567B116
ro.versioninfo.delivery=MocorDroid4.4_TShark28_2341A_W15.16.5
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
persist.sys.sprd.modemreset=1
ro.adb.secure=1
persist.sys.sprd.wcnreset=1
ro.xtsdisableverify=1
ro.storage.flash_type=2
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.msms.phone_count=2
persist.msms.phone_count=2
persist.msms.phone_default=0
ro.modem.w.count=2
persist.sys.support.vt=false
sys.usb.gser.count=4
lmk.autocalc=false
persist.sys.data_reserved=100
ro.config.ringtone=Huawei_Tune.ogg
ro.config.ringtone0=Huawei_Tune.ogg
ro.config.ringtone1=Huawei_Tune_Piano.ogg
ro.config.notification_sound=Bongo.ogg
ro.config.alarm_alert=Creamy.ogg
persist.sys.wakeup.enable=0
ro.config.hw_timeformat=true
ro.config.timeformat=24
persist.sys.modem.diag=,none
persist.sys.slog=0
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r7
ro.build.display.id=Y541-U02V100R001C567B116
ro.config.max_starting_bg=3
ro.com.google.clientidbase=android-huawei
ro.com.google.clientidbase.yt=android-huawei
ro.com.google.clientidbase.am=android-huawei
ro.com.google.clientidbase.gmm=android-huawei
ro.com.google.clientidbase.ms=android-huawei
ro.dual.sim.phone=true
ro.config.hw_coop_no_setting=true
ro.config.remove_subscribe_menu=1
ro.config.hw_coop.ontim=true
ro.config.hw_coop.show_Sun=1
ro.config.app_big_icon_size=90
ro.config.hwcust_drawbgicon=false
ro.config.hw_coop_delay=true
ro.config.hwtheme=1
persist.radio.langu.rule=0
data.icon.onlyconnected=true
persist.sys.certification=103323
ro.config.is_support_my=true
ro.product.hwinternal.version=Y541-U02V100R001C567B116
ro.product.hwinternal.ver.time=160523.223910
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
ro.floatkey.show=false
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Notes:
These ROMs are repacked and tested first before being posted, so if one of these does not work, try another. If none worked, just wait, others will share a new partition dump.
These ROMs do not contain a system, custom and cache dump because these are for unbricking for now. Prerooted full repacks are coming soon.
Stock ZIPs
Notes:
As the device refuses any custom or modified stock binaries, Flashfire is the only way to go to install zips.
These are pre-rooted, deodexed, zipaligned, de-bloated, and of course tested.
None at the moment.
Troubleshooting
If the flash tool fails to download, either the downloaded ROM is incompatible with the device, or the cable is loose.
If the device shows a white screen but the booting sound is heard, try another one.
Support
If anyone happens to have the same device model in fully working condition but seems to be different, kindly make a partition dump of it and PM the link, so it can be processed and uploaded here.​
Credits & Sources
@najoor for the original KingRoot to SuperSU script.
GSM Flashfile Website
@Kingxteam for KingRoot
@Chainfire for SuperSU & Flashfire
Is there any customs available for this device
anil kalyan said:
Is there any customs available for this device
Click to expand...
Click to collapse
As of now, with the bootloader locked, there is none.
In future can we expect the same..........
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
techyzen101 said:
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
Click to expand...
Click to collapse
When can we expect this
Where we are on this Can we expect Lollipop rom anytime
Please provide the lollipop ROM
after flash check download state, last download maybe not complete.
Does anyone have a full file or link .pac file Y541-U02V100R001C567B116 ~ 1.5Gb
Y541-U02V100R001C567B112
I need This version pac file help plz
snmobilecenter said:
after flash check download state, last download maybe not complete.
Click to expand...
Click to collapse
hello can i ask if what can be done when you encouter this error upon power on?
tried flashing with research download and upgrade downgrade tool from spdflashtools.
got it to flash firmware v105. but after flashing, blank screen won't power on. also cannot go to recovery.
tried to flash it again with different version, did not go thru anymore and cannot go through any firmware versions.
stuck at FDL2 failing.
tried android usb drivers and spd /sci drivers still stuck at fdl2
please help.
how to get twrp?

Categories

Resources