Last Resort Emergency BootLoader Recovery - Revision history

GarthPS: /* Corrupted LVM */

2011-04-15T08:50:42Z

Corrupted LVM

RodWhitby at 13:58, 24 January 2011

2011-01-24T13:58:47Z

IDG: /* Token Backup */

2011-01-24T11:46:06Z

Token Backup

Darkconsole: /* Recovery Mode */

2011-01-24T03:27:04Z

Recovery Mode

Darkconsole: /* Recovery Mode */

2011-01-24T03:26:40Z

Recovery Mode

RodWhitby at 13:38, 23 December 2010

2010-12-23T13:38:05Z

RodWhitby at 12:25, 23 December 2010

2010-12-23T12:25:02Z

RodWhitby at 11:46, 23 December 2010

2010-12-23T11:46:04Z

RodWhitby at 08:33, 23 December 2010

2010-12-23T08:33:15Z

RodWhitby: libusb-dev dependency

2010-08-09T01:00:55Z

libusb-dev dependency

@@ Line 173: / Line 173: @@
   lvm.static pvremove -ff /dev/mmcblk0p3
-Then run the webOS Doctor again.
+Then run the webOS Doctor again. (WARNING!! the 2.1 doctor does not like this at all! DataPreCheckStage: mount: mounting /dev/mapper/store-media on /tmp_media failed: No such file or directory )
 == Recovery using OS/X ==

@@ Line 65: / Line 65: @@
   DMCLoAUTHNAME an integer number (probably 32 bits) in ASCII format
-'''Anyone is willing to provide a MD5 hash of these tokens on his device, to see if they're device unique or not?'''
+The tokens are unique to each device.
 == Token Editing ==

@@ Line 65: / Line 65: @@
   DMCLoAUTHNAME an integer number (probably 32 bits) in ASCII format
-'''NOTE:''' I've built a group of perl scripts to rebuild the token area of the NVRAM from a backup, should anyone need it.
+'''Anyone is willing to provide a MD5 hash of these tokens on his device, to see if they're device unique or not?'''
 == Token Editing ==

@@ Line 7: / Line 7: @@
 If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface.  At this time this operation has not been performed on a Pixi, and will not be the same as it has a different core.
-The OMAP method listed below worked successfully to reset the phone when the phone lock password was forgotten to rebuild the phone without losing the photos on the phone.
+The OMAP method listed below worked successfully to reset the phone when the phone lock password was forgotten to rebuild the phone without losing the photos on the Palm Pre phone.
 ==NVRAM Tokens==

← Older revision		Revision as of 03:26, 24 January 2011
Line 7:		Line 7:
	If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface. At this time this operation has not been performed on a Pixi, and will not be the same as it has a different core.		If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the Pre is still not "bricked" as the OMAP3430 processor in the Pre provides for a mechanism to boot code from its USB interface. At this time this operation has not been performed on a Pixi, and will not be the same as it has a different core.

		+	The OMAP method listed below worked successfully to reset the phone when the phone lock password was forgotten to rebuild the phone without losing the photos on the phone.

	==NVRAM Tokens==		==NVRAM Tokens==

@@ Line 45: / Line 45: @@
   MfgCode        SimLockDef
-The purpose of the "BATToCH", "BATToRSP", "DMCLoAUTHPW", "DMCLoNONCE", "DMSVRoAUTHPW", "DMSVRoNONCE" tokens are as yet not fully understood.  They appear to be unused, as they're never visible inside any part of the code as strings, and completely removing them does not seem to change anything in the device behavior.
+The purpose of the "BATToCH", "BATToRSP", "DMCLoAUTHPW", "DMCLoNONCE", "DMSVRoAUTHPW", "DMSVRoNONCE" tokens are as yet not fully understood.  They appear to be unused, as they're never visible inside any part of the code as strings, and completely removing them does not seem to change anything in the device behavior. However, on webOS 2.0 and later, it seems that they need to exist for a successful login to your Palm Profile.
 The BATToCH/BATToRSP is likely a challenge/response crypto system used to authenticate the battery pack. This means that Palm could use the capability to lock out "fake" batteries should they ever want to. So far they haven't implemented any of this, as it would probably affect the Seidio aftermarket packs.

@@ Line 169: / Line 169: @@
 == Corrupted LVM ==
-If your LVM disk volumes are completely corrupted, and the webOS Doctor will not run as a result, then us the Alternate Recovery technique above to enter a recovery shell, and run the following command to completely wipe the LVM disk labels and metadata:
+If your LVM disk volumes are completely corrupted, and the webOS Doctor will not run as a result, then use the Alternate Recovery technique above to enter a recovery shell, and run the following command to completely wipe the LVM disk labels and metadata:
   lvm.static pvremove -ff /dev/mmcblk0p3
@@ Line 182: / Line 182: @@
   /opt/nova/bin/cpuboot  -o -v -d usb -f /opt/nova/bin/recovery-castle.bin

← Older revision		Revision as of 11:46, 23 December 2010
Line 167:		Line 167:
	umount -a; tellbootie reboot		umount -a; tellbootie reboot

		+	== Corrupted LVM ==
		+
		+	If your LVM disk volumes are completely corrupted, and the webOS Doctor will not run as a result, then us the Alternate Recovery technique above to enter a recovery shell, and run the following command to completely wipe the LVM disk labels and metadata:
		+
		+	lvm.static pvremove -ff /dev/mmcblk0p3
		+
		+	Then run the webOS Doctor again.

	== Recovery using OS/X ==		== Recovery using OS/X ==

@@ Line 18: / Line 18: @@
 GSM Pre for O2 and Movistar: DMCARRIER=ROW, DMMODEL=castle, HWoRev=A, PN=180-10722-03, PRODoID=P100UEU
-GSM Pre Plus SFR: DMCARRIER=ROW, DMMODEL=P101UEU, HWoRev=A, KEYoBRD=w1 (AZERTY), PN=180-10773-01, PRODoID=P101UEU, installer=trenchcoat
+GSM Pre Plus SFR: DMCARRIER=ROW, DMMODEL=P101UEU, HWoRev=A, KEYoBRD=w1 (AZERTY), PN=180-10773-01, PRODoID=P101UEU
-Sprint Pixi: DMCARRIER=Sprint, DMMODEL=P200EWW, HWoRev=A, KEYoBRD=z, PN=180-10714-03, PRODoID=P200EWW, installer=trenchcoat
+Sprint Pixi: DMCARRIER=Sprint, DMMODEL=P200EWW, HWoRev=A, KEYoBRD=z, PN=180-10714-03, PRODoID=P200EWW
-Sprint Pre: DMCARRIER=Sprint, DMMODEL=P100EWW, HWoRev=A, KEYoBRD=z, PN=180-10642-05, PRODoID=P100EWW, installer=trenchcoat
+Sprint Pre: DMCARRIER=Sprint, DMMODEL=P100EWW, HWoRev=A, KEYoBRD=z, PN=180-10642-05, PRODoID=P100EWW
-Verizon Pixi Plus: DMCARRIER=Verizon, DMMODEL=P121EWW, HWoRev=A, KEYoBRD=z, PN=180-10714-01, PRODoID=P121EWW, installer=trenchcoat
+Verizon Pixi Plus: DMCARRIER=Verizon, DMMODEL=P121EWW, HWoRev=A, KEYoBRD=z, PN=180-10714-01, PRODoID=P121EWW
-Verizon Pre Plus: DMCARRIER=Verizon, DMMODEL=P101EWW, HWoRev=A, KEYoBRD=z, PN=180-10724-01, PRODoID=P101EWW, installer=trenchcoat
+Verizon Pre Plus: DMCARRIER=Verizon, DMMODEL=P101EWW, HWoRev=A, KEYoBRD=z, PN=180-10724-01, PRODoID=P101EWW
-AT&T Pre Plus: DMCARRIER=ATT, DMMODEL=P101UNA, HWoRev=A, KEYoBRD=z, PN=180-10725-03, PRODoID=P101UNA, installer=trenchcoat
+AT&T Pre Plus: DMCARRIER=ATT, DMMODEL=P101UNA, HWoRev=A, KEYoBRD=z, PN=180-10725-03, PRODoID=P101UNA
 If you want BlueTooth and Wifi to work, You may also want to set BToADDR=00:1D:FE:''xx:yy:zz'', WIFIoADDR=00:1D:FE:''uu:vv:ww'' and PalmSN=''serial''.  If you are unsure of your original MAC addresses, They can safely be any random number, the serial number is on the box and on a sticker inside the battery compartment.
@@ Line 89: / Line 93: @@
 If you have not libusb 0.1.3 installed on your computer, install it. It is needed for the header file /usr/include/usb.h
 On Ubuntu, make sure you have the libusb-dev package installed.
 Compile on Linux system with "make".  Optionally install with "sudo cp omap3_usbload /usr/local/bin"