04/05/2012, 09:56 PM
The following script process creating the webOS 2.2.4/4 Doctor have been tested by several users and myself (on an AT&T VEER)... YMMV, as we are using a Doctor process, I doubt it could brick yours but I must warn it has been reported A6 devices can be bricked.
I was asked could I create a script to create a VEER webOS 2.2.3/4 builds... Here they are... Please read this Post twice...
Follow this URL to install the meta-doctor application:
Application:MetaDoctor - WebOS Internals
Pushed Scripts to github, these scripts are now part of the Meta-Doctor Application; you no longer need to copy these scripts!
I have finally heard it works on a WR (ROW) device, (script has been tested and WR Doctor builds)...
Does this process work, yes for AT&T and for WR, does it pass validation YES, and does it eat a VEER for dinner...
Sure hope it does not but I must warn it has been reported A6 devices can be bricked...
Steps to create doctor, these scripts are now part of the meta-doctor scripts set so you should not have to copy the script to meta-doctor/scripts directory, but you still need to copy Veer and Pre2 doctors that are needed for the first script (the script will pull them down if not there), but it will want the webOS 2.2.3/4 files (I will not post the files or where to get them google is ones friend here).
Running the first script:
./scripts/build-veer-2.2.3 carrier optional --wifi-only
./scripts/build-veer-2.2.4 carrier optional --wifi-only
So for AT&T
So for AT&T WiFi Only
./scripts/build-veer-2.2.3 att --wifi-only
./scripts/build-veer-2.2.4 att --wifi-only
So for WR
So for WR WiFi Only
./scripts/build-veer-2.2.3 wr --wifi-only
./scripts/build-veer-2.2.4 wr --wifi-only
Running the second script (run the first script first, It will auto detect the carrier used by the doctor created in the first script and superfy it):
./scripts/super-veer-2.2.3 (Has not been released yet)
Background on First Script:
Now once the script runs the first time it unpacks the Veer 2.1.x and Pre2 (webOS 2.2.3 only) doctor(s), then stops informing that the directory “Not prepared for webOS 2.2.3/4 build extract” and “Please create 223/4 directory under …” and it gives you the directory where the directory “223/4” should be created…
For webOS 2.2.3: Use terminal to mkdir –p DOCTOR/223
For webOS 2.2.4: Use terminal to mkdir –p DOCTOR/224
Where DOCTOR is the name of the directory given to you by the last command.
Re-run the script now it complains, “Not prepared for webOS 2.2.3/4 build extract” and “webOS 2.2.3/4 rootfs file not present”.
Now copy the VEER webOS 2.2.3/4 rootfs file, the updated boot tar to the 223/4 directory (I will not tell anyone where to get the backup webOS 2.2.3/4 files, I will not tell you the file names, I will not tell you anything about them, except they exist in the wild), your custom boot logo, if you wish to stay with the HP one, the build will now pull the standard HP BootLogo under scripts/bootlogo.tga, and NOW you can copy a custom uImage.
Note: The script now handles this if a custom BootLogo is not found it will extract the HP BootLogo. The HP logo is in the following GZIPED TAR file, build/veer-p160una-att-2.1.2/rootfs/boot/boot-images.tar.gz. Just copy that GZIPED TAR and use gzip -d boot-images.tar.gz to unpack it, then use tar -xf boot-images.tar and copy the BootLogo.tga.
Re-run the script, now it will ungzip both webOS 2.2.3/4 files just copied and it will then copy the main rootfs file and then transform it…
When that script is done, a Veer webOS 2.2.3/4 doctor is created and moved to the “downloads” directory.
If you used the first script’s JAR file and run it, it will be a webOS 2.2.3/4 stock (but again not supered, this is just to test build the doctor, I got it according to the MD5SUMS the closest I can come to a stock webOS 2.2.3/4 doctor, there are a few files that had to change)
What the Stock Doctor does NOT do, Update the Touch Panel Firmware, however (if you are already updated it will not bring you back), A6 Update (on the Veer I am testing on it had brought it back each time, YMMV)... What will it do, if you need it, the doctor will update the Modem firmware (will not force). Why can't I update the TP and A6 well HP/PALM scripts run from the existing uImage (provided by the seed Veer doctor), which has the older version, they do not run the newer ROM just brought down, but the version contained within. But now the script can handle a custom uImage, which if used and modified correctly the entire custom Doctor can now handle the TouchPanel and A6 firmware.
So to fix the Stock/Custom Doctor I enabled Developer Mode by default (Based on herrie82 | HP Veer webOS 2.2.3/2.2.4 update they even have videos):
FYI to revert just remove the following file: novacom_enabled under /var/gadget.
Use novaterm to update the TP:
Use novaterm to update the A6:
Note: So if someone was able to use the existing open source palm rom (webOS 2.1.2) and uImage and could compile it with the rest of the commands needed and include the update TP/A6 firmware... We tried this on Page 4 (ugly did not work)!
This continued on page 8 now a procedure and python script to make it happen...
Unpacking and repacking U-Boot uImage files
Unpacking and repacking U-Boot images part 2
The first script (webOS 2.2.3) has been tested by others and it worked, I have not posted a second script that will create a new super doctor with updated webOS 2.2.3 components (from the Pre3 AT&T build), Updated Bing Maps, transforms webOS 2.1.2 Maps app to GoogleMaps, bring back the older YouTube App and Amazon MP3 (from webOS 2.1.2) and Motionapps Classic Bits. The main reason is the webOS 2.2.3 Pre3 version also has updated Screen Resolution which makes it un-usable on the Veer, if there is interest I can attempt to just replace the old versions with the current version and change the md5sums just for those files...
The first script (webOS 2.2.4) has been tested by others and it worked, I have posted a second script that will create a new super doctor with updated webOS 2.2.4 components (from the Pre2 build), Updated Bing Maps, transforms webOS 2.1.2 Maps app to GoogleMaps, bring back the older YouTube App and Amazon MP3 (from webOS 2.1.2) and Motionapps Classic Bits.
When there are errors:
The build creates two txt files one under the doctor/223/4 directory (by doctor it is that name of the doctor directory of the seed doctor IE for AT&T it is veer-p160una-att-2.1.2).
The super script creates a superveer.txt either post them or send them (PM) to me, so I can see what it was trying to do (you should also send me the output of the command line).
Let me know how it goes and Thanks for testing this process, and please report all issues discovered even if everything worked...
Version Log (at version 9.1)
V9.1- Fixed Bug in Build Veer script... (was 223 is now 224 for uImage detection)
V9 - Updated Scripts from meta doctor Application HP/Palm changed the Source URL.
V8 - Updated to handle custom uImage and if no custom BootLogo is found, it will extract the HP BootLogo from webOS 2.1.2.
V7 - Fix rootfs and got a doctor to build and test on an AT&T device, released Super Script, and webOS 2.2.3 base script.
V7 - Now pushed to the meta-doctor application set of scripts.
V6 - Removed lib boot files from build, so I think I proved it is something in the webOS 2.2.4 rootfs it does not like... (Removed V6/5 as they were failed by the rootfs).
V5 - Back to basics, modified V1 without XML conversion for webOS 2.2.4 disk structure...
V4 - Fixed AT&T XML file parse issue? The Logic for WR (ROW) was correct and did not need to change. (Removed V4&3 as the Pre 3 base Doctor will not work for webOS 2.2.4)
V3 - Updated script to use Pre3 Java Class Files (according to MANIFEST.MF file there are four files different from the Pre3 (WR) to the Pre2 WR webOS 2.2.4 build, the carrier.tar, webOS.tar, languagePicker.properties, and the recoverytools.config).
V2 - Updated script to use Pre2 Java Class Files (according to MANIFEST.MF file there are four files different from the Pre3 (Verizon) to the Pre2 WR webOS 2.2.4 build, the carrier.tar, webOS.tar, languagePicker.properties, and the recoverytools.config), also cleaned up the script. (Removed as the Pre 2 base Doctor will not work for webOS 2.2.4)
V1 - Released build-Veer-2.2.4-V1
*****First Release Veer Build Script Only (removed as the Veer base Doctor will not work for webOS 2.2.4)