According to Engadget China the N1 will be released this month in Taiwan. The cool thing about this news is that it will have the Play store! http://chinese.engadget.com/2015/04/13/nokia-n1-taiwan-leak/
syddd said:
According to Engadget China the N1 will be released this month in Taiwan. The cool thing about this news is that it will have the Play store! http://chinese.engadget.com/2015/04/13/nokia-n1-taiwan-leak/
Click to expand...
Click to collapse
Nice to know!
By the way syddd, Im back at home with my new N1. Whenever Ive got some time I will start playing with it.
Can someone make an image file from the Taiwan version?
Many thanks!
I bought my N1 from eglobalcentral and was very surprised when it arrived yesterday with all google stuff already installed so I'm assuming they sent me a Taiwanese version (anyone knows if there's a way to check this?). I'd be happy to take an image if someone tells me how to do it
hmm very interesting.
A few questions:
- In the Play store do you see some apps as unavailable? Like Google Chrome or Google maps? Does getting location works in maps?
-What is the build version you see in the about page (in the china version they are like A5CN315)?
-Have you tried to root it? If yes did you succeed?
So far all google apps that I would usually use are available , and even better, chrome, maps, gmail, hangouts etc are already preinstalled and there is no Chinese market by default. At first I thought that someone manually patched the tablet and installed all this but then I thought it was not likely as it came in a sealed box and secondly it didn't have all the caveats that come with manually installing google services / play store. Also, during the first startup it asks to sign in to google mail etc (not sure if the Chinese version does it).
Shortly after first bootup it asked me to install an update which I did and all google stuff was in place after the update process was finished.
I'll post the sw version number later on - I don't have the tablet with me at the moment
Update: asked my missus to take the screenshots for me.
Here's the version number:
{
"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"
}
And the home screen (MoonReader+ and Ghost Commander were installed by me, all other apps came with the tablet):
---------- Post added at 11:08 AM ---------- Previous post was at 10:48 AM ----------
Update: this page (here's google translated version) suggests that A5FM51C is indeed a Taiwanese version
PLZ share build.prop
Here you go:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=A5FM51C
ro.build.display.id=A5FM51C
ro.build.version.incremental=2015-05-28-R-023643
ro.build.version.sdk=21
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.0.2
ro.build.date=Thu May 28 10:37:44 CST 2015
ro.build.date.utc=1432780664
ro.build.type=user
ro.build.user=sam
ro.build.host=topaz0
ro.build.tags=release-keys
ro.product.model=N1
ro.product.brand=Nokia
ro.product.name=N1
ro.product.device=Nokia_N1
ro.product.board=moorefield
ro.setupwizard.mode=OPTIONAL
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86
ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Nokia
ro.product.locale.language=zh
ro.product.locale.region=TW
ro.wifi.channels=
ro.board.platform=moorefield
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Nokia_N1
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=N1-user 5.0.2 A5FM51C 2015-05-28-R-023643 release-keys
ro.build.fingerprint=Nokia/N1/Nokia_N1:5.0.2/A5FM51C/2015-05-28-R-023643:user/release-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
drm.service.enabled=true
ro.blankphone_id=1
ro.fxn.ota.sku=tw2015
ro.com.widevine.cachesize=16777216
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.0_r2
ro.com.google.clientidbase=android-foxconn
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=200m
dalvik.vm.heapsize=348m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
dalvik.jit.code_cache_size=1048576
ro.hwui.texture_cache_size=72
ro.hwui.layer_cache_size=48
ro.hwui.r_buffer_cache_size=8
ro.hwui.gradient_cache_size=1
ro.hwui.path_cache_size=32
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
ro.hwui.shape_cache_size=3
ro.fxn.def.dns1=8.8.8.8
ro.fxn.def.dns2=8.8.4.4
persist.sys.dalvik.vm.lib.2=libart.so
ro.ril.status.polling.enable=0
bt.hfp.WideBandSpeechEnabled=true
dalvik.vm.isa.x86.features=sse4_2,aes_in,popcnt,movbe
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.intel.corp.email=1
Anyway we can flash with this new one's ROM?
Many thanks!!
---------- Post added at 05:24 AM ---------- Previous post was at 05:22 AM ----------
Your new one Build Number comes with "FM". While the Mainland Chinese one came with "CN". Yours definitely is full version one.
wodz69 said:
And the home screen (MoonReader+ and Ghost Commander were installed by me, all other apps came with the tablet):
Click to expand...
Click to collapse
How do you find this Taiwan N1? Wondering how smooth and lag free it is. I've been hanging back on getting a Chinese release without the Play Store then rooting due to all the issues. Hoping this release is smooth as silk without glitches.
How long did delivery take from eGlobalCentral?
Have u managed to pull out the image of your os ?
Sent from my A0001 using Tapatalk
wodz69 said:
So far all google apps that I would usually use are available , and even better, chrome, maps, gmail, hangouts etc are already preinstalled and there is no Chinese market by default. At first I thought that someone manually patched the tablet and installed all this but then I thought it was not likely as it came in a sealed box and secondly it didn't have all the caveats that come with manually installing google services / play store. Also, during the first startup it asks to sign in to google mail etc (not sure if the Chinese version does it).
Shortly after first bootup it asked me to install an update which I did and all google stuff was in place after the update process was finished.
I'll post the sw version number later on - I don't have the tablet with me at the moment
Update: asked my missus to take the screenshots for me.
Here's the version number:
And the home screen (MoonReader+ and Ghost Commander were installed by me, all other apps came with the tablet):
---------- Post added at 11:08 AM ---------- Previous post was at 10:48 AM ----------
Update: this page (here's google translated version) suggests that A5FM51C is indeed a Taiwanese version
Click to expand...
Click to collapse
you can use fiddler to caught firmware.
xkernels said:
you can use fiddler to caught firmware.
Click to expand...
Click to collapse
View attachment 3410939
View attachment 3410942
Sorry for delayed reply - I was on holidays. I'll try to dump the images sometime this weekend. Which partitions would be of interest: boot, system, recovery, ...?
Your N1 got update after you buy it? I want know Product_ID=N1-china2015 of Taiwan version N1.
I finally got around to root the tablet and dump the images of boot, recovery and system - you can find them at the following link:
https://www.dropbox.com/sh/drmfv30k54jgb35/AABc9uPxpOSUNHsV1lSD-k_1a?dl=0
There are a few more partitions that might be of interest - please let me know if you wanted me to dump them
[email protected]_N1:/mnt/shell/emulated/0 # ll /dev/block/by-name/
ll /dev/block/by-name/
lrwxrwxrwx root root 2015-07-26 14:56 boot -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-26 14:56 boot-one-shot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-26 14:56 cache -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-26 14:56 config -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-26 14:56 data -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-26 14:56 factory -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-26 14:56 fastboot -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-26 14:56 infork -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-26 14:56 logs -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-26 14:56 misc -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-26 14:56 panic -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-26 14:56 persistent -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-26 14:56 ramdump -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-26 14:56 recovery -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-26 14:56 reserved -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-26 14:56 silentlake -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-26 14:56 splashscreen -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-26 14:56 system -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-26 14:56 userkeystore -> /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Xkernels - not sure where to find the product_id you are referring to. If you let me know where to look for and I'll post it
Thanks a lot, buddy!
wodz69 said:
I finally got around to root the tablet and dump the images of boot, recovery and system - you can find them at the following link:
https://www.dropbox.com/sh/drmfv30k54jgb35/AABc9uPxpOSUNHsV1lSD-k_1a?dl=0
There are a few more partitions that might be of interest - please let me know if you wanted me to dump them
Xkernels - not sure where to find the product_id you are referring to. If you let me know where to look for and I'll post it
Click to expand...
Click to collapse
you can use Fiddler to find product_id,you can refer the pic which I post above.
Thanks a lot wodz69.
Did someone test it already? Can i simply install the system image in recovery?
Same question.
I am quite afraid to be the first to test it
Did someone try to apply it?
Thanks for reply! :fingers-crossed:
Related
I've extracted the ramdisk from the boot.img which was posted by Football in the RUU_Supersonic_1.32.651.1_Radio_1.39.00.04.26 file.
This contains all the bootable files which are executed once the kernel loads...
to extract all the files from the ramdisk
normally, these are the commands:
mkdir ramdisk
cd ramdisk
gzip -dc ../boot.img-ramdisk.gz | cpio -i
BUT for some reason between my uploading and the host, the .gz gets corrupted. i put all the files into a .tar
tar -xvf EVO-stock-ROM-ramdisk.tar
http://www.joeyconway.com/evo/kernel/EVO-stock-ROM-ramdisk.tar
this is the directory listing from the ramdisk (yea im using my moment dev environment...)
[email protected]:~/evo/updates/dst/boot/ramdisk$ ls -l
total 168
-rw-r--r-- 1 moment moment 216 2010-05-22 16:23 bootcomplete.supersonic.rc
drwxrwx--x 2 moment moment 4096 2010-05-22 16:23 data
-rw-r--r-- 1 moment moment 118 2010-05-22 16:23 default.prop
drwxr-xr-x 2 moment moment 4096 2010-05-22 16:23 dev
-rwxr-x--- 1 moment moment 103548 2010-05-22 16:23 init
-rwxr-x--- 1 moment moment 1677 2010-05-22 16:23 init.goldfish.rc
-rwxr-x--- 1 moment moment 14403 2010-05-22 16:23 init.rc
-rwxr-x--- 1 moment moment 4840 2010-05-22 16:23 init.supersonic.rc
drwxr-xr-x 2 moment moment 4096 2010-05-22 16:23 proc
drwxr-x--- 2 moment moment 4096 2010-05-22 16:23 sbin
-rw-r--r-- 1 moment moment 75 2010-05-22 16:23 shutdown.supersonic.rc
drwxr-xr-x 2 moment moment 4096 2010-05-22 16:23 sys
drwxr-xr-x 2 moment moment 4096 2010-05-22 16:23 system
Edit: To flash kernels on the EVO, I created a simple app: FlashImageGUI - http://forum.xda-developers.com/showthread.php?t=1083260
i can't download this, it give me a error saying file is damaged
super-6-1 said:
i can't download this, it give me a error saying file is damaged
Click to expand...
Click to collapse
wow, good catch. im not sure why its being corrupted so i made all the files and directory into a .tar!
thanks for the feedback!
there are a few scripts to do what uve done here. 1) extract-ramdisk.pl and 2) split-bootimg.pl. there are a few others but these are the two i choose to use. anyhow it looks like a normal ramdisk from a snapdragon device.
toastcfh said:
there are a few scripts to do what uve done here. 1) extract-ramdisk.pl and 2) split-bootimg.pl. there are a few others but these are the two i choose to use. anyhow it looks like a normal ramdisk from a snapdragon device.
Click to expand...
Click to collapse
sweet, i used split-bootimg.pl, worked great. im new to all this so im very glad we're on the same page!
what kind of tools do we have to put a modified boot.img back onto the EVO?
Could we update the boot.img by utilizing the ROM Update Utility functionality--by flashing an updated .nbh to the phone?
joeykrim said:
sweet, i used split-bootimg.pl, worked great. im new to all this so im very glad we're on the same page!
what kind of tools do we have to put a modified boot.img back onto the EVO?
Click to expand...
Click to collapse
google "rom cooking lox" and ull find all u need to know about it
toastcfh said:
google "rom cooking lox" and ull find all u need to know about it
Click to expand...
Click to collapse
thanks! i googled it and found this thread
http://htcpedia.com/forum/showthread.php?t=1404
and then a thread of yours linking back to that thread.
from what i've read in that thread and other threads, using the recovery on the phone to apply an update.zip which we create and sign, seems to be the most common method to update the phone with our own ROM.
i have one question. will the stock recovery on the EVO apply the update.zip i build and sign? or do we need a custom recovery before we can apply our update.zip files we've built and signed?
also for anybody with an EVO, feel like testing? im willing to work and create a custom update.zip which I think should give us root, I have a few different methods in mind from my last rooting experience of an Android phone,the samsung moment android 2.1 upgrade, a few weeks ago...but its really hard for me to know never having used or seen the HTC android platform and not having the EVO until the 4th...
i wish i had an EVO to test with...!
joeykrim said:
thanks! i googled it and found this thread
and then a thread of yours linking back to that thread.
from what i've read in that thread and other threads, using the recovery on the phone to apply an update.zip which we create and sign, seems to be the most common method to update the phone with our own ROM.
i have one question. will the stock recovery on the EVO apply the update.zip i build and sign? or do we need a custom recovery before we can apply our update.zip files we've built and signed?
also for anybody with an EVO, feel like testing? im willing to work and create a custom update.zip which I think should give us root, I have a few different methods in mind from my last rooting experience of an Android phone,the samsung moment android 2.1 upgrade, a few weeks ago...but its really hard for me to know never having used or seen the HTC android platform and not having the EVO until the 4th...
i wish i had an EVO to test with...!
Click to expand...
Click to collapse
I believe that the current SPL will only run signed HTC updates, and that the common attack vector is to find a way to overwrite the default SPL with a custom widget in order to disable checks for signed updates and other annoyances. (please correct me if I'm wrong!)
My question I'm trying to figure out now is how does HTC sign the ROMs?
andrew500 said:
I believe that the current SPL will only run signed HTC updates, and that the common attack vector is to find a way to overwrite the default SPL with a custom widget in order to disable checks for signed updates and other annoyances. (please correct me if I'm wrong!)
My question I'm trying to figure out now is how does HTC sign the ROMs?
Click to expand...
Click to collapse
They take their private key and sign it...
This is mindboggling, nonetheless.
Oh the joy.
{
"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"
}
{
"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"
}
DOWNLOAD STRAIGHT FROM GOOGLE:
http://android.clients.google.com/packages/ota/verizon_trygon/2a903016f227.signed-trygon-IMM76L-from-HLK75H.2a903016.zip
Instructions:
* You will also need to be on Android build HLK75H
1. Download the file from above and drop it on a USB stick or SD card that can be put in a USB Stick.
2. Turn your XOOM off.
3. When you power it back on, tap Volume Down at the red M logo until it says:
–> Android Recovery
4. Tap Volume Up to enter recovery mode.
5. At the green Android logo, press Volume Up and Power.
6. Plug in your USB drive to a USB host cable and then into your XOOM.
7. Scroll down to “apply update via USB drive” and select it with Power.
8. Scroll down to the .zip update file from above and use Power to select it.
9. Your XOOM will now update.
Click to expand...
Click to collapse
Has anyone applied this update with success?
patrickhills said:
Has anyone applied this update with success?
Click to expand...
Click to collapse
I did, its legit. However I SBF'd back to HC before applying the update. ( I prefer to go the SBF route)
Hulu Plus STILL giving error 91
However, works fine. I see no reason to use any other rom.
Yup. Works. Thanks
Sent from my Xoom using XDA
Can someone pull their /system once the update's been installed, please? This will help the ROM community out quite a bit. Thanks!
---------- Post added at 08:56 PM ---------- Previous post was at 08:17 PM ----------
... and share the output of "fastboot getvar all" (while in "Fastboot Mode", of course), too (you can leave out your serial number if you wish)? Thanks!
I am on EOS 2.0.
I am assuming I will lose root,but that can be corrected.
Will I need to revert back to stock?
Or should I just stfu and be happy with EOS until we get a pre rooted rom?
tcbj said:
should I just stfu and be happy with EOS until we get a pre rooted rom?
Click to expand...
Click to collapse
Probably.
Can anyone confirm that there's a new radio? I've heard that there are 4G improvements.
Also, any general impressions? How does it stack up to something like Bugless Beast?
jm9843 said:
Can anyone confirm that there's a new radio?
Click to expand...
Click to collapse
Yes, for both the LTE and the original CDMA radios.
I NEED A SYSTEM DUMP!
kcrudup said:
Yes, for both the LTE and the original CDMA radios.
I NEED A SYSTEM DUMP!
Click to expand...
Click to collapse
I have one but unfortunately didnt pull it until after I had rooted and installed the latest busybox. If you want it I will upload it for you.
Edit: added build.prop for reference
Here is the link.
https://www.dropbox.com/s/lnlvkvc1zkp41ak/xoom_system_IMM76L.7z
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76L
ro.build.display.id=IMM76L
ro.build.version.incremental=345519
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Wed May 2 19:56:06 UTC 2012
ro.build.date.utc=1335988566
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpbs18.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Xoom
ro.product.brand=verizon
ro.product.name=trygon
ro.product.device=stingray
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Motorola
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=stingray
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=trygon-user 4.0.4 IMM76L 345519 release-keys
ro.build.fingerprint=verizon/trygon/stingray:4.0.4/IMM76L/345519:user/release-keys
ro.build.characteristics=tablet
# end build properties
# RIL and telephony related settings
rild.libargs=-d /dev/chnlat10
#Point to lte, CDMA, MM RILs
lte_ril.libpath=/system/lib/libmoto_lte_ril.so
cdma_ril.libpath=/system/lib/libmoto_cdma_ril.so
rild.libpath=/system/lib/libmoto_mm_ril.so
ril.rat=LTE
persist.ril.mux.ttydevice=/dev/usb/tty2-1:1.2
# Increase # channels to 10 to allow M2M communication
persist.ril.mux.noofchannels=10
persist.ril.modem.mode=1
# Enable ALWAYS_READ_IMSI_FROM_SIM
persist.ril.features=800
ro.cdma.home.operator.numeric=310004
ro.cdma.home.operator.alpha=Verizon
ro.cdma.homesystem=64,65,76,77,78,79,80,81,82,83
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
persist.ril.modem.ttydevice=/dev/usb/tty2-1:1.4
persist.ril.tcmd.ttydevice=/dev/usb/tty2-1:1.3
persist.ril.diag.ttydevice=/dev/usb/tty2-1:1.0
ril.wrigley.modem.tty=/dev/usb/tty1-1:1.10
#Leave default mode to 4 (CDMA) but need it to be Global (7) for LTE/CDMA
ro.telephony.default_network=4
# Disable ims by setting imsapp.mode to all_dependency_met
#imsapp.mode=all_dependency_met
# The value of the kernel command line product_type variable for lte on cdma devices
telephony.lteOnCdmaProductType=clw
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
# Indicate carrier OTA SP number schema
# refer to frameworks/base/telephony/java/com/android/
# internal/telephony/cdma/CDMAPhone.java for the schema:
ro.cdma.otaspnumschema=SELC,1,80,99
# Give extra time for LTE bug dumps
ril.dumpstate.timeout=75
# Retry config when GSM DCT is used for EHRPD/LTE call
ro.gsm.data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.gsm.2nd_data_retry_config=max_retries=infinite,default_randomization=2000,0,0,80000,125000,485000,905000
ro.ril.panic.reporter=apr
ro.ril.fccid=IHDP56LU2
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.google.clientidbase=android-verizon
ro.config.ringtone=Sceptrum.ogg
ro.config.notification_sound=Cobalt.ogg
ro.config.alarm_alert=Cesium.ogg
keyguard.no_require_sim=true
ro.setupwizard.mode=OPTIONAL
drm.service.enabled=true
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
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
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
cellzealot said:
I have one but unfortunately didnt pull it until after I had rooted and installed the latest busybox. If you want it I will upload it for you.
Click to expand...
Click to collapse
Yes, that's fine- as long as the busybox files are only the ones you've changed.
The patch scripts in the update have the SHA1 of the result files listed in it, so I can verify the integrity of the ones we really need, which are mostly just the VZ and NVidia proprietary files. (Interestingly enough, none of the WiFi files changed, but the BT firmware did).
I have tried installing this update multiple times, but keep getting this error when trying to install:
Code:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:Failed to seek in /tmp/sideload/package.zip (Invalid argument)
E:Signature verification failed
Installation aborted.
I have tried multiple times with the same result. I am running stock HLK75H, unlocked bootloader but no root or custom recovery. Any help would be great! Thanks.
dawynkoop said:
I have tried installing this update multiple times, but keep getting this error when trying to install:
Code:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:Failed to seek in /tmp/sideload/package.zip (Invalid argument)
E:Signature verification failed
Installation aborted.
I have tried multiple times with the same result. I am running stock HLK75H, unlocked bootloader but no root or custom recovery. Any help would be great! Thanks.
Click to expand...
Click to collapse
Is your S-OFF or S-ON? I think you need to have signature verification ON in order to apply an OTA update.
Original Firmwares
Since I got my Ascend P1 I've been playing around with it alot.
Here's my list of official firmwares for the Ascend P1.
DISCLAIMER
I am not responsible for any bricked devices.
Software downloads
TWRP-2.4.4.0_P1.zip (7.0 MB)
https://mega.co.nz/#!hg4SCQoT!VGUiFxRo6RhlZWCEdbOSWQzsp0AyDDDNbePj9QO4Uok
MD5: 8e95c08d8bb33bf6e393a558c88d611f
cwm_touch_recovery_viva_beta.zip (5.8 MB)
https://mega.co.nz/#!I0A3GZKQ!I3YBzyz63NivAdH7b0tMcSjP5-JmIwuOpUkfCx0Fljg
MD5: cc13117567ad2c85be408c4ab2fdbdcf
CWM-6.0.1.9.U9200.zip (7.0 MB)
https://mega.co.nz/#!Uxxi1brY!J1XcZghxObG-LPm3Dk3jnVIgFu984YnZjVdfikfQxBA
MD5: bc8dbd969e301d49289f24c93872c6f0
SuperSU package with Busybox
CWM-SuperSU-v0.98.zip (670 KB)
https://mega.co.nz/#!Yt42WZ6I!Lrc182C2sUYFjOD83MZ-hn_YI8hFkjhPQ3xcvOM23FA
Root access on all firmwares (Ice Cream Sandwich + Jelly Bean) using TWRP
When you've flashed one of your official Huawei firmwares you need to do this.
Flash or boot into Teamwin Recovery on your Huawei Ascend P1
Go to the "Mount" menu and mount System.
Then go to the Reboot menu and reboot the system.
When it detects you are not rooted TWRP will ask if you want to root.
Swipe to do so and let it boot back into the system.
When done just hit the SuperSU icon and let it setup for the first time. Either by downloading a flashable zip or by going to the Play Store.
After that you've got a rooted device.
Root access on all Huawei Ice Cream Sandwich (4.0.X) firmwares using CWM
Now to get root access on the Ascend P1 I've done it in a couple of different ways.
Download the SuperSU package with Busybox and place it on your external SD card (The card you can put into the side of the Ascend P1)
The easiest way for me was to boot ClockWorkMod Recovery from fastboot.
You need to have ADB and fastboot drivers set up and activated USB debugging on your device.
When that is done you can do some command lines to check the device is recognized and ready to go.
Step 1:
Launch a Command Promt and go to the directory where your ADB is setup.
Step 2:
Connect your device to the computer and make sure USB debugging is activated under the Developers options.
Step 3:
Type in:
ADB devices
and you should get a long unique ID of your device.
Step 4:
Type in:
ADB reboot bootloader
Step 5:
When the phone has rebooted into bootloader (There will just be a Huawei logo) check if the device is responding by typing:
fastboot devices if it's not you need to install the fastboot driver (Android ADB Interface).
Step 6:
If it's there you need to boot to the new CWM recovery by placing the CWM recovery image (cwm_touch_recovery_viva_beta.img) in the same library as your fastboot folder and type:
fastboot boot cwm_touch_recovery_viva_beta.img
Then your phone will reboot into CWM recovery where you can chose the SuperSU package with Busybox zip file and flash it.
That will gain root to your phone.
Step 7 (Optional):
When you're in the CWM recovery you can backup your entire device so you always can get back to it if you need to.
This is done in the back and recovery menu.
HOW-TO Flash these different regions.
If you're coming from a different region firmware than the one you want to flash, you have to do some preparations before it will flash.
This is due to a verification in the recovery and build.prop.
So for this to work you need to have root access on your current firmware.
When you flash a different region firmware the recovery checks the build.prop for matching regions.
The relevant part is at the bottom an looks like this.
Code:
ro.product.board=U9200
ro.confg.hw_systemversion=U9200-1V100R001C185B103_SYSTEM
ro.build.display.id=U9200-1V100R001C185B103
ro.product.model=U9200
ro.product.brand=Huawei
ro.build.tags=ota-rel-keys,release-keys
ro.product.manufacturer=HUAWEI
ro.product.name=U9200
ro.product.device=hwu9200
ro.build.id=HuaweiU9200
ro.build.version.incremental=C185B103
ro.build.description=U9200-user 4.0.3 HuaweiU9200 C185B103 ota-rel-keys,release-keys
ro.build.fingerprint=Huawei/U9200/hwu9200:4.0.3/HuaweiU9200/C185B103:user/ota-rel-keys,release-keys
Here you must replace all the current build details which in this case is U9200-1V100R001C185B103 and if you want to move to U9200-1V100R001C00B226 you need to replace it with that or any of the other region build numbers.
I will add CWM flashable zip files for the different regions later.
So here is the edited version.
Code:
ro.product.board=U9200
ro.confg.hw_systemversion=[COLOR="YellowGreen"]U9200-1V100R001C00B226[/COLOR]_SYSTEM
ro.build.display.id=[COLOR="YellowGreen"]U9200-1V100R001C00B226[/COLOR]
ro.product.model=U9200
ro.product.brand=Huawei
ro.build.tags=ota-rel-keys,release-keys
ro.product.manufacturer=HUAWEI
ro.product.name=U9200
ro.product.device=hwu9200
ro.build.id=HuaweiU9200
ro.build.version.incremental=[COLOR="YellowGreen"]C00B226[/COLOR]
ro.build.description=U9200-user 4.0.3 HuaweiU9200 [COLOR="YellowGreen"]C00B226[/COLOR] ota-rel-keys,release-keys
ro.build.fingerprint=Huawei/U9200/hwu9200:4.0.3/HuaweiU9200/[COLOR="YellowGreen"]C00B226[/COLOR]:user/ota-rel-keys,release-keys
Now with that done you need to flash the recovery.img from the build you want to move to.
I will supply the recovery.img files later.
I've put some recovery.img in some of the packages. But will upload them separately later when I've extracted them all.
Now this is very similar to what you did when rooting.
Step 1:
Do a reboot to bootloader again by typing:
ADB reboot bootloader
Step 2:
Check the device is there by typing:
Fastboot devices
Step 3:
Flash the recovery by typing:
Fastboot flash recovery recovery.img (the recovery name can vary)
Step 4:
Type:
Fastboot reboot
Let it boot up and then go to:
Settings->Storage->Software Upgrade->SD card Upgrade->Confirm->Upgrade
This will erase all apps and settings, so remember to backup your stuff.
There is also a force upgrade mode which you can enter by holding down Volume Up and Volume Down keys right after the vibration when the device boots up.
Installation of EmotionUI B704 with all langauges enabled.
SO DON'T SETUP YOUR PHONE RIGHT AFTER YOU'VE FLASHED IT, YOU WILL HAVE TO DO A FACTORY RESET!
So if you flash B704 you'll notice when you want to change the locale on it that it only contains 4 languages, some Asian ones and English.
To get all languages you'll need to flash a zip in TWRP that I made to enable them again.
Procedure:
Flash B704 through normal means (stock recovery)
If it fails you need to flash the intermediate firmware then flash B704 (intermediate firmware can be found in the download links below).
When B704 installation is complete reboot the device to bootloader.
From there boot TWRP 2.4.4.0 with the command:
Code:
fastboot boot "recovery_image_name.img" (usually just recovery.img or twrp_recovery.img but can vary)
Flash GAPPS for 4.1.x (http://goo.im/gapps/gapps-jb-20121011-signed.zip)
Flash my language enabler package - This can be found below in the links section or as an attachment.
Optional step if you want root:
When you do a Reboot system from TWRP it will ask you if you want to root as it can see you don't have it.
If you want that just slide the slider and click the SuperSU icon when your back in Android.
If you don't want root just click the button above that ignores that.
Final step:
When you're booted back into Android go to Setting > Backup & Reset and press the Factory data reset button.
This is necessary if you want the languages to be enabled as the settings is being read and reinitialized from the cust partition.
{
"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"
}
Official Huawei Firmwares
English Huawei Ascend P1 EmotionUI website
Chinese Huawei Ascend P1 EmotionUI website
Intermediatepack.zip (235.7 MB)
https://mega.co.nz/#!48x2hLBa!EkJ2NxuM4-kGmj38a_QbywtQFaIASxA2deT4ZmCsizQ
MD5: 0ceb2b4cb89ecfcc138855e798a7d7e2
U9200-1V100R001C00B226.zip (486.2 MB) [Generel Global Version]
https://mega.co.nz/#!1xIQ3CpK!KOWAh3CoerA5UI9WcYdKDTqCvmdAJ6wNI6A1MlPK__4
MD5: 3e14da9fac783dc5494fcf5b105ed4ed
U9200-1V100R001C00B229.zip [Generel Global Version]
MD5: d8faf295f41981f4f79c9cf7416fd454
https://mega.co.nz/#!Bh5BzZzK!dCEzsU_a3tO-UWdz_qsjaE-h7tZr0RIXib6f6v2g_3Y
Included in package: boot.img, recovery.img and build.prop
U9200-1V100R001C185B105.zip (501.4 MB) [North European Version]
https://mega.co.nz/#!U4QBTJAY!PHV2tw3wn85QZ3isW6h0uke1vJcKH78waol4ADSL6M0
U9200-1V100R001CHNC00B124.zip (532.3 MB) [Chinese Version]
http://www.multiupload.nl/H0JQLQ5PTD
MD5: 76d1b1d0500ee6ce30e6c1cb94348281
U9200-1V100R001CHNC00B525_681031.zip (658.5 MB) [EMUI 1.5 Jelly Bean Beta]
https://mega.co.nz/#!A5BDyTqQ!UkfiiQCf3e8dCBryH-SNsib6GosVVNq0TeNtKHmD5R8
U9200-EmotionUI_1.5_V100R00G411D00B315.zip (923.2 MB) [Global EMUI 1.5 Jelly Bean Beta]
https://mega.co.nz/#!IlxGgCSa!E4NNy1ee_57dreKlCGvUGURfojtu5JC_pH15ohBHJ-0
MD5: 241df4f9105c9ffbb2eee98dbdd142cb
U9200-EmotionUI_1.5_V100R001CHNC00B605SP01.zip (588.0 MB) [Chinese EMUI 1.5 Jelly Bean Beta 2013-07-24]
https://mega.co.nz/#!AxxhBbab!LqbhWBtuKfeie7sHoo69-gxniHUMr25KpcNkE_eUPpg
MD5: 7cbe1045136e071a9eb45009a0b5d67a
U9200-EmotionUI_1.6_V100R001CHNC00B701.zip (602.0 MB) [Chinese EMUI 1.6 Jelly Bean Beta 2013-08-08]
https://mega.co.nz/#!94YQjbwJ!GCjjAyUdhpLehdw-ZF41-CrDl8tkMydK5k-uJCOzStI
MD5: b9ec867dc064d7324eb2d7a2002abd8a
U9200_EmotionUI_1.6_V100R001CHNC00B704.zip (611.8 MB) [Chinese EMUI 1.6 Stable Jelly Bean 2013-30-08]
https://mega.co.nz/#!FpxFELrD!DRt26h3GZzh9G1jmR4tFSw9wdq0NOomUZFG2BkqywR0
MD5: ac400e52face499f6ca3c69ee95999ab
Language enabler works for both B704 & B706.
U9200_EmotionUI_1.6_B704_enable_language-signed.zip (283 KB)
https://mega.co.nz/#!lkAiyb6b!FemgigBmdVDOCX60uV3VhAKDvQNFh_En8ji4iKu3LOk
MD5: c7dbb50f41fc014056530971c5a6bf70
Unofficial Huawei Ascend P1 ROMS
Cyanogen Mod 10.1
Cyanogen Mod 10.2
MoKee OpenSource
MIUI
JellyBeer
AOKP
PAC
RootBox
Nice!
Hey dude . thanks for sharing that .
i wonder what ICS version is it ? cuz i need Android ICS 4.0.4 for my Huawei Ascend p1 .
saob007 said:
Hey dude . thanks for sharing that .
i wonder what ICS version is it ? cuz i need Android ICS 4.0.4 for my Huawei Ascend p1 .
Click to expand...
Click to collapse
I've only seen 4.0.3 in all ICS firmwares for the Ascend P1.
Hi Arkedk
How can I root my ascend p1.
I have B226 FW.
Sorry for bad english.
Sent from my U9200 using xda premium
demhaa said:
Hi Arkedk
How can I root my ascend p1.
I have B226 FW.
Sorry for bad english.
Sent from my U9200 using xda premium
Click to expand...
Click to collapse
There is external pages that runs you through that.
Team Android:
http://www.teamandroid.com/2012/08/...nd-p1-android-40-b113-b115-official-firmware/
Johnny Paranoia:
http://johnnyparanoia.blogspot.dk/search/label/Huawei Ascend P1 U9200
Or you can boot cwm recovery and flash a the SuperSU package with Busybox from this thread.
http://forum.xda-developers.com/showthread.php?t=1993331
Hello, happy New Year
Version U9200-1V100R001C00B226 it is multilingual or only in English, to see if I can put it on my Ascend P1 french
I believe they all are multi lingual. But I've only used English in them and don't remember if they contained all languages. The global version has most languages.
Sent from my U9200 using xda app-developers app
Hello , i have firmware version b023 ( vodafone )
How do I install this firmware? I want to install the B226
thank
best regards
Great stuff bud!
I just got my Huawei Ascend P1 U9200 a few weeks back. Really enjoying it.
I currently have B105 FW. Waiting patiently on how to flash B525 on the U9200 :good:
Shaheenem said:
Great stuff bud!
I just got my Huawei Ascend P1 U9200 a few weeks back. Really enjoying it.
I currently have B105 FW. Waiting patiently on how to flash B525 on the U9200 :good:
Click to expand...
Click to collapse
I've updated the thread with a upgrade tutorial, this is a bit advanced if you're not used to use ADB and Fastboot and haven't set it up.
I will make a complete walk through on how to set it all up later.
Shaheenem said:
Great stuff bud!
I just got my Huawei Ascend P1 U9200 a few weeks back. Really enjoying it.
I currently have B105 FW. Waiting patiently on how to flash B525 on the U9200 :good:
Click to expand...
Click to collapse
me too go go go
U9200-1V100R001CHNC00B525_681031.zip (658.5 MB) [EMUI 1.5 Jelly Bean Beta]
Click to expand...
Click to collapse
does this have google play?
Help
Hi
I bought a laptop a Chinese fashion modelmid-gsm.'ve Upgraded version now gone.
I want to return to the previous version
You can help
This is the version of Android I 4.0.3.My Tablet Model: MID-GSM
Android Version: 4.0.3
Baseband Version: M1190_V 1.0.3
Kernel Version: 3.0.8
software_pub @ compiler # 11
Build Number: 20120526-LY-F8S.0.5.5
Please tell me where to download this version
Please get help immediately
zanyarzz said:
Hi
I bought a laptop a Chinese fashion modelmid-gsm.'ve Upgraded version now gone.
I want to return to the previous version
You can help
This is the version of Android I 4.0.3.My Tablet Model: MID-GSM
Android Version: 4.0.3
Baseband Version: M1190_V 1.0.3
Kernel Version: 3.0.8
software_pub @ compiler # 11
Build Number: 20120526-LY-F8S.0.5.5
Please tell me where to download this version
Please get help immediately
Click to expand...
Click to collapse
This makes no sense. Looks like a Google Translate. These firmwares is ONLY for Huawei Ascend P1 (U9200).
Let it boot up and then go to:
Settings->Storage->Software Upgrade->SD card Upgrade->Confirm->Upgrade
This will erase all apps and settings, so remember to backup your stuff.
There is also a force upgrade mode which you can enter by holding down Volume Up and Volume Down keys right after the vibration when the device boots up.
U9200-1V100R001C00B226.zip (486.2 MB) [Generel Global Version]
MD5: 3e14da9fac783dc5494fcf5b105ed4ed
U9200-1V100R001C185B105.zip (501.4 MB) [North European Version]
MD5: 90870fbf130bafb05c694df38283440e
Click to expand...
Click to collapse
I have on my polish P1 U9200-1V100R001C185B104 software. I can't play youtube videos in you tube stock&new app and on browsers (maxthoon, chrome, boat). If I turn off dolby sond in Music+ app then I can once (but not always) play a video on YT app. Aftrer 3-4 times trying to play a video phone gets lags worse than HTC Wildfire, sreen moves/shakes few pixels to right showing on left something orange and after few minutes it reboots. When phone boot up it works without lags but video playback don't work.
And here are my questions:
Can I force install of North European Version or Generel Global Version without installing cwm?
If it might help and won't cruch my new phone or I should go to Huawei Authorized Service Center??
no but you can download them separately. http://goo.im | *jb-_date_of_release_*
the only problem for me was it overwrote the '/cust' folder and didnt let me make calls. only sms and data.. :/
I think it has something to do with the telephony app, not sure.
otherwise works great.
anyone know the diffrence betwen U9200-1V100R001C185B105.zip and U9200-1V100R001C185B104.zip ?
arkedk said:
I've updated the thread with a upgrade tutorial, this is a bit advanced if you're not used to use ADB and Fastboot and haven't set it up.
I will make a complete walk through on how to set it all up later.
Click to expand...
Click to collapse
I was able to bypass the verification check by using clockwork to format boot, cache,system,data and dalvik , hope this helps
---------- Post added at 09:50 AM ---------- Previous post was at 09:48 AM ----------
s.l.f said:
anyone know the diffrence betwen U9200-1V100R001C185B105.zip and U9200-1V100R001C185B104.zip ?
Click to expand...
Click to collapse
Yes, one is B104 firmware and the other is B105 firmware lol
Hello,
I do this
Code:
Settings->Storage->Software Upgrade->SD card Upgrade->Confirm->Upgrade
and just seen this
Code:
[COLOR="Sienna"]Huawei SD card update processing...
Please wait several minutes...
Version list verify fail!
Huawei SDcard update fail......[/COLOR]
How can Update my phone with U9200-1V100R001CHNC00B525_681031.zip
tnx.
I also changed build.prop like below:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun 29 17:54:05 CST 2012
ro.build.date.utc=1340963645
ro.build.type=user
ro.build.user=d81004864
ro.build.host=sapp9-android-server2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.wifi.channels=
ro.board.platform=omap4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=viva
# Do not try to parse ro.build.description or .fingerprint
ro.build.characteristics=default
# end build properties
# begin of volatile config
##############################################################
#
#modify history author date reason
#DTS2011120602683 d00185874 2011/12/06 add audio modem interface
#DTS2011120105354 z00192837 20111220 merge the funtion of FM on ICS
#DTS2011102003963 l00186420 20111020 defined the function of press key on MMITest
#DTS2011121904887 c00204148 2011/12/19 modify the USE_FLASHLESS instead of system-prop way
#DTS2012021603135 h58695 2012/02/16 add switch main storage location function
#DTS2012022802590 w000193878 2012/03/07 add internal sd card flag
##############################################################
wifi.interface=wlan0
com.ti.omap_enhancement=true
#DTS2011120602683 d00185873 2011/12/06 Start
audioril.lib=libhuawei-audio-ril.so
#DTS2011120602683 d00185873 2011/12/06 End
#/*<DTS2011120105354 z00192837 20111220 begin*/
ro.config.fm_type=libbcmfm_if
#/*DTS2011120105354 z00192837 20111220 end>*/
#DTS2011102003963 l00186420 20111020 begin
ro.config.KeyPassToUser=true
#DTS2011102003963 l00186420 20111020 end
# <DTS2011112304441 k00159607 20111124 sync BU5D00953 begin
# Whether use the way of resource customize
# <DTS2012032005482 huhao 20120320 begin
ro.config.hw_isCustomize=true
# The Customize Type we need
ro.config.hw_customizeType=1
# DTS2012032005482 huhao 20120320 end>
# DTS2011112304441 k00159607 20111124 sync BU5D00953 end>
#DTS2011120606556 f00189446 20111206 begin
# ro.config.hw_addsettingsdbex is added for DTS2010081400204 by h00152727&x00165767
ro.config.hw_addsettingsdbex=1
# ro.config.hw_menu_unlockscreen is added for DTS2011030204519 by s00159653
ro.config.hw_menu_unlockscreen=false
#DTS2011120606556 f00189446 20111206 end
#DTS2011120503999 liuhao 20111205 begin
ro.config.incall_notify_mms=true
#DTS2011120503999 liuhao 20111205 end
# DTS2011032202087 g00194542 20111212 begin
# Enable closing the Gsensor when Activity needn't
ro.config.hw_GSensorOptimize=true
# DTS2011032202087 g00194542 20111212 end
# <DTS2012021507323 taoning 20111103 Begin
# <DTS2011110200257 taoning 20111103 Begin
ro.config.hw_vcardBase64=true
# DTS2011110200257 taoning 20111103 End>
# DTS2012021507323 taoning 20111103 End>
#DTS2010101603090 jinsu 20101020 begin! synchronization BU6D00416 yuanzhiquan , for taiwan
ro.config.endstksession=true
#DTS2010101603090 jinsu 20101020 end! synchronization BU6D00416 yuanzhiquan , for taiwan
# DTS2011112101441 h00152727 for omacp 20111121 begin
ro.config.hw_omacp=1
# DTS2011112101441 h00152727 for omacp 20111121 end
# DTS2011092101089 k00159607 20110921 begin
ro.config.hw_RemindWifiToPdp=true
# DTS2011092101089 k00159607 20110921 end
#DTS2010060300084 xiongshiyi 00165767 20100603 begin
ro.config.keypasstouser=true
#DTS2010060300084 xiongshiyi 00165767 20100603 end
# <DTS2011121603221 ningzhenyu00184073 20111221 begin
ro.config.hw_lockscreen=true
# DTS2011121603221 ningzhenyu00184073 20111221 end>
# <DTS2010111202622 mengxiaokun00172620 20101112 begin
ro.config.hw_proximity=true
# DTS2010111202622 mengxiaokun00172620 20101112 end>
#DTS2011033000979 caolibin begin
ro.config.hwft_PinPukUnlockscr=true
#DTS2011033000979 caolibin end
#DTS2011021201507 lishilong begin
ro.backlight.space = 5000
#DTS2011021201507 lishilong end
#DTS2011101004724 liutianbao lkf59271 20111208 begin
ro.config.bro_about=true
ro.config.bro_exit=true
#DTS2011101004724 liutianbao lkf59271 2011208 end
# <DTS2011120504027 luowentao59275 20111205 begin
ro.config.hw_toolbox=true
# DTS2011120504027 luowentao59275 20111205 end
# DTS2011121206253 luowentao kf59275 20111212 begin
ro.config.hw_temperature_warn=true
# DTS2011121206253 luowentao kf59275 20111212 end
# DTS2010082001008 by liuxiangning 20100820 begin
# DTS2012041003089 z00183808 20120410 begin
ro.config.hw_uaprof=http://wap1.huawei.com/uaprof/HUAWEI_U9200_UAProfile.xml
# DTS2012041003089 z00183808 20120410 end
# DTS2010082001008 by liuxiangning 20100820 end
# DTS2010092701023 mengxiaokun00172620 20100930 begin
# allow to tear down mobile data connection when device is idle
ro.config.hw_power_saving=true
# DTS2010092701023 mengxiaokun00172620 20100930 end
# DTS2011102703577 niguanhua 20111123 begin
ro.config.hw_voicerecord=true
# DTS2011102703577 niguanhua 20111123 end
# DTS2011112503270 yangchenghai 00184280 20111205 begin
#DTS2012051007729 jiangxiaoke KF59274 20120510 delete
# DTS2011112503270 yangchenghai 00184280 20111205 end
#DTS2011121600561 niguanhua 20111216 begin
#DTS2012022900500 nkf59272 20120229 begin
ro.config.hw_show_number=false
#DTS2012022900500 nkf59272 20120229 end
#DTS2011121600561 niguanhua 20111216 end
# DTS2011101004724 w00193978 20110713 begin
ro.config.bro_about=true
ro.config.bro_exit=true
# DTS2011101004724 w00193978 20110713 end
# DTS2011112504993 fujinhu 20111124 begin
ro.config.AM_PM_STYLE=2
# DTS2011112504993 fujinhu 20111124 end
# DTS2010121704813 jinhui 20101228 begin
ro.config.do_sdcard_upgrade=true
# DTS2010121704813 jinhui 20101228 end
# DTS2012032305353 fujinhu 20120323 begin
# DTS2012031508008 xiazhonglin 00206005 20120315 begin
# DTS2011120600123 wuye 00193878 20111206 begin
ro.config.hw_quickpoweron=true
# DTS2011120600123 wuye 00193878 20111206 end
# DTS2012031508008 xiazhonglin 00206005 20120315 end
# DTS2012032305353 fujinhu 20120323 end
# <DTS2011122600794 g00204739 20111226 bein
# for custom-make emergency numbers, the format is ECC category + ECM number
ro.config.hw_ecclist_withcard=1+110,6+119,8+118
ro.config.hw_ecclist_nocard=1+110,6+119,8+118
# DTS2011122600794 g00204739 20111226 end>
# DTS2011121904887 c00204148 20111219 begin
ro.config.hw_flashless=false
# DTS2011121904887 c00204148 20111219 end
#DTS2011102405215 x00186492 20111021 BEGIN
ro.config.hw_test_version=true
#DTS2011102405215 x00186492 20111021 END
ro.config.hw_sns_acc_support=38
# DTS2011121904887 c00204148 20111219 end
# BEGIN PN:DTS2012010505568,Added by fengfeng00172574, 2012/1/6
persist.sys.strictmode.visual=false
# END PN:DTS2012010505568,Added by fengfeng00172574, 2012/1/6
# DTS2012011207615 zhaowei 00195747 20120112 begin
ro.cellbroadcast.emergencyids=0-65534
# DTS2012011207615 zhaowei 00195747 20120112 end
#DTS2012011902027 guanjunujie 20120120 begin
ro.config.hw_allowformat=true
#DTS2012011902027 guanjunujie 20120120 end
# DTS2012010500726 w00166520 for fast power on 20120105 begin
persist.sys.quickpoweron=normal
persist.sys.animationstart=false
ro.config.hw_poanimation=5000
# DTS2012010500726 w00166520 for fast power on 20120105 end
# <DTS2012010500769 w00166520 poweroff alarm 20120105 begin
persist.sys.powerup_reason=
ro.poweroff_alarm=true
persist.sys.actualpoweron=true
#DTS2012010500769 w00166520 poweroff alarm 20120105 end
#DTS2012011902069 guanjunujie 20120120 begin
ro.config.hw_allow_ums_and_mtp=true
#DTS2012011902069 guanjunujie 20120120 end
#DTS2012020907712 guqi00194542 20120210 begin
keyguard.no_require_sim=true
#DTS2012020907712 guqi00194542 20120210 end
#DTS2012021302244 xiazhonglin00206005 20120213 begin
ro.config.notification_sound=Glory.ogg
ro.config.alarm_alert=Pmukkale.ogg
ro.config.ringtone=Huawei_Tune.ogg
#DTS2012021302244 xiazhonglin00206005 20120213 end
#DTS2012021402184 z00181848 20120221 begin
ro.config.hw_proximitySensor=true
#DTS2012021402184 z00181848 20120221 end
#DTS2012021607935 guanjunujie 20120214 begin
ro.config.switchPrimaryVolume=true
#DTS2012021607935 guanjunujie 20120214 end
#DTS2012021603135 h58695 begin
persist.sys.main_storage=internal_sd
#DTS2012021603135 h58695 end
#DTS2012022308202 f00189446 begin
#/*<DTS2010091000150 yangzijin 20100921 begin
ro.opengles.version=131072
#DTS2010091000150 yangzijin 20100921 end>*/
#DTS2012021704226_zhaojingjing_zhouming_20120217_begin
ro.config.hw_dolby=true
#DTS2012021704226_zhaojingjing_zhouming_20120217_end
# <DTS2012021702623 taoning 20120220 Begin
ro.config.sim_hot_swap=true
# DTS2012021702623 taoning 20120220 End>
#DTS2012013105290 jinyan 00193806 20120221 begin
ro.config.hw_subtitle_support=true
#DTS2012013105290 jinyan 00193806 20120221 end
# <DTS2012021002468 g00204739 20120210 begin
# global version
ro.config.hw_globalEcc = true
# DTS2012021002468 g00204739 20120210 end>
#DTS2012022308202 f00189446 end
# DTS2012021305624 h00152727 for WMA support 20120223 begin
ro.config.helix_enable=true
# DTS2012021305624 h00152727 for WMA support 20120223 end
#DTS2012022204471 litao 20120225 begin
ro.config.CphsOnsEnabled=false
#DTS2012022204471 litao 20120225 end
#DTS2012030302036 jinkehan 20120227 begin
ro.camera.sound.forced=1
#DTS2012030302036 jinkehan 20120227 end
# DTS2012020701830 jkf59274 20120302 begin
ro.config.always_animation=true
# DTS2012020701830 jkf59274 20120302 end
# DTS2012022802590 wuye00193878 20120229 begin
ro.config.internal_sdcard=yes
# DTS2012022802590 wuye00193878 20120229 end
# DTS2012030604690 z00181848 20120309 begin
gsm.sim.num.pin2=3
gsm.sim.num.puk2=10
# DTS2012030604690 z00181848 20120309 end
# DTS2012030603076 yufei y00205987 20120310 begin
#ro.com.google.mcc_fallback=262
# DTS2012030603076 yufei y00205987 20120310 end
#DTS2012021000837 s00190137 20120223 begin
ro.config.hw_use_browser_ua=http://wap1.huawei.com/uaprof/HUAWEI_U9200_UAProfile.xml
#DTS2012021000837 s00190137 20120223 end
# DTS2012011103951 lianmin 20111228 begin
ro.config.hw_gcf_mms=true
# DTS2012011103951 lianmin 20111228 end
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
# DTS2012052207487 t00192950 2012/05/22 Start
ro.com.google.gmsversion=ics_signed_r2
# DTS2012052207487 t00192950 2012/05/22 End
# DTS2012052501919 w00182909 20120612 begin
hw.net.tcp.buffersize.default=4096,262140,523264,4096,49152,523264
hw.net.tcp.buffersize.umts=4096,262140,523264,4096,49152,523264
hw.net.tcp.buffersize.edge=4096,78840,105120,4096,49152,105120
hw.net.tcp.buffersize.gprs=4096,26280,35040,4096,26280,35040
hw.net.tcp.buffersize.hspa=4096,262140,523264,4096,49152,523264
# DTS2012052501919 w00182909 20120612 end
# end of volatile config
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
hwui.render_dirty_regions=false
ro.opengles.version=131072
ro.sf.lcd_density=240
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.product.board=U9200
ro.confg.hw_systemversion=U9200-1V100R001C185B103_SYSTEM
ro.build.display.id=U9200-1V100R001C185B103
ro.product.model=U9200
ro.product.brand=Huawei
ro.build.tags=ota-rel-keys,release-keys
ro.product.manufacturer=HUAWEI
ro.product.name=U9200
ro.product.device=hwu9200
ro.build.id=HuaweiU9200
ro.build.version.incremental=C185B103
ro.build.description=U9200-user 4.0.3 HuaweiU9200 C185B103 ota-rel-keys,release-keys
ro.build.fingerprint=Huawei/U9200/hwu9200:4.0.3/HuaweiU9200/C185B103:user/ota-rel-keys,release-keyss
But again get that error!
ElementalX Kernel
for Moto G4 and G4 Plus
{
"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"
}
ElementalX is designed for maximum stability. It is made for people who depend on their phone every day.
Features
Easy installation and setup with Aroma installer
Fingerprint sensor as home button
Sweep2sleep
Block wakelocks
Rootable
Sound control
Overclock or underclock CPU
NTFS r/w support
Option to disable fsync
advanced color control
performance and power optimizations
upstream ZRAM with lz4 compression
KSM enabled
brighter HBM
adjust or disable vibration
FIOPS i/o scheduler
Does not modify system partition
Does not overwrite modules
Compatible with systemless root
Installation
1. Flash in recovery
For maximum compatibility with all ROMs, ElementalX uses your existing ramdisk.
Notes
This works on both the G4 and the G4 Plus but NOT the G4 Play.
Flashing this does not modify your system partition, only the boot.img. Back up your stock boot.img in recovery or with an app and you can easily restore it if you want to return to stock or install OTAs.
EX Kernel Manager can be used to configure settings and install or update the kernel.
You can also use my free app Button Mapper to customize the actions of the fingerprint sensor if you have the G4 Plus
Google+ Community
Download
Stock Android 8.1.0 Oreo
ElementalX-G4-3.01
Stock Android 7.0
ElementalX-G4-2.01
LineageOS-based Android 7..1.1/7.1.2
ElementalX-G4-1.11-LOS
Stock Android 6.0.1
ElementalX-G4-0.07
CM-based Android 6.0.1
ElementalX-G4-0.07-cm
Source code
https://github.com/flar2/kernel-msm
_____________________________________
XDA:DevDB Information
ElementalX-G4, Kernel for the Moto G4 Plus
Contributors
flar2
Source Code: https://github.com/flar2/kernel-msm
Kernel Special Features:
Version Information
Status: Stable
Created 2016-07-24
Last Updated 2019-03-21
Reserved
0.02:
-build optimizations (linaro 4.9 -O2)
-headphone gain control
0.01:
-Fingerprint sensor as home button
-Sweep2sleep
-Overclock or underclock CPU
-NTFS r/w support
-Option to disable fsync
-advanced color control
-performance and power optimizations
-upstream ZRAM with lz4 compression
-KSM enabled
-brighter HBM
-adjust or disable vibration
-FIOPS i/o scheduler
Reserved
Hi, I have not worked WiFi.
wizard-dima said:
Hi, I have not worked WiFi.
Click to expand...
Click to collapse
Please tell me your model number and build number from the about phone page in settings.
flar2 said:
Please tell me your model number and build number from the about phone page in settings.
Click to expand...
Click to collapse
G4 plus XT1642
build number - MPJ24.139-48
You can add doubletap2wake?
Sweep2sleep only works right to left.
Although I chose to either side.
wizard-dima said:
G4 plus XT1642
build number - MPJ24.139-48
You can add doubletap2wake?
Sweep2sleep only works right to left.
Although I chose to either side.
Click to expand...
Click to collapse
I would also like to see the output of
Code:
lsmod
from adb shell or terminal.
WiFi working and no issues so far
Moto G4
XT1625
BUILD- MPJ24.139-49
LSMOD OUTPUT
Module Size Used by
wlan 4215738 0
core_ctl 20182 0
qdrbg_module 30626 0
qcrypto_module 145880 0
flar2 said:
I would also like to see the output of
Code:
lsmod
from adb shell or terminal.
Click to expand...
Click to collapse
You kernel:
Module Size Used by
qdrbg_module 30626 0
qcrypto_module 145880 0
Stock kernel:
Module Size Used by
core_ctl 20182 0
wlan 4215738 0
qdrbg_module 30626 0
qcrypto_module 145880 2
zanoli99 said:
WiFi working and no issues so far
Moto G4
XT1625
BUILD- MPJ24.139-49
LSMOD OUTPUT
Module Size Used by
wlan 4215738 0
core_ctl 20182 0
qdrbg_module 30626 0
qcrypto_module 145880 0
Click to expand...
Click to collapse
perfect, thanks!
wizard-dima said:
Module Size Used by
qdrbg_module 30626 0
qcrypto_module 145880 0
Click to expand...
Click to collapse
One more question:
Can you show me the output of these commands:
Code:
ls -la /system/lib/modules/
Code:
su -c insmod /system/lib/modules/wlan.ko
flar2 said:
One more question:
Can you show me the output of these commands:
Code:
ls -la /system/lib/modules/
D:\ADB>adb shell ls -la /system/lib/modules/
-rw-r--r-- root root 9404 2009-01-01 09:00 ansi_cprng.ko
-rw-r--r-- root root 128788 2009-01-01 09:00 core_ctl.ko
-rw-r--r-- root root 8736 2009-01-01 09:00 dma_test.ko
-rw-r--r-- root root 6400 2009-01-01 09:00 evbug.ko
-rw-r--r-- root root 6592 2009-01-01 09:00 gpio_axis.ko
-rw-r--r-- root root 7216 2009-01-01 09:00 gpio_event.ko
-rw-r--r-- root root 9712 2009-01-01 09:00 gpio_input.ko
-rw-r--r-- root root 10648 2009-01-01 09:00 gpio_matrix.ko
-rw-r--r-- root root 4200 2009-01-01 09:00 gpio_output.ko
-rw-r--r-- root root 228528 2009-01-01 09:00 isdbt.ko
-rw-r--r-- root root 43304 2009-01-01 09:00 mcDrvModule.ko
-rw-r--r-- root root 20608 2009-01-01 09:00 mcKernelApi.ko
-rw-r--r-- root root 47104 2009-01-01 09:00 mmc_block_test.ko
-rw-r--r-- root root 36916 2009-01-01 09:00 mmc_test.ko
-rw-r--r-- root root 44852 2009-01-01 09:00 oprofile.ko
drwxr-xr-x root root 2009-01-01 09:00 pronto
-rw-r--r-- root root 18088 2009-01-01 09:00 spidev.ko
-rw-r--r-- root root 28816 2009-01-01 09:00 test-iosched.ko
lrw-r--r-- root root 2009-01-01 09:00 wlan.ko -> /system/lib/mo
dules/pronto/pronto_wlan.ko
Code:
su -c insmod /system/lib/modules/wlan.ko
Click to expand...
Click to collapse
D:\ADB>adb shell su -c insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
wizard-dima said:
D:\ADB>adb shell su -c insmod /system/lib/modules/wlan.ko
insmod: failed to load /system/lib/modules/wlan.ko: File exists
Click to expand...
Click to collapse
I should have mentioned this, I need that output withe ElementalX installed.
flar2 said:
I should have mentioned this, I need that output withe ElementalX installed.
Click to expand...
Click to collapse
Sorry, WiFi works.
The problem was that during the first installation I did not have root access.
For the team of your su needed the right, so that's posleh their installation, with no WiFi key problems.
I think it is necessary to specify in the instructions, and a large red font)
wizard-dima said:
Sorry, WiFi works.
The problem was that during the first installation I did not have root access.
For the team of your su needed the right, so that's posleh their installation, with no WiFi key problems.
I think it is necessary to specify in the instructions, and a large red font)
Click to expand...
Click to collapse
Thanks for the head's up.
So without root, no wifi.
I'll see if I can fix that.
on the standard firmware, the phone spends too much charge in sleep mode. You can it somehow fix it?
I don't think I can get the wifi module to load without root.
The problem is I need to mount an image at /system/lib/modules but selinux won't allow it. It is only possible with SuperSu installed unless somebody knows how to modify sepolicy without SuperSU.
wizard-dima said:
on the standard firmware, the phone spends too much charge in sleep mode. You can it somehow fix it?
Click to expand...
Click to collapse
I'm not sure what you mean?
flar2 said:
I'm not sure what you mean?
Click to expand...
Click to collapse
You can add doubletap2wake?
wizard-dima said:
You can add doubletap2wake?
Click to expand...
Click to collapse
I don't know. I think it might cause battery drain on this device. There also isn't a big need for it since the fingerprint sensor is on the front and wakes up the device (at least on the G4 Plus)
working perfectly..thanks bro.
WiFi working ..now i can able to use finger print sensor as home button..thank very much bro..
Moto G4 plus
XT1643
BUILD- MPJ24.139-23.1
LSMOD OUTPUT
Module Size Used by
wlan 4215738 0
core_ctl 20182 0
qdrbg_module 30626 0
qcrypto_module 145880 0
Custom Splash Screen
{
"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"
}
Requirements: Rooted Samsung Galaxy A50 (ONEUI 1 or 2 & GSI)
Splash screens:
A50 Dark
A50 Light
A50 Dark No Knox
A50 Light No Knox
Google Dark
Google Light
No Recovery Button:
A50 Dark
A50 Light
A50 Dark No Knox
A50 Light No Knox
Google Dark
Google Light
Steps:
Download the file you want from the list above (or on the mobile app, the list below... for some reason)
Rename the downloaded file to up_param.tar
Start terminal (you can try this one)
Gain root access using
su
Type / copy this command into the terminal
dd if=/storage/emulated/0/Download/up_param.tar of=/dev/block/platform/13520000.ufs/by-name/up_param
Mission accomplished
If you need any help or have any ideas for other splash screens i could create, please comment down below. Thanks
Thanks to yamen_tn for the installation instructions
I'm going to make versions without the recovery button.
Working Awesome...got rid of that annoying unlocked bootloader warning msg with a cool new look...thnz bro...
Albermarle said:
I tried to remove the "Hold for recovery" messages with Photoshop and repacked the .tar with 7z and it shows some corrupted-ass lines lol better leave this to the pros
Click to expand...
Click to collapse
Ah, dw, i'm gonna upload the ones without recovery now. Just needs some trailing zero's in hex tis all
Albermarle said:
I tried to remove the "Hold for recovery" messages with Photoshop and repacked the .tar with 7z and it shows some corrupted-ass lines lol better leave this to the pros
Click to expand...
Click to collapse
New versions without recovery button now uploaded
Thanks for sharing with us
flashed your dark splash screen w/o knox, looks fine and i'm very happy to get rid of the annoying samsung messages :highfive:
A50 is getting alot of development started. Is this something that is kind of cross compatible with the a70 now that twrp is out?
ykjae said:
A50 is getting alot of development started. Is this something that is kind of cross compatible with the a70 now that twrp is out?
Click to expand...
Click to collapse
It does not require you to have TWRP, just root. I can Look into it, I'd just need to find the a70 stock up_param file
Hi!
Fellow A70 user here. Great job on getting this working. We were also try something similar out, but have failed yet.
If I haven't interpreted wrong, it seems that the up_params partition on the A50 is a simple tar archive with all the splash pngs. Well unfortunately the A70 does not have an 'up_params' partition, it instead has a 'params' partition that isn't a tar apparently. (Probably because it's a Snapdragon and this is an exynos).
Here's the ls of the bootdevice:
abl cmnlib efs logfs persistent system
aop cmnlib64 em misc pmic tz
apdp ddr fota modem product uefisecapp
apnhlos debug fsc modemst1 qupfw userdata
bksecapp devcfg fsg modemst2 recovery vbmeta
bluetooth devinfo hidden msadp sec_efs vendor
boot dpo hyp omr secdata vk
bota dqmdbg keymaster pad ssd xbl
btd dsp keystore param steady xbl_config
cache dtbo limits persist storsec
I'll try to upload the params image and send it in a couple hours.
Any idea what might be going on? Any help is appreciated
---------- Post added at 06:46 PM ---------- Previous post was at 06:30 PM ----------
@randomajl Here's the param: https://anonfile.com/g944Wc7cnc/param
FriendlyNeighborhoodShane said:
Hi!
Fellow A70 user here. Great job on getting this working. We were also try something similar out, but have failed yet.
If I haven't interpreted wrong, it seems that the up_params partition on the A50 is a simple tar archive with all the splash pngs. Well unfortunately the A70 does not have an 'up_params' partition, it instead has a 'params' partition that isn't a tar apparently. (Probably because it's a Snapdragon and this is an exynos).
Here's the ls of the bootdevice:
abl cmnlib efs logfs persistent system
aop cmnlib64 em misc pmic tz
apdp ddr fota modem product uefisecapp
apnhlos debug fsc modemst1 qupfw userdata
bksecapp devcfg fsg modemst2 recovery vbmeta
bluetooth devinfo hidden msadp sec_efs vendor
boot dpo hyp omr secdata vk
bota dqmdbg keymaster pad ssd xbl
btd dsp keystore param steady xbl_config
cache dtbo limits persist storsec
I'll try to upload the params image and send it in a couple hours.
Any idea what might be going on? Any help is appreciated
---------- Post added at 06:46 PM ---------- Previous post was at 06:30 PM ----------
@randomajl Here's the param: https://anonfile.com/g944Wc7cnc/param
Click to expand...
Click to collapse
The param file is something different, on A50 we also have param. Hmm
RandomAJL said:
The param file is something different, on A50 we also have param. Hmm
Click to expand...
Click to collapse
Considering that we don't have the UP_param the param.bin is the safest bet to find the pictures since thats how it stored the png files on older Samsung devices
Hi, thanks for these amazing splash screens!
Could you make one where the "Press to continue" tab is between the logo and the "powered by android"?
Now it overlaps the logo and I think it will look cleaner when it's centered and lower.
I was thinking about something like this:
Thanks!
Edit: it looks like the image server is down atm, but i hope you understand what i mean
Chris3007 said:
Hi, thanks for these amazing splash screens!
Could you make one where the "Press to continue" tab is between the logo and the "powered by android"?
Now it overlaps the logo and I think it will look cleaner when it's centered and lower.
I was thinking about something like this:
Thanks!
Edit: it looks like the image server is down atm, but i hope you understand what i mean
Click to expand...
Click to collapse
I know what you mean. The reasoning for that placement is that it is telling you what button to press.
awsome!!! And it works!! Thank you very much!
FriendlyNeighborhoodShane said:
Hi!
Fellow A70 user here. Great job on getting this working. We were also try something similar out, but have failed yet.
If I haven't interpreted wrong, it seems that the up_params partition on the A50 is a simple tar archive with all the splash pngs. Well unfortunately the A70 does not have an 'up_params' partition, it instead has a 'params' partition that isn't a tar apparently. (Probably because it's a Snapdragon and this is an exynos).
Here's the ls of the bootdevice:
abl cmnlib efs logfs persistent system
aop cmnlib64 em misc pmic tz
apdp ddr fota modem product uefisecapp
apnhlos debug fsc modemst1 qupfw userdata
bksecapp devcfg fsg modemst2 recovery vbmeta
bluetooth devinfo hidden msadp sec_efs vendor
boot dpo hyp omr secdata vk
bota dqmdbg keymaster pad ssd xbl
btd dsp keystore param steady xbl_config
cache dtbo limits persist storsec
I'll try to upload the params image and send it in a couple hours.
Any idea what might be going on? Any help is appreciated
---------- Post added at 06:46 PM ---------- Previous post was at 06:30 PM ----------
@randomajl Here's the param: https://anonfile.com/g944Wc7cnc/param
Click to expand...
Click to collapse
Same with galaxy fold. Any idea?
A30 please!
I am A30, i need a bootlogo for my please. Light versión.
would this work on the a20
The first question here is: How to gain root access in TERMUX ? "apt install tsu" doesn't work.
Is it necessary to install root repo ?
jasoncardeira said:
The first question here is: How to gain root access in TERMUX ? "apt install tsu" doesn't work.
Is it necessary to install root repo ?
Click to expand...
Click to collapse
Just use su
nahuelarias17 said:
I am A30, i need a bootlogo for my please. Light versión.
Click to expand...
Click to collapse
I'd need your stock file then