{
"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"
}
For anyone that has followed my work in the past, you will be familiar with the rom name. It was a line of Roms i made for the ZTE Warp, Warp Sequent, Desire 510, and the Motorola Moto G in addition to Awesome Android, Cyanogenmod and AOKP builds.
I will be reintroducing the rom on the Alcatel Idol 4 Cricket Variant
ROM Features
Init.d support
Build.prop Tweaks
Various System Tweaks
Cpu Core Clock Control tweaks
Deodexed
Optimized
All Bloatware Removed
New Bootanimation
Code:
Changelog
To Do: Make more awesomeness!
Test Version 1
-Initial Beta Test
-Deodexed Rom
-Replaced Joy Launcher with Google Now Launcher
-Added Google Assistant
-Debloated
-Added Init.d Support
-Adjusted factory CPU core clockspeed
-Adjusted CPU Core hotplug
-Zipaligned
-Changed BootAnimation
-Adjusted Minfree values
-Adjusted Low Memory Killer Values
This Rom is for the Cricket 6055U
do not install on other variants!
You Have been warned!!
Once you have TWRP flashed to your device
Copy Shinjitsu_Rom_Beta_1.zip to Sdcard
(You May need an external sdcard for this)
Boot into TWRP and flash the zip
Bug report, bug report, bug report
If something isn't working report back and,
i will try to get it fixed in a timely manner
(Keep in mind i do have a full time job)
Code:
Removed APks
JrdFota.apk
Exchange.apk
Email.apk
Compass.apk
JrdUser2Root.apk
NewsWeather.apk
FileManager.apk
Browser.apk
Music.apk
TctSoundRecorder.apk
TctCalculator.apk
TctWeather.apk
Launcher.apk
WallpaperCropperOverlay.apk
VpnDialogs-overlay.apk
TctWeather-overlay.apk
TctSoundRecorder-overlay.apk
TctFMRadio-overlay.apk
TctFileManager-overlay.apk
TctEmail-overlay.apk
TctCamera-overlay.apk
Tag-overlay.apk
SystemUI-overlay.apk
SmartSuite-overlay.apk
Shel-overlay.apk
SettingProvider-overlay.apk
Settings-overlay.apk
Protips-overlay.apk
PrintSpooler-overlay.apk
PrimaryCardController-overlay.apk
PhotoTable-overlay.apk
PhaseBeam-overlay.apk
PartnerBookmarksProvider-overlay.apk
OTAProvisioningClient-overlay.apk
NoiseField-overlay.apk
NfcNci-overlay.apk
Music-overlay.apk
MusicFX-overlay.apk
Mms-overlay.apk
MediaProvider-overlay.apk
MaxxService-overlay.apk
MaxxAudio-overlay.apk
ManagedProvision-overlay.apk
MagicLock-overlay.apk
LiveWallpaperPicker-overlay.apk
LiveWallpapers-overlay.apk
Launcher-overlay.apk
KeyChanin-overlay.apk
JrdSsv-overlay.apk
JrdFota-overlay.apk
InputDevices-overlay.apk
HTMLViewer-overlay.apk
HoloSpiralWallpaper-overlay.apk
Gallery-overlay.apk
Galaxy4-overlay.apk
FusedLocation-overlay.apk
framework-res-overlay.apk
ExternalStorageProvider-overlay.apk
Elabel-overlay.apk
DrmProvider-overlay.apk
DownloadProviderUi-overlay.apk
DownloadProvider-overlay.apk
DocumanetsUI-overlay.apk
Dialer-overlay.apk
DefaultContainerService-overlay.apk
ContactsProvider-overlay.apk
Contacts-overlay.apk
Compass-overlay.apk
ChromeCustomizations-overlay.apk
CertInstaller-overlay.apk
CellBroadcastReceiver-overlay.apk
CaptivePortalLogin-overlay.apk
CalendarProvider-overlay.apk
Browser-overlay.apk
Bluetooth-overlay.apk
BluetoothExt-overlay.apk
BasicDreams-overlay.apk
BackupRestoreConfirmation-overlay.apk
ATTDMClient-overlay.apk
Code:
Debloated apks
Google Books
Cloud Print
Google Drive
Gmail
Hangouts
Play Music
News Stand
Play Games
Plus One
Talkback
Play Videos
YouTube
Proofs of CPU Core hot-plugging and Deep Sleep
Links are in the Download Section!
XDA:DevDB Information
Shinjitsu Rom, ROM for the Alcatel Idol 4S
Contributors
shinru2004
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Cricket 6055u
Based On: Stock
Version Information
Status: Beta
Current Beta Version: 3.31.18
Beta Release Date: 2018-03-30
Created 2018-04-01
Last Updated 2018-04-01
Perfect rom but camera recording does not work.
Fix please
Not seeing a link, would like to try it out
Thanks so much for this. Everything working smoothly minus the camera like stated above.
Ok, but i need install any zip of gapps ?
variant 6055b forgotten ???
Orionpax5000 said:
variant 6055b forgotten
Click to expand...
Click to collapse
6055k too
Will 6070k support be available in the future?
where do i download the zip from
Download the file from the OPs other thread
i left in the wrong camera.apk i'll update the zip in a bit and that will fix it.
Updated the Camera.apk everything should work now. New zip can be found in the downloads section
Hi, I installed the rom cause´I thought that I would have the sim unlock off, I had a trouble, My phone was working perfect yesterday and I wanted to get root acces, I followed the instructions using Sugar QCT and I got another android version that has SIM lock. Do you know how can I stop the simlock process or another method to be able to use my sim? I'm from El Salvador, Central America
@shinru2004, This rom wont install on my 2 Cricket phones, model 6055U. The error was this is for Cricket idol4, you have idol 4. When I looked at the updater-script, you have it set to look for 6055K. I changed that according to the info in my build.prop and it installs fine now. For anyone else running into this problem, here is a modified updater-script so this will install on a 6055U Cricket model, for which this rom was made. Nice rom and I thank you much for the time and effort in releasing this.
Modified updater-script https://drive.google.com/open?id=1-DnIa7C3RuzqN80-7kv9-sRIRqRPy-th
To anyone wondering if this will work on any other model idol 4, i'll say this for sure. Any model idol 4 that can swap stock rom with the 6055U and works will work on this rom. Just edit the updater-script or let me know and i'll post a modified updater-script for you. to get this working, simply open the rom with winrar, navigate to where updater-script is and overwrite the original with my modified one and you should be good. Rom looks like a breath of fresh air compared to the stock and will tide me over until @Unjustified Dev releases Lineage OS.
LTE doesnt appear to be working? Checked the APN settings and they are the same as my stock. All my fiances phone is getting is 4G. Other than that, the rom runs great so far.
Compatibility
Is it compatibgle with 6055P?
PizzaG said:
@shinru2004, This rom wont install on my 2 Cricket phones, model 6055U. The error was this is for Cricket idol4, you have idol 4. When I looked at the updater-script, you have it set to look for 6055K. I changed that according to the info in my build.prop and it installs fine now. For anyone else running into this problem, here is a modified updater-script so this will install on a 6055U Cricket model, for which this rom was made. Nice rom and I thank you much for the time and effort in releasing this.
Modified updater-script https://drive.google.com/open?id=1-DnIa7C3RuzqN80-7kv9-sRIRqRPy-th
To anyone wondering if this will work on any other model idol 4, i'll say this for sure. Any model idol 4 that can swap stock rom with the 6055U and works will work on this rom. Just edit the updater-script or let me know and i'll post a modified updater-script for you. to get this working, simply open the rom with winrar, navigate to where updater-script is and overwrite the original with my modified one and you should be good. Rom looks like a breath of fresh air compared to the stock and will tide me over until @Unjustified Dev releases Lineage OS.
Click to expand...
Click to collapse
Here is my build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=~CricketRom~ Beta4
ro.build.version.incremental=~CricketRom~ Beta4
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2017-07-01
ro.build.version.base_os=
ro.build.date=2018年 05月 25日 星期五 11:05:08 CST
ro.build.date.utc=1496977508
ro.build.type=userdebug
ro.build.user=PizzaG
ro.build.host=aclgcl-ubnt171
ro.build.tags=release-keys
ro.build.flavor=idol452_voltecricket-userdebug
ro.product.model=Alcatel 6055U
ro.product.brand=TCL
ro.product.name=Alcatel_6055U
ro.product.device=idol4
ro.product.board=msm8952
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=TCL
ro.wifi.channels=
ro.board.platform=msm8952
# ro.build.product is obsolete; use ro.product.device
ro.build.product=idol452_voltecricket
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=idol452_voltecricket-user 6.0.1 MMB29M vCCJ-0 release-keys
ro.build.fingerprint=TCL/Alcatel_6055U/idol4:6.0.1/MMB29M/vCCJ-0:user/release-keys
ro.build.characteristics=nosdcard
ro.tct.product=idol452_voltecricket
You can make one updater-script to me ?
you have my rom currently installed and trying to install Shinjitsu rom?
---------- Post added at 10:11 PM ---------- Previous post was at 10:04 PM ----------
oLdSchool991 said:
Here is my build.prop:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=~CricketRom~ Beta4
ro.build.version.incremental=~CricketRom~ Beta4
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2017-07-01
ro.build.version.base_os=
ro.build.date=2018年 05月 25日 星期五 11:05:08 CST
ro.build.date.utc=1496977508
ro.build.type=userdebug
ro.build.user=PizzaG
ro.build.host=aclgcl-ubnt171
ro.build.tags=release-keys
ro.build.flavor=idol452_voltecricket-userdebug
ro.product.model=Alcatel 6055U
ro.product.brand=TCL
ro.product.name=Alcatel_6055U
ro.product.device=idol4
ro.product.board=msm8952
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=TCL
ro.wifi.channels=
ro.board.platform=msm8952
# ro.build.product is obsolete; use ro.product.device
ro.build.product=idol452_voltecricket
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=idol452_voltecricket-user 6.0.1 MMB29M vCCJ-0 release-keys
ro.build.fingerprint=TCL/Alcatel_6055U/idol4:6.0.1/MMB29M/vCCJ-0:user/release-keys
ro.build.characteristics=nosdcard
ro.tct.product=idol452_voltecricket
You can make one updater-script to me ?
Click to expand...
Click to collapse
Updater Script based on your current build.prop so you can install Shinjitsu Rom
https://drive.google.com/open?id=1QH1AyqFpClQSQFUZrQhQYvY-feKrj33n
it's to try new roms, but your rom is incredible
oLdSchool991 said:
it's to try new roms, but your rom is incredible
Click to expand...
Click to collapse
Thank You, I appreciate that:good:
That updater script will only work for installing Shinjitsu Rom though, so be sure to read my instructions on how to put it into Shinjitsu Rom
Related
Hi
After flashing a new ROM. I missing many apps like "Opera", "YouTube" And much more.. Only some apps appears in my market.
I've re-flash the ROM but did fixed. I did many things like clear market cache. Rebooting and... But no way
Any idea please?
[Fixed]
Steps:
* Do a Reset Factory for the device.
* Connect to Wi-Fi (DO NOT ADD YOUR GOOGLE ACCOUNT).
* Enable: Settings -> Unknown source
* Run "Samsung Apps" & update it.
* Download some app from "Samsung Apps".
* Go to "Market" then add your account.
* Enjoy.
Any idea?
Sent from my GT-I9000 using XDA App
This is a know issue with all 3rd party ROMs. You will not get the full list of apps in the market if you use ROMs other than stock from Samsung. It is not the fault of the market it is the fault of the ROM.
This is just one issue of many which devs refuse to warn people about in their threads.
ArtificialSweetener said:
This is a know issue with all 3rd party ROMs. You will not get the full list of apps in the market if you use ROMs other than stock from Samsung. It is not the fault of the market it is the fault of the ROM.
This is just one issue of many which devs refuse to warn people about in their threads.
Click to expand...
Click to collapse
this is speculatory.
web.designer.iq,
check your build.prop signature id. this is what the market uses to identify your device. inquire with the rom developer to see if it has been modified. compare build.prop from your stock rom against your current custom rom's build.prop.
pershoot said:
this is speculatory.
web.designer.iq,
check your build.prop signature id. this is what the market uses to identify your device. inquire with the rom developer to see if it has been modified. compare build.prop from your stock rom against your current custom rom's build.prop.
Click to expand...
Click to collapse
This is not speculatory. Its because the ROMs are changed with different IDs other than original from Samsung. This causes the problem in the market as real developers have no knowledge of these hacked devices hence their apps do not show up to these user.
Such was the case with VMware View in the market. Users with hacked ROMs installed were bombarding VMware stating that their app was not showing up. The Devs over at VMware confirmed that the Tab 10.1 was in the list of compatible devices and they had no issues with any of the units they had in their office. Little did VMware know all the users posting about it in their forum were running ROMs from this website as it was later found.
This is just another reason I am against 3rd party ROMs. They dont work correctly, cause confusion, and generally just wastes everyone time due to incompatibilities and instability. The worst thing about these kind of situations is that the real Devs that make apps for the market get confused and have to waste time deal with these users.
ArtificialSweetener said:
This is not speculatory. Its because the ROMs are changed with different IDs other than original from Samsung. This causes the problem in the market as real developers have no knowledge of these hacked devices hence their apps do not show up to these user.
Such was the case with VMware View in the market. Users with hacked ROMs installed were bombarding VMware stating that their app was not showing up. The Devs over at VMware confirmed that the Tab 10.1 was in the list of compatible devices and they had no issues with any of the units they had in their office. Little did VMware know all the users posting about it in their forum were running ROMs from this website as it was later found.
This is just another reason I am against 3rd party ROMs. They dont work correctly, cause confusion, and generally just wastes everyone time due to incompatibilities and instability. The worst thing about these kind of situations is that the real Devs that make apps for the market get confused and have to waste time deal with these users.
Click to expand...
Click to collapse
So what are you here for then?
Synergy Sensation!
Because he can't use his other two screen names. He gets banned like once a week.
Sent from xda premium app
Stardate Tab 10.1 said:
Because he can't use his other two screen names. He gets banned like once a week.
Sent from xda premium app
Click to expand...
Click to collapse
Dont they ban the IP Address and not just the SN?
Synergy Sensation!
ArtificialSweetener said:
This is not speculatory. Its because the ROMs are changed with different IDs other than original from Samsung. This causes the problem in the market as real developers have no knowledge of these hacked devices hence their apps do not show up to these user.
Such was the case with VMware View in the market. Users with hacked ROMs installed were bombarding VMware stating that their app was not showing up. The Devs over at VMware confirmed that the Tab 10.1 was in the list of compatible devices and they had no issues with any of the units they had in their office. Little did VMware know all the users posting about it in their forum were running ROMs from this website as it was later found.
This is just another reason I am against 3rd party ROMs. They dont work correctly, cause confusion, and generally just wastes everyone time due to incompatibilities and instability. The worst thing about these kind of situations is that the real Devs that make apps for the market get confused and have to waste time deal with these users.
Click to expand...
Click to collapse
You can be against whatever you want. It causes confusion and wastes a considerable amount of forum bandwith, when users take seriously the opinion of evangelists (such as yourself) who are not qualified in this regard to give subjective advice to the populous.
Thanks for all
* I did not installed a custom ROM. I just installed a custom Kernel.
* The market was working perfectly with me. Without any issues. Until i re flashed the ROM to the Samsung Stock Europe ROM.
* I use the Original ROM Provided from Samsung for Europe OR Middle East. By Build No is:: HMJ37.XXKFC P7510XXKFC
* There's very stranger problem. So, When i search for opera the folowing page appears to me:
{
"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"
}
Just find a solution please. don't worry about app. I have purcheased many root tools like: Titanium Bakcup, ROM Manager (Premium), Root Explorer and much more. So, I just need a solution how to fix it or i will donate my GT 10.1 to Africa.
Thanks
This is my build.prop file:
* I have also attached a screen capture of my About Tablet.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HMJ37
ro.build.display.id=HMJ37.XXKFC
ro.build.version.incremental=XXKFC
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Thu Jun 23 21:13:45 KST 2011
ro.build.date.utc=1308831225
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-07
ro.build.tags=release-keys
ro.product.model=GT-P7510
ro.product.brand=samsung
ro.product.name=GT-P7510
ro.product.device=GT-P7510
ro.product.board=GT-P7510
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-P7510
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-P7510-user 3.1 HMJ37 XXKFC release-keys
ro.build.fingerprint=samsung/GT-P7510/GT-P7510:3.1/HMJ37/XXKFC:user/release-keys
ro.build.characteristics=tablet,nosdcard
# Samsung Specific Properties
ro.build.PDA=P7510XXKFC
ro.build.hidden_ver=P7510XXKFC
ro.build.changelist=317542
ro.build.buildtag=jenkins-HUDSON_GA_HONEYCOMB_P4-WIFI-TW_MERGE-369
# end build properties
#
# system.prop for P3
#
ro.opengles.version = 131072
wifi.interface=eth0
rild.libpath=/system/lib/libsec-ril-apalone.so
rild.libargs=-d /dev/ttys0
keyguard.no_require_sim=yes
# Samsung Tvout Service
ro.sectvout.enable=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.ringtone=S_Minimal_tone.ogg
ro.config.notification_sound=S_On_time.ogg
ro.config.alarm_alert=Good_Morning.ogg
dev.sfbootcomplete=0
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=288m
ro.secdevenc=true
ro.carrier=wifi-only
drm.service.enabled=true
ro.setupwizard.mode=OPTIONAL
ro.setupwizard.enterprise_mode=1
ro.com.google.gmsversion=3.1_pre-r1
ro.error.receiver.system.apps=com.google.android.feedback
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-samsung
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Up...
Up...
Since I have received the JB update, I have rebuilt the cifs.ko module for my kernel version 3.0.31-256827 as well as 3.0.31-204919
If you have other kernel versions, please let me know and I will try to build the modules for that specific version.
Good news is that patchs3k is not needed anymore! Samsung did the right thing and we don't need to patch the kernel at runtime.
Per @jfrm request, UTF-8 module is now included but DO NOT FORGET to add iocharset=utf8 as options when defining the share in CifsManager.
{
"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
Use at your own risk!
For JB Kernel 3.0.31-368423
cifs_md4-368423.tar.gz
For JB Kernel 3.0.31-256827:
cifs_md4-256827.tar.gz
For JB Kernel 3.0.31-204919
cifs_md4-204919.tar.gz
For JB Kernel 3.0.31-566833
cifs_md4-566833.tar.gz
For JB Kernel 3.0.31-742798
cifs_md4-742798.tar.gz
------
Old topic below, related to the 4.0.1 versions / firmware
Attached you will find a bundle (including the cifs.ko module) that allows you to mount Samba shares on your Galaxy S3 phone. md4.ko module is also included.
You do not need to flash a different kernel, it works with the stock one!
Supported firmwares: XXALE8, XXALEF, ZSALED
Install
a) copy cifs_s3.tar.gz to your /sdcard folder
a) create folder /system/xbin/lib (after you remount your /system as read/write)
b) unpack the tar into that folder
c) execute script load_cifs.sh
Code:
cd /system/xbin/lib
tar xf /sdcard/cifs_s3.tar.gz
./load_cifs.sh
The archive includes the patchs3k executable I have created that changes the live stock kernel to accept any module.
Without running the patchs3k file, no modules can be inserted ...
It means that you cannot use tools that insert the modules at reboot since they will fail if patchs3k is not executed before that.
For this, you will find the load_cifs.sh which is already written so that it can be executed from Script Manager at boot / as super user.
Then you need to use CifsManager (or other mount managers) to mount everything you want
Download
Use at your own risk!
For firmware: XXALE8, XXALEF
cifs_s3.tar.gz
For firmware: ZSALED
cifs_s3.ZSALED.tar.gz
ZSALED can't use it.
Unfortunatly, when I try to run insmod, I get this: insmod: init_module '/system/xbin/lib/cifs.ko' failed (Exec format error)
@vasha100 - thanks for letting me know. I tested only on European one, XXALE8 ...
I will send you a PM and I can get it to run for your firmware too, not the module - the module stays as it is, but I will post another patchs3k file.
on firmwares: XXALEF works,
Thank you so much!
Thanks for the feedback, I have updated the main post - so that people could see what firmwares are supported. If the exact kernel image is used, chances are that the patchs3k will work.
thanks!
Nice work!
Thank you,
With help from fellow member vasha100 - I was able to test the release for ZSALED and confirmed it working too. Everything had to be recompiled, since the kernel is not exactly what runs on the other firmwares ..
Could you build tun.ko module? That will be great if you do this.
tun.ko was my first choice before starting but I was surprised to see that is already precompiled in the stock kernel.
You can just install the OpenVPN installer and Settings apps, copy over your certificates and so on and it will work.
updated the fw to XXALF5, the last official update for Russia (it is on wi-fi, accidentally pressed the install)
method of root CF-Root v6.3
Сopy cifs_s3.tar.gz - all the instructions ... execute script load_cifs.sh, restart your phone....
Сopy cifs_s3.ZSALED.tar.gz, execute script load_cifs.sh, wrote the script is executed ...
I go to the cifsmanager, run a share, write error (mount no such device)
need your help)
I have kernel XALEB
what can I do ?
Hello guys,
I will shortly put a tutorial on how you can send me the details which would help create the patch.
mrmrmrmr said:
I have kernel XALEB
what can I do ?
Click to expand...
Click to collapse
this has worked on my kernel XALEB when I run patchs3k.
But I really wonder the affect of patchs3k on the kernel. What does it really do ?
it doesn't modify the kernel but changes a parameter in /proc ?
now , I need to run this in each boot.
how can we automize it ?
@mrmrmrmr
The effects of patchs3k is that it cancels the checksum verifications of module symbols. This is done within the kernel and it can't be done just by changes within /proc filesystem.
As for adding support of other kernels not already supported, please do the following and post here the values as well as your firmware:
Code:
cat /proc/kallsyms | grep -A 1 check_version
and
Code:
uname -a
I will get them done in few days ...
Hi,
My baseband: I9300XXLE8
Build: IMM76D.I9300XXALEB
cat /proc/kallsyms | grep -A 1 check_version
Code:
c00b5200 t check_version
c00b52d0 t get_modinfo
--
c03cd0b0 t picolcd_check_version
c03cd188 t picolcd_probe
uname -a :
Code:
Linux localhost 3.0.15-554452-user #1 SMP PREEMPT Fri May 18 00:04:22 KST 2012 armv71 GNU/Linux
if you prepare a cifs.ko for these values, I assume I will not need to run patchs3k at every boot.
am I correct ?
Btw, I have a linux box with armv7 compiler. Can you tell me how to prepare the setup for compiling a kernel (or modules) for Galaxy S3 ?
is there a quick guide ?
Thanks.
Baseband: I9300XXLF5
Build: IMM76D.I9300XXALF5
uname -a
Code:
linux localhost 3.0.15-686526-user #1 SMP PREEMPT Thu Jun 7 20:04:56 kst 2012 armv71 GNU/Linux
cat /proc/kallsyms | grep -A 1 check_version
Code:
c00b5248 t check_version
c00b5318 t get_modinfo
--
c03cd574 t picolcd_check_version
c03cd64c t pricolcd_probe
mrmrmrmr said:
Hi,
My baseband: I9300XXLE8
Build: IMM76D.I9300XXALEB
cat /proc/kallsyms | grep -A 1 check_version
Code:
c00b5200 t check_version
c00b52d0 t get_modinfo
--
c03cd0b0 t picolcd_check_version
c03cd188 t picolcd_probe
uname -a :
Code:
Linux localhost 3.0.15-554452-user #1 SMP PREEMPT Fri May 18 00:04:22 KST 2012 armv71 GNU/Linux
if you prepare a cifs.ko for these values, I assume I will not need to run patchs3k at every boot.
am I correct ?
Btw, I have a linux box with armv7 compiler. Can you tell me how to prepare the setup for compiling a kernel (or modules) for Galaxy S3 ?
is there a quick guide ?
Thanks.
Click to expand...
Click to collapse
I'd appreciate an answer
wow how many kernels are out there ??
Kidding I will do them this weekend..
Hi,
can you give me a more detailed description how to do this? Is it done via file explorer and terminal app on the phone itself? Because i tried it this way and cant create the required folder.
Sorry for the stupid question, but Im quit new to this stuff.
Hi,I have a problem with my sgs3, it's working for 5-10 minutes only, after, I cannot make/receive calls/sms,everything else work.
But get connected to 3G/H+ with no problem, and stay connected.
After 5-10 minutes , if i try to make a call or send sms i get "not registred" ,but the 3g/h+ icon is there, and I can navigate in internet through my carrier connection.
I searched every post but didn't find something similar.
It's very strange that a 3G/H+ connection can work and gsm calls/sms not, I don't think it can be a carrier side issue.
SGS3 Int (i9300 exynos)
(wiped)
stock 4.1.2(I9300XXEMC2_ITVEMC1_Italy, tried also other, with the same success )
recovery ->cwm latest
rooted cf autoroot
efs ok
sn ok
imei ok
I tried different modems,different firmwares,same thing.
I really apreciate if someone will share some similar experience so I can get the right direction.Thanks!
try this
http://forum.xda-developers.com/showthread.php?t=1918601
First contact your network operator, probably just a bad SIM card.
Bad SIM Card or Network coverage.
First, try to change you uSIM card.
If it doesn't change the problem, try to change the Modem (some Modem have better performance with some network provider).
Finaly, change your provider.
boomboomer said:
First contact your network operator, probably just a bad SIM card.
Click to expand...
Click to collapse
lelinuxien52 said:
Bad SIM Card or Network coverage.
First, try to change you uSIM card.
If it doesn't change the problem, try to change the Modem (some Modem have better performance with some network provider).
Finaly, change your provider.
Click to expand...
Click to collapse
I call network operator:No problem they said...
I got a new microsim from same operator .same problem, I can make some calls for a while may be for 5 minutes or may be for an hour, the last night had no problem at all , this morning after some calls I get the same message...
the last one is like lelinuxien52 said is to change operator, but it's really strange because I had no problem with the same simcard on my sensation for 1 year...
rednit said:
try this
http://forum.xda-developers.com/showthread.php?t=1918601
Click to expand...
Click to collapse
I have allready tried the ariza patch, I thought that ariza patch have some bug, but wiped ,reflashed original I9300XXEMC2 and also tried different modems :XXEMB5,DXELK1.with the ril match.so... I really don't know what can be....
The only way to get it work is go offline/online, or if doesn't work restart, and I can make/receive some calls...
if I try to manualy connect to my network I get Q message if I want to disconect data service and list available networks(is connected to 3g/h, asks if I want to disconnect),and after another message could not connect to network.Try later...
"Logic"if it ask to disconect, means is connected ,
if I get network not registred when I try to call ...
It means some modem problem, tried other modems,the same ...,may be operator error but i had no problem for 1 year with the same sim with my sensation...
conclusion my logic is.....?Or?..
ps. thanks all for replies!
Try to borrow a SIM from another network, if still the same problem then you may have to return to service centre for warranty repair. You seem to have eliminated all the easy solutions.
boomboomer said:
Try to borrow a SIM from another network, if still the same problem then you may have to return to service centre for warranty repair. You seem to have eliminated all the easy solutions.
Click to expand...
Click to collapse
I don't think I have a valid waranty, I bought s3 from a private and hi had a unreadable payticket,he forgot it in the car and the sun made it allmost all black...so...
nstnkt said:
I don't think I have a valid waranty, I bought s3 from a private and hi had a unreadable payticket,he forgot it in the car and the sun made it allmost all black...so...
Click to expand...
Click to collapse
I have tried other sim .same result.
Can be other software problem ?other than modem/ril?
I opened the phone clean all antenna contacts, inspect antennas patch/joint, also cleaned...nothing.
Installed NoSignalAlert ( https://play.google.com/store/apps/details?id=com.smartandroidapps.missedcall&hl=en )
I have emergency-only event every minute or so...
I make some shots...
moments when everything is good and everyone is happy making a call to operator (155)
{
"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 how it's look when it'sad (note imei ,sn, and I don't get [Service state= out of service] and [mobile network state=connected])
nosignalallert
but,
if( I can navigate in internet even the device says: out of service, not registred, emergency call only ,end of the world...)
then(is not hardware issue)
else(use as (media player | digital Picture Frame | kids toy | professional samsung dust collector))
At night it'd a stable signal with no losing network, I made some change in efs if works i post them.
Today, you have news about your trouble ?
The problem can provide from bad tweaks in your /system/build.prop file.
lelinuxien52 said:
Today, you have news about your trouble ?
The problem can provide from bad tweaks in your /system/build.prop file.
Click to expand...
Click to collapse
It stay more time online looking at the log ,it losed connection every 3-4 hours...
about tweaks, it's fresh original flash
I also changed the right gsm/wcdma frequency bands for my carrier...
this is how it looks
build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.I9300XXEMC2
ro.build.version.incremental=I9300XXEMC2
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Mon Mar 11 17:37:01 KST 2013
ro.build.date.utc=1362991021
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-84
ro.build.tags=release-keys
ro.product.model=GT-I9300
ro.product.brand=samsung
ro.product.name=m0xx
ro.product.device=m0
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=exynos4
# ro.build.product is obsolete; use ro.product.device
ro.build.product=m0
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=m0xx-user 4.1.2 JZO54K I9300XXEMC2 release-keys
ro.build.fingerprint=samsung/m0xx/m0:4.1.2/JZO54K/I9300XXEMC2:user/release-keys
ro.build.characteristics=default
# Samsung Specific Properties
ro.build.PDA=I9300XXEMC2
ro.build.hidden_ver=I9300XXEMC2
ro.build.changelist=1042335
# end build properties
#
# system.prop for smdk4x12
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=320
ro.lcd_min_brightness=20
ro.kernel.qemu=0
ro.tvout.enable=true
persist.sys.storage_preload=1
net.streaming.rtsp.uaprof=http://wap.samsungmobile.com/uaprof/
# Multimedia property for Smart View
media.enable-commonsource=true
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.opengles.version=131072
debug.hwui.render_dirty_regions=false
ro.sf.lcd_density=320
ro.error.receiver.default=com.samsung.receiver.error
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.hdcp2.rx=tz
ro.secwvk=220
ro.sec.fle.encryption=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.com.google.gmsversion=4.1_r4
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
All in your build.prop file seam to be right.
How have you change gsm/wcdma frequency ? The problem can be here !
Have you try to enable only GSM mode for example (only EDGE data connection) ?
Maybe your problem is because your phone always switch between 2.5G and 3G antenna.
change frequency band
*#0011#>option>back>phone control>network control>band selection>gsm||wcdma>bands(850/900/1800......................)
there is other way to get in service mode I not remember the code
first was all automatic, after i changed to manul same thing can make some cals for a while...
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"
}
Code:
I'm not responsible if you brick your device or your device explodes or anything similar!!
Back up before you flash ANYTHING !
Note:
Sorry I have small one concerns at present with the creation of my updater-script. We are thus going to pass by a method different from flash
INSTALLATION
Place the flashable-signed_D5833_1.0.1_LB.zip or flashable-signed_D5833_1.0.1_UB on your sdcard (official ftf_D5833_SG_23.2.A.1.62 Sony Pré-rooted/XdualRecovery/Xposed)
Boot Into Recovery
Wipe Data, Cache, Dalvik Cache and system
Install flashable-signed_D5833_23.2.A.1.62.zip
Reboot and enjoy
Include DRM Function Restoration in flashable-signed_D5833_1.0.1_UB
Download
flashable-signed_D5833_1.0.1_LB.zip
flashable-signed_D5833_1.0.1_UB.zip
Version KitKat
SCREENSHOTS
Code:
I'm not responsible if you brick your device or your device explodes or anything similar!!
Back up before you flash ANYTHING !
Note:
I just build this rom on my own by extracting the ftf of 4.4.4 and deodexed all the system apps and pre-rooted it
HOW TO
unlock bootloader
install recovery Custom
Boot Into Recovery
Wipe Data, Cache and Dalvik Cache
Flash Zip
Reboot and enjoy
Features
# Debloat
# Deodex
# Zipalign
# Root SuperSu v2.40
# Busy Box
# DRM FUNTION RESTORATION FOR UB DEVICE Patch | Xperia Z* Series
# Paranoid Android Notification Peek
# Xposed Installer
# Viper4Android
# Xperia ™ Xposed (KK) 3.3
# Blurred System UI - v1.9
# Textdroider_DPI
# Fauxclock
# AndroPlusKernel v19a
# ......................
Integration of Viper4 Xhfi in the parameters sound.
Integration of Viper4 in the parameters sound
You can install Impulse Response Samples thanks to zhuhang
Abolition of CPU Setting and CPU Statistics, replaced by Fauxclock
Modification du Build.pro
# Better Image & Audio Quality
ro.media.enc.jpeg.quality=100
ro.ril.disable.power.collapse=0
debug.performance.tuning=1
video.accelerate.hw=1
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
# Save battery
wifi.supplicant_scan_interval=180
pm.sleep_mode=1
# Fix some application issues
ro.kernel.android.checkjni=0
# Enables 270 Degree Rotation
windowsmgr.support_rotation_270=true;
# Better Responsiveness & Speed
windowsmgr.max_events_per_sec=90
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
# Signal Tweaks
persist.cust.tel.eons=1
ro.config.hw_fast_dormancy=1
ro.ril.hsxpa=2
ro.ril.gprsclass=10
ro.ril.hep=1
ro.ril.enable.dtm=1
ro.ril.hsdpa.category=10
ro.ril.enable.a53=1
ro.ril.enable.3g.prefix=1
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.hsupa.category=5
# No Delay In Making Call
ro.telephony.call_ring.delay=0
ring.delay=0
# Net Speed Tweaks
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,163 84,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,163 84,256960
Deletion of googles apps, but you can reinstall them with the folder "Gapps_rEctifY".
Attention : Gapps_rEctify are to be installed after a restart following the installation of the Rom
In the folder Gapps_rEctify there is :
# Books
# Drive
# Magazines
# Maps
# Music2
# PlayGames
# PlusOne
# Videos
# GoogleKeep.
Download
D5833_rEctifY.1.0.3a.zip
D5833_rEctifY.Beta.zip
Gapps_rEctify
Credit
Ticklefish
Chainfire
Ben Ling
Pandemic
Madaditya
Saqib Nazm
AndroPlus
DooMLoRD
[NUT]
serajr
niaboc79
Without their contributions on xdadevelopers, I would not have been able to present it.
Thanking to the donors
@ PUFF1N
@gugorio
XDA: DevDB Information
rEctifY Xperia Z3 compact, ROM for the Sony Xperia Z3 compact
Contributors
_MutantX_
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: none
Based On: D5833_Customized HK_23.2.A.1.62
Version Information
Status: Stable
Created 2015-01-20
Last Updated 21-05-2015
Here is a banner for the one that it interests
Réservé
I'll give it a shot.
Backing up in a moment. Hopefully I won't have any feedback until after 4 or 5 days after the ROM and kernel settle in, which would mean no bugs noticed
PantsDownJedi said:
I'll give it a shot.
Backing up in a moment. Hopefully I won't have any feedback until after 4 or 5 days after the ROM and kernel settle in, which would mean no bugs noticed
Click to expand...
Click to collapse
Uploade of a stable version She will be there in the evening
Give this one a try anyway
PantsDownJedi said:
Give this one a try anyway
Click to expand...
Click to collapse
" REctifY 1.0.3a " launched
And sadly enough, I just booted into the old one and had this as a quoted posy notification in my email.
In case it isn't fixed btw, the kernel image in the build I downloaded earlier wasnt good. I tried it first with the install I had and it didn't boot at all. Flashed back the old kernel. Tried just now the full install and same thing. The install is running but literally just booked though I had to flash an Androkernel at fastboot the same as before; same issue, didn't boot at all. No animation or anything, could only turn the phone off and hit fastboot and flash modes.
I've never used viper for Android. Can you briefly explain what I need to download for it and where to put it please.
---------- Post added at 08:26 PM ---------- Previous post was at 08:12 PM ----------
Off the bat, one other thing I'm noticing from the first beta, before I install the update, and it may well not be a problem, is that the data icon doesn't go away on wifi. I can't tell if data is still being used or not; the input and output indicators stop but the letter is still there... 3G, H, G, etc. The traffic arrows move to the wifi icon. I'll try to test it by looking at the usage if I see the same thing in the update but probably have no time today.
When you installed " rEctifY 1.0.3a ", the device does not start?
If it arrives it is a defect of of the kernel. Would be it a defect of Androkernel V19a? Tried it to you? Tested is work
For Viper4Android look at the subject http://forum.xda-developers.com/showthread.php?t=2191223
Your kernel installed first when I extracted it and simply fastboot it. It also installed (presumably) when I installed the whole ROM with TWRP. In both cases it didn't get to a boot animation. I got a black screen on reboot as if the phone was off. When I hit the power button it vibrated once after a very very short wait, nothing as long as what you'd expect of any Shutdown forced or otherwise. Right now I'm using your alpha ROM after flashing an image of AndroKernrel with fastboot.
As for the AndroKernrel version, right now I'm using 14 and earlier I'd flashed 16. I had them on my computer convenient to find. My phone has run every version of that kernel up to the current one with my previous install.
I'm wondering if its possible that its a file permission of the image.... I pulled a stock one from an ftf recently that didn't flash despite the file command in Linux sort of indicating it was at least an image for this arch, however yours did flash but just didn't boot. I don't know what else to give you on it. Hope it helps.
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
Sorry, to be accurate, I've run version 12 to current of Andro.
PantsDownJedi said:
Off the bat, one other thing I'm noticing from the first beta, before I install the update, and it may well not be a problem, is that the data icon doesn't go away on wifi. I can't tell if data is still being used or not; the input and output indicators stop but the letter is still there... 3G, H, G, etc. The traffic arrows move to the wifi icon. I'll try to test it by looking at the usage if I see the same thing in the update but probably have no time today.
Click to expand...
Click to collapse
It is certainly of in the firmware D5833_23.0.1. Has 5.77_R11B_Unbranded_Brazil.ftf that I used. Which firmware have to I use as base?
... Download finished. I'll let you know more within an hour if I get other stuff done.
PantsDownJedi said:
Your kernel installed first when I extracted it and simply fastboot it. It also installed (presumably) when I installed the whole ROM with TWRP. In both cases it didn't get to a boot animation. I got a black screen on reboot as if the phone was off. When I hit the power button it vibrated once after a very very short wait, nothing as long as what you'd expect of any Shutdown forced or otherwise. Right now I'm using your alpha ROM after flashing an image of AndroKernrel with fastboot.
As for the AndroKernrel version, right now I'm using 14 and earlier I'd flashed 16. I had them on my computer convenient to find. My phone has run every version of that kernel up to the current one with my previous install.
I'm wondering if its possible that its a file permission of the image.... I pulled a stock one from an ftf recently that didn't flash despite the file command in Linux sort of indicating it was at least an image for this arch, however yours did flash but just didn't boot. I don't know what else to give you on it. Hope it helps.
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
Sorry, to be accurate, I've run version 12 to current of Andro.
Click to expand...
Click to collapse
OK, I have of the credit note a bad reassembly of the beta. Everything is back to normal again on the 1.0.3a
Yeah it looks good so far. Have all my apps reinstalled and whatnot.
As for the letter on the network signal, I'm thinking that since I had a ROM specific to my carrier that this might be something they added on a data switch. I rather like being able to see the band, now, anyway and confirmed it isn't leaking data; that it appears to indeed turn off when I switch to wifi.
Booted fine.
Had issues with the play store after Titanium reinstalled more than a page full of xposed mods but as suspected, reboot solved the issue.
Looks very solid so far.
Also, only tested camera but looked just as good as my previous one with the restoration flash.
Good rom, Good battery
lamducthien said:
Good rom, Good battery
Click to expand...
Click to collapse
Same here on battery.
Uninstalled now for simple reason that I prefer stock. Wanted it to check out Viper for Android and it was really impressed, but at the end of the day I'm always paranoid of malware on custom ROMs. That said, its well done, fears set aside.
Viper for Android sort of makes
Kernel sound implementation look sad, I found, and thats just the least of the settings it has.
DRM keys are not restore. I check marlin, ckb, widevine is error and miracast is not working
Hi!
Sorry for offtopic.
D5833 Users with unlocked and rooted device. We need us at here for get root in Locked Bootloaders:
http://forum.xda-developers.com/z3-...t-unlocking-bootloader-method-t2940539/page93
zxz0O0 said:
Currently the tool can only root D5803. To support other devices I need:
Code:
cat /proc/version
su
echo 0 > /proc/sys/kernel/kptr_restrict
cat /proc/kallsyms > /data/local/tmp/kallsyms
chmod 777 /data/local/tmp/kallsyms
Upload kallsyms and post output. Obviously you need root to get this information. Additionally you should be on a early firmware (< october).
Click to expand...
Click to collapse
Does encryption work with this ROM (including SD-Card)?
ROM as prerooted
Can i flash this ROM with rooted locked bootloader?
Dual Recovery without installing bootloader unlocked state .
Dual Recovery without installing bootloader unlocked state .
Might I installed the rom in its current state ? The model 5833 .
Thanks to xda member @fatouraee the EVR-AL00 firmware has been posted here. I've taken the time to download and dissect it and found a few interesting tidbits.
For starters it appears to be a engineering or internal build
build.prop lists it as an August security patch, so it is old.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PPR1.180610.001
ro.build.version.incremental=eng.root.20181019.195045
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.base_os=
config.disable_consumerir=true
ro.build.version.security_patch=2018-08-05
ro.build.version.min_supported_target_sdk=17
ro.build.date=Fri Oct 19 19:50:42 CST 2018
ro.build.date.utc=1539949842
ro.build.type=eng
ro.build.user=root
ro.build.host=sh0514826b41539948706875-7099393-jgmgb
ro.build.tags=test-keys
ro.build.system_root_image=true
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=unknown
ro.product.locale=en-US
ro.wifi.channels=
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=generic_a15-eng 9 PPR1.180610.001 eng.root.20181019.195045 test-keys
ro.build.fingerprint=Huawei/generic_a15/generic_a15:9/PPR1.180610.001/root10191950:eng/test-keys
ro.build.characteristics=default
# end build properties
#
# from device/emui/generic_a15/system.prop
#
persist.sys.cpuset.enable=1
persist.sys.cpuset.subswitch=16
persist.sys.iaware.cpuenable=true
persist.sys.fast_h_duration=2000
persist.sys.fast_h_max=50
persist.sys.max_rdh_delay=0
ro.config.enable_rcc=true
ro.config.hw_sensorhub=true
system_init.hwextdeviceservice=1
bastet.service.enable=true
dalvik.vm.boot-dex2oat-threads=4
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.control_privapp_permissions=log
ro.opa.eligible_device=true
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=9_201806
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm64.variant=generic
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a15
dalvik.vm.isa.arm.features=default
ro.kernel.android.checkjni=1
dalvik.vm.lockprof.threshold=0
dalvik.vm.image-dex2oat-filter=verify-at-runtime
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.expect.recovery_id=0xf227db076aec861e23fda4c530f3156b69ef8804000000000000000000000000
ro.build.display.id=System-FAC 9.0.0.062(00IE)
ro.comp.sys_support_vndk=
But, here's where things get interesting!
{
"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"
}
It appears to be rooted already. Of course, with no up to date software available, you will more than likely be stuck on this build until shipping/retail firmware becomes available. Someone should take one for the team and flash it.
Join our developer telegram group here for help flashing and testing out theories so that we may soon develop a method and guide to post on XDA regarding root and/or rebrand.
What did you use to extract the img files?
And we need to do a form or comparison of the two and see where the differences are for rebranding. and its possibility. Because rooting wouldnt be an issue to inject into a L29 rom before flashing, or at least i dont think
AngelDeath said:
What did you use to extract the img files?
And we need to do a form or comparison of the two and see where the differences are for rebranding. and its possibility. Because rooting wouldnt be an issue to inject into a L29 rom before flashing, or at least i dont think
Click to expand...
Click to collapse
i used a tool to convert to ext4 then simply browsed with 7zip
you could also probably mount it in linux with no problems.
freeza said:
i used a tool to convert to ext4 then simply browsed with 7zip
you could also probably mount it in linux with no problems.
Click to expand...
Click to collapse
Granted the August security patch. Would the ro.build of 10/19 perhaps say it's a newer build however just old patch?
antiochasylum said:
Granted the August security patch. Would the ro.build of 10/19 perhaps say it's a newer build however just old patch?
Click to expand...
Click to collapse
It's possible. But then again I would assume they were simply pushing builds out quick to iron out bugs, then once it was ready, simply updated it to the latest patch.
freeza said:
It's possible. But then again I would assume they were simply pushing builds out quick to iron out bugs, then once it was ready, simply updated it to the latest patch.
Click to expand...
Click to collapse
Thanks for the direction, last question, have you had trouble opening the update app from the L29 rom? I used the Huawei Update extractor, but if fails with a trustfirmware invalid header error, unchecking verify header checksum in settings let it extract, but then I cant extract the system.img file every app I use crashes, but yet I've had no issues with any of the other img files or from the AL00 rom.
AngelDeath said:
Thanks for the direction, last question, have you had trouble opening the update app from the L29 rom? I used the Huawei Update extractor, but if fails with a trustfirmware invalid header error, unchecking verify header checksum in settings let it extract, but then I cant extract the system.img file every app I use crashes, but yet I've had no issues with any of the other img files or from the AL00 rom.
Click to expand...
Click to collapse
You're probably going to have to mount it in Linux as root. I had to do that on previous Huawei devices . Then you can zip the system and save it.
On previous devices I've used HwOta8 along with the stock rom to roll back to over firmware. I'm not sure if that would still apply to Pie devices.
ajsmsg78 said:
You're probably going to have to mount it in Linux as root. I had to do that on previous Huawei devices . Then you can zip the system and save it.
On previous devices I've used HwOta8 along with the stock rom to roll back to over firmware. I'm not sure if that would still apply to Pie devices.
Click to expand...
Click to collapse
Great...every img opens with no issues except this system img file from L29.
Well digging through the Product.img file there seems to be two things I found interesting. The first there is another model # "EVR-L09" which doing a search isnt coming up with anything on google. The other is there seems to be a apk to enroll OKGoogle as the hot word, which I think is the obvious, but when I pulled the apk to try and install it, it comes back that the apk does not have a certificate.
AngelDeath said:
Great...every img opens with no issues except this system img file from L29.
Well digging through the Product.img file there seems to be two things I found interesting. The first there is another model # "EVR-L09" which doing a search isnt coming up with anything on google. The other is there seems to be a apk to enroll OKGoogle as the hot word, which I think is the obvious, but when I pulled the apk to try and install it, it comes back that the apk does not have a certificate.
Click to expand...
Click to collapse
All we need now is a working "TWRP"...
AngelDeath said:
Great...every img opens with no issues except this system img file from L29.
Well digging through the Product.img file there seems to be two things I found interesting. The first there is another model # "EVR-L09" which doing a search isnt coming up with anything on google. The other is there seems to be a apk to enroll OKGoogle as the hot word, which I think is the obvious, but when I pulled the apk to try and install it, it comes back that the apk does not have a certificate.
Click to expand...
Click to collapse
Here's a link to download the L29 9.0.0.108 system/vendor/cust that I extracted:
https://www.androidfilehost.com/?w=files&flid=285746
And here is the AL00 System:
https://www.androidfilehost.com/?fid=11410963190603853598
ajsmsg78 said:
Here's a link to download the L29 9.0.0.108 system that I extracted:
https://www.androidfilehost.com/?fid=11410963190603853592
Click to expand...
Click to collapse
Thanks, any chance you can pull these two as well?
Cust.img
Vendor.img
AngelDeath said:
Thanks, any chance you can pull these two as well?
Cust.img
Vendor.img
Click to expand...
Click to collapse
Sure, give me a few and I'll add them to the last post. Ok good to go, updated the link.
I'll look at them tomorrow, but in the mean time if anyone is curious the hotword for ok google is located in product.img. One thing I saw unless I read it wrong, the recovery images are the same size in both so I'm going to guess the partiton table are going to be the same. And if anyone wants to disect the apk, its attached below
AngelDeath said:
I'll look at them tomorrow, but in the mean time if anyone is curious the hotword for ok google is located in product.img. One thing I saw unless I read it wrong, the recovery images are the same size in both so I'm going to guess the partiton table are going to be the same. And if anyone wants to disect the apk, its attached below
Click to expand...
Click to collapse
I would compare the files too forget how I did this-recall finding differences even when the size was the same on Samsung models (Latin America versus ROW models for one of their Tablet phones the T705 versus T705M)
edit must have been diff image but it was some offline (not online) checker-there were small differences in the BL and modem on those devices even though they appeared identical size-wise on those devices from what I recall (nevermind that there were actual hardware differences in the radio between those two unlike in the case of the L00 and L29-at least the bands and connectivity appear common)
mac231us said:
I would compare the files too forget how I did this-recall finding differences even when the size was the same on Samsung models (Latin America versus ROW models for one of their Tablet phones the T705 versus T705M)
edit must have been diff image but it was some offline (not online) checker-there were small differences in the BL and modem on those devices even though they appeared identical size-wise on those devices from what I recall (nevermind that there were actual hardware differences in the radio between those two unlike in the case of the L00 and L29-at least the bands and connectivity appear common)
Click to expand...
Click to collapse
I have two offline programs that compare, I'll see what I find and let you know.
AngelDeath said:
I have two offline programs that compare, I'll see what I find and let you know.
Click to expand...
Click to collapse
A quick look by two different apps (Getting an update to one of them for final comparison) shows that either both the Recovery_Vendor.img and Recovery_ramdisk.img are complete different based on comparison, or because one is a internal rooted rom (AL00) and the L29 isnt, could be why there is such a massive difference in coding. Basically the whole file is different in both, My whole screen is red except the last 3 hex lines. But checking to see if updating the app makes a difference (probably not).
I should be receiving my device hopefully sometime next week. Looking forward to seeing what's possible
freeza said:
I should be receiving my device hopefully sometime next week. Looking forward to seeing what's possible
Click to expand...
Click to collapse
Here is a comparison of the ramdisk.img. To me I think the large difference is one is internal testing, the other is released. But just looking at this, you can see from the legend on the left its all red meaning its completely different, but yet its exactly the same partition size, got to see the rest.
AngelDeath said:
Here is a comparison of the ramdisk.img. To me I think the large difference is one is internal testing, the other is released. But just looking at this, you can see from the legend on the left its all red meaning its completely different, but yet its exactly the same partition size, got to see the rest.
Click to expand...
Click to collapse
Just PMd you
fatouraee said:
Just PMd you
Click to expand...
Click to collapse
Got it