|
Ok so here goes, I updated my Veer to 2.2.3
C:\Users\Owner\Desktop\PALM\veer 2.2.3\veer bat files>veer22xupdater.bat install
Veer 2.2.3/2.2.4 update by Herrie, thanks to all who helped in getting this done
.
Special thanks goes out to NB for the support and the providers of the backups
(you know who you are ) WebOS-Internals Main Page - WebOS Internals and
Pre-Central http://forums.precentral.net for all their support and tools.
THIS NEEDS TO BE RUN IN USB-CHARGING MODE AND WILL WIPE
EVERYTHING EXCEPT THE NVRAM PARTITION FROM YOUR DEVICE AND
TRY TO INSTALL 2.2.3/2.2.4 ON IT. IT MAY OR MAY NOT WORK.
IF IT DOESN'T WORK YOU'RE INVITED TO USE THE uninstall OR
uninstall-from-recovery PARAMETERS AND THEN RESTORE USING
WEBOS DOCTOR.
Rebooting your phone into recovery mode ...
novacomd socket was closed prematurely
novacom: unexpected EOF from server
Waiting for the phone to come back (20 seconds)
Done!
"Transfer nova installer to device and reboot your device with it ..."
Waiting for the phone to come back (20 seconds)
The fun begins. DESTROYING ALL YOUR VEER PARTITIONS.
Reading all physical volumes. This may take a while...
Found volume group "store" using metadata type lvm2
8 logical volume(s) in volume group "store" now active
Logical volume "filecache" successfully removed
Logical volume "media" successfully removed
Logical volume "root" successfully removed
Logical volume "update" successfully removed
Logical volume "log" successfully removed
Logical volume "mojodb" successfully removed
Logical volume "swap" successfully removed
Logical volume "var" successfully removed
Now everything is gone. Not even the webOS Doctor will save your Veer
Waiting for 10 seconds before continuing
Continuing
Rebuilding the Veer partitions
Creating root partition
Logical volume "root" created
Creating var partition
Logical volume "var" created
Creating update partition
Logical volume "update" created
Creating log partition
Logical volume "log" created
Creating mojodb partition
Logical volume "mojodb" created
Creating filecche partition
Logical volume "filecache" created
Creating swap partition
Logical volume "swap" created
Setting up swapspace version 1, size = 516092 KiB
no label, UUID=e8033f3a-165b-4be5-a796-50ca60436ad2
Creating media partition
Logical volume "media" created
mkdosfs 2.11 (12 Mar 2005)
Partitions recreated. You now even may run the WebOS Doctor. Did I scare you?
Waiting for 10 seconds before continuing
Continuing
Mounting partitions in place
Reading all physical volumes. This may take a while...
Found volume group "store" using metadata type lvm2
8 logical volume(s) in volume group "store" now active
Waiting for 5 seconds before continuing
Continuing
Filesystems mounted. Installing now... please hold on...
Restoring root, might take 5-10 minutes
Wed Dec 7 22:15:00 UTC 2011
Restore the var
Restore the update
Restore the media
bin/tar: .: implausibly old time stamp 1970-01-01 00:00:00
Restore the filecache
278528+0 records in
278528+0 records out
142606336 bytes (136.0MB) copied, 48.658475 seconds, 2.8MB/s
Restore the mojodb
294912+0 records in
294912+0 records out
150994944 bytes (144.0MB) copied, 50.214698 seconds, 2.9MB/s
Restore the boot
Rebooting your phone ...
bad or error response from other side: ''
Waiting for the phone to come back (20 seconds)
Done!
PREPARES FIRMWARE UPDATE FILES, BUT DOES NOT UPDATE THEM!
YOU NEED TO MANUALLY RUN THE SCRIPTS IN /TMP/MEDIA USING NOVATERM
TO RUN THE FIRMWARE UPDATES.
Preparing modem update script
Preparing touchpanel update script
(00044/246255970) hidd (stop) running, process 1836
(00044/246749134) hidd (stop) pre-stop, (main) process 1836
(00044/246979928) hidd (stop) stopping, process 1836
(00044/248220488) hidd (stop) killed, process 1836
(00044/276307566) hidd (stop) post-stop
(00044/276491485) hidd (stop) waiting
Now starting Novaterm for optional firmware updates.
'novaterm' is not recognized as an internal or external command,
operable program or batch file.
Exiting
Then I did the touchscreen fix...
C:\Users\Owner\Desktop\PALM>"C:/Program Files/Palm, Inc/novacom.exe" -d dd06df77
b8b1e8df56c371d37ee734c02b6ea26e -t open tty://
root@webos-device:/# ←[Jcd/temp/media
cd/temp/media
/bin/sh: cd/temp/media: not found
root@webos-device:/#
root@webos-device:/# cd /tmp/media
cd /tmp/media
root@webos-device:/tmp/media#
root@webos-device:/tmp/media# sh tpupdate.sh
sh tpupdate.sh
id: 0582, family/die: 70, major rev: 12
installed version: 13
programmed version: 10
firmware needs update
retrieving rom data...
global idac table: 141 144 146 148 150 150 145 139 145 146 148 149 149 135
local idac table: 11 12 13 14 14 16 18 13 14 14 14 15 15 20 9 10 11 11 11 11 12
17 12 12 12 11 11 14 20 19 19 18 18 18 17 21 19 18 18 18 18 21 15 14 14 14 13 13
12 17 14 14 14 14 14 17 25 25 25 24 24 24 22 12 22 22 22 22 21 9
panel id: 20110423-2137-1500-0201-000000077744
scratch: (empty)
programming '/lib/firmware/cy8ctma300e'...
restoring calibration data...
calibrating panel for self-cap...
restoring panel id...
root@webos-device:/tmp/media#
root@webos-device:/tmp/media# start hidd
start hidd
(00769/626547640) hidd (start) waiting
(00769/627643506) hidd (start) starting
(00769/628054476) hidd (start) pre-start
(00769/629272737) hidd (start) spawned, process 3287
(00769/633014762) hidd (start) post-start, (main) process 3287
(00769/633499137) hidd (start) running, process 3287
root@webos-device:/tmp/media#
root@webos-device:/tmp/media#
novacomd socket was closed prematurely
novacom: unexpected EOF from server
I had WiFi only, so I followed the Option 2 instructions, ended up with a Full Erase, reboot, and now it looks like I'm stuck on the Sign-In screen, and this is it. Stuck.
Is there something I can do here? I didn't get to the part of the modem update, as I was following the instructions, in order. So is it bricked now? Or is there something I can do?
When I plug it into the PC, it makes the usual connection sound.
Or just put it into recovery, then run the old ATT Doctor? (and try it again)
Guess I talked my way through it, currently doctoring, and sitting at 12% (currently, doesn't look like it's stalling.)
So I'm thinking that I should have done the modem update prior to the Full Erase. If someone can confirm it, I'll just try it out again later this evening.
|
|
|