Database Develop

OpenVNP certificate issue ?

Hi guys !
I've been reading the thread about the OpenVPN working on Kaiser, tried it out and got stuck cause of the certificate verification.
Config file that works on my laptop for some time now:
tls-client
dev tun
remote XXX.XXX.XXX.XXX
float
resolv-retry infinite
port 1194
keepalive 10 60
ping-timer-rem
persist-tun
persist-key
ca ca.crt
cert my-laptop.crt
key my-laptop.key
pull
verb 4
Here's part of the log error that I get from Kaiser:
Tue Feb 05 17:49:09 2008 us=33000 OpenVPN 2.1_rc2e Win32-MSVC++ [SSL] [LZO2] built on Apr 1 2007
Tue Feb 05 17:49:09 2008 us=73000 MANAGEMENT: TCP Socket listening on 127.0.0.1:10000
Tue Feb 05 17:49:09 2008 us=74000 Need hold release from management interface, waiting...
Tue Feb 05 17:49:09 2008 us=234000 MANAGEMENT: Client connected from 127.0.0.1:10000
Tue Feb 05 17:49:09 2008 us=275000 Using Windows Connection Manager...
Tue Feb 05 17:49:09 2008 us=276000 Fetching Windows Connection Manager GUID for hostname '213.147.119.146'
Tue Feb 05 17:49:09 2008 us=278000 Formatting Windows Connection Manager GUID...
Tue Feb 05 17:49:09 2008 us=279000 Using Windows Connection Manager with destination 'auto' resolving to provider guid
Tue Feb 05 17:49:09 2008 us=366000 Acquisition of Windows Connection Manager provider succeeded...
Tue Feb 05 17:49:09 2008 us=368000 WARNING: No server certificate verification method has been enabled.
Tue Feb 05 17:49:09 2008 us=393000 MANAGEMENT: Client disconnected
Tue Feb 05 17:49:09 2008 us=396000 Cannot load certificate file my-laptop.crt: error:02001002:system library:fopen:No such file or directory: error:20074002:BIO routines:FILE_CTRL:system lib: error:140AD002:SSL routines:SSL_CTX_use_certificate_file:system lib
Tue Feb 05 17:49:09 2008 us=397000 Exiting
I tried changing the path of the certificates as mentioned in other thread and still no luck:
ca "\\Program Files\\OpenVPN\\ca.crt"
cert "\\Program Files\\OpenVPN\\my-laptop.crt"
key "\\Program Files\\OpenVPN\\my-laptop.key"
Is it possible that certificates somehow get corrupted while transfering thru activesync?
Any ideas?
Thanks,
T.

Bumping the post
Anyone ppl?

SOLVED !
Aaaaaaaaaaa.... It was the path in the end !!!
ca "\\Program Files\\OpenVPN\\config\\ca.crt"
cert "\\Program Files\\OpenVPN\\config\\my-laptop.crt"
key "\\Program Files\\OpenVPN\\config\\my-laptop.key"
Spent so much time and it turned out to be so obvious
Anyway, hope this will help others not to feel stupid as I do right now
T.

I "pseudo bricked" my device.

Never thought I'd actually be asking for help here...
ANYWAYS, I believe I have, so to speak, clayed my device. First off, I ran the 3.0.5 doctor in CMD.
Code:
Aug 11, 2012 5:24:47 AM com.palm.nova.installer.recoverytool.CardController logP
rint
INFO: SaveLogsBeforeFlash: WARNING:: Issue with saving logs
Aug 11, 2012 5:24:47 AM com.palm.nova.installer.recoverytool.CardController logP
rint
INFO: SaveLogsBeforeFlash: Done with SaveLog stage
Aug 11, 2012 5:24:47 AM com.palm.nova.installer.core.MountUtils umountPart
INFO: Unmounting /dev/mapper/store-media
Aug 11, 2012 5:24:47 AM com.palm.nova.installer.core.MountUtils umountPart
INFO: MountUtils: unmount successful
Aug 11, 2012 5:24:48 AM com.palm.nova.installer.core.MountUtils umountPart
INFO: Unmounting /dev/mapper/store-log
Aug 11, 2012 5:24:48 AM com.palm.nova.installer.core.MountUtils umountPart
WARNING: MountUtils: unmount failed, retrying in 1 second
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.MountUtils umountPart
SEVERE: MountUtils: unmount failed: umount: can't umount /dev/mapper/store-log:
No such file or directory
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.recoverytool.CardController post
FlashEvent
WARNING: Flash Failure
err -1 "unmount failed"
at com.palm.nova.installer.core.MountUtils.umountPart(MountUtils.java:32
0)
at com.palm.nova.installer.core.MountUtils.umount(MountUtils.java:335)
at com.palm.nova.installer.core.stages.SaveLogsBeforeFlashStage.run(Save
LogsBeforeFlashStage.java:71)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:333
)
at java.lang.Thread.run(Unknown Source)
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.recoverytool.CardController post
FlashEvent
INFO: Flash End time (Fail) 1344680689553
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: from C:\Users\qmarchi\AppData\Local\Temp\PalmWebOsRecoveryToolLog0.log.2
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: to C:\Users\qmarchi\AppData\Local\Temp\palmInstallerError0.log
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: from C:\Users\qmarchi\AppData\Local\Temp\PalmWebOsRecoveryToolLog0.log.0.l
ck
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: to C:\Users\qmarchi\AppData\Local\Temp\palmInstallerError1.log
java.io.IOException: The process cannot access the file because another process
has locked a portion of the file
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at com.palm.nova.installer.core.RdxUtils.saveLogs(RdxUtils.java:219)
at com.palm.nova.installer.recoverytool.CardController.saveLogs(CardCont
roller.java:166)
at com.palm.nova.installer.recoverytool.CardController.handleFailCase(Ca
rdController.java:686)
at com.palm.nova.installer.recoverytool.CardController.postFlashEvent(Ca
rdController.java:860)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:675
)
at java.lang.Thread.run(Unknown Source)
Aug 11, 2012 5:24:51 AM com.palm.nova.installer.recoverytool.CardController hand
leFailCase
INFO: something failed, query to see if device is plugged in
Aug 11, 2012 5:24:51 AM com.palm.nova.installer.recoverytool.CardController hand
leFailCase
INFO: exiting handleFailCase()
err -1 "unmount failed"
at com.palm.nova.installer.core.MountUtils.umountPart(MountUtils.java:32
0)
at com.palm.nova.installer.core.MountUtils.umount(MountUtils.java:335)
at com.palm.nova.installer.core.stages.SaveLogsBeforeFlashStage.run(Save
LogsBeforeFlashStage.java:71)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:333
)
at java.lang.Thread.run(Unknown Source)
Aug 11, 2012 5:24:52 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscov
eryRunner$DeviceDiscoveryThread run
INFO: got controller
Aug 11, 2012 5:24:52 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscov
eryRunner$DeviceDiscoveryThread run
INFO: got devices 1
Aug 11, 2012 5:24:52 AM com.palm.nova.installer.recoverytool.CardController runn
erFinished
INFO: device runner done
Aug 11, 2012 5:24:52 AM com.palm.nova.installer.recoverytool.CardController runn
erFinished
WARNING: flashing failed, move to failed card
The first thing that tipped me off is that it could not unmount... Now that's strange.
Second of all, it could not open the log due to a pre existing log....
I have reformatted the TP with all of the correct partitions.....
Novatermed and set them active.
You name it I bet you a cookie I've tried it.
Now is there anyone who thinks they have an "out-of-the-box" solution, who could help me?

qmarchi said:
Never thought I'd actually be asking for help here...
ANYWAYS, I believe I have, so to speak, clayed my device. First off, I ran the 3.0.5 doctor in CMD.
Code:
Aug 11, 2012 5:24:47 AM com.palm.nova.installer.recoverytool.CardController logP
rint
INFO: SaveLogsBeforeFlash: WARNING:: Issue with saving logs
Aug 11, 2012 5:24:47 AM com.palm.nova.installer.recoverytool.CardController logP
rint
INFO: SaveLogsBeforeFlash: Done with SaveLog stage
Aug 11, 2012 5:24:47 AM com.palm.nova.installer.core.MountUtils umountPart
INFO: Unmounting /dev/mapper/store-media
Aug 11, 2012 5:24:47 AM com.palm.nova.installer.core.MountUtils umountPart
INFO: MountUtils: unmount successful
Aug 11, 2012 5:24:48 AM com.palm.nova.installer.core.MountUtils umountPart
INFO: Unmounting /dev/mapper/store-log
Aug 11, 2012 5:24:48 AM com.palm.nova.installer.core.MountUtils umountPart
WARNING: MountUtils: unmount failed, retrying in 1 second
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.MountUtils umountPart
SEVERE: MountUtils: unmount failed: umount: can't umount /dev/mapper/store-log:
No such file or directory
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.recoverytool.CardController post
FlashEvent
WARNING: Flash Failure
err -1 "unmount failed"
at com.palm.nova.installer.core.MountUtils.umountPart(MountUtils.java:32
0)
at com.palm.nova.installer.core.MountUtils.umount(MountUtils.java:335)
at com.palm.nova.installer.core.stages.SaveLogsBeforeFlashStage.run(Save
LogsBeforeFlashStage.java:71)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:333
)
at java.lang.Thread.run(Unknown Source)
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.recoverytool.CardController post
FlashEvent
INFO: Flash End time (Fail) 1344680689553
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: from C:\Users\qmarchi\AppData\Local\Temp\PalmWebOsRecoveryToolLog0.log.2
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: to C:\Users\qmarchi\AppData\Local\Temp\palmInstallerError0.log
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: from C:\Users\qmarchi\AppData\Local\Temp\PalmWebOsRecoveryToolLog0.log.0.l
ck
Aug 11, 2012 5:24:49 AM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: to C:\Users\qmarchi\AppData\Local\Temp\palmInstallerError1.log
java.io.IOException: The process cannot access the file because another process
has locked a portion of the file
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at com.palm.nova.installer.core.RdxUtils.saveLogs(RdxUtils.java:219)
at com.palm.nova.installer.recoverytool.CardController.saveLogs(CardCont
roller.java:166)
at com.palm.nova.installer.recoverytool.CardController.handleFailCase(Ca
rdController.java:686)
at com.palm.nova.installer.recoverytool.CardController.postFlashEvent(Ca
rdController.java:860)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:675
)
at java.lang.Thread.run(Unknown Source)
Aug 11, 2012 5:24:51 AM com.palm.nova.installer.recoverytool.CardController hand
leFailCase
INFO: something failed, query to see if device is plugged in
Aug 11, 2012 5:24:51 AM com.palm.nova.installer.recoverytool.CardController hand
leFailCase
INFO: exiting handleFailCase()
err -1 "unmount failed"
at com.palm.nova.installer.core.MountUtils.umountPart(MountUtils.java:32
0)
at com.palm.nova.installer.core.MountUtils.umount(MountUtils.java:335)
at com.palm.nova.installer.core.stages.SaveLogsBeforeFlashStage.run(Save
LogsBeforeFlashStage.java:71)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:333
)
at java.lang.Thread.run(Unknown Source)
Aug 11, 2012 5:24:52 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscov
eryRunner$DeviceDiscoveryThread run
INFO: got controller
Aug 11, 2012 5:24:52 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscov
eryRunner$DeviceDiscoveryThread run
INFO: got devices 1
Aug 11, 2012 5:24:52 AM com.palm.nova.installer.recoverytool.CardController runn
erFinished
INFO: device runner done
Aug 11, 2012 5:24:52 AM com.palm.nova.installer.recoverytool.CardController runn
erFinished
WARNING: flashing failed, move to failed card
The first thing that tipped me off is that it could not unmount... Now that's strange.
Second of all, it could not open the log due to a pre existing log....
I have reformatted the TP with all of the correct partitions.....
Novatermed and set them active.
You name it I bet you a cookie I've tried it.
Now is there anyone who thinks they have an "out-of-the-box" solution, who could help me?
Click to expand...
Click to collapse
I'm not sure if this is right or not, but I remember reading something similar to what happened to you. The solution was to doctor to 3.0.0. Once you do that you can go to 3.0.5 normally.
The reason you first have to use 3.0.0 is because it's the only one that can format or partition or something like that. Go to WebOS Nation Forums and search for doctor 3.0.0. I hope this helps. Good luck.

This is true
Sent from my SGH-I897 using xda premium

THIS THREAD HERE walks you through the partition-making and formatting you need for WebOS Doctor 3.0.0 (the factory reset guide).

CWM for RAZR i

Well, after figuring out the image format for boot and recovery, I built a CWM image for the RAZR i. I had to fix and hack around quite a bit of code to have it building (arm is hardcoded on several places ), and it's completely untested as I don't own the device, so try at your own risk
Download: https://dl.dropbox.com/u/553461/recovery-razri.img
If it works I'll talk with koush and see how we can get all this broken code fixed to support x86 devices
After a session of remote debugging with @mattlgroff's phone, here's the first usable razr i recovery image!
Download https://dl.dropbox.com/u/553461/recovery-razri-try4.img
There's still a couple of bugs to kill on it (like keys being a little.. slow to generate events) but it's usable and mattlgroff was able to nandroid his phone with it.
After more debugging with @mattlgroff's phone today, touch works now, and I have implemented a workaround for the screen refresh issue.
Download: https://dl.dropbox.com/u/553461/recovery-razri-tryAtouch.img
You can use both touch and buttons on it. Power button selects the highlighted option, camera button goes back, vol+/- highlight the next/previous option. The recovery should be "4.2-ready".
I appreciate all the donations I have received lately. As you probably noticed already, I have recently been working on the RAZR i but I don't own the phone. If I receive enough donations to be able to afford it, I plan to purchase one to port CM to and do my own testing

turl1 said:
Well, after figuring out the image format for boot and recovery, I built a CWM image for the RAZR i. I had to fix and hack around quite a bit of code to have it building (arm is hardcoded on several places ), and it's completely untested as I don't own the device, so try at your own risk
Download: https://dl.dropbox.com/u/553461/recovery-razri.img
If it works I'll talk with koush and see how we can get all this broken code fixed to support x86 devices
Click to expand...
Click to collapse
Just to know, if I test it and doesn't works what can occurs to my device? I'll have a way to back to stock recovery?

ReeSilva said:
Just to know, if I test it and doesn't works what can occurs to my device? I'll have a way to back to stock recovery?
Click to expand...
Click to collapse
Fast boot stock recovery back...
And I tested, boots to a black screen.
Sent from my XT890 using Tapatalk 2

mattlgroff said:
Fast boot stock recovery back...
And I tested, boots to a black screen.
Sent from my XT890 using Tapatalk 2
Click to expand...
Click to collapse
So I won't test, but, thanks for the tip

Can you use ADB while the screen is black?

turl1 said:
Can you use ADB while the screen is black?
Click to expand...
Click to collapse
I will try that now. Will edit in results
EDIT: No dice

mattlgroff said:
I will try that now. Will edit in results
EDIT: No dice
Click to expand...
Click to collapse
Can you try on another OS just to be sure? Windows and its silly need to install drivers for all the things can cause an issue or two

turl1 said:
Can you try on another OS just to be sure? Windows and its silly need to install drivers for all the things can cause an issue or two
Click to expand...
Click to collapse
Yeah silly Winblows.
Code:
[email protected]:~$ adb devices
List of devices attached
TA23700S5B device
[email protected]:~$ adb wait-for-device reboot recovery
[email protected]:~$ adb wait-for-device devices
^C
[email protected]:~$ adb devices
List of devices attached
TA23700S5B recovery
[email protected]:~$ adb shell
~ # ls
boot etc sd-ext
cache init sdcard
data init.rc sys
datadata proc system
default.prop res tmp
dev root ueventd.goldfish.rc
emmc sbin ueventd.rc
~ # cat default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=cm_smi-userdebug 4.1.2 JZO54K eng.root.20121105.023150 test-keys
ro.build.version.incremental=eng.root.20121105.023150
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Mon Nov 5 02:32:23 UTC 2012
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=root
ro.build.host=laptop
ro.build.tags=test-keys
ro.product.model=cm_smi
ro.product.brand=generic_x86
ro.product.name=cm_smi
ro.product.device=smi
ro.product.board=smi
ro.product.cpu.abi=x86
ro.product.manufacturer=Motorola
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=smi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=cm_smi-userdebug 4.1.2 JZO54K eng.root.20121105.023150 test-keys
ro.build.fingerprint=generic_x86/cm_smi/smi:4.1.2/JZO54K/eng.root.20121105.023150:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=smi
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10-20121105-UNOFFICIAL-smi
ro.modversion=10-20121105-UNOFFICIAL-smi
ro.config.ringtone=CyanTone.ogg
ro.config.notification_sound=CyanMessage.ogg
ro.config.alarm_alert=CyanAlarm.ogg
ro.carrier=unknown
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
~ #
Code:
[email protected]:~$ adb reboot recovery
[email protected]:~$ adb logcat
- waiting for device -
^C
[email protected]:~$ adb logcat
/sbin/sh: exec: line 1: logcat: not found
[email protected]:~$ adb shell
~ # logcat
/sbin/sh: logcat: not found
~ # cd system
/system # ls
bin
/system # cd bin
/system/bin # ls
/system/bin #
^^^
Looks like there isn't a way for me to log errors.. at least from what I see.

Recovery logs errors on /tmp, it should be /tmp/recovery.log

turl1 said:
Recovery logs errors on /tmp, it should be /tmp/recovery.log
Click to expand...
Click to collapse
Here you are
http://pastebin.com/XuwkAjQH

thats really impressive...
and helpful

Well, judging by the output it looks like it's crashing over and over. I'll see if I can get CWM running on a virtual machine and debug further that way.

I built a new one, give it a try and let me know if there's any progress
https://dl.dropbox.com/u/553461/recovery-razri-try2.img
If it doesn't work, /tmp/recovery.log will be appreciated

turl1 said:
I built a new one, give it a try and let me know if there's any progress
https://dl.dropbox.com/u/553461/recovery-razri-try2.img
If it doesn't work, /tmp/recovery.log will be appreciated
Click to expand...
Click to collapse
Still going to a black screen. How can I extract the log?

ReeSilva said:
Still going to a black screen. How can I extract the log?
Click to expand...
Click to collapse
My previous post shows the adb commands I used. I am trying it now...
http://pastebin.com/GyQtUn8q
Same issue

mattlgroff said:
My previous post shows the adb commands I used. I am trying it now...
http://pastebin.com/GyQtUn8q
Same issue
Click to expand...
Click to collapse
Man, that command that u send early doesn't work. There is another command to back to stock recovery?

ReeSilva said:
Man, that command that u send early doesn't work. There is another command to back to stock recovery?
Click to expand...
Click to collapse
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery recovery_signed
Code:
fastboot flash recovery razr_i_recovery.img
I don't know what your filename is for your stock recovery, but I will show example below.
Code:
fastboot flash recovery example

Well, just in case, there's my log.
Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
/tmp # cat recovery.log
Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
Starting recovery on Tue Nov 6 04:25:17 2012
Starting recovery on Tue Nov 6 04:25:22 2012
Starting recovery on Tue Nov 6 04:25:27 2012
Starting recovery on Tue Nov 6 04:25:32 2012
/tmp # cat recovery.log
Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
Starting recovery on Tue Nov 6 04:25:17 2012
Starting recovery on Tue Nov 6 04:25:22 2012
Starting recovery on Tue Nov 6 04:25:27 2012
Starting recovery on Tue Nov 6 04:25:32 2012
/tmp # cat recovery.log
Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
Starting recovery on Tue Nov 6 04:25:17 2012
Starting recovery on Tue Nov 6 04:25:22 2012
Starting recovery on Tue Nov 6 04:25:27 2012
Starting recovery on Tue Nov 6 04:25:32 2012
Starting recovery on Tue Nov 6 04:25:37 2012
/tmp # cat recovery.log
Starting recovery on Tue Nov 6 04:24:51 2012
Starting recovery on Tue Nov 6 04:24:57 2012
Starting recovery on Tue Nov 6 04:25:02 2012
Starting recovery on Tue Nov 6 04:25:07 2012
Starting recovery on Tue Nov 6 04:25:12 2012
Starting recovery on Tue Nov 6 04:25:17 2012
Starting recovery on Tue Nov 6 04:25:22 2012
Starting recovery on Tue Nov 6 04:25:27 2012
Starting recovery on Tue Nov 6 04:25:32 2012
Starting recovery on Tue Nov 6 04:25:37 2012
Starting recovery on Tue Nov 6 04:25:42 2012
---------- Post added at 02:29 AM ---------- Previous post was at 02:27 AM ----------
mattlgroff said:
Code:
fastboot flash recovery recovery.img
Code:
fastboot flash recovery recovery_signed
Code:
fastboot flash recovery razr_i_recovery.img
I don't know what your filename is for your stock recovery, but I will show example below.
Code:
fastboot flash recovery example
Click to expand...
Click to collapse
Can u send to me the stock recovery img?

ReeSilva said:
Can u send to me the stock recovery img?
Click to expand...
Click to collapse
Stock Recovery.

mattlgroff said:
Stock Recovery.
Click to expand...
Click to collapse
Thank u, man

USB File Transfer - "not an MTP device"

After personalizing my Z3 Play, I put in my SD card and went to transfer my media back to it.
When I changed the USB mode to File Transfer, I got no usual notification in KDE.
Watching the linux log, I saw:
Code:
Oct 05 21:24:46 computername kernel: usb 2-4: new high-speed USB device number 33 using xhci_hcd
Oct 05 21:24:46 computername kernel: usb 2-4: New USB device found, idVendor=05c6, idProduct=9092, bcdDevice= 4.04
Oct 05 21:24:46 computername kernel: usb 2-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct 05 21:24:46 computername kernel: usb 2-4: Product: Moto Z3 Play
Oct 05 21:24:46 computername kernel: usb 2-4: Manufacturer: motorola
Oct 05 21:24:46 computername kernel: usb 2-4: SerialNumber: <sanitized>
Oct 05 21:24:46 computername mtp-probe[1845138]: checking bus 2, device 33: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4"
Oct 05 21:24:46 computername mtp-probe[1845138]: bus: 2, device: 33 was not an MTP device
Oct 05 21:24:46 computername mtp-probe[1845152]: checking bus 2, device 33: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-4"
Oct 05 21:24:46 computername mtp-probe[1845152]: bus: 2, device: 33 was not an MTP device
And that would be the same similar response to selecting PTP or MIDI (which gives some pulseaudio log stuff).
If I select "USB tethering", it DOES come up with a notification, but it's more like a false-positive.
There is no mention of the mtp-probe, but rather:
Code:
Oct 05 21:31:12 computername kernel: rndis_host 2-4:1.0 usb0: register 'rndis_host' at usb-0000:00:14.0-4, RNDIS device, <sanitized>
and other related stuff.
There was mention of "kf5.kiod.kmtpd: LIBMTP_Open_Raw_Device_Uncached: Could not open MTP device".
This is all after I did a factory reset.
I'll also state that I did unlock the bootloader and sideload Magisk via "fastboot boot" for TWRP.
I've seen topics about this suggesting things like fiddling with the ADB setting in Developer mode, but nothing I've read has resulted in any change.
I was really hoping maybe I messed up with changing permissions, but figured the factory reset would put everything back in place. Nope.
Also, I have no idea if the file transfer mode EVER worked on this device, since I only tried it now after upgrading to pie and patching the boot image with Magisk.
Is anyone with this device able to use the File Transfer mode, and if so, did you also modify things like patching boot with Magisk?
I wouldn't think the two would be related.
EDIT0:
I thought I might add the following as well since it is different, but also maybe not related
Code:
05c6:9092 Qualcomm, Inc. Moto Z3 Play
That is what it is now after patching the boot image with Magisk.
The VID used to be 22b8 and I think the PID maybe something like 2e81.
I set the rules in /etc/udev for like 6 different combinations I had seen through my various tests.
EDIT1:
Hmm, looks like the Magisk/VID could very well have been the issue.
I changed to slot b (instead of a), booted that up and right away no problems with File Transfer.
I'll have to look at it more closely. I may just see what happens if I flash the stock boot image back to slot a.
EDIT2:
So the takeaway for anyone else, don't try to be adventurous and deviate from https://topjohnwu.github.io/Magisk/install.html
I had originally sideloaded magisk and I guess somewhere in all of that, things went a little (not completely) awry.
The VIDID are back to normal and MTP is working right, AND I have magisk installed the way I was originally supposed to.

How To Guide How to compile the OmniROM 13 for the Android Zenfone 8

Compiling the CustomROM OmniROM 13 from within Linux is again a very simple and straight forward process -- the developer for the OmniROM did once again a really amazing good job setting up the build environment for the OmniROM 13.
Notes:
As of 22.01.2023 there is an additional repository required for compiling OmniROM 13 -- see below for details. I also added some more details at the end of this post.
This HowTo is about how to compile the OmniROM 13 for the ASUS Zenfone 8 -- see How to compile the OmniROM for the ASUS Zenfone 8 for how to compile the OmniROM 12 for the ASUS Zenfone 8.
Most (but not all) of the necessarry steps to sync the repositories are described in the section "Getting Started" here: https://github.com/omnirom/https://github.com/omnirom/android.
Prerequisites
Some of the repositories for OmniROM 13 are on https://gitlab.com and the access to these repositories for the repository sync is done via ssh. Therefor to sync these repositories a user account on gitlab.com with configured public ssh key is required. The user account on gitlab.com is free of charge and the public ssh key can be uploaded into the user profile on gitlab.com (see here: https://docs.gitlab.com/ee/user/ssh.html)
The repositories on github.com are currently accessed via https but that might change in the future. Therefor it's recommended to create a user on https://github.com and add the ssh public key to the profile of that user also.
Note:
To check how the access to the repositories is configured use this command:
Code:
[email protected] /data/develop/android/OmniROM_13.0/.repo]$ grep fetch $( find . -name "*xml" )
./local_manifests/local_manifest.xml: fetch="https://github.com/DonkeyCoyote" />
./manifests/omni-aosp.xml: fetch="https://github.com/" />
./manifests/omni-aosp.xml: fetch="ssh://[email protected]/omnirom" />
./manifests/omni-aosp.xml: fetch="https://github.com/omnirom"
./manifests/omni-caf.xml: fetch="https://github.com/" />
./manifests/omni-caf.xml: fetch="https://github.com/omnirom"
./manifests/omni-caf.xml: fetch="https://git.codelinaro.org/clo/la"
./manifests/omni-private.xml: fetch="ssh://[email protected]/omnirom"
./manifests/default.xml: fetch="https://android.googlesource.com"
[[email protected] /data/develop/android/OmniROM_13.0/.repo]$
The tool repo is required to maintain the repositories for the OmniROM 13; you can download the tool "repo" from https://gerrit.googlesource.com/git-repo
It's not necessary to install additional tools for creating an OmniROM image -- all necessary tools to create the image are in the repositories for the OmniROM 13.
Creating the local copies of the repositories for the OmniROM 13
To create a local copy of the repositories for OmniROM 13 these steps are required:
First create a new directory for the repositories and change the working directory to the new directory, e.g.:
Bash:
mkdir /data/develop/android/OmniROM_13.0
cd /data/develop/android/OmniROM_13.0
Init the local repositories using the command:
Bash:
repo init -u https://github.com/omnirom/android.git -b android-13.0
Note that the command repo init only creates a hidden directory called .repo.
Next do the initial sync of the repositories using the command:
Bash:
repo sync
Be aware that the repositories need about 160 GB disk space so this will take a while.
The initial repository sync will download all repositories necessary to create the OmniROM image except the hardware dependent repositories (these repos are different for the various phone models).
Therefor you must add the repositories for the vendor and device tree for your phone to the manifests in the local repositories after the download finished.
This should be done in the file .repo/local_manifests/local_manifest.xml (if the directory .repo/local_manifests does not exist create it).
For the ASUS Zenfone 8 the file should look like this:
Code:
[[email protected] /data/develop/android/OmniROM_13.0]$ cat .repo/local_manifests/local_manifest.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="DonkeyCoyote"
fetch="https://github.com/DonkeyCoyote" />
<project path="device/asus/zenfone8" name="android_device_asus_zenfone8" remote="omnirom" revision="android-13.0" />
<project path="vendor/asus" name="proprietary_vendor_asus" remote="DonkeyCoyote" revision="android-13.0" />
<project path="vendor/microg" name="android_prebuilts_prebuiltapks" remote="omnirom" revision="android-13.0" />
<project path="vendor/images/asus" name="android_vendor_images_asus" remote="gitlab" revision="android-13.0" />
</manifest>
[[email protected] /data/develop/android/OmniROM_13.0]$
Note:
The repository android_prebuilts_prbuiltapks is only necessary for OmniROM images that should include the MicroG packages.
Update 22.01.2023
The repository android_vendor_images_asus is now also required; currently this repository only contains the ASUS Galery.
After updating the file local_manifest.xml do another
Bash:
repo sync
to sync the added repositories. This time the download will be faster because only the two (or three) additional repos will be downloaded.
Now you can start the build with these commands:
Bash:
# optional:
#
# to create an OmniROM image with MicroG packages set the environment variable ROM_BUILDTYPE to MICROG before starting the build
#
# to create an OmniROM image with GAPPS packages set the environment variable ROM_BUILDTYPE to GAPPS before starting the build
# (that will only work if the repositories for the GAPPS are configured, of course)
#
export ROM_BUILDTYPE=MICROG
. build/envsetup.sh
brunch omni_zenfone8-user
in the directory with the downloaded repositories (use the command "breakfast" instead of "brunch" to see other possible targets)
Note that the first time the compile process will take 4 hours or more. And keep in mind that the compile process will need additional 140 GB for the temporary output files.
If everything is fine there will be a ZIP file with your own CustomROM image in the directory ./out/target/product/zenfone8/ when the compile script is done, e.g. for images with MicroG packages:
Code:
[[email protected] /data/develop/android/OmniROM_13.0]
[[email protected] /data/develop/android/OmniROM_13.0]$ ls -l out/target/product/zenfone8/omni-13-2022*-zenfone8-*.zip
-rw-rw-r--. 3 xtrnaw7 xtrnaw7 1258920226 Nov 14 11:55 out/target/product/zenfone8/omni-13-202211141148-zenfone8-MICROG.zip
[[email protected] /data/develop/android/OmniROM_13.0]$
[[email protected] /data/develop/android/OmniROM_13.0]$
The image can now be installed on the ASUS Zenfone 8 using the LineageOS Recovery or TWRP.
Notes
Be aware that each new ROM image created with brunch will overwrite the existing ROM images (even if the name of the image is different), e.g.
Code:
[[email protected] /data/develop/android/OmniROM_13.0]$ ls -li out/target/product/zenfone8/omni-13-2022*-zenfone8-*.zip
77928215 -rw-rw-r--. 3 xtrnaw7 xtrnaw7 1258920226 Nov 14 11:55 out/target/product/zenfone8/omni-13-202211131612-zenfone8-MICROG.zip
77928215 -rw-rw-r--. 3 xtrnaw7 xtrnaw7 1258920226 Nov 14 11:55 out/target/product/zenfone8/omni-13-202211141148-zenfone8-MICROG.zip
[[email protected] /data/develop/android/OmniROM_13.0]$
[[email protected] /data/develop/android/OmniROM_13.0]$ cksum out/target/product/zenfone8/omni-13-2022*-zenfone8-*.zip
2429251380 1258920226 out/target/product/zenfone8/omni-13-202211131612-zenfone8-MICROG.zip
2429251380 1258920226 out/target/product/zenfone8/omni-13-202211141148-zenfone8-MICROG.zip
[[email protected] /data/develop/android/OmniROM_13.0]$
Therefor you should move the zip file with the new image to a new directory before building new image
For OS images that should be used on the phone for daily use I strongly recommend to create your own certificates for the OS.
In the OmniROM development directory tree the neccessary files, platform.pk8 and platform.x509.pem, are in the directory
./build/make/target/product/security
in your build tree for the CustomROM, e.g.
Code:
[[email protected] /data/develop/android/OmniROM]$ ls -l ./build/make/target/product/security/platform.*
-rw-------. 1 xtrnaw7 xtrnaw7 1219 Jun 25 09:39 ./build/make/target/product/security/platform.pk8
-rw-rw-r--. 1 xtrnaw7 xtrnaw7 1460 Jun 25 09:39 ./build/make/target/product/security/platform.x509.pem
[[email protected] /data/develop/android/OmniROM]$
Replace these files with your own certificate files and recreate the image using the command brunch (see above).
See here https://source.android.com/devices/tech/ota/sign_builds for how to create your own certificate.
To manually create the keys use these commands:
Android uses 2048-bit RSA keys with public exponent 3. You can generate certificate/private key pairs using the openssl tool from openssl.org:
Code:
# generate RSA key
#
[[email protected] /data/develop/android/test1]$ openssl genrsa -3 -out temp.pem 2048
[[email protected] /data/develop/android/test1]$ ls -ltr
total 4
-rw-------. 1 xtrnaw7 xtrnaw7 1704 Nov 14 13:24 temp.pem
# create a certificate with the public part of the key
#
[[email protected] /data/develop/android/test1]$ openssl req -new -x509 -key temp.pem -out releasekey.x509.pem -days 10000 -subj '/C=DE/ST=Hessen/L=Frankfurt am Main/O=Android/OU=Android/CN=Android/[email protected]'
[[email protected] /data/develop/android/test1]$
[[email protected] /data/develop/android/test1]$ ls -ltr
total 8
-rw-------. 1 xtrnaw7 xtrnaw7 1704 Nov 14 13:24 temp.pem
-rw-rw-r--. 1 xtrnaw7 xtrnaw7 1456 Nov 14 13:25 releasekey.x509.pem
[[email protected] /data/develop/android/test1]$
# create a PKCS#8-formatted version of the private key
#
[[email protected] /data/develop/android/test1]$ openssl pkcs8 -in temp.pem -topk8 -outform DER -out releasekey.pk8 -nocrypt
[[email protected] /data/develop/android/test1]$
[[email protected] /data/develop/android/test1]$ ls -ltr
total 12
-rw-------. 1 xtrnaw7 xtrnaw7 1704 Nov 14 13:24 temp.pem
-rw-rw-r--. 1 xtrnaw7 xtrnaw7 1456 Nov 14 13:25 releasekey.x509.pem
-rw-------. 1 xtrnaw7 xtrnaw7 1218 Nov 14 13:25 releasekey.pk8
[[email protected] /data/develop/android/test1]$
# securely delete the temp.pem file
#
[[email protected] /data/develop/android/test1]$ shred --remove temp.pem
[[email protected] /data/develop/android/test1]$
[[email protected] /data/develop/android/test1]$ ls -ltr
total 8
-rw-rw-r--. 1 xtrnaw7 xtrnaw7 1456 Nov 14 13:25 releasekey.x509.pem
-rw-------. 1 xtrnaw7 xtrnaw7 1218 Nov 14 13:25 releasekey.pk8
[[email protected] /data/develop/android/test1]$
From the documentation:
The openssl pkcs8 command given above creates a .pk8 file with no password, suitable for use with the build system. To create a .pk8 secured with a password (which you should do for all actual release keys), replace the -nocrypt argument with -passout stdin; then openssl will encrypt the private key with a password read from standard input. No prompt is printed, so if stdin is the terminal the program will appear to hang when it's really just waiting for you to enter a password. Other values can be used for the-passout argument to read the password from other locations; for details, see the openssl documentation.
The temp.pem intermediate file contains the private key without any kind of password protection, so dispose of it thoughtfully when generating release keys. In particular, the GNUshred utility may not be effective on network or journaled filesystems. You can use a working directory located in a RAM disk (such as a tmpfs partition) when generating keys to ensure the intermediates are not inadvertently exposed.
Click to expand...
Click to collapse
Updating the local repositories [Update 22.01.23]
To update the local repositories change the working directory to the directory with the repositories for OmniROM 13 and execute
Bash:
repo sync
After the synchronization is complete, create a new operating system image using the commands described above.
It is recommended to create a new image at least once a month after the new security patches for Android are added to the repositories for OmniROM.
To view the date of the security patch in the source files for OmniROM do:
Code:
[ OmniRom 13 Dev - [email protected] /data/develop/android/OmniROM_13.0 ] $ grep "^[[:space:]]*PLATFORM_SECURITY_PATCH[[:space:]]*:=" ./build/make/core/version_defaults.mk
PLATFORM_SECURITY_PATCH := 2023-01-05
[ OmniRom 13 Dev - [email protected] /data/develop/android/OmniROM_13.0 ] $
Moving the repositories to another directory [Update 22.01.23]
In case you want to move the repositories to another directory or rename the directory with the repositories:
Be aware that the make scripts create some absolute links in the output directory; to list these absolute links use:
Spoiler: find . -type l -ls | grep " $PWD"
Code:
[ OmniRom 13 Dev - [email protected] /data/develop/android/OmniROM_13.0 ] $ find . -type l -ls | grep " $PWD"
79960553 4 lrwxrwxrwx 1 xtrnaw7 xtrnaw7 93 Dec 18 18:49 ./out/soong/.intermediates/prebuilts/build-tools/prebuilt_py3-launcher-autorun/linux_glibc_x86_64/py3-launcher-autorun -> /data/develop/android/OmniROM_13.0/prebuilts/build-tools/linux-x86/bin/py3-launcher-autorun64
79960558 4 lrwxrwxrwx 1 xtrnaw7 xtrnaw7 73 Dec 18 18:46 ./out/soong/.intermediates/prebuilts/build-tools/m4/linux_glibc_x86_64/m4 -> /data/develop/android/OmniROM_13.0/prebuilts/build-tools/linux-x86/bin/m4
78782027 0 lrwxrwxrwx 1 xtrnaw7 xtrnaw7 53 Jan 22 09:07 ./out/target/product/zenfone8/obj/DTBO_OBJ/source -> /data/develop/android/OmniROM_13.0/kernel/asus/sm8350
78931423 0 lrwxrwxrwx 1 xtrnaw7 xtrnaw7 53 Jan 22 09:07 ./out/target/product/zenfone8/obj/DTB_OBJ/source -> /data/develop/android/OmniROM_13.0/kernel/asus/sm8350
78792528 0 lrwxrwxrwx 1 xtrnaw7 xtrnaw7 53 Jan 15 11:56 ./out/target/product/zenfone8/obj/PACKAGING/kernel_modules_intermediates/lib/modules/5.4.147-Omni-qgki-perf-g3e8f0551c618/source -> /data/develop/android/OmniROM_13.0/kernel/asus/sm8350
78792529 4 lrwxrwxrwx 1 xtrnaw7 xtrnaw7 77 Jan 15 11:56 ./out/target/product/zenfone8/obj/PACKAGING/kernel_modules_intermediates/lib/modules/5.4.147-Omni-qgki-perf-g3e8f0551c618/build -> /data/develop/android/OmniROM_13.0/out/target/product/zenfone8/obj/KERNEL_OBJ
84806159 0 lrwxrwxrwx 1 xtrnaw7 xtrnaw7 53 Jan 22 09:13 ./out/target/product/zenfone8/obj/PACKAGING/kernel_modules_intermediates/lib/modules/5.4.147-Omni-qgki-perf-g875131b91949/source -> /data/develop/android/OmniROM_13.0/kernel/asus/sm8350
84806160 4 lrwxrwxrwx 1 xtrnaw7 xtrnaw7 77 Jan 21 11:25 ./out/target/product/zenfone8/obj/PACKAGING/kernel_modules_intermediates/lib/modules/5.4.147-Omni-qgki-perf-g875131b91949/build -> /data/develop/android/OmniROM_13.0/out/target/product/zenfone8/obj/KERNEL_OBJ
78788578 0 lrwxrwxrwx 1 xtrnaw7 xtrnaw7 53 Jan 22 09:10 ./out/target/product/zenfone8/obj/KERNEL_OBJ/source -> /data/develop/android/OmniROM_13.0/kernel/asus/sm8350
[ OmniRom 13 Dev - [email protected] /data/develop/android/OmniROM_13.0 ] $
Before starting another build after moving the directories with the repositories you must correct these links.