Database Develop

SM-G730A CyanogenMod help

I have an AT&T Samsung S3 Mini Sm-G730A and would like to try/help making CyanogenMod 10.2 for this.
I found this generic guide that may be helpful:
http://wiki.cyanogenmod.org/w/Doc:_porting_intro
Official source code can be downloaded from here, just click 'mobile phones' > then scroll down to your model number SM-G730_NA (I believe the NA stands for National version): http://opensource.samsung.com/
Rooting this device is possible with instructions from here: www.forum.xda-developers.com/showthread.php?t=2469413
Phone information:
Code:
Model number: Sumsung-SM-G730A
Android version:
4.2.2
Baseband version:
G730AUCUAMH4
Kernel Version:
3.4.0-1299773
[email protected] #1
Wed Aug 21 13:15:42 KST 2013
Build version:
JDQ39.G730AUCUAMH4
Partition information:
$ cat /proc/partitions
Code:
major minor #blocks name
7 0 5229 loop0
253 0 204800 zram0
179 0 7634944 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 12800 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 7160 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 8 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 1351680 mmcblk0p20
179 21 716800 mmcblk0p21
179 22 16384 mmcblk0p22
179 23 5390319 mmcblk0p23
179 32 7761920 mmcblk1
179 33 1 mmcblk1p1
179 37 7761919 mmcblk1p5
254 0 5229 dm-0
Build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=JDQ39.G730AUCUAMH4
ro.build.version.incremental=G730AUCUAMH4
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Wed Aug 21 13:27:12 KST 2013
ro.build.date.utc=1377059232
ro.build.type=user
ro.build.user=se.infra
ro.build.host=R0210-01
ro.build.tags=release-keys
ro.product.model=SAMSUNG-SM-G730A
ro.product.brand=samsung
ro.product.name=goldenlteuc
ro.product.device=goldenlteatt
ro.product.board=MSM8960
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm8960
# ro.build.product is obsolete; use ro.product.device
ro.build.product=goldenlteatt
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=goldenlteuc-user 4.2.2 JDQ39 G730AUCUAMH4 release-keys
ro.build.fingerprint=samsung/goldenlteuc/goldenlteatt:4.2.2/JDQ39/G730AUCUAMH4:user/release-keys
ro.build.characteristics=att
# Samsung Specific Properties
ro.build.PDA=G730AUCUAMH4
ro.build.hidden_ver=G730AUCUAMH4
ro.build.changelist=1299773
ro.product_ship=true
ro.chipname=MSM8930
# end build properties
#
# system.prop for surf
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=gpu
debug.compbypass.enable=1
dalvik.vm.heapsize=36m
debug.enable.wl_log=1
persist.hwc.mdpcomp.enable=true
#
# system props for the cne module
#
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=false
persist.cne.snsr.based.rat.mgt=false
persist.cne.bat.based.rat.mgt=false
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
persist.cne.feature=0
#
# System prop for Tvout/HDMI
#
persist.sys.camera.connect=0
persist.sys.videomode=0
ro.hdmi.enable=true
ro.yas.enable=true
ro.yas-selftest.enable=true
lpa.decode=true
lpa.use-stagefright=true
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
#
# system props for the data modules
#
ro.use_data_netmgrd=true
#system props for time-services
persist.timed.enable=true
# System props for audio
persist.audio.fluence.mode=endfire
persist.audio.vr.enable=false
persist.audio.handset.mic=digital
# System prop to select audio resampler quality
af.resampler.quality=255
# System prop to select MPQAudioPlayer by default on mpq8064
mpq.audio.decode=true
#
# system prop for opengles version
#
# 131072 is decimal for 0x20000 to report version 2
ro.opengles.version=131072
#
# system property for Bluetooth Handsfree Profile version
#
ro.bluetooth.hfp.ver=1.6
#
#system prop for Bluetooth hci transport
ro.qualcomm.bt.hci_transport=smd
#
# system prop for requesting Master role in incoming Bluetooth connection.
#
ro.bluetooth.request.master=true
#
# system prop for Bluetooth Auto connect for remote initated connections
#
ro.bluetooth.remote.autoconnect=true
# system property for Bluetooth discoverability time out in seconds
# 0: Always discoverable
#debug.bt.discoverable_time=0
#system prop for switching gps driver to qmi
persist.gps.qmienabled=true
# System property for cabl
ro.qualcomm.cabl=1
# System property for Default Brightness
ro.lcd_min_brightness=40
ro.lcd_brightness=160
ro.button_key_light=6000
#
# System prop for sending transmit power request to RIL during WiFi hotspot on/off
#
ro.ril.transmitpower=true
#
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
ro.hwui.text_cache_width=2048
#
# Supports warmboot capabilities
#
ro.warmboot.capability=1
ro.sf.lcd_density=240
#
# System property for SIM
#
persist.radio.apm_sim_not_pwdn=1
# System property for PreloadInstaller
persist.sys.storage_preload=1
# System proverty for sys info indication
persist.radio.add_power_save=1
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.vendor.extension_library=/system/lib/libqc-opt.so
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
ro.sec.fle.encryption=true
ro.config.ringtone=ATT_Firefly_Default.ogg
ro.config.notification_sound=Whisper.ogg
ro.config.alarm_alert=Alarm_Morning_flower.ogg
ro.config.media_sound=Over_the_horizon_Acoustic.ogg
ro.monkey=0
ro.error.receiver.default=com.samsung.receiver.error
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
ro.crypto.support=recovery_mount|others
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.setupwizard.mode=DISABLED
ro.com.google.apphider=off
ro.com.google.clientidbase.ms=android-att-us
ro.com.google.clientidbase.am=android-att-us
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.gmsversion=4.2_r2
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.qc.sdk.izat.premium_enabled=0
persist.gps.qc_nlp_in_use=0
System dump (freshly restored before the dump):
https://www.dropbox.com/s/1b4x1h1d3tmte1n/sysdump-g730a.tgz
Note to moderators: If this is allowed to be in the development section, i'd like to request it to be moved. Thanks

This is really a good step. i search for this without any luck, i really don't know how i don't came across with this you found the source code for the Samsung-SM-G730A.
+100
Sent from my SAMSUNG-SM-G730A using XDA Premium 4 mobile app

I edited the OP to include the build.prop information.
Edit: And I added specific phone information, including kernel version.

I havn't seen anyone provide a system dump yet.

tys0n said:
I haven't seen anyone provide a system dump yet.
Click to expand...
Click to collapse
Thanks for the help. I did a system dump 800mb I will find somewhere to upload it to. What would you say is the next step? Attempting to dump boot (by following a guide) gave me this error: Segmentation fault
Edit: I added a link to the system dump in the Original Post.
Edit: Here's a odin file for stock boot and recovery in one package.
SM-G730A_boot_rec.tar.md5 - 14.76 MB (Credit goes tys0n)

dylan07 said:
Thanks for the help. I did a system dump 800mb I will find somewhere to upload it to. What would you say is the next step? Attempting to dump boot (by following a guide) gave me this error: Segmentation fault
Edit: I added a link to the system dump in the Original Post.
Edit: Here's a odin file for stock boot and recovery in one package.
SM-G730A_boot_rec.tar.md5 - 14.76 MB (Credit goes tys0n)
Click to expand...
Click to collapse
i would like to help out on this ad i have a system dump file too but looks like everyone started helping too. anything i can do to put some work into this? im also trying to unlock the device and include system properties to the modem part. im kinda handy with finding sections of the phone and able to write code to compile.

krayzieiyian23 said:
i would like to help out on this ad i have a system dump file too but looks like everyone started helping too. anything i can do to put some work into this? im also trying to unlock the device and include system properties to the modem part. im kinda handy with finding sections of the phone and able to write code to compile.
Click to expand...
Click to collapse
we need someone to create a recovery before anything with a custom rom is possible. with root, you can use any given recovery flasher from the play store, i know recovery tools works. ODIN on this thing doesn't like unsigned packages. someone just needs to create a custom recovery.img, i am more than willing to test for myself, for everyone, for science!

You might be a goldenlteatt owner if...
A CyanogenMod maintainer raids the system dump you post in the thread you created asking for a CyanogenMod port for blobs for his official CyanogenMod phone.
https://github.com/TheMuppets/propr...mmit/415916c37644993c5747c1232989624126c6ef5b

any news on cyanogenmod?
Sent from my GT-I9195 using xda app-developers app

Not from me. But thanks for the blobs. @arco maintains a similar device perhaps he can help you
Sent from my Nexus 7 using Tapatalk

recovery?
So has anyone had any luck on this?

onelostmind said:
So has anyone had any luck on this?
Click to expand...
Click to collapse
I believe a recovery was compiled, but it cannot be flashed due to the locked bootloader. Until the bootloader is locked, you guys are out of luck in terms of custom roms/recoveries/kernels.

trying to flash my rom to g730a :/
Hi everyone,
I am trying to flash a custom ROM that I created (Android 4.2.2 downloaded from google repo and kernel downloaded from samsung opensource) to my g730a. The problem is that this phone seems impossible to flash with unsigned or non-samsung roms!
I tried to upload boot.img and system.img through heimdall and it gives me an error (ERROR: Failed to confirm end of file transfer sequence!).
I tried to upload it with ODIN but gives me an error (Security check error)
I tried to create a zip with Android Kitchen and install it from the recovery mode and this time the error is about the sign of the zip. I tried to look for a customized version of recovery mode but I could not find one compatible with this phone. So, I cannot install it from the zip since I cannot sign the zip as samsung.
At this point I am tempted to take the phone and flush it in the toilet!!!
Any suggestion or anyone that could install a custom ROM?
Thanks
Marco

brok85 said:
Hi everyone,
I am trying to flash a custom ROM that I created (Android 4.2.2 downloaded from google repo and kernel downloaded from samsung opensource) to my g730a. The problem is that this phone seems impossible to flash with unsigned or non-samsung roms!
I tried to upload boot.img and system.img through heimdall and it gives me an error (ERROR: Failed to confirm end of file transfer sequence!).
I tried to upload it with ODIN but gives me an error (Security check error)
I tried to create a zip with Android Kitchen and install it from the recovery mode and this time the error is about the sign of the zip. I tried to look for a customized version of recovery mode but I could not find one compatible with this phone. So, I cannot install it from the zip since I cannot sign the zip as samsung.
At this point I am tempted to take the phone and flush it in the toilet!!!
Any suggestion or anyone that could install a custom ROM?
Thanks
Marco
Click to expand...
Click to collapse
You need to unlock the booloader before flashing; and there's currently no way of unlocking the bootloader...

g730a custom rom
You mean that in general is not possible to unlock the bootloader or is not possible only for the g730a?
If the second case, is there a specific reason for that?
Thanks,
Marco
Exothermic said:
You need to unlock the booloader before flashing; and there's currently no way of unlocking the bootloader...
Click to expand...
Click to collapse

brok85 said:
You mean that in general is not possible to unlock the bootloader or is not possible only for the g730a?
If the second case, is there a specific reason for that?
Thanks,
Marco
Click to expand...
Click to collapse
The latter; it's typically carriers that lock the bootloaders of their phones AT&T and Verizon are notorious for this, I do believe you have the Telus version? Not sure if that's locked.
If not, you can try sending a copy of your stock recovery.img to cwm builder and see if that flashes okay for your phone.
BTW: you need a custom recovery to flash ROMs hence why you were getting the not samsung verified zip msg.

customize g730a
Not sure if Telus. How can I check?
I have downloaded the stock recovery from the link posted previously in this thread...should I download it from my phone?
sorry I am not really an expert...
Exothermic said:
The latter; it's typically carriers that lock the bootloaders of their phones AT&T and Verizon are notorious for this, I do believe you have the Telus version? Not sure if that's locked.
If not, you can try sending a copy of your stock recovery.img to cwm builder and see if that flashes okay for your phone.
BTW: you need a custom recovery to flash ROMs hence why you were getting the not samsung verified zip msg.
Click to expand...
Click to collapse

brok85 said:
Not sure if Telus. How can I check?
I have downloaded the stock recovery from the link posted previously in this thread...should I download it from my phone?
sorry I am not really an expert...
Click to expand...
Click to collapse
Googled SM-G730A and it's at&t, so it seems like you're out of luck.

g730a custom rom
Any way I can create a zip with original signature of samsung?
that would be a solution...
Exothermic said:
Googled SM-G730A and it's at&t, so it seems like you're out of luck.
Click to expand...
Click to collapse

brok85 said:
Any way I can create a zip with original signature of samsung?
that would be a solution...
Click to expand...
Click to collapse
Not that I'm aware of, otherwise there wouldn't be a need for a custom recovery.

[GUIDE] [HOW-TO] [4.0-4.4] [CM9/10/10.1/10.2/11] [ICS/JB/KK] PORTING ROMs'

This is guide that deals with porting ROM's [4.0-4.4] in 9 SIMPLE STEPS!
What type of ROM can i port using this GUIDE?
Any ROM (except Stock/manufacturer based)
ROMs' from similar devices
From same Resolution devices
What do I need??
A machine to work on. Duh!
BASE & PORT ROMs
Notepad++(if on windows)
Special ingrediant
What is BASE Rom:
The ROM which is Developed For your Mobile..​
What is PORT Rom:
The Rom Which you want to port to your Device.
just keep checking all ROM's from the forum and find one of your choice that you would like to port to your device.​
So now we have a BASE and a PORT ROM.
Next we need a Machine to work on(but obvious) (I'd be using a Win 7 PC here)
Lets Start!
Step 1:
Take ANY clean AOSP/CM ROM , which has been developed for your device as BASE ROM.
And the ROM you want to port as PORT ROM
Extract both of them, and name the folders appropriately.
It should look like this now.
{
"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"
}
​
Step 2 : Delete app, font, framework, media [and priv-app if porting Kitkat].
​Step 3: Copy app, font, framework, media [and priv-app if porting Kitkat] from PORT to BASE folder.
​
NOTE: If You find any extra file or folder in system folder of PORT ROM than copy them to your base rom system folder.
Step 4: Open etc in both PORT & BASE.
Step 5: Open init.d folder and
**Delete all files except 00banner from BASE.
**Copy all files from PORT except 00banner to BASE.
Step 6: Open Permissions in both BASE & PORT
**Copy all files{EXCEPT platform.xml and handheld_core_hardware.xml} from PORT to BASE
​
Step 7: Get to the build.prop and open both in notepad++
replace following line from PORT to BASE.
ro.config.ringtone=
ro.config.notification_sound=
ro.config.alarm_alert=
Click to expand...
Click to collapse
Also copy any other lines or tweaks you find in build.prop like this one
You can edit the following to what you wish or leave them as they are.
ro.build.id=
ro.build.display.id=
ro.build.date=
ro.modversion=
Click to expand...
Click to collapse
Step 8: Open both ROMs' updator-script
(get to them by going to >>> BASE/PORT folder > Meta-inf > com > google > android > here)
and delete all the lines setting permissions {set_perm() or set_metadata()} from BASE updator-script
Copy all set_perm()/set_metadata() lines from PORT to BASE updator-script.Save it !
>>> As a precaution you can check the file/folder name in set_metadata/set_perm lines exists in your BASE ROM or not, for instance SEMC devices do not have a firmware folder in vendor and if you set permission for a file/folder that does not exist in your ROM then probably you would be getting a Status 6 error while flashing.
IF YOU ARE HAVING BOOTLOOP THEN COPY THESE LIB FILES TO BASE ROM FROM PORT ROM:
libandroid_runtime.so
libandroid_servers.so
libmedia_jni.so
Click to expand...
Click to collapse
Step 9:
If you are porting ROM's which have features like say, Xperia Walkman, then those apps have their dependencies too.
So copy all unique files(which are only in PORT folder) from following folders of PORT to appropriate Folders of BASE:
lib
etc
bin
Now just zip the BASE folder flash it and post it! ​
IF YOUR BASE ROM HAS ISSUES THEN YOUR PORTED ROM TOO WILL HAVE ISSUES.
DON'T FORGET TO GIVE CREDITS TO THE DEVELOPER OF PORT ROM..
IF IT HELPED YOU THAN PRESS THANKS AND RATE THIS POST 5 STARS...
Cheers
The Guide is based on @rishabh.raj37 's Guide.
All credit for the Guide goes to him
Second and third posts are also from the original thread.
Click to expand...
Click to collapse

How to logcat?
Many of you are having problems while porting and I know that those problems cannot be solved simply by guesswork..
There is a solution to find the problems which are causing BOOTLOOPS OR OTHER PROBLEMS IN YOUR PORT ROM..
The SOLUTION IS TO TAKE A LOGCAT..
LOGCAT ARE OF TWO TYPES:
In your Phone(if the ROM is booting)
Through adb(if you are stuck in bootloop)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
In your Phone:
There are two ways to take LOGCAT in mobile:
FIRST WAY--THROUGH APPS WHICH ARE MADE TO TAKE LOGCAT:
There are two apps which you can use to take a LOGCAT..
They are aLogcat or Catlog.
Taking logcat through apps is very easy.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
SECOND WAY--THROUGH TERMINAL EMULATOR
SEE THE INSTRUCTIONS BELOW TO TAKE A LOGCAT THROUGH adb
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
HOW TO MAKE PC READY FOR LOGCAT?
IN WINDOWS:
Download Android SDK From Here
Install or Extract it to your desired Directory..
You also need to install Java JDK.
Download it here
In the Guide, we are taking C: as the Root Directory and android as the main Folder
Navigate to Android SDK folder and open 'SDK Manager.exe'
Only check 'Android SDK Tools' and 'Android SDK Platform-tools'
First connect the device via USB to your computer
Be sure to have USB debugging enabled
Now Navigate to C:/Android/android-sdk/platform-tools/
Now Open a Command Prompt there By holding Shift+Right Click Button
Click to expand...
Click to collapse
IN LINUX:
IMPORTANT: If someone has a 64bit linux then they need to download 32-bit libs
for this, before all these steps run this:
Code:
sudo apt-get install ia32-libs
Make sure that you have Android-SDK and JDK downloaded on your PC
If you have not installed them, Android SDK from here and Java JDK in this way:
Code:
sudo add-apt-repository ppa:ferramroberto/java
sudo apt-get update
sudo apt-get install sun-java6-jdk sun-java6-jre sun-java6-plugin
OR
$ sudo add-apt-repository ppa:sun-java-community-team/sun-java6
$ sudo apt-get update
$ sudo apt-get install sun-java6-jre sun-java6-bin sun-java6-jdk
OR You Can Simply Do This: (Credits to @Androguide.fr)
This process saves a lot of storage. It uses the Ubuntu Touch ppa:
Code:
sudo add-apt-repository ppa:phablet-team/tools
sudo apt-get install android-tools-adb
You can also install fastboot in the same fashion:
Code:
sudo apt-get install android-tools-fastboot
Then follow the Below Instructions Carefully:
Make a new directory by this command in terminal:
Code:
mkdir android
Then extract the downloaded SDK by
Code:
tar -zxvf ~/Downloads/android-sdk_r21.0.1-linux.tgz
Then move it to the directory we just made
Code:
mv android-sdk-linux ~/android/sdk
Then open android sdk manager by
Code:
android/sdk/tools/android
This will open Android sdk manager. Just select android sdk tools and android sdk platform tools for adb and then select install packages
Go into your Home folder and Press CTRL+H (This is done to show hidden folders and files)
Look for the file '.bashrc'
Open it and put the following or similar:
Code:
export PATH=$PATH:~/android/sdk
export PATH=$PATH:~/android/sdk/platform-tools
export PATH=$PATH:~/android/sdk/tools
You will need to add something for any devices to be recognized:
Open terminal(Ctrl+alt+T) and enter:
Code:
sudo gedit /etc/udev/rules.d/51-android.rules
Enter the following in the file:
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="0502", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="413c", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0489", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="091E", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="12d1", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0482", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="1004", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0955", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="10A9", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="04dd", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="0fce", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="19D2", MODE="0666"
Now save and close the file, and in terminal enter:
Code:
sudo chmod +x /etc/udev/rules.d/51-android.rules
Now Type:
Code:
sudo gedit /etc/rc.local
This will open a file
now add the line mentioned below just above where it is written exit 0
Code:
/home/user/android/sdk/platform-tools/adb start-server
"Enter your username in place of user"
After this we don't need to cd to adb directory..We just have to type adb devices and the phone will surely show up.
Now that everything is installed
Open terminal and type:
Code:
android
android
Or, if it doesnt work
Code:
cd ~/android/sdk/tools
./android
Click to expand...
Click to collapse
HOW TO TAKE LOGCAT?
To verify that the device is connected Type:
Code:
adb devices
Now type:
Code:
adb logcat > logcat.txt
The LOGCAT will be Saved in the logcat.txt File
You can also type:
Code:
adb logcat -f logcat.txt
or
Code:
adb logcat -v long > logcat.txt
With the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Meanings of symbols in a logcat !
You usually see this at the start of a sentence in logcat .
I/> ===> Information
S/> ===> Silent
D/> ===> Debug
W/> ===> Warning
E/> ===> Error
F/> ===> Fatal
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CREDITS:
blahbl4hblah
paxChristos
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Build.prop and Updater-Script Terminology and Guide to Edit it
Thanks to @ rishabh.raj37
Standard build.prop properties
Please read the hashed out lines : It is selfexplanatory.
So the normal build properties start with:
Code:
# begin build properties
# autogenerated by buildinfo.sh
This mentions that the build prop is built by build info shell script during the compilation of the ROM.
Code:
#First up the build id (Here JZO54K) is the build id for the version number for Jellybean 4.1.2
ro.build.id=JZO54K
#It is the version of the ROM which appears in the about phone. This is a cm10 build by sakindia123.
ro.build.display.id=cm_pico-userdebug 4.1.2 JZO54K eng.sakindia123.20121117.161006 test-keys
#This is the software development kit version which is needed and used for building the ROM.
ro.build.version.incremental=eng.sakindia123.20121117.161006
ro.build.version.sdk=16
#3's codename.
ro.build.version.codename=REL
#This is the android version of the ROM.
ro.build.version.release=4.1.2
#This is the time and date of when the ROM and Kernel were built together. (ROM only).
ro.build.date=Sat Nov 17 16:10:21 GMT 2012
#More details in the kernel.
ro.build.date.utc=1353168621
#Userdebug ROMs has usb debugging set to 0 and eng are for general release.
ro.build.type=userdebug
#Name of the person building the ROM & kernel.
ro.build.user=sakindia123
ro.build.host=build1
#Test keys suggests that the ROM is not an official version of the ROM. Release keys are for official releases.
ro.build.tags=test-keys
Click to expand...
Click to collapse
This part of the build prop shows the information about our phone and not the build of the ROM of our phone.
Code:
#Model of our device
ro.product.model=HTC Explorer A310e
#Brand of device. ( In some case carrier ) for which the android version has been made for.
ro.product.brand=htc_europe
#Name is an alternative ( codename ) of the device during its development. For Explorer its pico, for Nexus 7 : grouper for Nexus 4 : mako for SG Ace its cooper etc.
ro.product.name=pico
ro.product.device=pico
ro.product.board=pico
#It is the first instruction set (CPU + ABI convention type) of the code. Ours is an arm type arch cpu and abi version 7a )
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
#Name of manufacturer.
ro.product.manufacturer=HTC
#Language of the software ( read ROM)
ro.product.locale.language=en
#Region of operation of software.
ro.product.locale.region=US
ro.wifi.channels=
#Name of board on which software has been built.
ro.board.platform=msm7x27a
# ro.build.product is obsolete; use ro.product.device
ro.build.product=pico
# Do not try to parse ro.build.description or .fingerprint Never attempt to modify this value ! This can lead to bootloop (possibly hard brick) of your phone. This is the unique fingerprint of the software of your phone.
ro.build.description=cm_pico-userdebug 4.1.2 JZO54K eng.sakindia123.20121117.161006 test-keys
ro.build.fingerprint=htc_europe/htc_pico/pico:2.3.5/GRJ90/207463.1:user/release-keys
ro.build.characteristics=default
ro.cm.device=pico
# end build properties
#
Click to expand...
Click to collapse
System properties::
What is RIL?
A Radio Interface Layer (RIL) is a layer in an operating system which provides an interface to the hardware's radio and modem on e.g. a mobile phone.
Code:
#These are basically the links between your phones hardware and software , i.e. it tells your phone where to find the libs for RIL and also detects whether you have any arguments in place of the operation of your libs to provide to the vendor.
rild.libpath=/system/lib/libhtc_ril.so
rild.libargs=-d /dev/smd0
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
#
ril.subscription.types=NV,RUIM
#Architecture of baseband radio.
ro.baseband.arch = msm
#ro.ril.ecc.HTC-xxx=nnn,nnn,nnn
#These are basically the emergency call numbers(codes) for your phone. Its different according to your region. ( here xxx ) . The numbers can be 911 , 101,100 etc etc ( here nnn)
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-Dutch=112
ro.ril.ecc.HTC-SPA=112, 911,112, 911
ro.ril.ecc.HTC-FRA=112,911
ro.ril.ecc.HTC-ITA=112,911
ro.ril.ecc.HTC-EastEurope=112
#Something to do with GPRS, AFAIK.
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
#HSDPA category : High speed downlink packet access category. ( 8 == 7.2 mbit/s )
ro.ril.hsdpa.category=8
#HSXPA : High speed ( type ) packet . ( values 1- HSDPA 2-HSDPA/HSUPA ( High speed uplink packet access )
ro.ril.hsxpa=1
#Something to do with 3G.
ro.ril.fast.dormancy.rule=1
#
ro.ril.disable.fd.plmn.prefix=23402,23410,23411,23420,27202
#Ability of enabling data roaming.
ro.ril.enable.managed.roaming=1
#Class of GPRS network that needs to be routed to phone.
ro.ril.gprsclass=10
#No sim emergency call codes list
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
#
ro.ril.emc.mode=2
#This is somehow related to mobile data and its stablility. ( adding skipbrokendatacall adds stability ).
ro.telephony.ril.v3=signalstrength,singlepdp,skipbrokendatacall
#
ro.ril.htcmaskw1.bitmask = 4294967295
#
ro.ril.htcmaskw1 = 14449
#Related to ril audio.
ro.ril.update.acoustic.table = 1
#
ro.ril.avoid.pdp.overlap = 1
#Default type of data connection.
ro.telephony.default_network = 0
Click to expand...
Click to collapse
Wi-Fi Related:
Code:
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
wifi.supplicant_scan_interval=180
wifi.interface=eth0
wifi.softap.interface=eth0
Click to expand...
Click to collapse
Density(DPI) Related:
Code:
# density in DPI of the LCD of this board. This is used to scale the UI
# appropriately. If this property is not defined, the default value is 160 dpi.
ro.sf.lcd_density = 160
Display and OpenGLrelated
Code:
# View configuration for QVGA
view.fading_edge_length = 8
view.touch_slop = 15
view.minimum_fling_velocity = 25
view.scroll_friction = 0.008
Code:
# The OpenGL ES API level that is natively supported by this device.
# This is a 16.16 fixed point number
ro.opengles.version = 131072
Code:
# For no auto focus devices
ro.workaround.noautofocus = 1
# Increase SKIA decode memory capability for progressive jpg file
ro.media.dec.jpeg.memcap = 20000000
# For QC perf binary hooks
# src:vendor/qcom/proprietary/android-perf/release/lib/<CPU arch>/libqc-opt.so
ro.vendor.extension_library=/system/lib/libqc-opt.so
Additional Build Properties:
Code:
# Misc.
#There is a provision.apk in system/app requires this line.
DEVICE_PROVISIONED=1
#Enabling certain audio libs.
htc.audio.alc.enable = 1
htc.audio.swalt.enable = 1
#Least amount of RAM that can be given to any application to run.
dalvik.vm.heapsize=48m
#OpenGL 2.x.x
ro.opengles.version = 131072
#this is actually the software composition method. CAF suggests mdp for msm7x27a boards
debug.composition.7x27A.type=mdp
#media.stagefright is nothing but the type of media framework that is being supported and its various properties are in the build.prop. ( type of media playback : local media as well as online streaming like 3gp mpeg mp4 etc etc ).
media.stagefright.enable-player=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
#It is the pixel format of RGB 565 with a constant value of 4
ro.staticwallpaper.pixelformat=RGB_565
#Something to do with app + data cache.
ro.max.fling_velocity=4000
#HTML Related.
httplive.enable.discontinuity=true
#Some thing with surface flinger hardware, aka our gpu.( probably framerate)
dev.pm.dyn_samplingrate=1
#Probably sampling rate of all media. ( Sound , picture quality etc etc . )
dev.pm.dyn_sample_period=700000
com.qc.hardware=true
#Something to do with the processes of above names.
com.qc.hdmi_out=false
#--
debug.camcorder.disablemeta=0
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.enabletr=false
#debug surface flinger hardware. One of the best known tweaks , i.e. GPU Hardware acceleration.
debug.sf.hw=1
#Encoding media quality (jpeg)
ro.media.enc.jpeg.quality=100
#Setupwizard ( google or otherwise ) enabling
ro.setupwizard.mode=OPTIONAL
#Related to Hardware acceleration settings
hwui.print_config=choice
hwui.disable_vsync=true
#By pass setup wizard.
ro.setupwizard.enable_bypass=1
#Media decoding of audio and video of wma and wmv formats respectively.
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
#Sync enabled at bootup.
ro.config.sync=yes
#something to do with phone storage. ( probably install location .. not sure)
ro.phone_storage=0
#hardware platform. msm7x27a.
ro.hw_plat=7x27a
#Hwui
hwui.use.blacklist=true
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Original thread-
[REF] Build prop terminology [INFO]
Click to expand...
Click to collapse
Click to expand...
Click to collapse
CREDITS:
akshat.shenoy for his hard work
Click to expand...
Click to collapse

The Guide is based on @rishabh.raj37 's guide , complete credits go to him.

Moderators please feel free to move the thread if i posted in wrong section
Thanks

Awesome work dude!!!!
:good::good:

That's very interesting. I will give it a try when I have some time
Sent from my Xperia Z using Tapatalk

[RECOVERY][sprout] TWRP 2.8.0.0 touch recovery [2014-09-26]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
{
"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"
}
Tablet look:
CHANGELOG for 2.8.0.0:
-Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
-Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
-Add support for color in the console and give error, warning, and highlight lines different colors
-Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
-Improve handling of /misc thanks to mdmower
-Improve setting of time on Qualcomm devices thanks to [NUT]
-Allow using images on slidervalue GUI objects thanks to Tassadar
-Allow using variables and addition and subtraction in variables for easier theming
-Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
-Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
-Other minor fixes and improvements
Over the course of the last year or so, bigbiff has worked to migrate various Java functions from Android's MTP implementation to bring you a fully C++ based MTP implementation that allows you to transfer files to both emulated storage and Micro SD cards. It's confirmed to work on various Nexus devices but we may have to make some changes on other devices to keep Windows happy. Windows is very picky about USB IDs and its drivers. We have tested it on Windows 7 and 8 as well as Ubuntu 14.04 Trusty. MTP is enabled by default, but we do toggle it off and on automatically during certain operations such as if you choose to wipe a storage partition. You can enable or disable MTP under the mount menu in TWRP. For more about what MTP is here.
Note: Due to a weird bug with our MTP setup, you cannot copy a zip file to the root of storage with Windows. You can change the .zip to something else like .txt and then copy it to the root and rename the file back to .zip once it's copied to the device. You can also copy the zip into any subfolder.
Command line support is also now available. You can perform various OpenRecoveryScript commands via the adb shell. Depending on what you are doing you may wish to do a "twrp set tw_mtp_enabled 0" and then reboot to prevent the MTP auto toggle from killing your adb interface. You can use this option to create and restore backups, wipe, install zips, and more. Via adb shell, type twrp followed by a space then enter the OpenRecoveryScript command and hit enter. Find more OpenRecoveryScript commands here.
CHANGELOG for 2.7.1.0:
-Add GUI option to change or repair file systems on individual partitions. The change is destructive so backup your data including internal sdcard first. This option should make it a little easier to migrate a device from ext4 -> f2fs, for instance. You will find this option under Wipe -> Advanced Wipe, then select only one partition and then press the Repair or Change File System button. If a developer has added f2fs support for your device and we don't have it in TWRP, please contact me via PM to arrange for it to be added.
-Various bugfixes to backup and restore
-Improvements to USB storage handling
-Added a class to search for files to make finding the correct brightness file automatic in most cases
-Various other bugfixes and tweaks
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes
DOWNLOAD:
You can download the image here
INSTRUCTIONS:
Same as CWM
XDA:DevDB Information
Team Win Recovery Project, a Recovery for Android One devices
Contributors
varun.chitre15
Version Information
Status: Testing
Created 2014-09-26
Last Updated 2014-09-26

Thanks...!!

Really looking forward to twrp, love twrp more than cwm though
Sent from my Micromax AQ4501 using XDA Free mobile app

Thank You!

Flashed twrp, looks good now.
Can I backup my stock ROM now? @varun.chitre15
Sent from my Micromax AQ4501 using XDA Free mobile app

I am unable to backup my current rom using twrp.it works only a few times.sometimes the backup file is about 10 MB which is corrupted.
Other than that its rocking

official twrp 2.8.1.0 is out now..
official twrp is out now version 2.8.1.0 .. chk it out

problems after backuping stock unrooted and bootloader locked rom
hi all.
i backuped the stock rom on my dream uno without rooting or unlocking the bootloader and got 13 files some with .tar extension some with .tar.a and 1 with .tar.b extension and 2 files with .img extension
now the problem is.
1. if i try to open any file using winrar i get a error the archive is ither in unknown format or is damaged.
2. if i use 7zip to open .tar files i get error there are no trailing 0filled records if i open .tar.a files the files open properly but when i go to extract the contents i get error unable to open output file when i open data.ext4.tar.a i get error unexpected end of archive.tar and if i click on ok i can see the files in the archive but if i go to extract it again the same error unable to open output file comes if i open data.ext4.tar.b i get error 7zip cannot open data.ext4.tar.b as archive what is the problem?
how can i extract the files?
hear is my recovery.log file.
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Sat Nov 8 14:38:30 2014
No /etc/extra.fstab
recovery filesystem table
=========================
0 /boot emmc /dev/block/platform/mtk-msdc.0/by-name/boot 0
1 /recovery emmc /dev/block/platform/mtk-msdc.0/by-name/recovery 0
2 /system ext4 /dev/block/platform/mtk-msdc.0/by-name/system 0
3 /data ext4 /dev/block/platform/mtk-msdc.0/by-name/userdata 0
4 /cache ext4 /dev/block/platform/mtk-msdc.0/by-name/cache 0
5 /external_sd auto /dev/block/mmcblk1p1 0
6 /tmp ramdisk ramdisk 0
I:Connected to Vold..
I:200 0 Volumes listed.
I:skiping get_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
Checking arguments.
stage is []
can't open /dev/tty0: No such file or directory
framebuffer: fd 5 (480 x 854)
PhilZ Touch 6.57.9
ClockworkMod v6.0.5.1
Ievice target: sprout
I:Touch GUI revision: 1.41
I:device_recovery_start()
I:auto_restore_settings set to default (true)
I:check_root_and_recovery set to default (true)
I:compression_value set to default (low)
I:twrp_backup_mode set to default (false)
I:enable_md5sum set to default (1)
I:show_nandroid_size_progress set to default (1)
I:use_nandroid_simple_logging set to default (1)
I:nand_prompt_on_low_space set to default (1)
I:signature_check_enabled set to default (0)
I:install_zip_verify_md5 set to default (0)
I:brightness_user_path=/sys/class/leds/lcd-backlight/brightness
I:set_brightness set to default (160)
I:menu_height_increase set to default (24)
I:show_virtual_keys set to default (true)
I:min_log_rows set to default (3)
I:background_image set to default (default)
I:background_image set to default
Iefault stitch background loaded.
I:show_background_icon set to default (false)
I:show_battery set to default (true)
I:show_clock set to default (true)
I:menu_text_color set to default (8)
I:menu_background_color set to default (1)
I:menu_highlight_color set to default (7)
I:normal_text_color set to default (0)
I:menu_separator_color set to default (6)
I:header_text_color set to default (8)
I:batt_clock_color set to default (2)
I:menu_background_transparency set to default (102)
I:menu_highlight_transparency set to default (102)
I:menu_separator_transparency set to default (102)
I:show_menu_separation set to default (true)
I:dim_timeout set to default (60)
I:blank_timeout set to default (180)
I:scroll_sensitivity set to default (48)
I:touch_accuracy set to default (7)
I:touch_to_validate set to default (true)
I:enable_vibrator set to default (true)
I:boardEnableKeyRepeat set to default (true)
I:wait_after_install set to default (true)
I:slide_left_action set to default (5)
I:slide_right_action set to default (3)
I:double_tap_action set to default (2)
Iress_lift_action set to default (4)
Iress_move_action set to default (1)
I:t_zone set to default (0)
I:t_zone_offset set to default (0)
I:use_dst_time set to default (false)
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT0!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
I:Current time: 2014-11-08 14:38:32 (UTC 0:00)
I:use_qcom_time_daemon set to default (0)
I:use_qcom_time_data_files set to default (0)
I:use_qcom_time_offset set to default (0)
Command: "/sbin/recovery"
ro.cm.device=sprout
ro.cm.display.version=11-20140925-UNOFFICIAL-sprout
ro.cm.version=11-20140925-UNOFFICIAL-sprout
ro.cm.releasetype=UNOFFICIAL
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
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.boot.emmc=0
ro.boot.hardware=sprout
ro.boot.serialno=Mi498HA14090035
ro.boot.bootloader=0.5.17
ro.emmc=0
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=mt6582
ro.build.id=KTU84Q
ro.build.date=Thu Sep 25 13:18:39 EDT 2014
ro.build.date.utc=0
ro.build.host=ketan
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=root
ro.build.display.id=cm_sprout-userdebug 4.4.4 KTU84Q b75c7a7c94 test-keys
ro.build.product=sprout
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.4
ro.build.version.codename=REL
ro.build.version.incremental=b75c7a7c94
ro.build.description=cm_sprout-userdebug 4.4.4 KTU84Q b75c7a7c94 test-keys
ro.build.fingerprint=Micromax/cm_sprout/sprout:4.4.4/KTU84Q/b75c7a7c94:userdebug/test-keys
ro.build.characteristics=default
ro.config.ringtone=Orion.ogg
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.carrier=unknown
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=cm_sprout
ro.product.board=
ro.product.brand=Micromax
ro.product.model=A1
ro.product.device=sprout
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=Micromax
ro.baseband=unknown
ro.bootmode=unknown
ro.hardware=sprout
ro.revision=0
ro.serialno=Mi498HA14090035
ro.bootloader=0.5.17
ro.debuggable=1
ro.modversion=11-20140925-UNOFFICIAL-sprout
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
dalvik.vm.lockprof.threshold=500
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.sys.dun.override=0
persist.sys.usb.config=adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.dalvik.multithread=false
persist.sys.root_access=1
persist.sys.recovery_update=false
service.adb.root=1
keyguard.no_require_sim=true
I:Checking for extendedcommand & OpenRecoveryScript...
I:Ignoring 'extendedcommand' boot-script: file not found
I:Ignoring 'openrecoveryscript' boot-script: file not found
I:Checking for recovery lock...
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:skiping set_bootloader_message: no /misc
I:blank_timeout was set to 300
I:blank_timeout was set to 600
I:blank_timeout was set to 900
I:blank_timeout was set to 1800
I:blank_timeout was set to 0
I:dim_timeout was set to 120
I:dim_timeout was set to 180
I:dim_timeout was set to 240
I:dim_timeout was set to 300
I:dim_timeout was set to 0
I:skiping set_bootloader_message: no /misc
No files found.
I:ro.modversion set to default (noname)
I:ro.romversion set to default (noname)
I:ro.build.display.id=KPW53
I:Checking needed space for backup '/external_sd/clockworkmod/backup/2014-11-08.14.40.12_KPW53'
I:found device mmcblk link: '/dev/block/platform/mtk-msdc.0/by-name/recovery' -> '/dev/block/mmcblk0p8'
I:/recovery backup size (/proc)=10Mb
I:found device mmcblk link: '/dev/block/platform/mtk-msdc.0/by-name/boot' -> '/dev/block/mmcblk0p7'
I:/boot backup size (/proc)=10Mb
I:/system backup size (stat)=692Mb
I:/cache backup size (stat)=4Mb
I:/data: tot size=2322Mb, free=730Mb, backup size=1538Mb, used=1538Mb, media=0Mb
I:/external_sd/.android_secure backup size=5Mb
>> Free space: 6875Mb (90%)
>> Needed space: 2260Mb
>> Backing up /boot...
Backing up boot image...
Backup of boot image completed.
>> Backing up /recovery...
Backing up recovery image...
Backup of recovery image completed.
>> Backing up /system...
Press Back to cancel.
Backup of system completed.
>> Backing up /data...
Press Back to cancel.
Backup of data completed.
>> Backing up /external_sd/.android_secure...
Press Back to cancel.
Backup of .android_secure completed.
>> Backing up /cache...
Press Back to cancel.
Backup of cache completed.
I:No sd-ext found. Skipping backup of sd-ext.
>> Generating md5 sum...
> .android_secure.vfat.tar.a
> .android_secure.vfat.tar
> boot.img
> cache.ext4.tar
> cache.ext4.tar.a
> data.ext4.tar.a
> data.ext4.tar.b
> data.ext4.tar
> recovery.img
> system.ext4.tar.a
> system.ext4.tar

austinpinto said:
hi all.
i backuped the stock rom on my dream uno without rooting or unlocking the bootloader...............
Click to expand...
Click to collapse
you have to root and unlock the bootloader first.

Swapnil Solanki said:
you have to root and unlock the bootloader first.
Click to expand...
Click to collapse
hi.
i read somewhare that you can backup the entire rom without unlocking the bootloader and without rooting the phone by downloading the recovery.img file.
putting it into the platform tools folder opening the command prompt booting your phone into fast boot mode and typing fastboot boot recovery then once the recovery boots i can use the backup to sd card feature is this right? can i do this? the entire size of the backup folder is about 2.6gb but the only problem is i cannot open some tar files and tar.b files and extract data from all files is not working

:good:

Touch not working on my a1, i installed it through sp.. Where im going wrong?? No inputs from the touch.. Please help

terroboy k9 said:
Touch not working on my a1, i installed it through sp.. Where im going wrong?? No inputs from the touch.. Please help
Click to expand...
Click to collapse
try installing using fastboot...

Twrp 2.8.4.0
terroboy k9 said:
Touch not working on my a1, i installed it through sp.. Where im going wrong?? No inputs from the touch.. Please help
Click to expand...
Click to collapse
Try the stable build twrp 2.8.4.0 from the official website.

Not working yet

really awesome recovery for android one....:good::good::good:

Please help I'm not able to use touch with twrp

terroboy k9 said:
Please help I'm not able to use touch with twrp
Click to expand...
Click to collapse
Use Flashify to flash the recovery img. I did just that and it worked in the first trial.

Hi
I'm having a problem on my Micromax AQ4501.
Whenever I'm in recovery, and I try to reboot, the phone goes dead. Even a hard reboot (using the power button) doesn't work. I have to do a battery pull each time.
Even if I do a power off within recovery, and try to restart using the power button, the same thing. Have to do a battery pull.
I'm on 2.8.6.0 - downloaded from official TWRP site.
Any help would be appreciated!

alfavictor said:
Hi
I'm having a problem on my Micromax AQ4501.
Whenever I'm in recovery, and I try to reboot, the phone goes dead. Even a hard reboot (using the power button) doesn't work. I have to do a battery pull each time.
Even if I do a power off within recovery, and try to restart using the power button, the same thing. Have to do a battery pull.
I'm on 2.8.6.0 - downloaded from official TWRP site.
Any help would be appreciated!
Click to expand...
Click to collapse
Is the recovery meant for your device or you're using some other device's recovery?

[STOCK][swift] Zenwatch 3 Partition Dump (system, boot, recovery & more)

DEPRECATED because I don't have the watch anymore. Might still work, might also not. Feel free to just try and iterate on my work.
Links are going to remain active for now. PM me if they are broken without me stating here that I deleted them.
Since Asus doesn't provide official factory images, I decided to extract them with adb and post them here.
These are the stock partitions of the Asus Zenwatch 3, unmodified and pulled via
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/<partition-name>
"Common" images, which are flashable via fastboot (means boot, recovery and system) are in the first zip (part1).
Second one contains some other partitions which might be of interest for reverse-engineering, bootloader modding, etc. Proceed at your own risk. They also can't most likely be flashed through fastboot if original partition gets broken (maybe with dd?), so be careful!
Dropbox links:
MWF76:
swift_partition_dump_part1 | boot, system, recovery | md5: 563d36c92028d1579826f2db6797c18d
swift_partition_dump_part2 | asusfw, devinfo, factory, misc, modem, modemst1, modemst2, oem, splash | md5: 0cc181c937773d69bc51099d804fcae9
MWG68:
swift_partition_dump_part1 | boot, system, recovery | md5: 159e488bdcc1aba281d4050d31d62791
How to flash:
Flash from fastboot, e.g.
Code:
fastboot flash boot bootm
fastboot flash system system.img
fastboot flash recovery recovery.img
OTA zips:
MWE76 to MWF76 - Thanks to @janjan for extracting!
NWD1.170623.001 (universal OTA, should even work to get back to stock) - Thanks to reddit user k3vink3vin! (MEGA mirror by @ingbrzy)

Thanks! So this should work with regular old "fastboot flash system system.img", etc.? The watches should be identical worldwide, right? I have one from Germany, and it looks like you're from Germany too, so that shouldn't be a problem, but I'm just wondering about other people.

jobarr said:
Thanks! So this should work with regular old "fastboot flash system system.img", etc.? The watches should be identical worldwide, right? I have one from Germany, and it looks like you're from Germany too, so that shouldn't be a problem, but I'm just wondering about other people.
Click to expand...
Click to collapse
Yes, you can flash with fastboot. Boards should be all the same, and since the watch doesn't have mobile data, the firmware files shouldn't differ much and be compatible with every model. My device name in settings is "ASUS ZenWatch 3 2458", for reference.
(edited)

UPDATE: I updated part1, so please redownload if you already downloaded it. The system.img wasn't flashable via fastboot before, but after I converted it to a sparse image with img2simg it now is.
 @janjan @jobarr

Great. I guess I'll give it a try.

It worked!

If anyone is unsure of how to do this:
1) Get the SDK Platform Tools for your platform:
https://developer.android.com/studio/releases/platform-tools.html
2) Connect to USB using the charger
3) Start up in fastboot mode (I enabled ADB debugging by going to Settings -> About and tapping again and again on the "Build number" to enable the Developer options, then Settings -> Developer options -> ADB debugging -> enable, and then typed "adb reboot-bootloader" at the command prompt)
5) Unlock watch with "fastboot oem unlock" <- This will erase everything on the watch
5) Flash the partitions with "fastboot flash boot boot.img", "fastboot flash recovery recovery.img", and "fastboot flash system system.img" (make sure you are in the same folder as the img files from Maxr1998 or modify the commands accordingly)
And that's it.

Hmm. I've had some weird issues since flashing this. Not sure if it is the firmware version itself or these files. It restarted twice while I was trying to setup Android Wear the first time after the flash, but I figured that was because my battery was pretty low. Right now though, I just tried to plug it in to charge and it basically immediately restarted. It restarted again after booting up (after showing the watch face and beeping to indicate charging). It only stopped restarting after I unplugged it. Just plugged it in again and it restarted again. Any ideas? If it keeps this up, I'll try a factory reset, but it actually already did that when I unlocked it.
Edit: Won't stop rebooting when charging. Did a factory reset, still rebooted twice while trying to setup Android Wear again. I'll try reflashing, just for fun.

jobarr said:
Hmm. I've had some weird issues since flashing this. Not sure if it is the firmware version itself or these files. It restarted twice while I was trying to setup Android Wear the first time after the flash, but I figured that was because my battery was pretty low. Right now though, I just tried to plug it in to charge and it basically immediately restarted. It restarted again after booting up (after showing the watch face and beeping to indicate charging). It only stopped restarting after I unplugged it. Just plugged it in again and it restarted again. Any ideas? If it keeps this up, I'll try a factory reset, gut it actually already did that when I unlocked it.
Edit: Won't stop rebooting when charging. Did a factory reset, still rebooted twice while trying to setup Android Wear again. I'll try reflashing, just for fun.
Click to expand...
Click to collapse
Yes i am facing the same issue. After flashing boot.img and system.img it starts reboot every 1 minute.

No luck. Factory reset, reflash, clear cache, wipe everything, fastboot oem lock... No change. My best guess now is that it's rebooting when it tries to enter (fast) charging mode. The first time I plug it in after starting up, it will charge, but only slowly (even though it shows the quick charge rocket icon). If I unplug it and plug it back in, it restarts. If I leave it plugged in while starting up, it keeps restarting every time it starts up just a few seconds after it shows the watch face.
Anyone else having any issues like this?
Edit: missed that last post. Ok, so it's probably not a hardware issue. Maybe the img files or the way of flashing. @Maxr1998, I assume I could flash this via "adb put ...", right? Do you know how to do that? Would I need the original firmware files you posted (not the img2simg version)?

jobarr said:
No luck. Factory reset, reflash, clear cache, wipe everything, fastboot oem lock... No change. My best guess now is that it's rebooting when it tries to enter (fast) charging mode. The first time I plug it in after starting up, it will charge, but only slowly (even though it shows the quick charge rocket icon). If I unplug it and plug it back in, it restarts. If I leave it plugged in while starting up, it keeps restarting every time it starts up just a few seconds after it shows the watch face.
Anyone else having any issues like this?
Edit: missed that last post. Ok, so it's probably not a hardware issue. Maybe the img files or the way of flashing. @Maxr1998, I assume I could flash this via "adb put ...", right? Do you know how to do that? Would I need the original firmware files you posted (not the img2simg version)?
Click to expand...
Click to collapse
Really weird. I must admit that I didn't flash the boot image, only system and recovery, and I don't have any problem. Fast charging works perfectly.
adb push probably won't work, but dd might (WARNING: DANGEROUS! Easily possible to screw up. Read tutorials on Google before and make sure you use the right partition). You should only try it with the boot image, others are probably fine.
Only system was converted to sparse img, boot and recovery are unmodified.
You could also try to build and flash the official kernel source (look at my other thread for that).

If no one has any other ideas tonight, I'll just try sending it back to Amazon.de and getting a new one...

jobarr said:
If no one has any other ideas tonight, I'll just try sending it back to Amazon.de and getting a new one...
Click to expand...
Click to collapse
Asus just enable the OTA update again. You should try to get it now. I successfully build my own kernel and it works fine.

What do you mean about the OTA? Is there another one?
I can look into building my own kernel later if that fixes it. Could you just give me yours?

System dump of WW_WI503Q_MWG23_20170123
Code:
#
# PRODUCT_OEM_PROPERTIES
#
import /oem/oem.prop ro.oem.*
import /oem/oem.prop oem.*
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MWG23
ro.build.display.id=MWG23
ro.build.version.incremental=3665037
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-01-05
ro.build.version.base_os=
ro.build.date=Mon Jan 23 20:22:55 UTC 2017
ro.build.date.utc=1485202975
ro.build.type=user
ro.build.user=android-build
ro.build.host=wphm9.hot.corp.google.com
ro.build.tags=release-keys
ro.build.flavor=swift-user
ro.product.model=ASUS ZenWatch 3
ro.product.brand=asus
ro.product.name=swift
ro.product.device=swift
ro.product.board=swift
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=asus
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=msm8909
# ro.build.product is obsolete; use ro.product.device
ro.build.product=swift
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=swift-user 6.0.1 MWG23 3665037 release-keys
ro.build.fingerprint=asus/swift/swift:6.0.1/MWG23/3665037:user/release-keys
ro.build.characteristics=nosdcard,watch
# end build properties
#
# from device/asus/swift/system.prop
#
#
# system.prop for msm8909
#
#rild.libpath=/system/lib/libreference-ril.so
rild.libpath=/system/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
debug.hwc.dynThreshold=2.5
debug.mdpcomp.logs=0
dalvik.vm.heapsize=36m
dev.pm.dyn_samplingrate=1
persist.demo.hdmirotationlock=false
#enable dirty rect
debug.sf.swaprect=1
#enable app buffer composition
debug.sf.hwc.canUseABC=1
#enable gpu perf hint
sys.hwc.gpu_perf_mode=1
#ro.hdmi.enable=true
#tunnel.decode=true
#tunnel.audiovideo.decode=true
#lpa.decode=false
#lpa.use-stagefright=true
#persist.speaker.prot.enable=false
#
# system props for the cne module
#
persist.cne.feature=1
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
#codecs:(PARSER_)AAC AC3 AMR_NB AMR_WB ASF AVI DTS 3GP 3G2 MKV MP2PS MP2TS MP3 OGG QCP WAV FLAC
mm.enable.qcom_parser=262143
# Default to AwesomePlayer
media.stagefright.use-awesome=false
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true
persist.data.mode=concurrent
#system props for time-services
persist.timed.enable=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
# System property for cabl
ro.qualcomm.cabl=2
# System property for QDCM
persist.tuning.qdcm=1
# System property for Screen Color
ro.qcom.screencolor=1
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#
# System property for Camera
# System prop to allocate Reprocess buffer as "1"
# during Longshot usecase
persist.camera.longshot.stages=1
#
# dirty ratio value when enable ums
#
ro.sys.umsdirtyratio=20
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true
#Set for msm8909
tunnel.audio.encode = false
#enable low_ram property on low-tier devices
ro.config.low_ram=true
#Buffer size in kbytes for compress offload playback
audio.offload.buffer.size.kb=64
#Minimum duration for offload playback in secs
audio.offload.min.duration.secs=30
#Enable offload audio video playback by default
av.offload.enable=true
#enable voice path for PCM VoIP by default
use.voice.path.for.pcm.voip=true
#
#System property for FM transmitter
#
ro.fm.transmitter=false
#enable dsp gapless mode by default
audio.offload.gapless.enabled=true
#Audio offload playback
audio.offload.disable=0
#Audio voice concurrency related flags
voice.playback.conc.disabled=true
voice.record.conc.disabled=true
voice.voip.conc.disabled=true
#Audio VoIP / playback record concurrency flags
rec.playback.conc.disabled=true
#Set composition for USB
#persist.sys.usb.config=diag,serial_smd,rmnet_qti_bam,adb
#Set read only default composition for USB
#ro.sys.usb.default.config=diag,serial_smd,rmnet_qti_bam,adb
# set max background services
ro.config.max_starting_bg=8
#property to enable user to access Google WFD settings
persist.debug.wfd.enable=1
#propery to enable VDS WFD solution
persist.hwc.enable_vds=1
#property to enable image unload by audio HAL
sys.audio.init=false
#property to enable DS2 dap
audio.dolby.ds2.enabled=true
#property to change touch screen resolution
persist.sys.synaptics_dsx.qhd=false
#HWUI properties
ro.hwui.text_large_cache_height=2048
# enable sta proxy bydefault
persist.mm.sta.enable=1
#Trim properties
ro.sys.fw.use_trim_settings=true
ro.sys.fw.empty_app_percent=50
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.trim_enable_memory=1073741824
# set cutoff voltage to 3200mV
ro.cutoff_voltage_mv=3200
#min/max cpu in core control
ro.core_ctl_min_cpu=2
ro.core_ctl_max_cpu=4
#Enable B service adj transition by default
ro.sys.fw.bservice_enable=true
ro.sys.fw.bservice_limit=5
ro.sys.fw.bservice_age=5000
#save memory property for camera daemon
cameradaemon.SaveMemAtBoot=1
#Disable sensors
ro.qti.sdk.sensors.gestures=false
ro.qti.sensors.scrn_ortn=false
ro.qti.sensors.facing=false
ro.qti.sensors.tilt=false
ro.qti.sensors.tilt_detector=false
ro.qti.sensors.tap=false
ro.qti.sensors.cmc=false
ro.qti.sensors.amd=false
ro.qti.sensors.rmd=false
ro.qti.sensors.pedometer=false
#Enable sensors
ro.qti.sensors.qheart=false
ro.qti.sensors.wrist_tilt=true
#Enable WearQSTA
ro.sensors.wearqstp=1
#WearQSTA Wakelock by default disabled
ro.sensors.wearqstp.lock=0
#reduce background apps limit to 16 on wearables
ro.sys.fw.bg_apps_limit=16
#Enable delay service restart
ro.am.reschedule_service=true
# No telephony or radio
setprop ro.radio.noril yes
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.vendor.extension_library=libqti-perfd-client.so
persist.radio.apm_sim_not_pwdn=1
persist.radio.sib16_support=1
ro.frp.pst=/dev/block/bootdevice/by-name/config
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
ro.ambient.plugged_timeout_min=5
ro.ambient.low_bit_enabled=false
ro.carrier=unknown
ro.config.low_ram=true
ro.bluetooth.hfp.ver=1.6
dalvik.vm.dex2oat-threads=1
ro.config.ringtone=Atria.ogg
ro.config.notification_sound=Tethys.ogg
ro.config.alarm_alert=Oxygen.ogg
ro.sf.lcd_density=280
ro.epad.model=swift
ro.force_screen_timeout=true
ro.build.csc.version=WW_WI503Q_MWG23_20170123
persist.sys.dalvik.vm.lib.2=libart
dalvik.vm.isa.arm.variant=cortex-a7
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.expect.bootloader=swift1003313
ro.expect.recovery_id=0x8483ccf7c509f998f3f26608974ee222fdac358a000000000000000000000000
DOWNLOAD WW_WI503Q_MWG23_20170123
Install via FASTBOOT commands
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Changelog MWF76 to MWG23
- Updated security patch to 2017-01-05

Ww_wi503q_mwg68_20170309
WW_WI503Q_MWG68_20170309
Code:
#
# PRODUCT_OEM_PROPERTIES
#
import /oem/oem.prop ro.oem.*
import /oem/oem.prop oem.*
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MWG68
ro.build.display.id=MWG68
ro.build.version.incremental=3798981
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-02-05
ro.build.version.base_os=
ro.build.date=Thu Mar 9 20:21:52 UTC 2017
ro.build.date.utc=1489090912
ro.build.type=user
ro.build.user=android-build
ro.build.host=wphm3.hot.corp.google.com
ro.build.tags=release-keys
ro.build.flavor=swift-user
ro.product.model=ASUS ZenWatch 3
ro.product.brand=asus
ro.product.name=swift
ro.product.device=swift
ro.product.board=swift
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=asus
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=msm8909
# ro.build.product is obsolete; use ro.product.device
ro.build.product=swift
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=swift-user 6.0.1 MWG68 3798981 release-keys
ro.build.fingerprint=asus/swift/swift:6.0.1/MWG68/3798981:user/release-keys
ro.build.characteristics=nosdcard,watch
# end build properties
#
# from device/asus/swift/system.prop
#
#
# system.prop for msm8909
#
#rild.libpath=/system/lib/libreference-ril.so
rild.libpath=/system/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
debug.hwc.dynThreshold=2.5
debug.mdpcomp.logs=0
dalvik.vm.heapsize=36m
dev.pm.dyn_samplingrate=1
persist.demo.hdmirotationlock=false
#enable dirty rect
debug.sf.swaprect=1
#enable app buffer composition
debug.sf.hwc.canUseABC=1
#enable gpu perf hint
sys.hwc.gpu_perf_mode=1
#ro.hdmi.enable=true
#tunnel.decode=true
#tunnel.audiovideo.decode=true
#lpa.decode=false
#lpa.use-stagefright=true
#persist.speaker.prot.enable=false
#
# system props for the cne module
#
persist.cne.feature=1
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
#codecs:(PARSER_)AAC AC3 AMR_NB AMR_WB ASF AVI DTS 3GP 3G2 MKV MP2PS MP2TS MP3 OGG QCP WAV FLAC
mm.enable.qcom_parser=262143
# Default to AwesomePlayer
media.stagefright.use-awesome=false
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true
persist.data.mode=concurrent
#system props for time-services
persist.timed.enable=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
# System property for cabl
ro.qualcomm.cabl=2
# System property for QDCM
persist.tuning.qdcm=1
# System property for Screen Color
ro.qcom.screencolor=1
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#
# System property for Camera
# System prop to allocate Reprocess buffer as "1"
# during Longshot usecase
persist.camera.longshot.stages=1
#
# dirty ratio value when enable ums
#
ro.sys.umsdirtyratio=20
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true
#Set for msm8909
tunnel.audio.encode = false
#enable low_ram property on low-tier devices
ro.config.low_ram=true
#Buffer size in kbytes for compress offload playback
audio.offload.buffer.size.kb=64
#Minimum duration for offload playback in secs
audio.offload.min.duration.secs=30
#Enable offload audio video playback by default
av.offload.enable=true
#enable voice path for PCM VoIP by default
use.voice.path.for.pcm.voip=true
#
#System property for FM transmitter
#
ro.fm.transmitter=false
#enable dsp gapless mode by default
audio.offload.gapless.enabled=true
#Audio offload playback
audio.offload.disable=0
#Audio voice concurrency related flags
voice.playback.conc.disabled=true
voice.record.conc.disabled=true
voice.voip.conc.disabled=true
#Audio VoIP / playback record concurrency flags
rec.playback.conc.disabled=true
#Set composition for USB
#persist.sys.usb.config=diag,serial_smd,rmnet_qti_bam,adb
#Set read only default composition for USB
#ro.sys.usb.default.config=diag,serial_smd,rmnet_qti_bam,adb
# set max background services
ro.config.max_starting_bg=8
#property to enable user to access Google WFD settings
persist.debug.wfd.enable=1
#propery to enable VDS WFD solution
persist.hwc.enable_vds=1
#property to enable image unload by audio HAL
sys.audio.init=false
#property to enable DS2 dap
audio.dolby.ds2.enabled=true
#property to change touch screen resolution
persist.sys.synaptics_dsx.qhd=false
#HWUI properties
ro.hwui.text_large_cache_height=2048
# enable sta proxy bydefault
persist.mm.sta.enable=1
#Trim properties
ro.sys.fw.use_trim_settings=true
ro.sys.fw.empty_app_percent=50
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.trim_enable_memory=1073741824
# set cutoff voltage to 3200mV
ro.cutoff_voltage_mv=3200
#min/max cpu in core control
ro.core_ctl_min_cpu=2
ro.core_ctl_max_cpu=4
#Enable B service adj transition by default
ro.sys.fw.bservice_enable=true
ro.sys.fw.bservice_limit=5
ro.sys.fw.bservice_age=5000
#save memory property for camera daemon
cameradaemon.SaveMemAtBoot=1
#Disable sensors
ro.qti.sdk.sensors.gestures=false
ro.qti.sensors.scrn_ortn=false
ro.qti.sensors.facing=false
ro.qti.sensors.tilt=false
ro.qti.sensors.tilt_detector=false
ro.qti.sensors.tap=false
ro.qti.sensors.cmc=false
ro.qti.sensors.amd=false
ro.qti.sensors.rmd=false
ro.qti.sensors.pedometer=false
#Enable sensors
ro.qti.sensors.qheart=false
ro.qti.sensors.wrist_tilt=true
#Enable WearQSTA
ro.sensors.wearqstp=1
#WearQSTA Wakelock by default disabled
ro.sensors.wearqstp.lock=0
#reduce background apps limit to 16 on wearables
ro.sys.fw.bg_apps_limit=16
#Enable delay service restart
ro.am.reschedule_service=true
# No telephony or radio
setprop ro.radio.noril yes
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.vendor.extension_library=libqti-perfd-client.so
persist.radio.apm_sim_not_pwdn=1
persist.radio.sib16_support=1
ro.frp.pst=/dev/block/bootdevice/by-name/config
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
ro.ambient.plugged_timeout_min=5
ro.ambient.low_bit_enabled=false
ro.carrier=unknown
ro.config.low_ram=true
ro.bluetooth.hfp.ver=1.6
dalvik.vm.dex2oat-threads=1
ro.config.ringtone=Atria.ogg
ro.config.notification_sound=Tethys.ogg
ro.config.alarm_alert=Oxygen.ogg
ro.sf.lcd_density=280
ro.epad.model=swift
ro.force_screen_timeout=true
ro.build.csc.version=WW_WI503Q_MWG68_20170309
persist.sys.dalvik.vm.lib.2=libart
dalvik.vm.isa.arm.variant=cortex-a7
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.expect.bootloader=swift1003313
ro.expect.recovery_id=0x5c5fe027d0eddfaade8a3734d02d171f1c8c7871000000000000000000000000
DOWNLOAD WW_WI503Q_MWG68_20170309
Install via FASTBOOT commands
Code:
adb reboot bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
Changelog MWG23 to MWG68
- Updated security patch to 2017-02-05

Hello, I have a problem with update. I first booted watch and it got ota. Now watches have MFW76 and it reboots every minute, even after a factory reset. Could someone help me with those? I bought it as present for my wife)

heckfycu said:
Hello, I have a problem with update. I first booted watch and it got ota. Now watches have MFW76 and it reboots every minute, even after a factory reset. Could someone help me with those? I bought it as present for my wife)
Click to expand...
Click to collapse
Did you flash any img from the first post? If not, contact Asus, if yes, try to reflash system and boot in fastboot, and if TWRP is installed don't allow it to modify /system.

Maxr1998 said:
Did you flash any img from the first post? If not, contact Asus, if yes, try to reflash system and boot in fastboot, and if TWRP is installed don't allow it to modify /system.
Click to expand...
Click to collapse
Yeah, thank you i used your images and reflashed device, even though asus support said that i can't do that and should send it to them)

ANDROID WEAR 2.0 NWD1.170623.001
DOWNLOAD
Code:
#
# PRODUCT_OEM_PROPERTIES
#
import /oem/oem.prop ro.oem.*
import /oem/oem.prop oem.*
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=NWD1.170623.001
ro.build.display.id=NWD1.170623.001
ro.build.version.incremental=4130756
ro.build.version.sdk=25
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=7.1.1
ro.build.version.security_patch=2017-06-01
ro.build.version.base_os=
ro.build.date=Fri Jun 23 19:40:31 UTC 2017
ro.build.date.utc=1498246831
ro.build.type=user
ro.build.user=android-build
ro.build.host=vpeb8.mtv.corp.google.com
ro.build.tags=release-keys
ro.build.flavor=swift-user
ro.product.model=ASUS ZenWatch 3
ro.product.brand=asus
ro.product.name=swift
ro.product.device=swift
ro.product.board=swift
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=asus
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=msm8909
# ro.build.product is obsolete; use ro.product.device
ro.build.product=swift
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=swift-user 7.1.1 NWD1.170623.001 4130756 release-keys
ro.build.fingerprint=asus/swift/swift:7.1.1/NWD1.170623.001/4130756:user/release-keys
ro.build.characteristics=nosdcard,watch
# end build properties
#
# from device/asus/swift/system.prop
#
#
# system.prop for msm8909
#
#rild.libpath=/system/lib/libreference-ril.so
rild.libpath=/system/vendor/lib/libril-qc-qmi-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
debug.sf.hw=1
debug.egl.hw=1
debug.composition.type=dyn
debug.hwc.dynThreshold=4.5
debug.mdpcomp.logs=0
dalvik.vm.heapsize=36m
dev.pm.dyn_samplingrate=1
persist.demo.hdmirotationlock=false
#enable dirty rect
debug.sf.swaprect=1
#enable app buffer composition
debug.sf.hwc.canUseABC=1
#enable gpu perf hint
sys.hwc.gpu_perf_mode=1
#ro.hdmi.enable=true
#tunnel.decode=true
#tunnel.audiovideo.decode=true
#lpa.decode=false
#lpa.use-stagefright=true
#persist.speaker.prot.enable=false
#
# system props for the cne module
#
persist.cne.feature=1
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
#codecs:(PARSER_)AAC AC3 AMR_NB AMR_WB ASF AVI DTS 3GP 3G2 MKV MP2PS MP2TS MP3 OGG QCP WAV FLAC
mm.enable.qcom_parser=262143
# Default to AwesomePlayer
media.stagefright.use-awesome=false
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true
persist.data.mode=concurrent
#system props for time-services
persist.timed.enable=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3
ro.opengles.version=196608
# System property for cabl
ro.qualcomm.cabl=2
# System property for QDCM
persist.tuning.qdcm=1
# System property for Screen Color
ro.qcom.screencolor=1
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#
# System property for Camera
# System prop to allocate Reprocess buffer as "1"
# during Longshot usecase
persist.camera.longshot.stages=1
#
# dirty ratio value when enable ums
#
ro.sys.umsdirtyratio=20
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
##fluencetype can be "fluence" or "fluencepro" or "none"
ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true
#Set for msm8909
tunnel.audio.encode = false
#enable low_ram property on low-tier devices
ro.config.low_ram=true
#Buffer size in kbytes for compress offload playback
audio.offload.buffer.size.kb=64
#Minimum duration for offload playback in secs
audio.offload.min.duration.secs=30
#Enable offload audio video playback by default
av.offload.enable=true
#enable voice path for PCM VoIP by default
use.voice.path.for.pcm.voip=true
#
#System property for FM transmitter
#
ro.fm.transmitter=false
#enable dsp gapless mode by default
audio.offload.gapless.enabled=true
#Audio offload playback
audio.offload.disable=0
#Audio voice concurrency related flags
voice.playback.conc.disabled=true
voice.record.conc.disabled=true
voice.voip.conc.disabled=true
#Audio VoIP / playback record concurrency flags
rec.playback.conc.disabled=true
#Set composition for USB
#persist.sys.usb.config=diag,serial_smd,rmnet_qti_bam,adb
#Set read only default composition for USB
#ro.sys.usb.default.config=diag,serial_smd,rmnet_qti_bam,adb
# set max background services
ro.config.max_starting_bg=8
#property to enable user to access Google WFD settings
persist.debug.wfd.enable=1
#propery to enable VDS WFD solution
persist.hwc.enable_vds=1
#property to enable image unload by audio HAL
sys.audio.init=false
#property to enable DS2 dap
audio.dolby.ds2.enabled=true
#property to change touch screen resolution
persist.sys.synaptics_dsx.qhd=false
#HWUI properties
ro.hwui.text_large_cache_height=2048
# enable sta proxy bydefault
persist.mm.sta.enable=1
#Trim properties
ro.sys.fw.use_trim_settings=true
ro.sys.fw.empty_app_percent=50
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.trim_enable_memory=1073741824
# set cutoff voltage to 3200mV
ro.cutoff_voltage_mv=3200
#min/max cpu in core control
ro.core_ctl_min_cpu=2
ro.core_ctl_max_cpu=4
#Enable B service adj transition by default
ro.sys.fw.bservice_enable=true
ro.sys.fw.bservice_limit=5
ro.sys.fw.bservice_age=5000
#save memory property for camera daemon
cameradaemon.SaveMemAtBoot=1
#Disable sensors
ro.qti.sdk.sensors.gestures=false
ro.qti.sensors.scrn_ortn=false
ro.qti.sensors.facing=false
ro.qti.sensors.tilt=false
ro.qti.sensors.tilt_detector=false
ro.qti.sensors.tap=false
ro.qti.sensors.cmc=false
ro.qti.sensors.amd=false
ro.qti.sensors.rmd=false
ro.qti.sensors.pedometer=false
#Enable sensors
ro.qti.sensors.qheart=false
ro.qti.sensors.wrist_tilt=true
#Enable WearQSTA
ro.sensors.wearqstp=1
#WearQSTA Wakelock by default disabled
ro.sensors.wearqstp.lock=0
#reduce background apps limit to 16 on wearables
ro.sys.fw.bg_apps_limit=16
#Enable delay service restart
ro.am.reschedule_service=true
# No telephony or radio
setprop ro.radio.noril yes
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.vendor.extension_library=libqti-perfd-client.so
persist.radio.apm_sim_not_pwdn=1
persist.radio.sib16_support=1
ro.frp.pst=/dev/block/bootdevice/by-name/config
ro.ambient.plugged_timeout_min=5
ro.ambient.low_bit_enabled=false
ro.stem_1.location.x=373
ro.stem_1.location.y=100
ro.stem_2.location.x=373
ro.stem_2.location.y=300
ro.stem_primary.location.x=400
ro.stem_primary.location.y=200
logd.logpersistd.size=256
debug.composition.type=dyn
debug.hwc.dynThreshold=4.5
debug.sf.hwc.canUseABC=1
dalvik.vm.boot-dex2oat-threads=4
dalvik.vm.dex2oat-threads=2
dalvik.vm.image-dex2oat-threads=4
sys.use_fifo_ui=1
ro.carrier=unknown
ro.config.low_ram=true
ro.config.max_starting_bg=8
ro.bluetooth.hfp.ver=1.6
ro.config.alarm_alert=Oxygen.ogg
ro.config.ringtone=Atria.ogg
ro.sf.lcd_density=280
ro.epad.model=swift
ro.force_screen_timeout=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=128m
dalvik.vm.heapmaxfree=8m
dalvik.vm.heapminfree=512k
dalvik.vm.heaptargetutilization=0.75
ro.build.csc.version=WW_WI503Q_NWD1.170623.001_20170623
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a7
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.build.expect.bootloader=swift-7.2.331.9
ro.expect.recovery_id=0x793d5d6660f71553b8719c2e5721561061e1874d000000000000000000000000
How to install:
Reboot to RECOVERY MODE
Select "apply update via ADB"
run command
Code:
adb sideload path/to/your/rom.zip

How to patch `system.img` to root the Samsung S10 5G (Qualcomm) device?

Hi All,
Device Detail:
- Samsung S10 5G
- Qualcomm Device
- Model: SM-G977U
- ROM: VZW-G977UVRU2ASH7-20190827135903
- Kernel-Version - Linux version 4.14.83-16633035 ([email protected]) (clang version 6.0.10 for Android NDK) #2 SMP PREEMPT Wed Aug 14 16:23:48 KST 2019
Background: I have
- rooted the device with instructions given by Magisk.
- I can successfully reboot to the recovery rootfs.
Problem: I am trying to modify the `system.img.ext4.lz4` file to root the device with normal boot. I am aware that it will not let the device install OTA Updates.
Unpack-Pack System and make new AP.tar, flash:
- Without any modification to the `system.img`, I have just unpacked `system.img.ext4.lz4`->`system.img.ext4`->`system.img`->mounted to system directory and packed it back to `system.img`->`system.img.ext4`->`system.img.ext4.lz4`.
- Replaced unpack-packed `system.img.ext4.lz4` with the AP `system.img.ext4.lz4` and make a tar of it.
- Then I have flashed it using Odin v3.13 along with BL, CP, and HOME_CSC.
- Odin has show PASS and I have rebooted the device into recovery mode.
- Done the Wipe data/factory reset and reboot to recovery again but released the recovery key combination on splash screen as mentioned in the root instructions .
- The device stuck in a boot loop.
Tries:
1. Disable Dm-verity
- Removed `avb` flag from `boot.img` with
Code:
magiskboot dtb boot.img patch
- Removed `avb` and `verify` flags from `dtbo.img` with
Code:
magiskboot dtb dtbo.img patch
- Patched `ramdisk.cpio` with
Code:
magiskboot cpio ./initrd 'patch false true'
Patched `boot.img` and `dtbo.img` is working fine with magisk patched AP file but the `ramdisk.cpio` creating the issue: Stuck at splash screen when trying to go to recovery after successfully flash with Odin. Download mode is appearing on splash screen.
So, I have used `boot.img` and `dtbo.img` along with unpack-packed `system.img.ext4.lz4` but the result is still a boot loop. I have also tried a combination of `boot.img` and `dtbo.img` along with unpack-packed `vendor.img.ext4.lz4` and flashed the AP.tar with other files but still the result is a boot loop.
So, I want to debug the problem and got to know about `pstore` which preserve the logs when kernel panic.
2. pstore
- Checked that `/sys/fs/pstore` is mounted by the system with following in init file: Grep the pstore using `find . | grep '\.rc' | xargs cat | grep pstore -n -i` and get following result:
Code:
314: # pstore/ramoops previous console log
315: mount pstore pstore /sys/fs/pstore nodev noexec nosuid
316: chown system log /sys/fs/pstore/console-ramoops
317: chmod 0440 /sys/fs/pstore/console-ramoops
318: chown system log /sys/fs/pstore/console-ramoops-0
319: chmod 0440 /sys/fs/pstore/console-ramoops-0
320: chown system log /sys/fs/pstore/pmsg-ramoops-0
321: chmod 0440 /sys/fs/pstore/pmsg-ramoops-0
- Checked the kernel config by pulling the file from /proc/config.gz.
Code:
$ cat config | grep PSTORE
CONFIG_PSTORE=y
CONFIG_PSTORE_ZLIB_COMPRESS=y
# CONFIG_PSTORE_LZO_COMPRESS is not set
# CONFIG_PSTORE_LZ4_COMPRESS is not set
CONFIG_PSTORE_CONSOLE=y
CONFIG_PSTORE_PMSG=y
CONFIG_PSTORE_PMSG_SSPLOG=y
CONFIG_PSTORE_RAM=y
- Check the `ramoops` configuration:
Code:
./sys/module/ramoops/parameters/console_size 262144
./sys/module/ramoops/parameters/dump_oops 1
./sys/module/ramoops/parameters/ecc 0
./sys/module/ramoops/parameters/ftrace_size 262144
./sys/module/ramoops/parameters/mem_address 3241148416
./sys/module/ramoops/parameters/mem_size 1048576
./sys/module/ramoops/parameters/mem_type 0
./sys/module/ramoops/parameters/pmsg_size 262144
./sys/module/ramoops/parameters/record_size 262144
`pstore` setup looks fine but when I am trying the get logs from `sys/fs/pstore` then I found nothing.
I have tried it by two ways:
1. Crash manually with panic kernel using:
Code:
echo 1 > /proc/sys/kernel/sysrq
echo c > /proc/sysrq-trigger
Followed Reading Kernel Logs
2. Flashing non-working rom that cause a boot loop and then flashed a working ROM with rooting steps and checked the file at `sys/fs/pstore`.
I need a favor in:
- Any steps to fix/debug the `pstore` problem?
- Any other way to find the kernel logs?
Update 1: I get the logs from recovery but I am not able to identify the problem.
Logs link: https://drive.google.com/file/d/1b-XNmjpYvH-L8lY0xA0SYr7XcITVCrVS/view?usp=sharing
Description: In this video, I have done the following:
1. Displayed recovery logs before: The last recovery logs are ends with 8.
2. Rebooted the device with a recovery key combination. I have already wipe data partition before making this video.
3. The boot loop happens and in the next reboot, I have pressed the recovery key combination to open the recovery mode where logs that end with 9 displayed.
4. Then I have recorded `last_history`, `last_avc_message_recovery`, `last_log.9` and `last_kmsg.9`
5. `last_history` and `last_avc_message_recovery` looks unchanged(same as before boot loop).
6. Then, I just have tried to mount the system but that didn't work.
7. At last, I have just rebooted the system normally without any recovery key combination.
Some Highlighted logs of last_log.9
exec -f /system/bin/e2fsck -v -y /dev/block/bootdevice/by-name/cache
error: _do_exec: can't run '/system/bin/e2fsck'
(errno 13 : Permission denied)
/system/bin/e2fsck terminated by exit(255)
...
E:Can't read /cache/recovery/last_locale: No such file or directory
...
W:Failed to unmount /efs: Device or resource busy
can't unmount /efs - Device or resource busy
...
W:Failed to set brightness: Invalid argument
I:Screensaver disabled
Atomic Commit failed in DisableNonMainCrtcs
Atomic Commit failed, rc = 0
...
Reboot Recovery Cause is [[BootChecker]RebootRecoveryWithKey]
...
print_recovery_cause() : reboot_reason=[[BootChecker]RebootRecoveryWithKey]
...
[property list]
persist.audio.fluence.speaker=true
...
ro.vendor.build.security_patch=2018-08-05
Supported API: 3
I:/efs is already mounted
W:Failed to unmount /efs: Device or resource busy
check_selective_file:Can't unmount /efs - Device or resource busy
just_reboot_after_update = 1
should_wipe_cahcewipe_cache
-- Wiping cache...
erase_volume(/cache)
...
MDF_I: Completed reset MDF flag!
MDF_I: Completed initialized MDF for Recovery!
mke2fs 1.43.3 (04-Sep-2016)
Discarding device blocksL 4096/153600??????????????????????????????done
Discard takes 0.00051s
Creating filesystem with 153600 4k blocks and 38400 inodes
...
Creating journal (2048 blocks): done
...
copy_logs
...
Cache wipe complete
[Checking pre-multi-csc2]
[start failed section]
sales_code=VZW
Carrier ID=[XAA]
[system partition space check]
The device has /product partition.
[out-recovery]
I:system root image is true, so need to change the unmount point from /system to /system_root
running out-recovery time : 0.000s
running recovery time: 1.738s
copy_avc_msg_to_data(1, )
I:fs_type "ext4" for /cache
copy_file 'proc/avc_msg' 'cache/recovery/last_avc_msg_recovery'
!__RECOVERY_FOR_ASSAMBLY
b_del_recovery_command = true
Rebooting...
## finish_recovery_terminate(del=1, reboot_cmd=reboot, clear_BCB=1)
## finish_recovery(delcmd=1,...
I:Saving locale "en-US"
I:fs_type "ext4" for /cache
I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vm-linux
I:## unlink /cache/recovery/command
copy_logs
I:fs_type "ext4" for /cache
copy_log_file :: create recovery log file '/cache/recovery/log'
copy_log_file :: create recovery log file '/cache/recovery/last_log'
Click to expand...
Click to collapse
Is anyone have experience in detecting problems from the kernel logs?

i can not help you, but we can collect ideas. what about re-sign the system.img? there is a key somewhere, i guess just deleting won't work but maybe it is possible to calculate checksum

or maybe you can switch to SuperSU 2.79 SR3 (latest release from chainfire) or at least look inside the update-binary shell script how to root system.
regarding dm-verity i would start with searching for "verify" flag in your fstabs and remove it. magisk is also doing some hex patches and re-signing, it's the best source to look inside magisk installer zip update-binary/ updater-script, if you have the knowledge to read code
another option is try to port a twrp recovery from another snapdragon (i wonder if somebody did this already) if you can find a porting guide

so the vzw s10 5g is unlockable?

elliwigy said:
so the vzw s10 5g is unlockable?
Click to expand...
Click to collapse
yes

aIecxs said:
yes
Click to expand...
Click to collapse
Figures lol.. I have a g975u from big red n don't plan on buying another lol

aIecxs said:
yes
Click to expand...
Click to collapse
Message me on telegram and I can help you if you help me.. I'm curious in some logs and what not.. I also might have something you can use..

Did you get it working? I have the same phone and I want to use the 600mgz tmobile 5g in a few days, so I need the right rom.

elliwigy said:
so the vzw s10 5g is unlockable?
Click to expand...
Click to collapse
aIecxs said:
yes
Click to expand...
Click to collapse
Snapdragon bootloader unlockable? How?
I'm a VZW customer and can get the phone on an upgrade, but want to root it...

i got a g977p and twrp n magisk working great

do you think it is possible to flash other branding on verizon devices with modded odin?

aIecxs said:
do you think it is possible to flash other branding on verizon devices with modded odin?
Click to expand...
Click to collapse
dunno.. its not possible on n976v..

Was there any luck on rooting the Verizon G977U?

@Vats12 has already successful rooted with magisk in recovery. this thread is for rooting system (kind of rooting where su binary is placed in /system/xbin like for older devices, which breaks OTA)

aIecxs said:
@Vats12 has already successful rooted with magisk in recovery. this thread is for rooting system (kind of rooting where su binary is placed in /system/xbin like for older devices, which breaks OTA)
Click to expand...
Click to collapse
So you want like the supersu method?

ExtremeGrief said:
So you want like the supersu method?
Click to expand...
Click to collapse
Yes, do you know how to do this?
Magisk (guide) does a lot of other things too..
Maybe we can use Magisk to disable the securities and then SuperSu can help in the rooting system?

Vats12 said:
Yes, do you know how to do this?
Magisk (guide) does a lot of other things too..
Maybe we can use Magisk to disable the securities and then SuperSu can help in the rooting system?
Click to expand...
Click to collapse
But why? Safetynet will be gone
What model is the device?

ExtremeGrief said:
But why? Safetynet will be gone
What model is the device?
Click to expand...
Click to collapse
model see OP! i guess because of the buttons needed for booting in magiskrecovery, but the reason is not important only HOW (for Vats12, not for me i don't own this device)

Sorry but this thread needs to be closed
aIecxs said:
model see OP! i guess because of the buttons needed for booting in magiskrecovery, but the reason is not important only HOW (for Vats12, not for me i don't own this device)
Click to expand...
Click to collapse
I don't want to be the one who shouts fake, but the instructions you gave a link to says you have to be able to flash a bootloader first, which means an unlocked blootloader, if you have Verizon rom this is not possible, as the blootloader is locked.
If you did find a way to flash a modified bootloader, or a modified recovery those are the instructions we need, because in fastboot you are unable to do this with a locked bootloader and you are unable to unlock the bootloader on Verizon. If you have a modified bootloader or recovery flashed on your device what did you use to flash it with Odin? Because only way to flash a boot.img is either get into download mode and flash with Odin, or with Edl, if you got into edl mode then can you provide instructions on that, because we would like to know how to get the device into EDL mode as well
Sorry boys this is a hoax.

@DroidisLINUX there is video proof in OP, and again for you:
This is not a tutorial about unlocking and rooting, it is a question how he can modify /system to permanently integrate su