2011年2月27日 星期日
Galaxy tab 刷機
也因為Tab, 我才從台灣, 對岸, 或國外的一些網站開始了解Android, 什麼是root, Firmware, 刷機, Market等名詞. Tab使用熟一點後, 發現兩個小不滿, 一個是Samsung Apps一直是空白的, 沒有apps可以下載, 看到有人可以下在NFS Shift,及NOVA, 是蠻羨慕的, 可是也沒有辦法. 另一個是, 檢查Firmware資訊, 電話打 *#1234#, 顯示版本怪怪的, 如下圖:
PDA:
PHONE: P1000ZUJJ2
CSC:
Tab首頁, 設定, 關於手機, 如下圖, 基頻是ZUJJ2
雖然使用上Tab功能都正常, 但看其他人的PDA及CSC都會有顯示相關的版本,而且Tab也有新的台版ROM釋出, 因此產生刷機的想法. 於是看了Mobile01平海大的貼文, samfirmware及國外XDA的許多刷機討論, 瞭解了Tab Firmware的檔案及刷機流程. 我只是初學者, 以下把我瞭解的一些整理出來, 分享給大家.
1. Tab firmware的版本: (可參考i9000類似)
- 主要依地區有分歐美版, 亞洲版, 阿拉伯版等, 再依國家或是電信公司, 及更新版本, 分別以不同的代號代表. 其他的不說, 以台灣版而言, 目前知道有三種代號.
- ZU: 中華電信客制版, 例如P1000ZUJJ2, P1000ZUJK1,.. P1000是Tab的產品代號, JJ2, JK1則是版本編號. 而JK1比JJ2新.
- ZF: 遠傳電信客制版, 例如P1000ZFJK1
- ZT: 台灣open版(不含中華或遠傳的一些客制apps), 例如P1000ZTJK1, P1000ZTJL1, 而JL1比JK1新
- 其他代號如ZH是香港版, DX是東南亞版, XX, XW是歐美版, JP, JV是阿拉伯版
2. Tab firmware檔案內容: (可參考i9000類似)
- 完整版的firmware, 會有PDA, PHONE, CSC三類的檔案, 附檔名以.md5或.tar的壓縮檔, 不完整的Firmware, 就可能只有PDA的檔案. Tab電話打 *#1234# 就會顯示每類的版本.
- PDA: 包含Android OS及附加的系統應用程式, 檔案size會很大, 一般會超過200MB以上
- PHONE: 檔名會內含MODEM字樣, 包含規範無線通訊晶片如何運作的檔案, 無線通訊如Wifi, 藍芽Bluetooth, 3G, GSM, CDMA等等, 無線通訊是跟每個國家或地區使用不同的無線規範相關. 檔案size一般在12MB左右.
- CSC: 是 Carrier Specific Customization簡寫, 檔名會內含CSC字樣, 包含如APN設定, 及跟不同國家或電信公司各自的應用設定. 檔案size一般在12MB-81MB左右.
- 完整firmware跟不完整firmware都可以刷機, 只是步驟會有不同.
以上說明漏漏長, 以下進入刷機實作:
刷機前準備手續:
1. 下載平海大的firmware壓縮檔, 或從對岸的網站找- P1000ZUJK1 及 P1000ZTJL1, 是7z壓縮檔, 要解壓縮.
2. 下載刷機所需軟體(Odin3 v1.7), 及PIT檔(P1_add_hidden.pit). 這兩個檔案可以在網路上找到, 或是到samfirmware.com下載. 注意PIT檔一定要是P1_add_hidden.pit, 不能拿其他名字的pit檔代替. PIT檔的作用, 相當於是Windows系統對硬碟進行分區partition. 用錯了就會刷機失敗.
3. Tab要先root, 可用z4root來做. z4root目前在market上已經沒有, 檔案如附件. 要root的目的是要安裝Titanium Backup做程式及資料備份.
附加壓縮檔: 201012/mobile01-99ea44c8fd9d08bd63bd19c9c12998d7.zip
4. 從Market下載Titanium Backup免費版安裝, 在偏好設定的備份設定, 將”備份資料夾名稱”更改為外部SD卡(原資料夾前要加上/external_sd/), 備份時選”所有應用程式與系統資料”. 如果不更改, 預設會備份到內部SD卡上. 改好後先批次備份一次, 然後看看外部SD卡有沒有TitaniumBackup資料夾內有沒有檔案, 就知道有沒有成功. 等刷機完成後, 再用Titanium Backup將應用程式及資料還原安裝回去Tab. 請看下圖 External Storage及備份目錄的地方.
5. 我的打算是將ZUJJ2中華電信版升級刷為ZUJK1中華電信版, 再刷為ZTJL1台灣open版.
補充: 請看我最底下12/23補充2, 刷機前先備份 efs 資料夾, 以免發生刷機失敗 imei 碼不見的情形. 我刷機前是沒做, 還好刷完後imei還在.
刷機過程:
1. Tab先充好電, 首頁, 設定, SD卡和行動電話儲存空間, 卸載SD卡, 來將外部SD卡卸載, 關機後將外部SD卡拿出.
2. 開機做hard reset回復出廠設定(首頁, 設定, 隱私設定, 重設為原廠設定, 或是電話 *2767*3855#), 這個步驟沒做應該也行, 我是要先把檔案清乾淨.
3. 在PC上把刷機軟體Odin3 v1.7及P1000ZUJK1的檔案放在同一資料夾下, 一共有5個檔案: Odin3 v1.7.exe, P1_add_hidden.pit, P1000ZUJK1-REV03-ALL-CL712217.tar.md5, MODEM_P1000ZUJK1_REV_00_CL644164.tar.md5, 及GT-P1000-CSC-CWTJJ3.tar.md5
4. 依照平海大介紹的步驟(http://www.mobile01.com/topicdetail.php?f=568&t=1899849)
- 此時Tab先不連上PC, 在PC上開啟Odin3 刷機軟體, 在Re-partition, Auto Reboot, F. Reset Time打勾, 然後點PIT, 選P1_add_hidden.pit
- PDA選P1000ZUJK1-REV03-ALL-CL712217.tar.md5)
- PHONE選MODEM_P1000ZUJK1_REV_00_CL644164.tar.md5
- CSC選GT-P1000-CSC-CWTJJ3.tar.md5
- 在Tab上同時壓下”音量下鍵”+”開機鍵”,進入”Download mode”, 然後將Tab接上電腦USB
- 等到Odin3抓到COM port後(COM port #視電腦而不同), 按Start開始刷機, 過2-3分鐘後就刷好了.
- 刷機完成出現PASS後, Tab跟電腦斷開, 再做一次hard reset *2767*3855#, reset後輸入*#1234#來確認升級後的版本
5. 我刷好ZUJK1中華電信版後的圖如下:
- 電話 *#1234#, 查詢升級後的版本
- 關於手機的圖, 基頻是ZUJK1
- 首頁的圖, 中間右方有中華電Hami widgets
- 程式頁面, 最上方有四個Hami的widgets
- 點Samsung Apps出現有9個apps可以下載, 其中有NFS Shift, NOVA. 終於可以下載了
6. 接著繼續把ZUJK1刷成ZTJL1(試驗性質, 要把Hami widgets拿掉). 在PC上把刷機軟體Odin3 v1.7及P1000ZTJL1的檔案放在同一資料夾下, 一共有4個檔案: Odin3 v1.7.exe, GT-P1000-CSC-BRIJJ1.tar.md5, MODEM_P1000ZTJL1_REV_00_CL614387.tar.md5, P1000ZTJK1-REV03-ALL-CL712217.tar.md5. 此處沒有P1_add_hidden.pit, 因為在刷ZUJK1時, 已經做過了分區re-partition, 不需要再重做.
7. 刷ZTJL1步驟:
- 此時Tab先不連上PC, 在PC上開啟Odin3 刷機軟體, 因為沒有PIT檔, 所以Re-partition不要打勾, 在Auto Reboot, F. Reset Time打勾. 切記沒有pit檔時, 如果Re-partition打勾, 就會刷機失敗.
- PDA選P1000ZTJK1-REV03-ALL-CL712217.tar.md5
- PHONE選MODEM_P1000ZTJL1_REV_00_CL614387.tar.md5
- CSC選GT-P1000-CSC-BRIJJ1.tar.md5
- 在Tab同時壓下”音量下鍵”+”開機鍵”,進入”Download mode”, 然後將Tab接上電腦USB
- 等到Odin3抓到COM port後(COM port #視電腦而不同), 按Start開始刷機, 過2-3分鐘後就刷好了.
- 刷機完成出現PASS後, Tab跟電腦斷開, 再做一次hard reset *2767*3855#, reset後輸入*#1234#來確認升級後的版本
8. 刷好ZTJL1台灣open版後的圖如下:
- 電話 *#1234#, 查詢升級後的版本
- 關於手機的圖, 基頻是ZTJL1
- 首頁的圖, 沒有中華電Hami widget
- 程式頁面, 上方已經沒有Hami的widget
- 點Samsung Apps出現有9個apps可以下載, 跟刷ZUJK1一樣
9. 程式及資料回復 - 刷好新firmware後, 把外部SD卡插回Tab上, root Tab(使用z4root), 從market下載Titanium Backup免費版安裝, 把”備份資料夾名稱”改到外部SD卡的TitaniumBackup資料夾, 然後按“備份/還原”, 就會列出所有已經備份的程式, 找到你要還原的程式, 輕輕點擊就可以把程式及資料安裝還原回去.
以上是Tab初學者對刷機的研究及實作分享, 大家鼓勵鼓勵.
---------------------------------
12/22補充: 其實是可以直接刷到ZTJL1, 不用中間多刷ZUJK1的. 不過直接刷ZTJL1時, 要用刷ZUJK1的方式.
12/23補充1: 刷完後, 感覺使用上差別不大, 跑Quadrant Standard 是1012, 可能要OCLF後才會更快(arickwu大的分數2244), 重點是 Samsung Apps 終於可以下載遊戲 NFS Shift, 跟NOVA, 這可是免費的.
12/23補充2: 看 macleod 大回文提醒, 及參考 XDA 上 i9000 刷機 efs 備份 的貼文, 最好先備份Tab上 efs 資料夾到外部SD卡上, 以免發生刷機失敗 imei 碼不見的情形. 我自己刷機前是沒有做, 還好 imei 還在. 亡羊補牢, 趕快做備份, 步驟如下:
- 電話打 *#06#, 會顯示imei碼, 一共15碼.
- Tab要root, 到 market 下載 rootexplorer, 或是對岸漢化後叫 R.E.管理器安裝
- 在根目錄下就會看到 efs 資料夾, 按 efs 久一些, 會出現選項, 選copy, 然後下拉到 sdcard 資料夾下, external_sd 資料夾, 點 paste, 就會copy到外部SD卡上.
12/23補充3: 預備安裝OCLF, 讓Tab操作更順. 可到 此 blog , 參考安裝過程, 也還蠻簡單的.
- 在先安裝好Ext2 tools後, 要再按Available做第二步OCLF安裝, 要等幾分鐘, Tab會自動重啟.
- 我安裝後跑 Quadrant Standard, 效能分數由安裝前是1012, 提高到2083.
- 如果以後還要再重新刷機, 需要記得先把 OCLF 反安裝才能去刷機
2011年2月16日 星期三
Linux without rescan disk
| powered by |
![]() |
Vmware Linux Guest Add a New Hard Disk Without Rebooting Guest
by Vivek Gite on July 18, 2009 · 23 comments
As a system admin, I need to use additional hard drives for to provide more storage space or to separate system data from user data. This procedure, adding physical block devices to virtualized guests, describes how to add a hard drive on the host to a virtualized guest using VMWare software running Linux as guest.
It is possible to add or remove a SCSI device explicitly, or to re-scan an entire SCSI bus without rebooting a running Linux VM guest. This how to is tested under Vmware Server and Vmware Workstation v6.0 (but should work with older version too). All instructions are tested on RHEL, Fedora, CentOS and Ubuntu Linux guest / hosts operating systems.
Step # 1: Add a New Disk To Vm Guest
First, you need to add hard disk by visiting vmware hardware settings menu.
Click on VM > Settings
Alternatively you can press CTRL + D to bring settings dialog box.
Click on Add+ to add new hardware to guest:
Select hardware type Hard disk and click on Next
Select create a new virtual disk and click on Next
Set virtual disk type to SCSI and click on Next
Set maximum disk size as per your requirements and click on Next
Finally, set file location and click on Finish.
Step # 2: Rescan the SCSI Bus to Add a SCSI Device Without rebooting the VM
A rescan can be issued by typing the following command:echo "- - -" > /sys/class/scsi_host/host#/scan
fdisk -l
tail -f /var/log/message
Sample outputs:
Replace host# with actual value such as host0. You can find scsi_host value using the following command:
# ls /sys/class/scsi_host2010年12月1日 星期三
NTFS comparison table
NTFS vs FAT
| Criteria | NTFS5 | NTFS | exFAT | FAT32 | FAT16 | FAT12 |
| Operating System | Windows 2000 | Windows NT | Windows CE 6.0 | DOS v7 and higher | DOS | DOS |
|
| ||||||
| Limitations | ||||||
| Max Volume Size | 264 clusters minus 1 cluster | 232 clusters minus 1 cluster | 128PB | 32GB for all OS. | 2GB for all OS. | 16MB |
| Max Files on Volume | 4,294,967,295 (232-1) | 4,294,967,295 (232-1) | Nearly Unlimited | 4194304 | 65536 | |
| Max File Size | 264 bytes (16 ExaBytes) | 244 bytes (16 TeraBytes) | 16EB | 4GB minus 2 Bytes | 2GB (Limit Only | 16MB (Limit Only |
| Max Clusters Number | 264 clusters minus 1 cluster | 232 clusters minus 1 cluster | 4294967295 | 4177918 | 65520 | 4080 |
| Max File Name Length | Up to 255 | Up to 255 | Up to 255 | Up to 255 | Standard - 8.3 | Up to 254 |
|
| ||||||
| File System Features | ||||||
| Unicode File Names | Unicode | Unicode | Unicode | System | System | System |
| System Records Mirror | MFT Mirror File | MFT Mirror File | No | Second Copy of FAT | Second Copy of FAT | Second Copy of FAT |
| Boot Sector Location | First and Last Sectors | First and Last Sectors | Sectors 0 to 11 | First Sector and | First Sector | First Sector |
| File Attributes | Standard and Custom | Standard and Custom | Standard Set | Standard Set | Standard Set | Standard Set |
| Alternate Streams | Yes | Yes | No | No | No | No |
| Compression | Yes | Yes | No | No | No | No |
| Encryption | Yes | No | No | No | No | No |
| Object Permissions | Yes | Yes | Yes | No | No | No |
| Disk Quotas | Yes | No | No | No | No | No |
| Sparse Files | Yes | No | No | No | No | No |
| Reparse Points | Yes | No | No | No | No | No |
| Volume Mount Points | Yes | No | No | No | No | No |
|
| ||||||
| Overall Performance | ||||||
| Built-In Security | Yes | Yes | Yes | No | No | No |
| Recoverability | Yes | Yes | Yes | No | No | No |
| Performance | Low on small volumes | Low on small volumes | High | High on small volumes | Highest on small volumes | High |
| Disk Space Economy | Max | Max | Max | Average | Minimal on large volumes | Max |
| Fault Tolerance | Max | Max | Yes | Minimal | Average | Average |
2010年11月25日 星期四
Create HPUX boot CD/DVE
On a system with a CD/DVD writer and the same version of Ignite-UX as on your tape, execute
the following command (iso_directory is the target directory for the .iso media file and
the -r option specifies the release, such as B.11.23 or B.11.31):
# make_media_install -r B.11.31 -m iso_directory
Avamar Oracle Can not view on the Backup console
2. make sure the oratab locate in the /vat/opt/oracle
3. Add the environment parameters
export LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:$ORACLE_HOME/lib: /opt/AVMRclnt/lib
4. run the /opt/AVMRclnt/bin/avoacle --browse
RMAN Archivelog crosscheck
$ rman target /
Recovery Manager: Release 9.2.0.4.0 - 64bit Production
Copyright (c) 1995, 2002, Oracle Corporation. All rights reserved.
connected to target database: AVATAR2 (DBID=2480694409)
當archive有刪除的時候要使用,RMAN 的備份才會可以備archive log,之後要設定incarnation numner , list incarnation ,set incarnation
RMAN> crosscheck archivelog all;
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=25 devtype=DISK
validation failed for archived log
archive log filename=/opt/oracle/oradata/avatar2/archive/1_2714.dbf recid=2702 stamp=545107659
validation failed for archived log
archive log filename=/opt/oracle/oradata/avatar2/archive/1_2715.dbf recid=2703 stamp=545108268
...........
validation failed for archived log
archive log filename=/opt/oracle/oradata/avatar2/archive/1_2985.dbf recid=2973 stamp=545399327
validation succeeded for archived log
Crosschecked 278 objects
2.使用delete expired archivelog all 命令删除所有過期日誌檔
RMAN> delete expired archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=12 devtype=DISK
List of Archived Log Copies
Key Thrd Seq S Low Time Name
------- ---- ------- - --------- ----
376 1 2714 X 23-NOV-04 =/opt/oracle/oradata/avatar2/archive/1_2714.dbf
.....
RMAN> report obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
Report of obsolete backups and copies
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set 125 01-NOV-04
Backup Piece 125 01-NOV-04 /data1/oracle/orabak/full_1_541045804
Backup Set 131 04-NOV-04
Backup Piece 131 04-NOV-04 /data1/oracle/orabak/full_AVATAR2_20041104_131
....
Backup Set 173 06-DEC-04
Backup Piece 173 06-DEC-04 /data1/oracle/orabak/full_AVATAR2_20041206_173
Backup Set 179 11-DEC-04
Backup Piece 179 11-DEC-04 /data1/oracle/orabak/arch544588206.arc
.....
Backup Piece 189 17-DEC-04 /data1/oracle/orabak/arch545106606.arc
Backup Set 190 17-DEC-04
Backup Piece 190 17-DEC-04 /data1/oracle/orabak/arch545106665.arc
Backup Set 191 20-DEC-04
Backup Piece 191 20-DEC-04 /data1/oracle/orabak/arch_AVATAR2_20041220_194
Archive Log 2973 20-DEC-04 /opt/oracle/oradata/avatar2/archive/1_2985.dbf
Archive Log 2971 20-DEC-04 /opt/oracle/oradata/avatar2/archive/1_2984.dbf
.....
Archive Log 2705 17-DEC-04 /opt/oracle/oradata/avatar2/archive/1_2717.dbf
Archive Log 2704 17-DEC-04 /opt/oracle/oradata/avatar2/archive/1_2716.dbf
Archive Log 2703 17-DEC-04 /opt/oracle/oradata/avatar2/archive/1_2715.dbf
Archive Log 2702 17-DEC-04 /opt/oracle/oradata/avatar2/archive/1_2714.dbf
使用delete obsolete命令删除過期備份檔:
RMAN> delete obsolete;
RMAN retention policy will be applied to the command
RMAN retention policy is set to redundancy 1
using channel ORA_DISK_1
Deleting the following obsolete backups and copies:
Type Key Completion Time Filename/Handle
-------------------- ------ ------------------ --------------------
Backup Set 125 01-NOV-04
Backup Piece 125 01-NOV-04 /data1/oracle/orabak/full_1_541045804
....
Archive Log 2704 17-DEC-04 /opt/oracle/oradata/avatar2/archive/1_2716.dbf
Archive Log 2703 17-DEC-04 /opt/oracle/oradata/avatar2/archive/1_2715.dbf
Archive Log 2702 17-DEC-04 /opt/oracle/oradata/avatar2/archive/1_2714.dbf
Do you really want to delete the above objects (enter YES or NO)? yes
deleted backup piece
backup piece handle=/data1/oracle/orabak/full_AVATAR2_20041206_173 recid=173 stamp=544156241
.....
deleted archive log
archive log filename=/opt/oracle/oradata/avatar2/archive/1_2715.dbf recid=2703 stamp=545108268
deleted archive log
archive log filename=/opt/oracle/oradata/avatar2/archive/1_2714.dbf recid=2702 stamp=545107659
Deleted 286 objects
RMAN> crosscheck archivelog all;
released channel: ORA_DISK_1
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=19 devtype=DISK
specification does not match any archive log in the recovery catalog
2010年8月25日 星期三
Oracle 11gR2 new feature
1.5.1.1 Flashback Data Archive Support for DDLs
Oracle Database 11g Release 2 (11.2) users can now use most DDL commands on tables that are being tracked with Flashback Data Archive. This includes:
-
Add, Drop, Rename, Modify Column
-
Drop, Truncate Partition
-
Rename, Truncate Table
-
Add, Drop, Rename, Modify Constraint
For more complex DDL (for example, upgrades and split table), the Disassociate and Associate PL/SQL procedures can be used to temporarily disable Total Recall on specified tables. The Associate procedure enforces schema integrity after association; the base table and history table schemas must be the same.
This feature makes it much easier to use the Total Recall option with complex applications that require the ability to modify the schema.
1.5.1.2 Instance Caging
Instance Caging allows the DBA to limit the CPU usage of an Oracle instance by setting the CPU_COUNT initialization parameter and enabling CPU resource management.
With Instance Caging, users can partition CPU resources among multiple instances running on a server to ensure predictable performance.
