CWM for RAZR i - RAZR i Android Development

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

Related

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.

[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).

[Q] dead touchpad... again!

Hi, I have my TP for over a year now.. but it wasn't an easy year tbh. Had it in repair in August, that took nearly 2 months by the way, however what service did was replacing the battery, as my TP was dead. Now when i get it back from repaired, after 2 months TP get stuck on HP logo screen and wont boot at all. I've read on forums to try webos doctor as it should recover my TP to point of origiin. Sadly im getting stuck at 72% with WARNING: flashing failed, move to failed card... any1 know what does this mean ? and if its again a must go to repair....
any help appreciated
Thanks
DarkLoola said:
Hi, I have my TP for over a year now.. but it wasn't an easy year tbh. Had it in repair in August, that took nearly 2 months by the way, however what service did was replacing the battery, as my TP was dead. Now when i get it back from repaired, after 2 months TP get stuck on HP logo screen and wont boot at all. I've read on forums to try webos doctor as it should recover my TP to point of origiin. Sadly im getting stuck at 72% with WARNING: flashing failed, move to failed card... any1 know what does this mean ? and if its again a must go to repair....
any help appreciated
Thanks
Click to expand...
Click to collapse
Read these 2 threads. It could help :
Read this thread : http://forum.xda-developers.com/show...426244&page=12
Pay special attention to page 12. It will show you how to do it without using novaterm. Also towards the beginning of the process you'll get asked a lot of questions, just answer yes to all. Good luck. Hold power and volume up at the same time, this will get you into correct mode (recovery). Edit : plug your tablet in for a few hours before trying the process.
http://forum.xda-developers.com/showthread.php?t=1971859
chicle_11 said:
Read these 2 threads. It could help :
Read this thread : http://forum.xda-developers.com/show...426244&page=12
Pay special attention to page 12. It will show you how to do it without using novaterm. Also towards the beginning of the process you'll get asked a lot of questions, just answer yes to all. Good luck. Hold power and volume up at the same time, this will get you into correct mode (recovery). Edit : plug your tablet in for a few hours before trying the process.
http://forum.xda-developers.com/showthread.php?t=1971859
Click to expand...
Click to collapse
Thank you for fast reply!,
I fallowed the steps in post u have mentioned however im getting stuck at 92% with ROM Check and thats what im getting:
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/lib/libGLESv2.so: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/frameworks/enyo/0.9/framework/source/palm/themes/
Onyx/css/Slider.css: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/frameworks/enyo/0.9/framework/source/palm/themes/
Onyx/css/Toaster.css: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/frameworks/enyo/0.9/framework/source/palm/themes/
Onyx/css/SlidingView.css: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/frameworks/enyo/0.9/framework/source/palm/themes/
Onyx/css/MenuItem.css: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/lib/purple-2/liboscar.so.0.0.0: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/sysmgr/images/normal-bg.png: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/com.palm.other
mail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/images/otherma
il32.png: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/images/otherma
il48.png: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/it/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/en/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/de/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/fr/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/fr/c
a/com.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/es/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:49 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: /usr/sbin/integcheck IPKG VERIFICATION FAILED, CODE 1
Nov 19, 2012 12:16:49 PM com.palm.nova.installer.recoverytool.CardController pos
tFlashEvent
WARNING: Flash Failure
err -1 "Base ROM Failed Verification"
at com.palm.nova.installer.core.stages.VerifyRomStage.printStreamToProgr
essReporter(VerifyRomStage.java:81)
at com.palm.nova.installer.core.stages.VerifyRomStage.printStreamToProgr
essReporter(VerifyRomStage.java:67)
at com.palm.nova.installer.core.stages.VerifyRomStage.runCommand(VerifyR
omStage.java:60)
at com.palm.nova.installer.core.stages.VerifyRomStage.run(VerifyRomStage
.java:38)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:518
)
at java.lang.Thread.run(Unknown Source)
Nov 19, 2012 12:16:49 PM com.palm.nova.installer.recoverytool.CardController pos
tFlashEvent
INFO: Flash End time (Fail) 1353327409990
Nov 19, 2012 12:16:49 PM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: from C:\Users\mike\AppData\Local\Temp\PalmWebOsRecoveryToolLog0.log.2
Nov 19, 2012 12:16:50 PM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: to C:\Users\mike\AppData\Local\Temp\palmInstallerError0.log
Nov 19, 2012 12:16:50 PM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: from C:\Users\mike\AppData\Local\Temp\PalmWebOsRecoveryToolLog0.log.1
Nov 19, 2012 12:16:50 PM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: to C:\Users\mike\AppData\Local\Temp\palmInstallerError1.log
Nov 19, 2012 12:16:52 PM com.palm.nova.installer.recoverytool.CardController han
dleFailCase
INFO: something failed, query to see if device is plugged in
Nov 19, 2012 12:16:52 PM com.palm.nova.installer.recoverytool.CardController han
dleFailCase
INFO: exiting handleFailCase()
err -1 "Base ROM Failed Verification"
at com.palm.nova.installer.core.stages.VerifyRomStage.printStreamToProgr
essReporter(VerifyRomStage.java:81)
at com.palm.nova.installer.core.stages.VerifyRomStage.printStreamToProgr
essReporter(VerifyRomStage.java:67)
at com.palm.nova.installer.core.stages.VerifyRomStage.runCommand(VerifyR
omStage.java:60)
at com.palm.nova.installer.core.stages.VerifyRomStage.run(VerifyRomStage
.java:38)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:518
)
at java.lang.Thread.run(Unknown Source)
Nov 19, 2012 12:16:53 PM com.palm.nova.installer.recoverytool.runner.DeviceDisco
veryRunner$DeviceDiscoveryThread run
INFO: got controller
Nov 19, 2012 12:16:53 PM com.palm.nova.installer.recoverytool.runner.DeviceDisco
veryRunner$DeviceDiscoveryThread run
INFO: got devices 1
Nov 19, 2012 12:16:53 PM com.palm.nova.installer.recoverytool.CardController run
nerFinished
INFO: device runner done
Nov 19, 2012 12:16:53 PM com.palm.nova.installer.recoverytool.CardController run
nerFinished
WARNING: flashing failed, move to failed card
And webos doctor is unable to restore my phone...
Any ideas?
Thanks
DarkLoola said:
Thank you for fast reply!,
I fallowed the steps in post u have mentioned however im getting stuck at 92% with ROM Check and thats what im getting:
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/lib/libGLESv2.so: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/frameworks/enyo/0.9/framework/source/palm/themes/
Onyx/css/Slider.css: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/frameworks/enyo/0.9/framework/source/palm/themes/
Onyx/css/Toaster.css: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/frameworks/enyo/0.9/framework/source/palm/themes/
Onyx/css/SlidingView.css: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/frameworks/enyo/0.9/framework/source/palm/themes/
Onyx/css/MenuItem.css: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/lib/purple-2/liboscar.so.0.0.0: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/sysmgr/images/normal-bg.png: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/com.palm.other
mail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/images/otherma
il32.png: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/images/otherma
il48.png: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/it/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/en/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/de/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/fr/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/fr/c
a/com.palm.othermail.json: FAILED
Nov 19, 2012 12:16:47 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: ./usr/palm/public/accounts/com.palm.othermail/resources/es/c
om.palm.othermail.json: FAILED
Nov 19, 2012 12:16:49 PM com.palm.nova.installer.recoverytool.CardController log
Print
INFO: ROM Verifyer: /usr/sbin/integcheck IPKG VERIFICATION FAILED, CODE 1
Nov 19, 2012 12:16:49 PM com.palm.nova.installer.recoverytool.CardController pos
tFlashEvent
WARNING: Flash Failure
err -1 "Base ROM Failed Verification"
at com.palm.nova.installer.core.stages.VerifyRomStage.printStreamToProgr
essReporter(VerifyRomStage.java:81)
at com.palm.nova.installer.core.stages.VerifyRomStage.printStreamToProgr
essReporter(VerifyRomStage.java:67)
at com.palm.nova.installer.core.stages.VerifyRomStage.runCommand(VerifyR
omStage.java:60)
at com.palm.nova.installer.core.stages.VerifyRomStage.run(VerifyRomStage
.java:38)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:518
)
at java.lang.Thread.run(Unknown Source)
Nov 19, 2012 12:16:49 PM com.palm.nova.installer.recoverytool.CardController pos
tFlashEvent
INFO: Flash End time (Fail) 1353327409990
Nov 19, 2012 12:16:49 PM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: from C:\Users\mike\AppData\Local\Temp\PalmWebOsRecoveryToolLog0.log.2
Nov 19, 2012 12:16:50 PM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: to C:\Users\mike\AppData\Local\Temp\palmInstallerError0.log
Nov 19, 2012 12:16:50 PM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: from C:\Users\mike\AppData\Local\Temp\PalmWebOsRecoveryToolLog0.log.1
Nov 19, 2012 12:16:50 PM com.palm.nova.installer.core.RdxUtils saveLogs
INFO: to C:\Users\mike\AppData\Local\Temp\palmInstallerError1.log
Nov 19, 2012 12:16:52 PM com.palm.nova.installer.recoverytool.CardController han
dleFailCase
INFO: something failed, query to see if device is plugged in
Nov 19, 2012 12:16:52 PM com.palm.nova.installer.recoverytool.CardController han
dleFailCase
INFO: exiting handleFailCase()
err -1 "Base ROM Failed Verification"
at com.palm.nova.installer.core.stages.VerifyRomStage.printStreamToProgr
essReporter(VerifyRomStage.java:81)
at com.palm.nova.installer.core.stages.VerifyRomStage.printStreamToProgr
essReporter(VerifyRomStage.java:67)
at com.palm.nova.installer.core.stages.VerifyRomStage.runCommand(VerifyR
omStage.java:60)
at com.palm.nova.installer.core.stages.VerifyRomStage.run(VerifyRomStage
.java:38)
at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:518
)
at java.lang.Thread.run(Unknown Source)
Nov 19, 2012 12:16:53 PM com.palm.nova.installer.recoverytool.runner.DeviceDisco
veryRunner$DeviceDiscoveryThread run
INFO: got controller
Nov 19, 2012 12:16:53 PM com.palm.nova.installer.recoverytool.runner.DeviceDisco
veryRunner$DeviceDiscoveryThread run
INFO: got devices 1
Nov 19, 2012 12:16:53 PM com.palm.nova.installer.recoverytool.CardController run
nerFinished
INFO: device runner done
Nov 19, 2012 12:16:53 PM com.palm.nova.installer.recoverytool.CardController run
nerFinished
WARNING: flashing failed, move to failed card
And webos doctor is unable to restore my phone...
Any ideas?
Thanks
Click to expand...
Click to collapse
If you followed the instructions in the first link (starting with webOS 3.0.0 then moving up to 3.0.5) and then added the commands in link 2 and you couldn't make it work, then I'm out of suggestions. Maybe try the process again? Make sure that the phone is fully charged before starting.
Good luck.
chicle_11 said:
If you followed the instructions in the first link (starting with webOS 3.0.0 then moving up to 3.0.5) and then added the commands in link 2 and you couldn't make it work, then I'm out of suggestions. Maybe try the process again? Make sure that the phone is fully charged before starting.
Good luck.
Click to expand...
Click to collapse
Hi, Im quite hard to get use of all this programing stuff....
So just to clryfiy all i did was
1. run novacom topaz image with TP in recovery mode using command promp
2. when the huge usb picture change to hp logo I writed new command: novacom -t open tty:// so i get into webos root.
3 next step I copied and pasted each line of commands as jakkzen sugested in one of those post above , here they are
Code:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Code:
4. after this is finished, I swap from Palm, Inc folder in command prompt to Program FIles\Java\jre7\bin
5 And write new command : java -jar....webosdoctor...
6 once entered I get webos doctor stared I also restarted TP and put i again into recovery mode so doctor could see it.
7. And now I failed at 8% =/ ...
I guess im doing it wrong somewhere...
DarkLoola said:
Hi, Im quite hard to get use of all this programing stuff....
So just to clryfiy all i did was
1. run novacom topaz image with TP in recovery mode using command promp
2. when the huge usb picture change to hp logo I writed new command: novacom -t open tty:// so i get into webos root.
3 next step I copied and pasted each line of commands as jakkzen sugested in one of those post above , here they are
Code:
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailurey
dd if=/dev/zero of=/dev/mmcblk0p14 bs=1024 count=1000
lvm.static pvcreate /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static vgcreate -s 8M store /dev/mmcblk0p14
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
lvm.static lvcreate -l 71 -i 1 -M y --major 254 --minor 0 -n root store
lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
lvm.static lvcreate -l 17 -i 1 -M y --major 254 --minor 5 -n filecache store
lvm.static lvcreate -l 3523 -i 1 -M y --major 254 --minor 6 -n media store
lvm.static lvcreate -l 64 -i 1 -M y --major 254 --minor 7 -n swap store
lvm.static vgscan --ignorelockingfailure
lvm.static vgchange -ay --ignorelockingfailure
mkdosfs -f 1 -s 64 /dev/store/media
Code:
4. after this is finished, I swap from Palm, Inc folder in command prompt to Program FIles\Java\jre7\bin
5 And write new command : java -jar....webosdoctor...
6 once entered I get webos doctor stared I also restarted TP and put i again into recovery mode so doctor could see it.
7. And now I failed at 8% =/ ...
I guess im doing it wrong somewhere...
Click to expand...
Click to collapse
Did you copy the image file (the one you're 'pushing') to your computer?
Also, make sure it's in the same directory as the novacom files.
You can also make a search for 8% over at webos nation forum. I've seen a thread there about that.
Good luck.
Edit : when you get to the part where it asks a lot of questions, answer yes to all.
Make sure that the commands you use are for your tp (either 32 or 16gb).
Edit 2 : I was just rereading your post and I noticed that you used commands to get to doctor - FIles\Java\jre7\bin 5 And write new command : java -jar....webosdoctor.......try this : reboot the TP into recovery, connect the TP to the computer, and in Windows Explorer, double click on webos doctor 3.0.0. It should work.
Edit 3 : write the commands one at a time and hit enter after each one.
chicle_11 said:
Did you copy the image file (the one you're 'pushing') to your computer?
Also, make sure it's in the same directory as the novacom files.
You can also make a search for 8% over at webos nation forum. I've seen a thread there about that.
Good luck.
Edit : when you get to the part where it asks a lot of questions, answer yes to all.
Make sure that the commands you use are for your tp (either 32 or 16gb).
Edit 2 : I was just rereading your post and I noticed that you used commands to get to doctor - FIles\Java\jre7\bin 5 And write new command : java -jar....webosdoctor.......try this : reboot the TP into recovery, connect the TP to the computer, and in Windows Explorer, double click on webos doctor 3.0.0. It should work.
Edit 3 : write the commands one at a time and hit enter after each one.
Click to expand...
Click to collapse
Thanks you ! after having 2 days out of my life i finally managed to boot into webos! Great.
Excellent help!
Thanks
Mike

[Q][T][Solved] Troubles creating my own kernel.elf

My long term goal is to compile my own kernel for my Xperia T.
But before I go about that, I tried to extract and rebuild a stock kernel.elf without any changes. I am already failing at this fairly easy task.
I extracted a stock kernel.elf from this FTF with flashtool. So I ended up with following files:
Code:
-rw-r--r-- 1 gwodus gwodus 20971520 Oct 6 15:48 kernel.elf
-rw-r--r-- 1 gwodus gwodus 130 Oct 6 15:48 kernel.elf.bootcmd
-rw-r--r-- 1 gwodus gwodus 1072 Oct 6 15:48 kernel.elf.cert
-rw-r--r-- 1 gwodus gwodus 5655400 Oct 6 15:48 kernel.elf.Image
-rw-r--r-- 1 gwodus gwodus 1512035 Oct 6 15:48 kernel.elf.ramdisk.gz
-rw-r--r-- 1 gwodus gwodus 133372 Oct 6 15:48 kernel.elf.rpm.bin
-rw-r--r-- 1 gwodus gwodus 16 Oct 6 15:48 kernel.partinfo
-rw-r--r-- 1 gwodus gwodus 7306651 Oct 6 15:48 kernel.sin
Without changing any files I recomposed a new kernel2.elf with mkelf.py:
Code:
python mkelf.py -o kernel2.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
Then I flashed the kernel with fastboot:
Code:
sudo ./fastboot flash boot kernel2.elf
Unfortunately the phone did not boot anymore. When I soft reset the phone and flash the original kernel.elf, everything is back to normal.
I noticed that the original kernel.elf is a lot bigger then the kernel2.elf I created:
Code:
-rw-r--r-- 1 gwodus gwodus 7305033 Oct 6 15:51 kernel2.elf
-rw-r--r-- 1 gwodus gwodus 20971520 Oct 6 15:48 kernel.elf
My guess is that the parameters for mkelf.py might be wrong? I got those from some posts around here (mainly this one). Hopefully some Xperia developers can point me to the right track. Thanks in advance.
I did some further research on how an elf file is assembled and figured out how to extract the address-parameters from the original elf. And indeed there is a difference. The address for the ramdisk ist not 0x81300000 but 0x81400000. I compiled the elf again with that parameter, and what do you know, it works like a charm now.
So the correct command line for mkelf.py for the Xperia T is:
Code:
python mkelf.py -o kernel2.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
I don't know if that guide is just wrong, or if there are different models of the T or if it depends on the kernel version. I did some further search on the internet. Some people also use 0x81500000 or 0x81600000 for the ramdisk address on the Xperia T. Just for fun, I tried 0x81500000, which also worked.
Maybe somebody knowledgeable can shed some light on this topic.

Categories

Resources