Database Develop

[Q] [solved] OpenVPN?

I am trying to get OpenVPN working but so far I have had no luck..
The tun module is now loading and the openvpn script starts and almost does the job... The problem is route and ifconfig. I have tried several versions of busybox and I am now running1.17.4, where I can run ifconfig and route from commandline and get info..
Here is the log..:
Code:
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 PUSH: Received control message: 'PUSH_REPLY,route 10.1.1.0 255.255.255.0,route 10.99.99.0 255.255.255.0,topology net30,ping 10,ping-restart 120,ifconfig 10.99.99.30 10.99.99.29'
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:1: route (2.1.1)
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:2: route (2.1.1)
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 Options error: Unrecognized option or missing parameter(s) in [PUSH-OPTIONS]:6: ifconfig (2.1.1)
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 OPTIONS IMPORT: timers and/or timeouts modified
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 OPTIONS IMPORT: --ifconfig/up options modified
D/Tethering( 2852): tun0 is not a tetherable iface, ignoring
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 TUN/TAP device tun0 opened
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 TUN/TAP TX queue length set to 100
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 Initialization Sequence Completed
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 MANAGEMENT: >STATE:1324026309,CONNECTED,SUCCESS,,x.x.x.x
V/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-mgmt( 5471): onState(">STATE:1324026309,CONNECTED,SUCCESS,,x.x.x.x")
I/StatusBarManagerService( 2852): UPDATE-client.conf: Connected , 0x7f020003
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-daemon-stdout( 5471): Fri Dec 16 10:05:09 2011 MANAGEMENT: CMD 'bytecount 3'
D/OpenVPNDaemonEnabler( 5471): Received OpenVPN network state changed from Get Config to Connected
D/OpenVPN-DaemonMonitor[/sdcard/openvpn/client.conf]-mgmt( 5471): SUCCESS: bytecount interval changed
As you see, there is some problem with the options used for route and ifconfig.. Does anyone know how to fix this? Or which version of Busybox should work?
Edit: Found the solution, just had to install the latest version if Busybox (1.19.3)
Regards,
BTJ

Hi, can I ask you where did you get the tun.ko?
Thanks
Stefano

The module was already there... Guess it came with the kernel I installed...
BTJ

Thanks,
so what kernel was it?
Stefano

Not sure... I have switch a lot since then but I think most of the custom kernels come with tun.ko, like FM and Abyss...
BTJ

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.

Question TECHNICAL POST current issues on Realme 8 Pro (RMX3081)

Attention! Everything you do, you do at your own peril and risk! Installing modified firmware, custom recovery and obtaining ROOT rights will void your warranty! Before any actions with the firmware, we MUST make a Backup!​DOWNLOAD
All about firmware
Stock firmware:
11 android
A.24-A.41 ... A.24-A.48 ... A.27-A.48 ... Paid resources: A.30-A.47 ... A.44 ... A.27-A.45
12 android
C.18
C.19
C.20 (all countries + global)
C.19-20
C.20
Drivers: 01 ... 02 ... 03 ... Universal ADB
TWRP (official site): 01 (not yet)
INSTRUCTIONS
Firmware: preparation and process
How to distinguish the global version of Realme from the Chinese: 01
Developer Mode: 01 ... 02
Enable USB Debugging: 01
Connect smartphone to computer: 01
Backup: 01 ... 02 ... 03
Firmware update: 01 ... 02 ... 03
Preparing the device for official firmware: 01
PS: At the moment
= only firmware of original ROMs is available.
= Unable to unlock bootloader, unable to flash partial partitions/blocks.
= It is also impossible to get ROOT.
= Installing an updated (modified) firmware is not possible if it is not listed as an update!
Reset to factory settings (Hard Reset): 01
GSI firmware experience: 01 (Custom ROM for Realme 8 pro)
Firmware components and possible actions with them
Realme System Apps: Complete List: 01
Removing standard applications: 01
Unlocking privacy: 01
EFS Backup: 01
Enable dark theme: 01
On top of other apps: 01
Application cloning: 01
Second Space – it is a separate desktop with individual customization, installed applications and settings: 01
Update system apps: 01
Smartphone does not turn on: 01
Reset to factory settings (Hard Reset): 01
What is IMEI: 01
NFC setup (Google Pay): 01
Why disable NFC on your smartphone: 01
Vibration off 01
Take a screenshot or screen recording: 01 ... 02
How to clear "other": 01
Enable and configure Always On Display: 01
Optimization Realme UI 2.0: 01
Increase the amount of RAM: 01
Hide all personal data: 01
Safe mode: 01
Call recording: 01
Charge your smartphone correctly: 01
Connect smartphone to TV: 01
Game Mode Realme Game Space: 01
Realme Link: 01
Realme Share: 01
FAQ from the official site: 01
POPULAR QUESTIONS
List of questions
= How to calibrate the auto-brightness of the screen.
= How to bring contacts to the home screen for quick access.
= How to make a contact photo full screen.
= How to disable all ads in Realme without Root rights.
= Which Realmi models have call recording.
= How to make separate volume control.
= How to unlock Realme if you forgot your lock screen password.
= How to turn off the rising volume on a call.
= How to calibrate the gyroscope on Realme.
= How to disable digital wellbeing.
= How to calibrate the proximity sensor.
= How to calibrate the accelerometer.
= How to expand your Wi-Fi coverage area through Realme.
= How to increase the maximum screen brightness.
= How to connect a USB flash drive via OTG.
= How to put a video on your desktop wallpaper.
= How to block calls and sms from hidden numbers.
= How to increase speaker volume on Realme.
= How to clear the application cache.
= What to do if fingerprint unlock does not work.
= How to restrict Internet access to a specific application.
= How to adapt the screen to the application.
= How to enter Safe Mode.
= How to quickly turn on silent mode.
= How to turn on ear dialing.
= How to disable fast charging.
= How to remove media files from messengers in the gallery.
= Why is the update not coming over the air.
= How to manually install the downloaded update file.
= How to make a default third-party launcher.
Answers: 01 ... 02
USER TIPS
Forum XDA
Reviews: 01
Communication
Internet distribution without ROOT: 02
Frequency aggregation on Realme: 01
Decor
Theme Store: 01 ... 02
Change curtain and interface: 01
Add/Change Font: 01 ... 02 ... 03
Other
Reset your Google account without a computer: 01
ABOUT PHONE
Official site - Russian firmware: 01
Official site - European firmware: 01
Realme Support: 01
Check smartphone for authenticity: 01
Phone information based on WIN: 01
Engineering menu without connecting to a computer: 01
How to find out your SIM card number: 01
QCN Backup/IMEI Repair/Engineering Mode/Diagnostic Mode: 01
Unique Chips: 01
How to unlock Realme phone if you forgot your password 01
Realme account: 01
Camera discussion: 01
REPAIR
Dismantling: 01 ... 02 ... 03
Buy spare parts: 01
GETTING READY FOR UI 3.0
Detailed review (15 new features of Android 12): 01 ... 02 ... 03
Realme PC Connect: 01
Positions for reference only for the future​
Extract Realme stock firmware in OZIP format: 01
Python: 01 ... 02
Ozipdecrypt Tool: 01 ... 02
Unlock the bootloader (not possible yet): 01 ... 02 ... 03 ... 04 ... 05 ... 06 ... 07 ... 08 ... 09
Installing TWRP: 01 (on Android 11, it is currently impossible to install custom recovery on official firmware) ... 02 (official TWRP - not yet)
GDPR Codes in Engineering Mode: 01
Rooting: 01 (will be possible with the advent of custom recovery) ... 02 ... 03 ... 04 ... 05 ... 06 ... 07
EDL - a special mode with which you can flash even with a locked bootloader: 01 ... 02
Hydra Tool: 01 ... 02
Magisk Manager: 01 ... 02
Download separate adb and fastboot: 01
Android Ultimate Collection & Guides by Retrial​
PS: Sincere gratitude to the respected StratOS_HTC for the great work.
(Post under the control of the author)​

Hi there, yes if you are speaking about the phones included the GDPR versions of ROM.
Realmne 8 PRO phones on GDPR roms (Proj ID 20713) even won't get the UI 3.0 unoficially.

Regarding GDPR :
It's really hard without flashing on locked bootloader.
Dev block are not acessible (no root), also fastboot is not working on locked and secured rom.
EDL auth/sign is not working ...
ISP UFS is working but hard to manage it ...
Only workable (but stock) is via MSM auth login (resseller) or production/factory credentials.
But it's payed. For reseller credential cca 4 $.
Looking forward for any1 info for production credentials for only research/download.
All other things are securely saved in parted and encrypted and not accessed super partition.
It's userspaced problem.