[RECOVERY][cherry] TWRP 3.2.3-0 touch recovery for Huawei G620S, Honor 4/4x - Honor 4x ROMs, Kernels, Recoveries, & Other Develo

[RECOVERY][cherry] TWRP 3.2.3-0 touch recovery for Huawei G620S, Honor 4/4x - Honor 4x ROMs, Kernels, Recoveries, & Other Develo

Team Win Recovery Project 3.x, or twrp3 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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
All function in a normal TWRP
Build with latest TWRP source
Multi-language support
Support F2FS file system!
Battery capacity display works well!
Kernel based on android_kernel_cyanogen_msm8916
Changelog:
2016/2/6
First release
2016/2/19
Merge latest TWRP source from OmniROM
Fix slow wiping
Support installing opengapps(released after 20160217)
2016/3/19
Merge latest TWRP source from OmniROM
Add support for Honor 4x(Che1_CL10 Che1_CL20 Che1_L04)
2016/5/31
Merge latest TWRP source from OmniROM
Sync with latest CM kernel, support ext2/ext3
Fixed dancing touchscreen for some devices
2017/1/3
Merge latest TWRP source from OmniROM
Build with latest LineageOS 14.1 source, update to N kernel
Enable dt2w
2018/8/8
Misc updates, supports Oreo
Build with latest LineageOS 15.1 source, update to O kernel
Supported device:
C8817D
C8817E
G621-TL00
G620S-UL00
G620S-L01/L02/L03
Che1_CL10
Che1_CL20
Che1_L04
Screenshot:
{
"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"
}
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Run "fastboot flash recovery TWRP_3.2.3-0_O_cherry.img" in command line
4. Reboot and enjoy it
Download:
https://androidfilehost.com/?fid=3700668719832236215
Source code:
https://github.com/LineageTWRP/android_bootable_recovery
https://github.com/LineageOS/android_kernel_huawei_msm8916
XDA:DevDB Information
TWRP, ROM for all devices (see above for details)
Contributors
dianlujitao
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 9
Stable Release Date: 2018-08-08
Created 2016-02-06
Last Updated 2018-08-08

Reserved

Hello dianlujitao i have few bugs, with this version on G620S-L01
*random button blinking on home menu or random slide bar moving
*MTP, i don’t see any device on Windows, tried enable/disable MTP without success
*language and time zone settings are not saved after reboot
and problem with installing gapps, but that’s in warning
Otherwise its work great.

very important step to run the gapps we're in TWRP recovery to wipe
There we go to Advanced Wipe
Select up the system partition and we give Repair or Change File System
We will come out several options we give Resize File System
Best Regards

vavrof said:
Hello dianlujitao i have few bugs, with this version on G620S-L01
*random button blinking on home menu or random slide bar moving
*MTP, i don’t see any device on Windows, tried enable/disable MTP without success
*language and time zone settings are not saved after reboot
and problem with installing gapps, but that’s in warning
Otherwise its work great.
Click to expand...
Click to collapse
UPDATE
*random button blinking on every menu or random slide bar moving - this happens only when i moove,shake or flip phone, maybe some bad values from position sensors
*MTP, i don’t see any device on Windows, tried enable/disable MTP without success - my bad, wrong default windows driver, after change for right one work properly

Can this be installed on Honor 4x - Che1-L04?
Is it ready for Honor 4x - Che1-L04?

update 16/02/19

dianlujitao said:
update 16/02/19
Click to expand...
Click to collapse
Hello dianlujitao, please check your upload inside .img is Cyanogen Recovery

vavrof said:
Hello dianlujitao, please check your upload inside .img is Cyanogen Recovery
Click to expand...
Click to collapse
Fixed, thanks

Unfortunately I can't create a backup in recovery to my adopted SD card.
Error message is: "Can not crate '/external_sd...' folder (Out of memory). Failed to make backup folder."
Can You help me?

Recovery TWRP is crazy
Hello, the recovery on my huawei G620S-L01 goes crazy
whenever I give a box starts to touch others without sense
I leave the log on the recovery, if it's worth

Hi OP,
I'm asking another developer @Lanchon on Github to get Honor 4X a REPIT file to re-partition phone space, you can refer to this thread:
https://github.com/Lanchon/REPIT/issues/28
I was using your TWRP 2.8.7 and encounter some bugs (EDIT: actually just me being dumb!!!TWRP 2.8.7 was OK)
Then I think maybe I should use TWRP 3.0 to try again, but I have another error, when I flash the zip Lanchon provided, the script was checking my phone and an error message showed up "FATAL: required tool 'awk' missing (please use a recent version of TWRP to run this package)". Is there any advice you can give me on how to solve this awk issue? Thank you very much.

Should I need to unlock bootloader? o:
No "fastboot oem unlock"? o:

@dianlujitao, I tried this on my G620S-L01, but its not very usable - menu options are being selected randomly if you move the phone, its like its trying to read touch input from the gyro sensors, like @vavrof was saying about earlier builds.
Are there any logs that I could provide or tweaks I could try to help get this fixed?

EccTM said:
@dianlujitao, I tried this on my G620S-L01, but its not very usable - menu options are being selected randomly if you move the phone, its like its trying to read touch input from the gyro sensors, like @vavrof was saying about earlier builds.
Are there any logs that I could provide or tweaks I could try to help get this fixed?
Click to expand...
Click to collapse
1. Enter TWRP and mount /system
2. Connect your phone to a computer and open adb shell
3. run "getevent" in the shell
4. move your phone to trigger the issue you mentioned
5. paste shell output here
Sent from my NX510J using XDA-Developers mobile app

dianlujitao said:
1. Enter TWRP and mount /system
2. Connect your phone to a computer and open adb shell
3. run "getevent" in the shell
4. move your phone to trigger the issue you mentioned
5. paste shell output here
Sent from my NX510J using XDA-Developers mobile app
Click to expand...
Click to collapse
shell output
c:\adb>adb shell
[email protected]:/ # getevent
add device 1: /dev/input/event6
name: "qpnp_pon"
add device 2: /dev/input/event4
name: "compass"
add device 3: /dev/input/event2
name: "input_mt_wrapper"
could not get driver version for /dev/input/mice, Not a typewriter
add device 4: /dev/input/event1
name: "proximity"
add device 5: /dev/input/event0
name: "light"
add device 6: /dev/input/event5
name: "lis3dh-accel"
add device 7: /dev/input/event3
name: "synaptics_dsx_i2c"
add device 8: /dev/input/event7
name: "gpio-keys"
/dev/input/event5: 0003 0000 ffffe950
/dev/input/event5: 0003 0001 00001ca0
/dev/input/event5: 0003 0002 000032f0
/dev/input/event5: 0000 0004 00000189
/dev/input/event5: 0000 0005 2af8cf17
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe8c0
/dev/input/event5: 0003 0001 00001ce0
/dev/input/event5: 0003 0002 00003360
/dev/input/event5: 0000 0004 00000189
/dev/input/event5: 0000 0005 36e43c74
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe9a0
/dev/input/event5: 0003 0001 00001bd0
/dev/input/event5: 0003 0002 00003440
/dev/input/event5: 0000 0004 0000018a
/dev/input/event5: 0000 0005 07354969
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffeba0
/dev/input/event5: 0003 0001 00001bc0
/dev/input/event5: 0003 0002 00003520
/dev/input/event5: 0000 0004 0000018a
/dev/input/event5: 0000 0005 1320fcc3
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe9a0
/dev/input/event5: 0003 0001 00001c80
/dev/input/event5: 0003 0002 00003330
/dev/input/event5: 0000 0004 0000018a
/dev/input/event5: 0000 0005 1f0cc100
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffdb70
/dev/input/event5: 0003 0001 00001f70
/dev/input/event5: 0003 0002 00002d50
/dev/input/event5: 0000 0004 0000018a
/dev/input/event5: 0000 0005 2af8aff6
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffdcd0
/dev/input/event5: 0003 0001 00002290
/dev/input/event5: 0003 0002 ffffec90
/dev/input/event5: 0000 0004 0000018a
/dev/input/event5: 0000 0005 36e467fe
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffdd20
/dev/input/event5: 0003 0001 00001fe0
/dev/input/event5: 0003 0002 ffffe7e0
/dev/input/event5: 0000 0004 0000018b
/dev/input/event5: 0000 0005 07353133
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe920
/dev/input/event5: 0003 0001 00000eb0
/dev/input/event5: 0003 0002 00002630
/dev/input/event5: 0000 0004 0000018b
/dev/input/event5: 0000 0005 132104b2
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffeab0
/dev/input/event5: 0003 0001 00000be0
/dev/input/event5: 0003 0002 00003740
/dev/input/event5: 0000 0004 0000018b
/dev/input/event5: 0000 0005 1f0cefca
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe1f0
/dev/input/event5: 0003 0001 00001590
/dev/input/event5: 0003 0002 fffff3c0
/dev/input/event5: 0000 0004 0000018b
/dev/input/event5: 0000 0005 2af87837
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffd2c0
/dev/input/event5: 0003 0001 00001ee0
/dev/input/event5: 0003 0002 ffffe5a0
/dev/input/event5: 0000 0004 0000018b
/dev/input/event5: 0000 0005 36e433b4
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffcd80
/dev/input/event5: 0003 0001 00002150
/dev/input/event5: 0003 0002 ffffe2f0
/dev/input/event5: 0000 0004 0000018c
/dev/input/event5: 0000 0005 0735501f
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffd030
/dev/input/event5: 0003 0001 00002060
/dev/input/event5: 0003 0002 fffff060
/dev/input/event5: 0000 0004 0000018c
/dev/input/event5: 0000 0005 132129b8
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe860
/dev/input/event5: 0003 0001 00001940
/dev/input/event5: 0003 0002 000029c0
/dev/input/event5: 0000 0004 0000018c
/dev/input/event5: 0000 0005 1f0cbe5a
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffff6b0
/dev/input/event5: 0003 0001 00000fc0
/dev/input/event5: 0003 0002 ffffebf0
/dev/input/event5: 0000 0004 0000018c
/dev/input/event5: 0000 0005 2af8aef1
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe330
/dev/input/event5: 0003 0001 00002050
/dev/input/event5: 0003 0002 00000170
/dev/input/event5: 0000 0004 0000018c
/dev/input/event5: 0000 0005 36e437f9
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffffc10
/dev/input/event5: 0003 0001 00000cd0
/dev/input/event5: 0003 0002 00003560
/dev/input/event5: 0000 0004 0000018d
/dev/input/event5: 0000 0005 0735626e
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffd530
/dev/input/event5: 0003 0001 00001b40
/dev/input/event5: 0003 0002 00002270
/dev/input/event5: 0000 0004 0000018d
/dev/input/event5: 0000 0005 13212ece
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffd4f0
/dev/input/event5: 0003 0001 00001dc0
/dev/input/event5: 0003 0002 00002190
/dev/input/event5: 0000 0004 0000018d
/dev/input/event5: 0000 0005 1f0cba7c
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffd520
/dev/input/event5: 0003 0001 000018a0
/dev/input/event5: 0003 0002 000036d0
/dev/input/event5: 0000 0004 0000018d
/dev/input/event5: 0000 0005 2af8846b
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffcee0
/dev/input/event5: 0003 0001 00002730
/dev/input/event5: 0003 0002 00001050
/dev/input/event5: 0000 0004 0000018d
/dev/input/event5: 0000 0005 36e42d65
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe700
/dev/input/event5: 0003 0001 00001430
/dev/input/event5: 0003 0002 000036c0
/dev/input/event5: 0000 0004 0000018e
/dev/input/event5: 0000 0005 07354214
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffdd00
/dev/input/event5: 0003 0001 00001bd0
/dev/input/event5: 0003 0002 00002550
/dev/input/event5: 0000 0004 0000018e
/dev/input/event5: 0000 0005 1321061d
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffdd80
/dev/input/event5: 0003 0001 000025a0
/dev/input/event5: 0003 0002 ffffff50
/dev/input/event5: 0000 0004 0000018e
/dev/input/event5: 0000 0005 1f0ca4b7
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe640
/dev/input/event5: 0003 0001 00001ef0
/dev/input/event5: 0003 0002 00000c40
/dev/input/event5: 0000 0004 0000018e
/dev/input/event5: 0000 0005 2af889b5
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffec90
/dev/input/event5: 0003 0001 00001570
/dev/input/event5: 0003 0002 000040b0
/dev/input/event5: 0000 0004 0000018e
/dev/input/event5: 0000 0005 36e44c1d
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffdf10
/dev/input/event5: 0003 0001 00001e60
/dev/input/event5: 0003 0002 00002d70
/dev/input/event5: 0000 0004 0000018f
/dev/input/event5: 0000 0005 07351c3c
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe2a0
/dev/input/event5: 0003 0001 00001a20
/dev/input/event5: 0003 0002 00002a90
/dev/input/event5: 0000 0004 0000018f
/dev/input/event5: 0000 0005 13210da4
/dev/input/event5: 0000 0000 00000000

dianlujitao said:
1. Enter TWRP and mount /system
2. Connect your phone to a computer and open adb shell
3. run "getevent" in the shell
4. move your phone to trigger the issue you mentioned
5. paste shell output here
Sent from my NX510J using XDA-Developers mobile app
Click to expand...
Click to collapse
Followed your instructions, getting the same as @vavrof.
/event5 is just spamming input, /event3 seems to be me touching the screen.
Code:
C:\Users\lorde\Desktop\adbfastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:/ # getevent
add device 1: /dev/input/event6
name: "qpnp_pon"
add device 2: /dev/input/event4
name: "compass"
add device 3: /dev/input/event2
name: "input_mt_wrapper"
could not get driver version for /dev/input/mice, Not a typewriter
add device 4: /dev/input/event1
name: "proximity"
add device 5: /dev/input/event0
name: "light"
add device 6: /dev/input/event5
name: "lis3dh-accel"
add device 7: /dev/input/event3
name: "synaptics_dsx_i2c"
add device 8: /dev/input/event7
name: "gpio-keys"
/dev/input/event5: 0003 0000 ffffff90
/dev/input/event5: 0003 0001 00000290
/dev/input/event5: 0003 0002 00003e20
/dev/input/event5: 0000 0004 00000053
/dev/input/event5: 0000 0005 2b915ff2
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff50
/dev/input/event5: 0003 0001 00000260
/dev/input/event5: 0003 0002 00003ec0
/dev/input/event5: 0000 0004 00000053
/dev/input/event5: 0000 0005 377d1967
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff60
/dev/input/event5: 0003 0001 00000290
/dev/input/event5: 0003 0002 00003eb0
/dev/input/event5: 0000 0004 00000054
/dev/input/event5: 0000 0005 07ce1c97
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff80
/dev/input/event5: 0003 0001 000002d0
/dev/input/event5: 0003 0002 00003e70
/dev/input/event5: 0000 0004 00000054
/dev/input/event5: 0000 0005 13b9d7e0
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff60
/dev/input/event5: 0003 0001 00000280
/dev/input/event5: 0003 0002 00003e90
/dev/input/event5: 0000 0004 00000054
/dev/input/event5: 0000 0005 1fa59a7d
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff70
/dev/input/event5: 0003 0001 00000270
/dev/input/event5: 0003 0002 00003e60
/dev/input/event5: 0000 0004 00000054
/dev/input/event5: 0000 0005 2b915732
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff90
/dev/input/event5: 0003 0001 000002d0
/dev/input/event5: 0003 0002 00003e50
/dev/input/event5: 0000 0004 00000054
/dev/input/event5: 0000 0005 377d21be
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff80
/dev/input/event5: 0003 0001 00000270
/dev/input/event5: 0003 0002 00003e30
/dev/input/event5: 0000 0004 00000055
/dev/input/event5: 0000 0005 07ce0dbd
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffffa0
/dev/input/event5: 0003 0001 00000260
/dev/input/event5: 0003 0002 00003e40
/dev/input/event5: 0000 0004 00000055
/dev/input/event5: 0000 0005 13b9eea9
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff80
/dev/input/event5: 0003 0001 000002a0
/dev/input/event5: 0003 0002 00003e30
/dev/input/event5: 0000 0004 00000055
/dev/input/event5: 0000 0005 1fa5b2b2
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff70
/dev/input/event5: 0003 0001 00000280
/dev/input/event5: 0003 0002 00003e40
/dev/input/event5: 0000 0004 00000055
/dev/input/event5: 0000 0005 2b915c14
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffff80
/dev/input/event5: 0003 0001 000002c0
/dev/input/event5: 0003 0002 00003e70
/dev/input/event5: 0000 0004 00000055
/dev/input/event5: 0000 0005 377d1eb0
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffffe90
/dev/input/event5: 0003 0001 00000280
/dev/input/event5: 0003 0002 00003f10
/dev/input/event5: 0000 0004 00000056
/dev/input/event5: 0000 0005 07ce0f29
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00000bd0
/dev/input/event5: 0003 0001 fffff740
/dev/input/event5: 0003 0002 00003ff0
/dev/input/event5: 0000 0004 00000056
/dev/input/event5: 0000 0005 13b9d402
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00002510
/dev/input/event5: 0003 0001 fffff4e0
/dev/input/event5: 0003 0002 00002990
/dev/input/event5: 0000 0004 00000056
/dev/input/event5: 0000 0005 1fa5980b
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00003160
/dev/input/event5: 0003 0001 fffffe30
/dev/input/event5: 0003 0002 fffffb10
/dev/input/event5: 0000 0004 00000056
/dev/input/event5: 0000 0005 2b9165d8
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00001fb0
/dev/input/event5: 0003 0001 00000f00
/dev/input/event5: 0003 0002 00001770
/dev/input/event5: 0000 0004 00000056
/dev/input/event5: 0000 0005 377d47c9
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffe7d0
/dev/input/event5: 0003 0001 00001430
/dev/input/event5: 0003 0002 00002060
/dev/input/event5: 0000 0004 00000057
/dev/input/event5: 0000 0005 07ce16b0
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 ffffd710
/dev/input/event5: 0003 0001 00000b60
/dev/input/event5: 0003 0002 00002f30
/dev/input/event5: 0000 0004 00000057
/dev/input/event5: 0000 0005 13b9dc59
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 000006d0
/dev/input/event5: 0003 0001 ffffe1c0
/dev/input/event5: 0003 0002 00003fe0
/dev/input/event5: 0000 0004 00000057
/dev/input/event5: 0000 0005 1fa59ef5
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 000022f0
/dev/input/event5: 0003 0001 ffffd700
/dev/input/event5: 0003 0002 00002ba0
/dev/input/event5: 0000 0004 00000057
/dev/input/event5: 0000 0005 2b915bdf
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00002b40
/dev/input/event5: 0003 0001 fffff990
/dev/input/event5: 0003 0002 00000eb0
/dev/input/event5: 0000 0004 00000057
/dev/input/event5: 0000 0005 377d2225
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00003050
/dev/input/event5: 0003 0001 00000520
/dev/input/event5: 0003 0002 000012a0
/dev/input/event5: 0000 0004 00000058
/dev/input/event5: 0000 0005 07ce143e
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00003bf0
/dev/input/event5: 0003 0001 00000410
/dev/input/event5: 0003 0002 fffffd50
/dev/input/event5: 0000 0004 00000058
/dev/input/event5: 0000 0005 13b9deca
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00002bc0
/dev/input/event5: 0003 0001 fffffde0
/dev/input/event5: 0003 0002 000029b0
/dev/input/event5: 0000 0004 00000058
/dev/input/event5: 0000 0005 1fa59d54
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00000920
/dev/input/event5: 0003 0001 000000d0
/dev/input/event5: 0003 0002 00004410
/dev/input/event5: 0000 0004 00000058
/dev/input/event5: 0000 0005 2b9162ca
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffff910
/dev/input/event5: 0003 0001 00000c20
/dev/input/event5: 0003 0002 000036e0
/dev/input/event5: 0000 0004 00000058
/dev/input/event5: 0000 0005 377d22c1
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffff390
/dev/input/event5: 0003 0001 00000f90
/dev/input/event5: 0003 0002 00003850
/dev/input/event5: 0000 0004 00000059
/dev/input/event5: 0000 0005 07ce150e
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffff3d0
/dev/input/event5: 0003 0001 00001120
/dev/input/event5: 0003 0002 00003680
/dev/input/event5: 0000 0004 00000059
/dev/input/event5: 0000 0005 13b9dab8
/dev/input/event5: 0000 0000 00000000
/dev/input/event3: 0003 0039 00000004
/dev/input/event3: 0001 014a 00000001
/dev/input/event3: 0003 0035 000000a4
/dev/input/event3: 0003 0036 000004ce
/dev/input/event3: 0003 003a 00000039
/dev/input/event3: 0003 0030 00000005
/dev/input/event3: 0003 0031 00000003
/dev/input/event3: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffff400
/dev/input/event5: 0003 0001 000011d0
/dev/input/event5: 0003 0002 00003da0
/dev/input/event5: 0000 0004 00000059
/dev/input/event5: 0000 0005 1fa5b00b
/dev/input/event5: 0000 0000 00000000
/dev/input/event3: 0003 0039 ffffffff
/dev/input/event3: 0001 014a 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffff630
/dev/input/event5: 0003 0001 00001320
/dev/input/event5: 0003 0002 00003a60
/dev/input/event5: 0000 0004 00000059
/dev/input/event5: 0000 0005 2b916ab8
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffff380
/dev/input/event5: 0003 0001 000019d0
/dev/input/event5: 0003 0002 00003d90
/dev/input/event5: 0000 0004 00000059
/dev/input/event5: 0000 0005 377d269e
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 fffff8a0
/dev/input/event5: 0003 0001 00001120
/dev/input/event5: 0003 0002 00003b80
/dev/input/event5: 0000 0004 0000005a
/dev/input/event5: 0000 0005 07ce2555
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00000350
/dev/input/event5: 0003 0001 00000420
/dev/input/event5: 0003 0002 00003d50
/dev/input/event5: 0000 0004 0000005a
/dev/input/event5: 0000 0005 13b9eb32
/dev/input/event5: 0000 0000 00000000
/dev/input/event5: 0003 0000 00000050
/dev/input/event5: 0003 0001 00000490
/dev/input/event5: 0003 0002 00003f80
/dev/input/event5: 0000 0004 0000005a
/dev/input/event5: 0000 0005 1fa5ae9f

dancing touchscreen in TWRP fixed, already uploaded a new release

dianlujitao said:
dancing touchscreen in TWRP fixed, already uploaded a new release
Click to expand...
Click to collapse
Please help me #dianlujitao
My issue are
In twrp2.8.7.0
When flashing it through fastboot it shows "dtb" not found
In twrp2.8.6.0
Same issue like 2.8.6.0
In cm12.1
After flashing the cm12.1 unofficial cherry. zip trough twrp2.8.4.0 it goes to bootloader mode
In cm13
After flashing it through twrp2.8.4.0 my speaker and sound not working if sound works then phone over heated.
My device
Che1-l04
Snapdragon 400/410
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
dianlujitao said:
dancing touchscreen in TWRP fixed, already uploaded a new release
Click to expand...
Click to collapse
Please help me #dianlujitao
My issue are
In twrp2.8.7.0
When flashing it through fastboot it shows "dtb" not found
In twrp2.8.6.0
Same issue like 2.8.6.0
In cm12.1
After flashing the cm12.1 unofficial cherry. zip trough twrp2.8.4.0 it goes to bootloader mode
In cm13
After flashing it through twrp2.8.4.0 my speaker and sound not working if sound works then phone over heated.
My device
Che1-l04
Snapdragon 400/410
msm8916

subrajit96 said:
Please help me #dianlujitao
My issue are
In twrp2.8.7.0
When flashing it through fastboot it shows "dtb" not found
In twrp2.8.6.0
Same issue like 2.8.6.0
In cm12.1
After flashing the cm12.1 unofficial cherry. zip trough twrp2.8.4.0 it goes to bootloader mode
In cm13
After flashing it through twrp2.8.4.0 my speaker and sound not working if sound works then phone over heated.
My device
Che1-l04
Snapdragon 400/410
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
Please help me #dianlujitao
My issue are
In twrp2.8.7.0
When flashing it through fastboot it shows "dtb" not found
In twrp2.8.6.0
Same issue like 2.8.6.0
In cm12.1
After flashing the cm12.1 unofficial cherry. zip trough twrp2.8.4.0 it goes to bootloader mode
In cm13
After flashing it through twrp2.8.4.0 my speaker and sound not working if sound works then phone over heated.
My device
Che1-l04
Snapdragon 400/410
Click to expand...
Click to collapse
twrp3.0 is 100% compatible with cm13.0, I don't care about old software and won't do any fix
Sent from my NX510J using XDA-Developers mobile app

Related

Hermes ROM kitchen

I've created a wiki page to provide all the needed instructions and tools to cook your custom ROM images for Hermes devices. Those people cooking custom ROM images, please feel free to edit it and add more information, you can use this thread for discussing ROM editing on hermes.
Hermes_ROM_kitchen
Tools involved in the kitchen:
SSPL
Custom RUU
NBHextract
NBH generator
aChef
IMGFS tools
nb_image_converter

Excellent, thanks to all involved in creating this little lot.
Now I just need to find the time to play...

Nice - I just spent half the day yesterday searching through posts to figure out half of what you listed here! Nice work! One tool I found on a MS page which I found useful was this program, I'm sure everybody else has found it already but didn't see it listed. Basicially it will let you dump the user.hv and default.hv for easy reading I just basically used it like:
d_readvol.exe default.hv > default.txt
and I got a nice dump that made it much easier to root around. There's probably easier/better tools out there but this served my purpose and might help others
Thanks Pof and everybody else working so hard!!!

Incase people are interested in more on the program - found the link
http://blogs.msdn.com/ce_base/archi...Registry-Hives-and-CEDB-Database-Volumes.aspx

I'm a little confused about converting REG files back into HV files... Could someone address this please? (EDIT: Is this how you're doing it? http://forum.xda-developers.com/showpost.php?p=853755&postcount=72) When I do that, I get this error:
Code:
importing registry file ".\boot.rgu"...
Failed to parse value name HKEY_CURRENT_USER\Software\Microsoft\Windows
InitRegistry FAILED in file ".\boot.rgu" within a few lines of lin e 4
BuildBootHive: (RGUComp) !ERROR failed importing ".\boot.rgu"
wmain: (RGUComp) !ERROR failed building BOOT hive
Also, I read that modifying the "dump" directory, then converting back into an IMG file isn't supported. What does that mean exactly? Does that mean it doesn't work, or it works sometmes but not always, or what?

richy240 said:
I'm a little confused about converting REG files back into HV files... Could someone address this please?
Click to expand...
Click to collapse
Edit the .reg with ultraedit, add "REGEDIT4" string at the beginning of the file, then save it with UTF-16 format and lines terminated with CR+LF. Name the file boot.rgu and run "rgucomp.exe -b", this will produce the .hv file.
richy240 said:
Also, I read that modifying the "dump" directory, then converting back into an IMG file isn't supported. What does that mean exactly? Does that mean it doesn't work, or it works sometmes but not always, or what?
Click to expand...
Click to collapse
It means the resulting imgfs_raw_data.bin will produce bad blocks on device when flashed

pof said:
It means the resulting imgfs_raw_data.bin will produce bad blocks on device when flashed
Click to expand...
Click to collapse
Damn, I was afraid of that.
Should I be concerned with the error listed above? I do get a resulting HV file, but I am still getting this error even after following your directions exactly (UTF-16, CR+LF, etc.). When I convert the HV file back to REG for viewing, I get the folloowing:
Code:
[HKEY_CURRENT_USER\Software\Microsoft\Windows]
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:409
That's it. Four lines of the original file, and the error listed above mentions "InitRegistry FAILED in file ".\boot.rgu" within a few lines of line 4". Any info about this would be greatly appreciated! Here're the first few lines of my actual REG file:
Code:
REGEDIT4
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:409
[HKEY_CURRENT_USER\Software\Microsoft\Windows]
"DbPath"="\\mxip_initdb.vol" "LangDbPath"="\\mxip_lang.vol"
[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
"EnableNegotiate"=dword:1 "EnableHttp1_1"=dword:1 "ProxyHttp1.1"=dword:1 "AggressiveCacheFlush"=dword:0 "ShowDialogFullScreen"=dword:1 "DialogTimeOut"=dword:493e0 "EnableAutodial"=dword:0 "MaxConnectionsPerServer"=dword:4 "DisableCachingOfSSLPages"=dword:0 "SecureProtocols"=hex:A0,00,00,00
This http://forum.xda-developers.com/showpost.php?p=857801&postcount=149 seemed to generate a good boot.hv file; that is, rgucomp.exe produced no errors.
Thanks in advance!
(So are these some n00b questions or what? Sorry guys...)

pof said:
It means the resulting imgfs_raw_data.bin will produce bad blocks on device when flashed
Click to expand...
Click to collapse
Was the bad block device tested with the old make_prepare_imgfs.exe or the new aChef?
I think aChef may not produce bad block OS.nb but I haven't tested this yet.

It was tested with makeimgfs, haven't tested with aChef... probably we should try... and pray for our NAND

TO DO
We have two nice kitchen toolkits integrating some or all the tools above to cook ROMs:
Olipro's ROM Kitchen
dutty's rom koch
This is the list of things we still need to do to have a good framework for ROM cooking, in order of importance:
Try to flash a cooked rom using aChef + viewimgfs.exe + modify "dump" directory + BuildImgfs.exe + aChef and see if it produces a good imgfs flashable file (without bad blocks), if it does implement a OS.nb rom kitchen using that method.
Investigate on the ExtROM.nb format so we can extract and cook ExtROM also.
Have a tool like nb_image_converter.exe but which allows command line operation, so it can be integrated easily on the kitchen toolkits to cook splash screens
Anyone willing to help on any of this?

Also would be nice to know how to change page pool on WM6 roms, I think on xda-live OS.nb the right offset is this one:
Code:
[0x00000000003B6C90] > x
offset 0 1 2 3 4 5 6 7 8 9 A B C D E F 0123456789ABCDEF
----------------+----------------------------------------+----------------.
00000000003B6C90 4E4B 4B44 3800 0000 0000 0005 0000 0000 |NKKD8...........|
00000000003B6CA0 00C8 FFFF 8039 2D80 4060 2880 B069 2880 |[email protected]`(..i(.|
00000000003B6CB0 B869 2880 AC69 2880 144A 0180 805D 2D80 |.i(..i(..J...]-.|
00000000003B6CC0 602A 2D80 1829 0080 0000 0000 0000 0000 |`*-..)..........|
00000000003B6CD0 E7A8 39A8 E277 E349 BD98 F6D9 1559 A609 |..9..w.I.....Y..|
00000000003B6CE0 4400 0000 00C8 FFFF 8039 2D80 4060 2880 |[email protected]`(.|
00000000003B6CF0 B069 2880 B869 2880 AC69 2880 144A 0180 |.i(..i(..i(..J..|
00000000003B6D00 805D 2D80 602A 2D80 1829 0080 0000 0000 |.]-.`*-..)......|
00000000003B6D10 605D 2D80 0000 0000 3C58 E8F2 E237 B64F |`]-.....<X...7.O|
00000000003B6D20 A104 8B4C 7BF2 AE4C 6C00 0000 0000 0000 |...L{..Ll.......|
00000000003B6D30 0000 0000 0000 0000 0000 0000 0000 0000 |................|
00000000003B6D40 0000 0000 0000 0000 0000 0000 0000 0000 |................|
00000000003B6D50 0000 0000 0000 0000 0000 0000 0000 0000 |................|
00000000003B6D60 0000 0000 0000 0000 0000 0000 0000 0000 |................|
00000000003B6D70 0000 0000 0000 0000 0000 0000 0000 0000 |................|
00000000003B6D80 0000 0000 0000 0000 FF00 0000 A0D3 0180 |................|
00000000003B6D90 00C8 FFFF 8039 2D80 1027 0000 FF00 0000 |.....9-..'......|
00000000003B6DA0 3200 0000 F8F9 FAFB FCFD FEFF 44EB 0180 |2...........D...|
00000000003B6DB0 D0EC 0180 3CED 0180 B421 0080 C057 2D80 |....<....!...W-.|
00000000003B6DC0 60EA 0180 B8EB 0180 2CED 0180 C821 0080 |`.......,....!..|
00000000003B6DD0 A037 2D80 CCEA 0180 38EC 0180 34ED 0180 |.7-.....8...4...|
00000000003B6DE0 DC21 0080 2038 2D80 8037 2D80 A036 2D80 |.!.. 8-..7-..6-.|
00000000003B6DF0 4039 2D80 C038 2D80 6037 2D80 0038 2D80 |@9-..8-.`7-..8-.|
00000000003B6E00 2038 2D80 A037 2D80 411D 0000 FDFF FBFF | 8-..7-.A.......|
00000000003B6E10 C057 2D80 C036 2D80 C037 2D80 2037 2D80 |.W-..6-..7-. 7-.|
00000000003B6E20 4037 2D80 E036 2D80 E038 2D80 2039 2D80 |@7-..6-..8-. 9-.|
00000000003B6E30 6039 2D80 6038 2D80 E058 2D80 A038 2D80 |`9-.`8-..X-..8-.|
00000000003B6E40 9CB5 0180 1C24 0080 0C24 0080 FC23 0080 |.....$...$...#..|
00000000003B6E50 E423 0080 D423 0080 BC23 0080 A023 0080 |.#...#...#...#..|
00000000003B6E60 7C23 0080 FFFF FFFF FFFF FFFF FFFF FFFF ||#..............|
00000000003B6E70 FFFF FFFF FFFF FFFF FFFF BFFF FFFF BFFF |................|
00000000003B6E80 FFFF FFFF 0100 0000 D8CD 0280 0200 0000 |................|
00000000003B6E90 4002 0000 DC2D 0080 0000 0000 0000 0000 |@....-..........|
00000000003B6EA0 0000 0000 E400 0000 D82D 0080 0000 0000 |.........-......|
00000000003B6EB0 0000 0000 0000 0000 2400 0000 B02D 0080 |........$....-..|
00000000003B6EC0 0000 0000 0000 0000 0000 0000 A800 0000 |................|
00000000003B6ED0 942D 0080 0000 0000 0000 0000 0000 0000 |.-..............|
00000000003B6EE0 4000 0000 7C2D 0080 0000 0000 0000 0000 |@...|-..........|
00000000003B6EF0 0000 0000 1000 0000 702D 0080 0000 0000 |........p-......|
00000000003B6F00 0000 0000 0000 0000 0C02 0000 682D 0080 |............h-..|
00000000003B6F10 0000 0000 0000 0000 0000 0000 0004 0000 |................|
00000000003B6F20 602D 0080 0000 0000 0000 0000 0000 0000 |`-..............|
00000000003B6F30 8039 2D80 F700 0000 1027 0000 F41C 0480 |.9-......'......|
00000000003B6F40 581D 0480 C41C 0480 BC1C 0480 00B0 0400 |X...............|
00000000003B6F50 FFFF FFFF FFFF FFFF 9B4F FFFF 64B0 0000 |.........O..d...|
00000000003B6F60 6400 0000 A85B 0480 0000 [b]6000[/b] 0000 0000 |d....[....`.....|
00000000003B6F70 38E8 0180 C43C 0280 DC6B 0180 00B0 0380 |8....<...k......|
00000000003B6F80 882D 0280 FC2C 0280 D488 0480 5489 0480 |.-...,......T...|
00000000003B6F90 0C88 0480 9C86 0480 8C87 0480 1487 0480 |................|
00000000003B6FA0 3476 0480 68AF 0280 48B0 0280 A0B2 0280 |4v..h...H.......|
00000000003B6FB0 54B3 0280 58BB 0280 34BC 0280 14BD 0280 |T...X...4.......|
00000000003B6FC0 34B1 0280 10BA 0280 98B7 0280 04B0 0280 |4...............|
00000000003B6FD0 1486 0480 AC7A 0480 3C7B 0480 BC7B 0480 |.....z..<{...{..|
00000000003B6FE0 347C 0480 A47C 0480 3C7D 0480 BC7D 0480 |4|...|..<}...}..|
00000000003B6FF0 5C7E 0480 DC7E 0480 6C7F 0480 0480 0480 |\~...~..l.......|
00000000003B7000 8C80 0480 3481 0480 AC81 0480 3482 0480 |....4.......4...|
00000000003B7010 421D 0000 FDFF FBFF AC82 0480 5083 0480 |B...........P...|
00000000003B7020 1C84 0480 AC84 0480 2485 0480 9C85 0480 |........$.......|
00000000003B7030 A473 0480 1C74 0480 B474 0480 3475 0480 |.s...t...t..4u..|
00000000003B7040 B475 0480 C476 0480 9477 0480 1C78 0480 |.u...v...w...x..|
00000000003B7050 AC78 0480 2479 0480 9C79 0480 247A 0480 |.x..$y...y..$z..|
00000000003B7060 0CAF 0280 70B4 0280 48B5 0280 74B6 0280 |....p...H...t...|
00000000003B7070 0100 0000 E803 0000 E0FA 0480 7CFA 0480 |............|...|
00000000003B7080 0000 0200 0000 70B4 0000 50B6 0000 40B6 |[email protected]|
[0x00000000003B6C90] >
The actual page pool size is 6 Megabytes
I'm now testing 12Mb, 8Mb, 6Mb and 4Mb pagepools with spb benchmark, will post results on a new thread when finished...
EDIT: Results here.

pof said:
This is the list of things we still need to do to have a good framework for ROM cooking, in order of importance:
Try to flash a cooked rom using aChef + viewimgfs.exe + modify "dump" directory + BuildImgfs.exe + aChef and see if it produces a good imgfs flashable file (without bad blocks), if it does implement a OS.nb rom kitchen using that method.
Investigate on the ExtROM.nb format so we can extract and cook ExtROM also.
Have a tool like nb_image_converter.exe but which allows command line operation, so it can be integrated easily on the kitchen toolkits to cook splash screens
Anyone willing to help on any of this?
Click to expand...
Click to collapse
4. Investigate on the XIP area of OS.nb ( I will release new version of aChef to extract the XIP so that others could modify that area. )

pof said:
Edit the .reg with ultraedit, add "REGEDIT4" string at the beginning of the file, then save it with UTF-16 format and lines terminated with CR+LF. Name the file boot.rgu and run "rgucomp.exe -b", this will produce the .hv file.
It means the resulting imgfs_raw_data.bin will produce bad blocks on device when flashed
Click to expand...
Click to collapse
I modified the dumb directory and used buildimgfs.exe and then used aChef's tools to convert to an image. it all worked out fine..

madjokeer said:
I modified the dumb directory and used buildimgfs.exe and then used aChef's tools to convert to an image. it all worked out fine..
Click to expand...
Click to collapse
Yes, it's working!

pof said:
Yes, it's working!
Click to expand...
Click to collapse
--Deleted---

Hello All from Egypt
Hi Guys, I am brand new in this issue of cooking, never cooked a rom before, I read the Wiki and it is great but there is only one thing i want to know but i can't understand @ all let me get to my point,
If i want to add an application to a vanilla or any rom (just the os i won't be playing with anything else ) so wut kind of file i can use to add this application, like I have an application in .cab format how do I add it to my rom? I am using rom koch of dutty but i can use any other tool also.
thanx so much

Help needed
Guys plz answer me in that may be i am little new but i just want to start,
i am trying to get some roms and add some applications to it but i have them as a cab file can any body tell me how to convert them so that i cook my own rom with it ......plz anybody answer me
thanx

@sarwat: Read this thread, your question has been answered in comment #11.
Learn to search before posting.

pof said:
@sarwat: Read this thread, your question has been answered in comment #11.
Learn to search before posting.
Click to expand...
Click to collapse
thanx pof I next time i will search good

Hi pof... what is missing there is how to localize any WM6 rom... would be nice to see some instructions on that.
.wysiwyg { background-attachment: scroll; background-repeat: repeat; background-position: 0% 0%; background-color: #ffffcc; background-image: none; color: #000000; font-family: Verdana, Arial, Arial; font-style: normal; font-variant: normal; font-weight: 400; font-size: 10pt; line-height: normal } p { margin: 0px; }

[Sound WO hiss] Hardware volume control on P500

Hi to all!
(Sorry for bad English, and, please move this thread to development forum)
I'am trying to reduce noise (hiss) in LG P500. I think it is possible to implement h/w volume control like in FM Radio application, but I am newbie in C/C++ and Android programming and need help.
I found that it is possible to access and control WM9093 amplifier through i2c bus (bypass MSM7227 DSP). Also I found possibility to reduce hiss by reducing amplification.
The idea is:
- Software volume is always at max level
- Increase/decrease volume at h/w level via WM9093 registers
My test platform is mik_os's firmware 6.6.1 with 2.6.35.13 kernel.
Download it here: http://www.multiupload.com/5JLR9BUU7J
Here is modified i2c-gpio-custom driver:
http://pastebin.com/7YqUzg8M
It is allows to turn i2c bus On and Off. There is little trouble: DSP can not access WM9093 when i2c bus used by Linux kernel. So you need to turn it On before access, then do something with WM9093, and then turn it Off to allow DSP work with it.
To compile driver:
1) put in kernel_src/drivers/i2c/busses/
2) Add this
Code:
config I2C_GPIO_CUSTOM
tristate "GPIO-based I2C custom"
depends on GENERIC_GPIO
select I2C_ALGOBIT
help
GPIO-based I2C custom
to Kconfig
and this
Code:
obj-$(CONFIG_I2C_GPIO_CUSTOM) += i2c-gpio-custom.o
to Makefile in same folder.
3) Mark i2c-gpio-custom driver to build as a module
4)
Code:
make modules
How to use:
Code:
modprobe i2c-gpio-custom bus0=6,17,27
6 - bus number
17 - i2c SDA
27 - i2c SCL
Mount debugfs for module control:
Code:
mount debugfs /sys/kernel/debug/ -t debufs
Now you can activate and deactivate bus:
Code:
echo 1 >/sys/kernel/debug/custom_i2c/bus_state
echo 0 >/sys/kernel/debug/custom_i2c/bus_state
It is on by default.
After activating you can access WM9093 registers. WM9093 address is 0x6e. You can do it via i2c tools (i2cget, i2cset, i2cdump). E.g.:
Code:
i2cdump -y 6 0x6e w
Here are some dumps:
http://pastebin.com/3tgjzLv6 - FM Radio through headphones at volume level 1
http://pastebin.com/6HxXhfPs - FM Radio through headphones at volume level 3
As you can see, there are difference in 0x1c and 0x1d registers.
I think you can use datasheet from WM9090 for WM9093, registers looks same. You can download it at www.wolfsonmicro.com.
http://minus.com/mbozx2UIyP# - i2ctools source with Android.mk
http://minus.com/mbbv1SMcYK# - compiled i2c tools
P.S. Thanks to Mik_os for help with driver and for good FW!

Good news:
Code:
0,8 1,9 2,a 3,b 4,c 5,d 6,e 7,f
00: 9390 1b10 c060 0801 0000 0000 c001 0000
08: 0000 0000 0000 0000 0000 0000 0000 0000
10: 0000 0100 0000 0000 0000 0100 0300 0300
18: 0200 0200 8300 8300 2d00 2d00 0000 0000
20: 0000 0000 0011 0000 2000 c001 1b00 0000
28: 0000 0000 0000 0000 0000 0000 0000 0001
30: 0001 0000 0000 0000 0000 0000 0000 0000
38: 0000 0d00 0000 0000 0000 0000 0000 0000
40: 0000 0020 5e00 0000 0000 0300 0000 0000
48: 0000 0000 0000 0000 251f 192b c001 4c09
50: 002b 0400 c001 001c 0000 4a05 0700 0000
58: 0030 0000 0000 0000 0000 1a00 0800 0200
60: 0001 6000 4086 00c0 0002 4014 0000 0000
68: 0000 0000 0000 3302 0400 0000 0000 0000
70: 0000 0000 0000 0000 0000 0000 0000 0000
78: 0000 0000 0000 0000 0000 0000 0000 0000
80: 0000 4c0f 0106 0000 0000 3700 0030 0000
88: 0000 0000 0060 1048 4400 0000 0000 0000
90: 0000 0000 0000 0000 0000 2000 0000 0200
98: 0000 0000 0300 0f00 0000 0000 0200 0000
a0: 0000 0000 0000 0000 0000 0000 0000 0000
a8: 0000 0000 0000 0000 0000 0000 0000 0000
b0: 0000 0000 0001 0000 0000 0000 0000 0000
b8: 0000 0000 0000 0000 0000 0000 0000 0000
c0: 0000 0100 0400 0800 0000 0000 3701 0000
c8: 0000 0000 0000 0000 0000 0000 0000 0000
d0: 0000 0000 0000 0000 0000 0000 0000 0000
d8: 0000 0000 0000 0000 0000 0000 0000 0000
e0: 0000 0000 0000 0000 0000 0000 0000 0000
e8: 0000 0000 0000 0000 0000 0000 0000 0000
f0: 0000 0000 0000 0000 0000 0000 0000 0000
f8: 0000 0000 0000 0000 0000 0000 0000 0000
There is NO (at all) in call noise with these values.
0) Load module and deactivate i2c bus
1) Call someone
2) Activate i2c bus
echo 1 > /sys/kernel/debug/custom_i2c/bus_state
3) Set registers 0x1, 0x2, 0x3, 0x15, 0x18, 0x19, 0x26, 0x85
4) clear sound, no hisssss!
Anybody can help with development?
No one wants good sound wo hiss?

You should have posted in the Development section, your work if implemented sounds like a dream, that hissing noise is hell to our ears.
unfortunately is way over my head so in can't help

The problem is I am new to android development and do not know C++ enough to do it myself. But I know that it is possible, I am sure. I can not post in dev section, because have less than 10 posts.

bumping this back up, any kernel dev want to try?

Headset - scancode 240 detected, button hold removes the device

I have a creative 630i headset which button press gets detected as either a 226 or 240 scancode by the phone. I have added code 240 to keylayout so that the button always works but one problem remains. Holding the button when code 240 is detected "removes the device", that is, headset button does not work anymore and I have to disconnect and reconnect it.
Do any of you have an idea on how to disable dropping the device when '240' press and hold is detected?
Is it possible to force the phone to 'believe' that only code 226 is possible from the headset (convert all 240 to 226)?
from getevent:
Code:
add device 10: /dev/input/event3
name: "sec_jack"
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00e2 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00e2 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00e2 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00e2 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00e2 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00e2 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000001
/dev/input/event3: 0000 0000 00000000
/dev/input/event3: 0001 00f0 00000000
/dev/input/event3: 0000 0000 00000001
remove device 10: /dev/input/event3

It's because SGSII supports 3-buttons headset. Main button use short cirquit, while two other use resistors to make specific ADC value. Probably your headset somehow doesn't produce lower enough ADC value to make main button code. May be because of wires used in your headset or button resistance.
What u need is to remove ADC comparison value in sec_jack.c: function sec_jack_buttons_work:
this code:
Code:
adc = sec_jack_get_adc_data(hi->padc);
for (i = 0; i < pdata->num_buttons_zones; i++)
if (adc >= btn_zones[i].adc_low &&
adc <= btn_zones[i].adc_high) {
hi->pressed_code = btn_zones[i].code;
input_report_key(hi->input_dev, btn_zones[i].code, 1);
switch_set_state(&switch_sendend, 1);
input_sync(hi->input_dev);
pr_info("%s: keycode=%d, is pressed\n", __func__,
btn_zones[i].code);
return;
}
change to this:
Code:
i=0;
hi->pressed_code = btn_zones[i].code;
input_report_key(hi->input_dev, btn_zones[i].code, 1);
switch_set_state(&switch_sendend, 1);
input_sync(hi->input_dev);
pr_info("%s: keycode=%d, is pressed\n", __func__,
btn_zones[i].code);
return;
in other words: just remove ADC compare and make all buttons act as a play/pause

GPS makes my phone reboot (surnia)

I'm having an issue that I've been trying to fix for a month now, everytime an app tries to use the GPS, my phone crash and reboots. It happens with all roms except stock. Any idea what it could be?
build.board: MSM8916
build.bootloader: 0x8020
build.brand: Motorola
build.cpu_abi: armeabi-v7a
build.cpu_abi2: armeabi
build.device: surnia_umts
build.display: slim_surnia-userdebug 7.1.2 NJH47B 11e90beeff test-keys
build.fingerprint: motorola/surnia_retus/surnia_umts:5.0.2/LXI22.50-24.1/1:user/release-keys
build.hardware: qcom
build.host: autobuild
build.id: NJH47B
build.manufacturer: Motorola
build.model: XT1527
build.product: Moto E LTE (2nd gen)
build.radio: M8916_2020629.41.03.21.51R
build.serial: TA0930D46O
build.tags: test-keys
build.time: 1498185618000
build.type: userdebug
build.user: jenkins
version.codename: REL
version.incremental: 11e90beeff
version.release: 7.1.2
version.sdk_int: 25
--------- beginning of system
--------- beginning of crash
07-06 00:50:50.860 F/libc (1651): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x0 in tid 1759 (android.bg)
07-06 00:50:51.013 F/DEBUG (4923): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
07-06 00:50:51.013 F/DEBUG (4923): SLIM Version: 'Slim-7.1.2.build.0.29-BETA-20170623-0440'
07-06 00:50:51.013 F/DEBUG (4923): Build fingerprint: 'motorola/surnia_retus/surnia_umts:5.0.2/LXI22.50-24.1/1:user/release-keys'
07-06 00:50:51.013 F/DEBUG (4923): Revision: '0'
07-06 00:50:51.013 F/DEBUG (4923): ABI: 'arm'
07-06 00:50:51.014 F/DEBUG (4923): pid: 1651, tid: 1759, name: android.bg >>> system_server <<<
07-06 00:50:51.014 F/DEBUG (4923): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
07-06 00:50:51.014 F/DEBUG (4923): r0 97bfb100 r1 00000001 r2 00000000 r3 0000001c
07-06 00:50:51.014 F/DEBUG (4923): r4 adc05030 r5 a0180340 r6 97bfb100 r7 00000001
07-06 00:50:51.014 F/DEBUG (4923): r8 00000000 r9 b4285900 sl 00000001 fp a1d61198
07-06 00:50:51.014 F/DEBUG (4923): ip 00000008 sp a0180318 lr b3356d71 pc 00000000 cpsr 60070010
07-06 00:50:51.017 F/DEBUG (4923):
07-06 00:50:51.017 F/DEBUG (4923): backtrace:
07-06 00:50:51.018 F/DEBUG (4923): #00 pc 00000000 <unknown>
07-06 00:50:51.018 F/DEBUG (4923): #01 pc 00017d6f /system/lib/libandroid_servers.so
07-06 00:50:51.018 F/DEBUG (4923): #02 pc 0119f435 /data/dalvik-cache/arm/[email protected]@[email protected] (offset 0xc9b000)
--------- beginning of main
07-06 00:51:22.911 D/NetworkMonitor/NetworkAgentInfo [WIFI () - 101]( 5171): PROBE_DNS OK 38ms, www.google.com=172.217.0.228
07-06 00:51:22.914 D/NetworkMonitor/NetworkAgentInfo [WIFI () - 101]( 5171): PROBE_DNS OK 41ms, connectivitycheck.gstatic.com=172.217.2.99
07-06 00:51:22.977 D/NetworkMonitor/NetworkAgentInfo [WIFI () - 101]( 5171): PROBE_HTTP http://connectivitycheck.gstatic.com/generate_204 time=59ms ret=204 headers={null=[HTTP/1.1 204 No Content], Content-Length=[0], Date=[Thu, 06 Jul 2017 04:51:23 GMT], X-Android-Received-Millis=[1499316682975], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1499316682950]}
07-06 00:51:23.094 D/NetworkMonitor/NetworkAgentInfo [WIFI () - 101]( 5171): PROBE_HTTPS https://www.google.com/generate_204 time=176ms ret=204 headers={null=[HTTP/1.1 204 No Content], Alt-Svc=[quic=":443"; ma=2592000; v="39,38,37,36,35"], Content-Length=[0], Date=[Thu, 06 Jul 2017 04:51:23 GMT], X-Android-Received-Millis=[1499316683092], X-Android-Response-Source=[NETWORK 204], X-Android-Selected-Protocol=[http/1.1], X-Android-Sent-Millis=[1499316683060]}
Click to expand...
Click to collapse
Sorry for the spam down there, couldn't post the logcat since I didn't have 10 posts

..

..

..

..

..

..

..

Unyaffs not working for *.img

Failed mounting system.img with header
Hi all !
[history]
Three years ago I bought a phone (HTC Desire 320), the night I received it, I flash a ROM found on Internet and root it with the bad root application k*root.
(Bad because I install a firewall, and the app tried to connect to an IP from NSA, why ? Whatever...)
This weekend, I (by mistake) deleted a "framework" app, and the phone didn't start anymore. (In fact it start, but all applications restart, the pincode application, launchers, it was unusable anymore.)
Ok, so I reflash the ROM I had (I was more noob three years ago, I didn't make any dump of my "virgin" phone before flashing the other ROM found on the internet), by the way, "only" a weird version of SPflashtool (V5.1348_sec) can flash this phone, I don't know why, but it is another question, if someone have or could help me to get this version working on Linux, tell me please.
Right, my phone is repaired, as the virgin state. But I loose the root. I don't want to reuse any weird "one click root app". I've the system.img, I should be able to add it by myself ! But...
[/history]
I tried "unyaffs" but it didn't recognised the pattern. I tried "unsparse" (or sparse, or sparse.pl, I don't remember, all scripts I tried). But It didn't works.
After many trys, I'm still unable to mount it.
The last I tried is github.com/ehlers/unyaffs
Code:
$./unyaffs ../ROM/system.img
Can't determine flash layout, perhaps not a yaffs2 image
For example, a "normal" recovery.img (I don't know, but I guess in a yaffs format) should start with "ANDROID!", but before that, I've 0x4000 byte of header. I've maybe also a footer !
Code:
$ xxd -s 0x0000 -l 400 ./recovery.img
00000000: 4246 4246 0200 0000 0100 0000 0000 0001 BFBF............
00000010: 7265 636f 7665 7279 0000 0000 0000 0000 recovery........
00000020: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000030: 0078 4700 0000 0000 0000 0000 0000 0000 .xG.............
00000040: 3faa 9d18 1db9 8fbc b5e9 703f a5f9 9aa6 ?.........p?....
00000050: f8d3 ac26 8dc9 0a9d c912 ac32 6001 27d1 ...&.......2`.'.
00000060: 1e3f 7b14 79c3 3c0a 81f5 7f8d 50b3 aa17 .?{.y.<.....P...
00000070: a915 747b 548b 22d1 3b45 8522 5758 3d08 ..t{T.".;E."WX=.
00000080: 5bd9 679f 7866 7a47 e4ab 4b3b 3648 ded5 [.g.xfzG..K;6H..
00000090: caab 7f79 47f9 80b7 afce 02db c605 d367 ...yG..........g
000000a0: 5b49 9d72 bbce 2653 c2cd ef70 2f57 01e5 [I.r..&S...p/W..
000000b0: 458f 893d f33f a0fa 5398 f0d9 8e1c 2df0 E..=.?..S.....-.
000000c0: 302c d8f6 b5fe 6c0e b2b3 954f d6ee ec8d 0,....l....O....
000000d0: 65df 25ee 0000 0000 0000 0000 0000 0000 e.%.............
000000e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000100: 4246 4246 0200 0000 0100 0000 0000 0001 BFBF............
00000110: 7265 636f 7665 7279 0000 0000 0000 0000 recovery........
00000120: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000130: 0078 4700 0000 0000 0000 0000 0000 0000 .xG.............
00000140: 7f11 0413 6baa 5df2 fc06 dd6f e25f 4b62 ....k.]....o._Kb
00000150: 86a2 b6f5 0000 0000 0000 0000 0000 0000 ................
00000160: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000170: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000180: 0000 0000 0000 0000 0000 0000 0000 0000 ................
Code:
$ xxd -s 0x38F0 -l 400 ./recovery.img
00003f80: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003f90: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fa0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fb0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fc0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fd0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fe0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003ff0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00004000: 5353 5353 5439 3800 0023 2323 2323 2323 SSSST98..#######
00004010: 2323 2323 2323 2323 0a00 6420 6173 2030 ########..d as 0
00004020: 2c20 7468 0100 0000 9400 0000 4000 0000 , [email protected]
00004030: 797b 797b 0000 0000 0000 0000 0078 4700 y{y{.........xG.
00004040: 414e 4452 4f49 4421 08d3 3300 0080 0010 ANDROID!..3.....
00004050: 4e94 1300 0000 0011 0000 0000 0000 f010 N...............
00004060: 0001 0010 0008 0000 0000 0000 0000 0000 ................
00004070: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00004080: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00004090: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00004100: 0000 0000 0000 0000 0000 0000 0000 0000 ................
As see, there is an header. I don't know what to do. Is the header important ? For example, does it contains a checksum or a signature ? Or could I split the .img into three part, header, image, footer, modifying the image, and simple concatenate the three files ?
For the ./system.img :
Code:
$ xxd -s 0x0000 -l 400 ./system.img
00000000: 4246 4246 0200 0000 4500 0000 0000 0001 BFBF....E.......
00000010: 7379 7374 656d 0000 0000 0000 0000 0000 system..........
00000020: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000030: 40fc 2444 0000 0000 0000 0000 0000 0000 @.$D............
00000040: 3534 a9d8 4d3e 2088 687c 4a50 af50 34f4 54..M> .h|JP.P4.
00000050: fce6 1622 dc25 8b53 fdb4 cbac 35f5 fdda ...".%.S....5...
00000060: 9d5f f0e1 ad7c bf21 01e8 caff 8ddc cd33 ._...|.!.......3
00000070: 87d7 8964 d151 9b78 99a5 64c1 88a8 970b ...d.Q.x..d.....
00000080: f647 1650 0672 28f3 c260 a4b5 5931 0039 .G.P.r(..`..Y1.9
00000090: d375 9896 4cd1 f201 fcf1 c4ec 4fef aae6 .u..L.......O...
000000a0: 33cd 7866 96f1 71cb bbbc 63cb be74 2433 3.xf..q...c..t$3
000000b0: c55c e485 cd06 de44 498f 6ee4 670c ee30 .\.....DI.n.g..0
000000c0: 322d 7ab1 f289 e1bb 412f d8bd 2aac 152a 2-z.....A/..*..*
000000d0: 7fa4 8e3f 0000 0000 0000 0000 0000 0000 ...?............
000000e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000000f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000100: 4246 4246 0200 0000 4500 0000 0000 0001 BFBF....E.......
00000110: 7379 7374 656d 0000 0000 0000 0000 0000 system..........
00000120: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00000130: 40fc 2444 0000 0000 0000 0000 0000 0000 @.$D............
00000140: 56ad 592a ee85 9a0c caa6 1acd d400 13f6 V.Y*............
00000150: 115a fd02 2d29 baa3 56bd 3368 fccd 3df8 .Z..-)..V.3h..=.
00000160: be30 7254 acad 1da1 5163 7c49 b184 ce55 .0rT....Qc|I...U
00000170: f210 cebd d948 4e0d a909 7bca 207a dbf9 .....HN...{. z..
00000180: 83bb 9673 7bf0 4b49 faea 39b8 9dd9 0403 ...s{.KI..9.....
Code:
$ xxd -s 0x38F0 -l 400 ./system.img
00003f80: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003f90: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fa0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fb0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fc0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fd0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003fe0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00003ff0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00004000: 5353 5353 5439 3800 0023 2323 2323 2323 SSSST98..#######
00004010: 2323 2323 2323 2323 0a00 6420 6173 2030 ########..d as 0
00004020: 2c20 7468 0100 0000 9400 0000 4000 0000 , [email protected]
00004030: 797b 797b 0000 0000 0000 0000 40fc 2444 y{y{[email protected]$D
00004040: 3aff 26ed 0100 0000 1c00 0c00 0010 0000 :.&.............
00004050: 00ce 0400 0309 0000 0000 0000 c1ca 0000 ................
00004060: 0100 0000 0c10 0000 0000 0000 0000 0000 ................
00004070: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00004080: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00004090: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
000040f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................
00004100: 0000 0000 0000 0000 0000 0000 0000 0000 ................
For more information, I copy/paste some info from the scatter file here (cleared, without all lines).
Code:
- config_version: V1.1.1
platform: MT6582
project: uc81
boot_channel: MSDC_0
block_size: 0x20000
partition_name: PRELOADER
file_name: preloader_uc81.bin
type: SV5_BL_BIN
linear_start_addr: 0x0
physical_start_addr: 0x0
partition_size: 0xc00000
partition_name: MBR
file_name: MBR
type: NORMAL_ROM
linear_start_addr: 0xc00000
physical_start_addr: 0x0
partition_size: 0x80000
partition_name: EBR1
file_name: EBR1
type: NORMAL_ROM
linear_start_addr: 0xc80000
physical_start_addr: 0x80000
partition_size: 0x80000
partition_name: PRO_INFO
linear_start_addr: 0xd00000
physical_start_addr: 0x100000
partition_size: 0x300000
partition_name: NVRAM
linear_start_addr: 0x1000000
physical_start_addr: 0x400000
partition_size: 0x500000
partition_name: PROTECT_F
linear_start_addr: 0x1500000
physical_start_addr: 0x900000
partition_size: 0xa00000
partition_name: PROTECT_S
linear_start_addr: 0x1f00000
physical_start_addr: 0x1300000
partition_size: 0xa00000
partition_name: SECCFG
linear_start_addr: 0x2900000
physical_start_addr: 0x1d00000
partition_size: 0x20000
partition_name: UBOOT
file_name: lk.bin
type: NORMAL_ROM
linear_start_addr: 0x2920000
physical_start_addr: 0x1d20000
partition_size: 0x60000
partition_name: BOOTIMG
file_name: boot.img
type: NORMAL_ROM
linear_start_addr: 0x2980000
physical_start_addr: 0x1d80000
partition_size: 0x600000
partition_name: RECOVERY
file_name: recovery.img
type: NORMAL_ROM
linear_start_addr: 0x2f80000
physical_start_addr: 0x2380000
partition_size: 0x600000
partition_name: SEC_RO
file_name: secro.img
type: YAFFS_IMG
linear_start_addr: 0x3580000
physical_start_addr: 0x2980000
partition_size: 0x600000
partition_name: MISC
linear_start_addr: 0x3b80000
physical_start_addr: 0x2f80000
partition_size: 0x80000
partition_name: LOGO
file_name: logo.bin
type: NORMAL_ROM
linear_start_addr: 0x3c00000
physical_start_addr: 0x3000000
partition_size: 0x300000
partition_name: EBR2
file_name: EBR2
type: NORMAL_ROM
linear_start_addr: 0x3f00000
physical_start_addr: 0x3300000
partition_size: 0x80000
partition_name: RESV
linear_start_addr: 0x3f80000
physical_start_addr: 0x3380000
partition_size: 0x80000
partition_name: BLINKFEED
file_name: blinkfeed.img
type: YAFFS_IMG
linear_start_addr: 0x4000000
physical_start_addr: 0x3400000
partition_size: 0x2000000
partition_name: COTA
file_name: cota.img
type: YAFFS_IMG
linear_start_addr: 0x6000000
physical_start_addr: 0x5400000
partition_size: 0x3200000
partition_name: CUSTOM
file_name: custom.img
type: YAFFS_IMG
linear_start_addr: 0x9200000
physical_start_addr: 0x8600000
partition_size: 0x3700000
partition_name: EXPDB
linear_start_addr: 0xc900000
physical_start_addr: 0xbd00000
partition_size: 0xa00000
partition_name: ANDROID
file_name: system.img
type: YAFFS_IMG
linear_start_addr: 0xd300000
physical_start_addr: 0xc700000
partition_size: 0x4ce00000
partition_name: CACHE
file_name: cache.img
type: YAFFS_IMG
linear_start_addr: 0x5a100000
physical_start_addr: 0x59500000
partition_size: 0xc800000
partition_name: USRDATA
file_name: userdata.img
type: YAFFS_IMG
linear_start_addr: 0x66900000
physical_start_addr: 0x65d00000
partition_size: 0x78000000
partition_name: BMTPOOL
linear_start_addr: 0xFFFF00a8
physical_start_addr: 0xffff00a8
partition_size: 0x1500000
So, if I missed something, tell me and of course, any idea is welcome !
Jybz

Well !
Even if the scatter file says it is a "yaffs", I'm not sure.
Anyway, I split the file with a hexeditor, the first 0x403F byte in a first file, and the rest in another.
The resulting rest-file is managable by simg2img !
And mountable by mount -t ext4 -o loop ./rest.img /path/tmp !
Thank you my self.
I'm not done, I've to see if merging this files after modifying the second is working with the phone.
cya

Well well.
Spliting the file in two, simg2img the second part ( [ ^ - 0x403F ] & [ 0x4040 - $ ] ), mounting it, modifying it, u-mounting it, img2simg the modified second part, concatenate the both part, generates a mistake for flashing !
I fell on a error "BROM ERROR : S_SECURITY_SECURE_USB_DL_IMAGE_NOT_FOUND (6048), MSP ERROE CODE : 0x00." right after downloading the DL-agent (I guess).
After that, the phone boot loop if I don't reflash a non-modified (by myself) ROM. (Need to be unplug and plug again).
By the way, for my flash operation, it works well without sdcard, without simcard, without battery, and without touch combination. I often get a "1013 error", in that case, I just retry to flash by restarting the process again, and again, and again without disconnecting the phone, until it accepts to download the DL_Agent. Sometime it takes up to 10 tries (? try-plural).
Is it related to a S-ON/S-OFF phone ? Or to a locked/unlocked bootloader ? I don't really get it, refer to this page : www.droidwiki.org/wiki/Liste_der_Möglichkeiten_mit_S-OFF/UNLOCKED#Berechtigungen my bootloader should be "unlocked" because anyway I can flash/reflash ROMs, on partitions boot, system, ...
The recovery (turning on the phone with Vol+ pressed) of one rom looks like :
(sometime (like after the Factory Mode) the BOOTMODE=4... I've no idea what that mean.)
Code:
Android system recovery <3e>
1.00.401.3
HACK=1 BOOTMODE=1 20100101 00:00:09
Volume up/down move highlight;
enter button to select.
reboot system now
apply update from ADB
apply update from sdcard
apply update from cache
wipe data/factory reset
wipe cache partition
backup user data
restore user data
I will reflash after work the second ROM to show the recovery page.
The page "version" of the Factory Mode (turing on the phone with the Vol- pressed)(for hardware test) looks like :
Code:
Version
Batt Volt : 4.057 V
BB Chip : MT6582
MS Board. : htc_v01_u
IMEI : LOOOOL
Modem Ver. :
MOLY.WR8.W1315.MD.WG.MP.V4
Bar code :
701499364CB
Build Time : Thu Nov 27 19:24
Kernel Ver. :
3.4.67 ([email protected]
SMP PREEMPT Thu Nov 27 19:
Android Ver.: 4.4.2
SW Ver. : ALPS.KK1.MP1.V2.
Custom Build Verno.: 1.00.401
Ok... After the Factory Mode (and after a Vol+ & Vol- try to turn on), the recovery page changed :
Code:
Android system recovery <3e>
1.00.401.3
HACK=1 BOOTMODE=4 20130101 01:50:31
Volume up/down move highlight;
enter button to select.
reboot system now
apply update from ADB
apply update from sdcard
apply update from cache
wipe data/factory reset
wipe cache partition
backup user data
restore user data
Weird phone :'D
The "Vol+ + Vol-" try make the screen blink, and doesn't start. Is it a "fastboot mode" ??

So, I reflashed it with the second ROM I have, I don't know where it is from.
The previous one is "the famous" "by jamesjerss", which is also the same named "arabic version", or "TESTED_WORKING", or again "ROM 4.2.2" (not sure for that name, I deleted them, because the MD5 and SHA1 sums were exactly the same for boot.img, system.img etc.
That one is not the same, it is called "0PF1IMG_V01_U_K44_SENSE53_htc_europe_1.00.401.6_Radio_MOLY.WR8.W1315.MD.WG.MP.V42.F4_release", I don't know the particularity on this one, I don't know where it is from, Radio Moly ??
So, I could flash it and the first go on recovery mode shows :
Code:
Android system recovery <3e>
1.00.401.6
HACK=1 BOOTMODE=0 20130101 02:37:52
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
apply update from sdcard
apply update from cache
wipe data/factory reset
wipe cache partition
backup user data
restore user data
The "version" page of the "Factory Mode" shows :
Code:
Version
Batt Volt : 3.855 V
BB Chip : MT6582
MS Board. : htc_v01_u
IMEI : LOOOL
Modem Ver. :
MOLY.WR8.W1315.MD.WG.MP.V4
Bar code :
701299364CB
Build Time : Tue Jan 6 13:12
Kernel Ver. :
3.4.67 ([email protected]
SMP PREEMPT Tue Jan 6 13:0
Android Ver.: 4.4.2
SW Ver. : ALPS.KK1.MP1.V2.
Custom Build Verno.: 1.00.401.
Clearly, I can flash some, but why not what ever I want?
After the Version page, reentering in the recovery, the date changed :
Code:
Android system recovery <3e>
1.00.401.6
HACK=1 BOOTMODE=4 20180706 08:27:01
[...]

Well well well...
I can't loose my time anymore. HTCdev website can't help me to unlock bootloader / S-Off the phone (their app is too buggy/not working). I won't loose my time to try to crack the certificate key.
I'm quite disappointed about xda, I thought people here were competent, but with zero response, I've a big doubt about it...
Last advice : Don't buy a HTC, as saw, it is a ****, rootable only with bad apps. BTW, Kingoroot tried to connect to the DoDs/NSA, you can block it with AFWall+, findable on F-Droid. A firewall on a android device is a MUST.
Bye all, see you in many years.

Better Mobile App

welcome