Talk:Last Resort Emergency BootLoader Recovery
From WebOS Internals
Question: I'm curious if any progress has been made doing a similar procedure with the Pixi. I have a Pixi that will not boot and does not go into recovery mode using the standard hold volume up + insert USB cable.
Peef: The Pixi has a Qualcomm MSM7627 core rather than the Texas Instruments OMAP3430 that's in the Pre. My experience is that it's much easier to get information and tools from TI than it is from Qualcomm. I'm sure there is similar functionality, but until someone discovers the tool for loading boot code over USB, this is not possible. The only other way would be to crack it open and use JTAG, which is a whole other can of worms. Historically Qualcomm is very secretive and will not even give out datasheets on things unless you are a bigshot carrier who has signed many NDA's and have their secret police following you around 24/7. I recommend you sell it on ebay as a "parts only" phone. Someone will want the LCD or other parts.
Question: As far the NVRAM Tokens. How does one write these token values?
Answer: The tokens can be written by editing the castle.xml (pixie.xml for the Pixi) under resources/webOS under the "nvram" section. Entries look like this as an example.
Another Answer: The above will only work during restore (WebOS Doctor). The tokens are "live" in /dev/tokens if you want to change them on the fly. -pEEf
<Val name="DMCARRIER" action="overwrite" value="Sprint"/>
Question: What is the PN (product number) for the Sprint Pixi?
Question: Is the MfgCode token (8 hex digits) unique for each device?