Database Info

HTC EVO 4G LTE updated to 1.22.651.3 ?

Anyone Rooted update to the new HTC EVO 4G LTE updated to 1.22.651.3 ?

gomfam said:
Anyone Rooted update to the new HTC EVO 4G LTE updated to 1.22.651.3 ?
Click to expand...
Click to collapse
I have been trying to update since last night to no avail... I keep getting a failure notice "Error Flashing zip /sdcard/ext_sd/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.652.3-1.13" once I try to install it with the Team recovery app.

Cybnex said:
I have been trying to update since last night to no avail... I keep getting a failure notice "Error Flashing zip /sdcard/ext_sd/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.652.3-1.13" once I try to install it with the Team recovery app.
Click to expand...
Click to collapse
I was finally able to update

gomfam said:
I was finally able to update
Click to expand...
Click to collapse
How did you do it. I am unable to update

I'm with you guys. When I try to update I get this from TeamWinRecovery's error log:
/sdcard/Download/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3-1.13.651.1_release_268352pdwvnjlt5q0w5qsi.zip ...
Finding update package...
I:Update location: /tmp/sideload/package.zip
Opening update package...
Installing update...
script aborted: assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" ,
"SPCS_001") == "t"
assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" , "22222222" , "33333333" , "44444444" , "55555555" , "66666666" , "77777777" , "88888888" , "99999999" , "SPCS_001") == "t"
E:Error in /tmp/sideload/package.zip
(Status 7)
* Verifying filesystems...
I:=> Let's update filesystem types via verifyFst aka blkid.
* Verifying partition sizes...
+----------+-----------------------------+--------+----------+----------+---+---+
| Mount | Block Device | fst | Size(KB) | Used(KB) | M | B |
+----------+-----------------------------+--------+----------+----------+---+---+
| | | | 0 | 0 | 0 | u |
| system | /dev/block/mmcblk0p35 | ext4 | 1277951 | 926668 | 1 | f |
| data | /dev/block/mmcblk0p37 | ext4 | 2260991 | 550776 | 1 | f |
| boot | /dev/block/mmcblk0p21 | emmc | 16384 | 16384 | 0 | i |
| recovery | /dev/block/mmcblk0p22 | emmc | 16383 | 16383 | 0 | i |
| cache | /dev/block/mmcblk0p36 | ext4 | 229375 | 4260 | 1 | f |
| sdcard2 | /dev/block/mmcblk1p1 | vfat | 7768064 | 4882560 | 1 | n |
| sdcard | /dev/block/mmcblk0p38 | vfat | 10418176 | 2442368 | 1 | n |
| andsec | /sdcard | vfat | 32 | 32 | 0 | f |
| sd-ext | /dev/block/mmcblk1p2 | ext4 | 0 | 0 | 1 | f |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
| | | | 0 | 0 | 0 | n |
+----------+-----------------------------+--------+----------+----------+---+---+
Error flashing zip '/sdcard/Download/OTA_JEWEL_CL_ICS_40_Sprint_WWE_1.22.651.3-1.13.651.1_release_268352pdwvnjlt5q0w5qsi.zip'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'

The best option right now is to download and flash either the odexed or deodexed version of the Rooted Stock ROM, which can be found here on xda - http://forum.xda-developers.com/showthread.php?t=1766628

[Q] Factory Mode ?

Hey Guys! I was wondering what the heck factory mode is because every time my phone turns on it always starts up with it. I have no lock screen and when I hold the home button it pretty much just powers of without any confirmation. Anyone know how to get out of it? I have been stuck on this got a while, searching everywhere and I already got into trouble because if the power off sound going on in my bag.
Extra Info:
Device is working. Stock Rom. If an sdcard is needed I have a 16gb one.
On the hsome screen it shows the system information. No WiFi.

Have you done anything at all to the phone or is it stock? Root, etc., you know what I mean.
Sent from my SCH-I535 using xda premium

The problem is in the data contained in the file "/efs/FactoryApp/factorymode"
This may seem counter-intuitive, but the proper value is "ON". (without the quotes)
I think you'll need to root to be able to edit it.
EDIT: I ought to say this is my best guess - I haven't seen this problem myself and the stuff I found about this related to a different variant of the GS3 than ours.

x-y-no said:
The problem is in the data contained in the file "/efs/FactoryApp/factorymode"
This may seem counter-intuitive, but the proper value is "ON". (without the quotes)
I think you'll need to root to be able to edit it.
EDIT: I ought to say this is my best guess - I haven't seen this problem myself and the stuff I found about this related to a different variant of the GS3 than ours.
Click to expand...
Click to collapse
Thanks Bro! This seemed to work for me and my friend who's in sprint.

Excellent! Glad it worked for you.

Not working for me
Unfortunately this method:
echo -n ON > /efs/FactoryApp/factorymode
didn't work for me on my SCH-i535 (Verizon, US, latest stock jellybean, rooted of course). I solved an earlier problem where I had to rebuild my EMEI since I hosed my efs directory and did not have a backup - So phone and data works but I'm still stuck in Factory Mode. updated factorymode every which way possible. Here is a directory snapshot of my /efs folder (if someone who has a virgin efs could compare I would greatly appreciate it (some file and dir names obscured for security purposes)
/efs
|-- FactoryApp
| |-- baro_delta
| |-- factorymode
| |-- factorymode.bak
| |-- fdata
| |-- hist_nv
| |-- hw_ver
| |-- keystr
| |-- prepay
| |-- serial_no
| `-- test_nv
|-- bluetooth
| `-- bt_addr
|-- drm
| |-- dxhdcp2
| | `-- acGS***************e1aFGgUxE_
| | |-- et********************hEQM_
| | `-- zttE**************************RZM_
| |-- h2k
| | `-- 8tjf**************************fZTU_
| | |-- HA*******************************hE_
| | `-- S*****************************FM_
| |-- playready
| | |-- 00002.PRV
| | |-- EFPJyjN***********************S8_
| | | |-- -lndc*******************************QU_
| | | |-- 13*******************************9Pvc_
| | | |-- 2a8*******************************yqY_
| | | |-- 39*******************************Bss_
| | | |-- 39j-*******************************FY_
| | | |-- A*******************************zFwI_
| | | |-- fi*******************************Ms_
| | | |-- g2*******************************ij5w_
| | | |-- m*******************************u4M_
| | | |-- o*******************************FYw+ik_
| | | |-- sA*******************************a6Kc_
| | | |-- wH*******************************Dz4_
| | | `-- xm*******************************OFiI_
| | |-- bdevcert.dat
| | |-- devcert.dat
| | `-- license.hds
| `-- widevine
| `-- 5*******************************2K5InM_
| |-- D3*******************************434rc_
| `-- RX*******************************Bq8_
|-- h2k.dat
|-- imei
| `-- mps_code.dat
|-- nv.log
|-- sensors
|-- wifi
`-- wv.keys
14 directories, 38 files

EDITED with ext 4 [script] Wiping script for formating 2 and 3 partitions

Here i made a script that formates the partitions on mobile with script.......
so as for aosp roms like cm series (9,10,10.1)
2 partitions as per the instructions of the @cute_prince is done it doesnt matter of the sequence of the order sd>sd-data>sd-cache OR sd>sd-cache>sd-data .......................it just formate 2nd and 3rd partition on sd card......
as the sense roms requires 4 partitions it should have 4 partitions...
script for sense also formates 2nd,3rd,4th partitions......
FOR SENSE 4.1 ROMS ANOTHER SCRIPT NAMED FOR SENSE 4.1 USE IT FOR FLASHING....
NOTE:------------>Do remember the script of sense will format partitions as EXT2 and script for aosp roms will format partitions as EXT4 and sense 4.1 sctript will also format as EXT4​
i have made script for formating the sd partitions as we cant format it from any recovery......
ENJOY AND FLASH THE RIGHT 1..........

keval_104 said:
Here i made a script that formates the partitions on mobile with script.......
so as for aosp roms like cm series (9,10,10.1)
2 partitions as per the instructions of the @cute_prince is done it doesnt matter of the sequence of the order sd>sd-data>sd-cache OR sd>sd-cache>sd-data .......................it just formate 2nd and 3rd partition on sd card......
as the sense roms requires 4 partitions it should have 4 partitions...
script for sense also formates 2nd,3rd,4th partitions......
NOTE:------------>Do remember the script of sense will format partitions as EXT2 and script for aosp roms will format partitions as EXT4​
i have made script for formating the sd partitions as we cant format it from any recovery......
ENJOY AND FLASH THE RIGHT 1..........
Click to expand...
Click to collapse
@keval_104 make one more script to format the sd-ext partitions as ext4..It is required for sense 4.1 rom
Anyway good work. Makes the life of many users more easy.

keval_104 said:
Here i made a script that formates the partitions on mobile with script.......
Click to expand...
Click to collapse
Aaaa,great..I'll wait for it .. :victory:
Bro ,great work :good:

Hey keval do you mean that this script is for partitioning the sdcard for cute prince's new oc method.....????
That this script skips the steps of partitioning the sdcard through PC .....!! ???
If that's what this is them you are awesome........!
If not the then I don't get you.....!
Sent from my HTC Explorer A310e using xda premium

electron.hTcpico said:
Hey keval do you mean that this script is for partitioning the sdcard for cute prince's new oc method.....????
That this script skips the steps of partitioning the sdcard through PC .....!! ???
If that's what this is them you are awesome........!
If not the then I don't get you.....!
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
It is for formating the partitions directly from the mobile....not for partitioning.....i m currently working for the partitioning....

@keval_104
When I go flash script for aosp, I got error ***Formatting Sd-data script aborted(no error message)
E: error executing updater binary...
any help ?

marko94 said:
@keval_104
When I go flash script for aosp, I got error ***Formatting Sd-data script aborted(no error message)
E: error executing updater binary...
any help ?
Click to expand...
Click to collapse
Bro just change the binary files from any rom working....and rezip it.......
Sent from my HTC Explorer A310e using xda premium

very good tool for us
it make the procedure more convinient

keval_104 said:
Bro just change the binary files from any rom working....and rezip it.......
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
Yeah, i do that,and same error again
but now i got this error
***Formatting Sd-data script aborted
format() expects 5 args got 3
E: error executing updater binary...

okeys bro.....
marko94 said:
Yeah, i do that,and same error again
but now i got this error
***Formatting Sd-data script aborted
format() expects 5 args got 3
E: error executing updater binary...
Click to expand...
Click to collapse
bro updated try the new aosp 1......tested working for me....

keval_104 said:
bro updated try the new aosp 1......tested working for me....
Click to expand...
Click to collapse
Yeah,it works..
Thanks bro

@keval_104 you must create one more script for formatting the partitions like my new method.http://forum.xda-developers.com/showpost.php?p=39996481&postcount=3
Two ext2 partitions... :silly:

I get this error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
. .
. .
. .
..
. .
. .
. .
. .
*****>Formatting *SD-data* partition<*****
format: unsupported fs_type "ext4" partition_type "EMMC"script aborted (no error message)
script aborted (no error message)E:Error in /sdcard/xda_download/wipe script for aosp.zip
(Status 7)
Error flashing zip '/sdcard/xda_download/wipe script for aosp.zip'
Updating partition details...
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /sdcard/recovery.log
Using Twrp 2.4.1.0 recovery.
What can I do?
Sent from my HTC Explorer A310e using xda app-developers app

wmapt said:
I get this error:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
. .
. .
. .
..
. .
. .
. .
. .
*****>Formatting *SD-data* partition<*****
format: unsupported fs_type "ext4" partition_type "EMMC"script aborted (no error message)
script aborted (no error message)E:Error in /sdcard/xda_download/wipe script for aosp.zip
(Status 7)
Error flashing zip '/sdcard/xda_download/wipe script for aosp.zip'
Updating partition details...
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /sdcard/recovery.log
Using Twrp 2.4.1.0 recovery.
What can I do?
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
Bro which script u flashed???and which ext partition type u have???
abhinavthms said:
@keval_104 you must create one more script for formatting the partitions like my new method.http://forum.xda-developers.com/showpost.php?p=39996481&postcount=3
Two ext2 partitions... :silly:
Click to expand...
Click to collapse
Bro i will make 1.....and the one made for sense 4.0a can also work for it it will not affect any thing......it can b used i have tested.........
Sent from my HTC Explorer A310e using xda premium

keval_104 said:
Bro which script u flashed???and which ext partition type u have???
See in logs .... aosp.
Partition: primary, fat-ext4-ext4.
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse

Good job bro
Sent from my HTC Explorer A310e using xda premium

wmapt said:
keval_104 said:
Bro which script u flashed???and which ext partition type u have???
See in logs .... aosp.
Partition: primary, fat-ext4-ext4.
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
Bro try to format it with ext4 from computer 1s...cause it display fs_type unsupported....or backup 1s and repartition 1 or try gparted from ubuntu for formating.....
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse

keval_104 said:
wmapt said:
Bro try to format it with ext4 from computer 1s...cause it display fs_type unsupported....or backup 1s and repartition 1 or try gparted from ubuntu for formating.....
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
Same error.
I will try gparted tomorrow.
See logs:
Starting TWRP 2.4.1.0 on Sun Jun 30 18:15:52 2013
I:Single storage only.
I:No internal storage defined.
I:No storage defined, defaulting to /sdcard.
TW_DEFAULT_EXTERNAL_STORAGE := true
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file'
Starting the UI...Pixel format: 320x480 @ 32bpp
Pixel format: BGR_565
framebuffer: fd 3 (320 x 480)
=> Linking mtab
=> Processing recovery.fstab
Irocessing '/boot'
Irocessing '/cache'
Irocessing '/data'
Irocessing '/misc'
Irocessing '/recovery'
Irocessing '/sdcard'
I:Created '/sdcard' folder.
I:Created '/and-sec' folder.
I:Creating .android_secure: /sdcard/.android_secure
Irocessing '/system'
Irocessing '/sd-ext'
I:Created '/sd-ext' folder.
Irocessing '/devlog'
Updating partition details...
I:'/sd-ext' was 'ext3' now set to 'ext4'
I:Unmounting main partitions...
Partition Logs:
/boot | /dev/block/mtdblock2 | Size: 4MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mtdblock2
Display_Name: boot
Backup_Path: /boot
Backup_Name: boot
Current_File_System: mtd
Fstab_File_System: mtd
MTD_Name: boot
Backup_Method: flash_utils
/cache | /dev/block/mtdblock4 | Size: 59MB Used: 1MB Free: 57MB Backup Size: 1MB
Flags: Can_Be_Wiped Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mtdblock4
Display_Name: Cache
Backup_Path: /cache
Backup_Name: cache
Current_File_System: yaffs2
Fstab_File_System: yaffs2
MTD_Name: cache
Backup_Method: files
/data | /dev/block/mtdblock5 | Size: 158MB Used: 138MB Free: 19MB Backup Size: 138MB
Flags: Can_Be_Wiped Wipe_During_Factory_Reset Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mtdblock5
Display_Name: Data
Backup_Path: /data
Backup_Name: data
Current_File_System: yaffs2
Fstab_File_System: yaffs2
MTD_Name: userdata
Backup_Method: files
/misc | /dev/block/mtdblock0 | Size: 0MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mtdblock0
Display_Name: misc
Backup_Path: /misc
Backup_Name: misc
Current_File_System: mtd
Fstab_File_System: mtd
MTD_Name: misc
Backup_Method: flash_utils
/recovery | /dev/block/mtdblock1 | Size: 5MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mtdblock1
Display_Name: recovery
Backup_Path: /recovery
Backup_Name: recovery
Current_File_System: mtd
Fstab_File_System: mtd
MTD_Name: recovery
Backup_Method: flash_utils
/sdcard | /dev/block/mmcblk0p1 | Size: 14288MB Used: 482MB Free: 13805MB Backup Size: 0MB
Flags: Can_Be_Wiped Removable IsPresent Has_Android_Secure Is_Storage
Symlink_Path: /sdcard/.android_secure
Symlink_Mount_Point: /and-sec
Primary_Block_Device: /dev/block/mmcblk0p1
Alternate_Block_Device: /dev/block/mmcblk0
Display_Name: sdcard
Backup_Path: /and-sec
Backup_Name: and-sec
Storage_Path: /sdcard
Current_File_System: exfat
Fstab_File_System: exfat
Backup_Method: files
/system | /dev/block/mtdblock3 | Size: 236MB Used: 213MB Free: 22MB Backup Size: 213MB
Flags: Can_Be_Wiped Wipe_Available_in_GUI IsPresent
Primary_Block_Device: /dev/block/mtdblock3
Display_Name: System
Backup_Path: /system
Backup_Name: system
Current_File_System: yaffs2
Fstab_File_System: yaffs2
MTD_Name: system
Backup_Method: files
/sd-ext | /dev/block/mmcblk0p2 | Size: 610MB Used: 4MB Free: 606MB Backup Size: 4MB
Flags: Can_Be_Wiped Wipe_During_Factory_Reset Wipe_Available_in_GUI Removable IsPresent
Primary_Block_Device: /dev/block/mmcblk0p2
Display_Name: SD-Ext
Backup_Path: /sd-ext
Backup_Name: sd-ext
Current_File_System: ext4
Fstab_File_System: ext3
Backup_Method: files
/devlog | /dev/block/mtdblock6 | Size: 10MB
Flags: IsPresent
Primary_Block_Device: /dev/block/mtdblock6
Display_Name: devlog
Backup_Path: /devlog
Backup_Name: devlog
Current_File_System: mtd
Fstab_File_System: mtd
MTD_Name: devlog
Backup_Method: flash_utils
I:Loading package: TWRP (/script/ui.xml)
I:Loading package: TWRP (/sdcard/TWRP/theme/ui.zip)
I:Loading package: TWRP (/res/ui.xml)
I:Loading resources...
I:Loading variables...
I:Loading pages...
I:Loading page main
I:Loading page main2
I:Loading page install
I:Loading page flash_confirm
I:Loading page flash_zip
I:Loading page flash_done
I:Loading page clear_vars
I:Loading page confirm_action
I:Loading page action_page
I:Loading page action_complete
I:Loading page filecheck
I:Loading page rebootcheck
I:Loading page wipe
I:Loading page backup
I:Loading page backupname1
I:Loading page backupname2
I:Loading page backup_run
I:Loading page restore
I:Unable to open '/sdcard/TWRP/BACKUPS/SH1AMVN05750'
I:Loading page restore_select
I:Loading page renamebackup
I:Loading page restore_run
I:Loading page mount
I:Loading page usb_mount
I:Loading page usb_umount
I:Loading page reboot
I:Loading page settings
I:Loading page timezone
I:Loading page advanced
I:Loading page partsdcard
I:Loading page htcdumlock
I:Loading page lock
I:Loading page filemanagerlist
I:Loading page filemanageroptions
I:Loading page choosedestinationfolder
I:Loading page filemanagerrenamefile
I:Loading page filemanagerrenamefolder
I:Loading page filemanagerchmod
I:Loading page filemanagerconfirm
I:Loading page filemanageracction
I:Loading page decrypt
I:Loading page trydecrypt
I:Loading page terminalfolder
I:Loading page terminalcommand
I:Loading page sideload
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Switching packages (TWRP)
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.boot.pagesize=2048
ro.boot.lb=1
ro.boot.baseband=1.12.82.08
ro.boot.cid=HTC__032
ro.boot.devicerev=2
ro.boot.batt_poweron=good_battery
ro.boot.carrier=HTC-EastEurope
ro.boot.mid=PJ0310000
ro.boot.keycaps=qwerty
ro.boot.mode=recovery
ro.boot.serialno=SH1AMVN05750
ro.boot.bootloader=1.04.0000
ro.boot.nledhw=1
ro.serialno=SH1AMVN05750
ro.bootmode=recovery
ro.baseband=1.12.82.08
ro.bootloader=1.04.0000
ro.hardware=pico
ro.revision=128
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
persist.sys.usb.config=mass_storage,adb
persist.service.adb.enable=1
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
ro.build.id=JZO54K
ro.build.display.id=cm_pico-userdebug 4.1.2 JZO54K eng.bhargz.20130218.095712 test-keys
ro.build.version.incremental=eng.bhargz.20130218.095712
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Mon Feb 18 09:58:26 IST 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=bhargz
ro.build.host=the-punisher
ro.build.tags=test-keys
ro.product.model=HTC Explorer A310e
ro.product.brand=htc_europe
ro.product.name=pico
ro.product.device=pico
ro.product.board=pico
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x27a
ro.build.product=pico
ro.build.description=cm_pico-userdebug 4.1.2 JZO54K eng.bhargz.20130218.095712 test-keys
ro.build.fingerprint=htc_europe/htc_pico/pico:2.3.5/GRJ90/207463.1:user/release-keys
ro.build.characteristics=default
ro.cm.device=pico
rild.libpath=/system/lib/libhtc_ril.so
rild.libargs=-d /dev/smd0
rilswitch.vendorlibpath=/system/lib/libhtc_ril.so
ril.subscription.types=NV,RUIM
ro.baseband.arch=msm
ro.ril.ecc.HTC-GCC=999,112,997
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-Dutch=112
ro.ril.ecc.HTC-SPA=112, 911,112, 911
ro.ril.ecc.HTC-FRA=112,911
ro.ril.ecc.HTC-ITA=112,911
ro.ril.ecc.HTC-EastEurope=112
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.hsdpa.category=8
ro.ril.hsxpa=1
ro.ril.fast.dormancy.rule=1
ro.ril.disable.fd.plmn.prefix=23402,23410,23411,23420,27202
ro.ril.enable.managed.roaming=1
ro.ril.gprsclass=10
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
ro.telephony.ril.v3=signalstrength,singlepdp,skipbrokendatacall
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.update.acoustic.table=1
ro.ril.avoid.pdp.overlap=1
ro.telephony.default_network=0
ro.ril.enable.sdr=1
ro.ril.enable.amr.wideband=1
ro.ril.enable.r8fd=0
ro.ril.enable.pre_r8fd=1
ro.ril.fd.pre_r8_tout.scr_off=2
ro.ril.fd.pre_r8_tout.scr_on=3
ro.ril.fd.r8_tout.scr_off=0
ro.ril.fd.r8_tout.scr_on=0
wifi.supplicant_scan_interval=180
wifi.interface=eth0
wifi.softap.interface=eth0
ro.sf.lcd_density=160
view.fading_edge_length=8
view.touch_slop=15
view.minimum_fling_velocity=25
view.scroll_friction=0.008
ro.opengles.version=131072
ro.workaround.noautofocus=1
ro.media.dec.jpeg.memcap=20000000
ro.vendor.extension_library=/system/lib/libqc-opt.so
DEVICE_PROVISIONED=1
htc.audio.alc.enable=1
htc.audio.swalt.enable=1
dalvik.vm.heapsize=72m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
debug.composition.7x27A.type=mdp
media.stagefright.enable-player=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
ro.use_data_netmgrd=true
persist.data.ds_fmc_app.mode=0
ro.staticwallpaper.pixelformat=RGB_565
ro.max.fling_velocity=4000
httplive.enable.discontinuity=true
dev.pm.dyn_samplingrate=1
dev.pm.dyn_sample_period=700000
com.qc.hardware=true
com.qc.hdmi_out=false
debug.camcorder.disablemeta=0
debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.gr.numframebuffers=2
debug.qc.hardware=true
debug.enabletr=false
debug.hwui.render_dirty_regions=false
debug.sf.hw=1
ro.media.enc.jpeg.quality=100
ro.setupwizard.mode=OPTIONAL
ro.setupwizard.enable_bypass=1
ro.media.dec.aud.wma.enabled=1
ro.media.dec.vid.wmv.enabled=1
ro.config.sync=yes
ro.phone_storage=0
ro.hw_plat=7x27a
ro.HOME_APP_ADJ=1
ro.PERCEPTIBLE_APP_ADJ=0
ro.kernel.android.checkjni=0
dalvik.vm.verify-bytecode=false
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10-20130218-UNOFFICIAL-pico
ro.modversion=10-20130218-UNOFFICIAL-pico
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Deneb.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
ro.product.camera=pico
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.com.google.gmsversion=2.3_r6
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
ro.telephony.call_ring.multiple=false
ro.vold.umsdirtyratio=40
net.bt.name=Android
net.change=net.bt.name
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
mtd: successfully wrote block at 0
I:Set boot command ""
I:Attempt to load settings from settings file...
I:Version number saved to '/cache/recovery/.version'
I:Switching packages (TWRP)
I:Set page: 'install'
I:Set page: 'flash_confirm'
I:Set page: 'flash_zip'
I:Set page: 'flash_zip'
Installing '/sdcard/xda_download/wipe script for aosp.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
format: unsupported fs_type "ext4" partition_type "EMMC"script aborted (no error message)
. .
. .
. .
..
. .
. .
. .
. .
*****>Formatting *SD-data* partition<*****
script aborted (no error message)E:Error in /sdcard/xda_download/wipe script for aosp.zip
(Status 7)
Error flashing zip '/sdcard/xda_download/wipe script for aosp.zip'
Updating partition details...
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /sdcard/recovery.log
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse

@keval_104: bro thanks for this script
The script works fine but it does not format the SD-DATA and SD-CACHE in ext4 format ... Coz it's not made to format ext4 partition (it's for ext2 ) .
PS:Though it will work on ext2 partition but we need ext4 partition for better performance.
Just change the ext2 in the pic attached to ext4
PS: if I am wrong please correct me
Sent from my HTC Explorer A310e using Tapatalk 4 Beta

Saumitra Yadav said:
@keval_104: bro thanks for this script
The script works fine but it does not format the SD-DATA and SD-CACHE in ext4 format ... Coz it's not made to format ext4 partition (it's for ext2 ) .
PS:Though it will work on ext2 partition but we need ext4 partition for better performance.
Just change the ext2 in the pic attached to ext4
PS: if I am wrong please correct me
Sent from my HTC Explorer A310e using Tapatalk 4 Beta
Click to expand...
Click to collapse
Ya
This script also removes sd data and sd cache names
+ formats in ext2
I tried changing it to ex4 but zip flashing failed,i am using twrp

EFS, modemst1, modemst2, fsg, backup partitions - Backup needed and what do they do?

Sorry for posting this in Android Development, but I think this is important information that many other people might want to know as well:
In addition to the EFS partition, there are several partitions on our n9005 devices that do not exist in official odin roms.
This means that they must be unique to your phone, and they might be as important to back up as the EFS folder to prevent IMEI loss or other problems (like those bootloops many people get when flashing kernels, which appear to be tied to corrupted modemst1 partitions).
These partitions are: modemst1, modemst2, fsg, fsc, backup, dbi, ddr, pad
You can see them by executing the following command:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
---
CWM does not back up EFS at all afaik, and the EFS backup tools usually only take the EFS partition while ignoring the others.
TWRP is the only one which also backs up modemst1 and modemst2 as far as I can tell. (it creates 2 additional efs backup files with 3MB in size - which is exactly the size of these partitions.)
--
From further research (this was discussed in the S3 forum) it turns out that the "fsg" and the "backup" partitions are meant to take copies of the modemst1 and modemst2 partitions - this can be done/forced by executing "reboot nvbackup" in terminal or with adb. So these partitions are meant to hold the backups of modemst1 and modemst2. But I'm not sure if our devices ship with these backups already made - the S3's apparently did not, so users had to do this backup themselves. (and/or use dd to also create image backups of these partitions)
People in the S3 forum reported that when they had corrupted modemst1 and/or modemst2 partitions (and no backup available) that while they still had their imei through EFS backup (or written to the phone with qualcomm tool) that they could only use the phone on roaming with these partitions corrupted.
---
So does anyone actually know more about this? Please lets use this thread to figure out (and then create some sort of sticky with the info) what these partitions actually do and if they need backup.
The "bootloop" fix goes as far as formatting modemst1 and modemst2 (I done it myself too in terminal before) to fix the bootloop issue. And its said that the partitions contents are just recreated then. But from which source? EFS or the fsg / backup partitions? etc.
This really needs some further investigation I think.
---
What I also did was to compare all the backups I had and see if they were the same or if they did differ.... and the weird thing is that EVERY single backup I have of my EFS folder or the modemst1 and modemst2 partitions do differ in checksum and also in binary diff.
Even the EFS folder did change over the time it seems. (partially this is caused by me editing the wifi mac ... but even before I did that the efs backups did differ from backup to backup).
But nonetheless, it seems that my phone is actually working alright. I have my imei, and I can just normally log in to my carrier network (can only test hsdpa+ though) and wifi is alright too.
So it appears that modemst1 and modemst2 indeed get recreated if they are formatted, but what about those other partitions. Unfortunately (since I only have one backup of these, made by hand) I cannot compare them to see if they also changed over the time.
--
Last but not least: modemst1, modemst2, fsg (meant to have copy of modemst1) and backup (meant to hve copy of modemst2) also differ on my device..... (can you guys who are fit in the terminal maybe also test if the partitions differ on your phones or if they are indeed copies?)
...
Would really like to understand these partitions more...

Thank you so much, always wondered what all those things meant and what they did...very informative

thanks you for making this thread.
so we can understand it.
i edited and made a windows efs backup tool for making backup and restore EFS, modemst1, modemst2.
and i will edit aroma method too.
... if we need more backup of more partitions, i will edit EFS Tool for them (dd backup/restore method)
http://forum.xda-developers.com/showpost.php?p=49460571&postcount=4

so I got some more infos:
I checked the "fsg" and "backup" partition, and they did not change over the course of all my actions. Even the partitions on the system are exactly the same as they were when I took backups. (remember: EFS and modemst1 and modemst2 constantly changed, and I could not find 2 exact copies in my backups).
So this means fsg and backup are indeed left untouched.
----
Since they are meant to hold backups of modemst1 and modemst2 which can be restored with "reboot nvrestore" I tried that as well.
But apparently they do not contain valid backups when you first get your phone (just like in the S3 case).
When I tried nvrestore the device rebooted and showed a message like "no nvbackup found" in red letters. (phone was stuck in this mode, even with forced reboot by holding down power - only pulling the battery got my device back to normal life... man was I scared when this message kept reappearing on hard reset)..
---
So in turn this means, the best thing to do when you get a new N3 (and didnt mess up modemst1 and modemst2 yet by flashing) that you should run "reboot nvbackup" in terminal.
This will fill the fsg and backup partition with valid copies of modemst1 and modemst2 which later can be restored with "reboot nvrestore".
---
Still not sure what these partitions are really about - they seem to be the "nvram" of the device (whatever that is lol) ... and I *think* there are things stored like carrier specific settings from what I understood. So simlock and netlock etc is stored there apparently. But since the note3's are all simlock free as far as I know (at least our n9005s) this should not really be important to us.
But when they are corrupted we get the bootloops.
These can be fixed by simply formatting the partitions, but I'm not 100% sure if this has any downsides yet. (aka if we need our original modemst1 and modemst2, or if it does not matter....)
ADD: I read in another post that someone lost his imei when his modemst1 got corrupted/formatted. But I can just say that I manually formatted modemst1 and modemst2 before (if you try this, back them up first though!!!!!!!) and I kept my imei and could connect phone to carrier etc. So the imei does not seem to be stored there really.
---
Someone has to know more about this, please enlighten us.....

Interesting subject...
To add bits, pit file dump:
Code:
PIT dump v1.0 by LeTama
- 30 partitions in PIT file
- Format string = [COM_TAR2MSM8974]
01|APNHLOS | 0x00002000 | 0x00007800 | 8192 | 30720 | 15360 KB | NON-HLOS.bin
02|MODEM | 0x00009800 | 0x0001CB80 | 38912 | 117632 | 58816 KB | modem.bin
03|SBL1 | 0x00026380 | 0x00000400 | 156544 | 1024 | 512 KB | sbl1.mbn
04|DBI | 0x00026780 | 0x00000040 | 157568 | 64 | 32 KB | sdi.mbn
05|DDR | 0x000267C0 | 0x00000040 | 157632 | 64 | 32 KB |
06|ABOOT | 0x00026800 | 0x00001000 | 157696 | 4096 | 2048 KB | aboot.mbn
07|RPM | 0x00027800 | 0x00000400 | 161792 | 1024 | 512 KB | rpm.mbn
08|TZ | 0x00027C00 | 0x00000400 | 162816 | 1024 | 512 KB | tz.mbn
09|PAD | 0x00028000 | 0x00005000 | 163840 | 20480 | 10240 KB |
10|PARAM | 0x0002D000 | 0x00005000 | 184320 | 20480 | 10240 KB | param.bin
11|EFS | 0x00032000 | 0x00007000 | 204800 | 28672 | 14336 KB | efs.img.ext4
12|MODEMST1 | 0x00039000 | 0x00001800 | 233472 | 6144 | 3072 KB | nvrebuild1.bin
13|MODEMST2 | 0x0003A800 | 0x00001800 | 239616 | 6144 | 3072 KB | nvrebuild2.bin
14|BOOT | 0x0003C000 | 0x00005800 | 245760 | 22528 | 11264 KB | boot.img
15|RECOVERY | 0x00041800 | 0x00006800 | 268288 | 26624 | 13312 KB | recovery.img
16|FOTA | 0x00048000 | 0x00006800 | 294912 | 26624 | 13312 KB |
17|BACKUP | 0x0004E800 | 0x000037EE | 321536 | 14318 | 7159 KB |
18|FSG | 0x00051FEE | 0x00001800 | 335854 | 6144 | 3072 KB |
19|FSC | 0x000537EE | 0x00000002 | 341998 | 2 | 1 KB |
20|SSD | 0x000537F0 | 0x00000010 | 342000 | 16 | 8 KB |
21|PERSIST | 0x00053800 | 0x00004000 | 342016 | 16384 | 8192 KB | persist.img.ext4
22|PERSDATA | 0x00057800 | 0x00004800 | 358400 | 18432 | 9216 KB | persdata.img.ext4
23|SYSTEM | 0x0005C000 | 0x00480000 | 376832 | 4718592 | 2359296 KB | system.img.ext4
24|CACHE | 0x004DC000 | 0x00096000 | 5095424 | 614400 | 307200 KB | cache.img.ext4
25|HIDDEN | 0x00572000 | 0x0000F000 | 5709824 | 61440 | 30720 KB | hidden.img.ext4
26|USERDATA | 0x00581000 | 0x00000000 | 5771264 | 0 | 0 KB | userdata.img.ext4
70|PGPT | 0x00000000 | 0x00000022 | 0 | 34 | 17 KB | pgpt.img
71|PIT | 0x00000022 | 0x00000010 | 34 | 16 | 8 KB | MSM8974.pit
72|MD5 | 0x00000032 | 0x00000020 | 50 | 32 | 16 KB | md5.img
73|SGPT | 0x03A3DFDF | 0x00000021 | 61071327 | 33 | 16 KB | sgpt.img
-----------------
- signature /trailer size = [4204]
It's showing more locations than the one exposed by kernel like pgpt /sgpt (primary/secondary gpt partition table), pit table, md5 (?).
Last, there is the rpmb partition that we can't see without knowing the access key.

genius.lizard2 said:
thanks you for making this thread.
so we can understand it.
i edited and made a windows efs backup tool for making backup and restore EFS, modemst1, modemst2.
and i will edit aroma method too.
... if we need more backup of more partitions, i will edit EFS Tool for them (dd backup/restore method)
http://forum.xda-developers.com/showpost.php?p=49460571&postcount=4
Click to expand...
Click to collapse
Thank you, worked perfectly.:good:

Please help! My device wont connect to USB

Hey guys TCB here, I need help!
I rooted my phone and unlocked it used the all in one tool kit.There is no OS installed on the mobile, I installed a rom in twrp than after it as done, it boot looped than locked up and I accidentally deleted the OS
my phone is htc one s (s4)
I can get into bootloader / fastboot menu I can get into twrp, when I connect usb it says "fastboot usb in red" in the fastboot boot loader menu so that should be connected but its not. Only time it connects is in twrp, my computer will detect "htc mtp device" it shows up fine in device manager, but after about 10 secs the device is no longer be detected and yellow ! will show over "htc mtp device" in device manager. What is weird even more is I can run certain command with adb " adb devices" tells me its connected but it wont sideload or fastboot , it just says "waiting for device". I can restart the usb by "adb usb", it will temporary install and run but 10sec or so later is disconnects and yellow! will show over "htc mtp device" in the device manager. Does anyone have an idea how to fix this? Is my phone a hard brick now?
Please help me.
Thank you very much.

TCBCSM said:
Hey guys TCB here, I need help!
I rooted my phone and unlocked it used the all in one tool kit.There is no OS installed on the mobile, I installed a rom in twrp than after it as done, it boot looped than locked up and I accidentally deleted the OS
my phone is htc one s (s4)
I can get into bootloader / fastboot menu I can get into twrp, when I connect usb it says "fastboot usb in red" in the fastboot boot loader menu so that should be connected but its not. Only time it connects is in twrp, my computer will detect "htc mtp device" it shows up fine in device manager, but after about 10 secs the device is no longer be detected and yellow ! will show over "htc mtp device" in device manager. What is weird even more is I can run certain command with adb " adb devices" tells me its connected but it wont sideload or fastboot , it just says "waiting for device". I can restart the usb by "adb usb", it will temporary install and run but 10sec or so later is disconnects and yellow! will show over "htc mtp device" in the device manager. Does anyone have an idea how to fix this? Is my phone a hard brick now?
Please help me.
Thank you very much.
Click to expand...
Click to collapse
Installing '/sdcard/Liquid-Kitkat-v3.0-NIGHTLY-d2att.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Warning: No file_contexts
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
\ ) ( )\ ) )\ )
(()/ ( ( )\ ( (()/((()/(
(_)) ((_) (_)_) /((_)(_)) (_))
| | (_) / _ \ (_))( |_ _| | \
| |__ | || (_) || || | | | | |) |
|____||_| \__\_\ \_,_||___| |___/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
<%%% Liquid-Kitkat %%%>
<%%% By LiquidSmooth %%%>
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Erasing System...
error: make_ext4fs: open: No such file or directory
longjmp botch.
E:Error in /sdcard/Liquid-Kitkat-v3.0-NIGHTLY-d2att.zip
(Status 0)
Error flashing zip '/sdcard/Liquid-Kitkat-v3.0-NIGHTLY-d2att.zip'
Updating partition details...
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'flash_done'
I:Set page: 'clear_vars'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'wipe'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
Formatting Cache using mke2fs...
I:mke2fs command: mke2fs -t ext4 -m 0 /dev/block/mmcblk0p34
mke2fs 1.41.12 (17-May-2010)
Done.
I:Recreating /cache/recovery folder.
I:Version number saved to '/cache/recovery/.version'
Updating partition details...
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'wipe'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
Wiping Dalvik Cache Directories...
Cleaned: /data/dalvik-cache...
-- Dalvik Cache Directories Wipe Complete!
Updating partition details...
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'vfat'
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'wipe'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /sdcard/recovery.log
Copied recovery log to /sdcard.
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'advanced'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'install'
I:Set page: 'main'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'clear_vars'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:fix permissions started!
I:Mount: Unable to find partition for path '/sd-ext'
Can't check permissions
after Factory Reset.
Please boot rom and try
again after you reboot into
recovery.
I:Unmounting main partitions...
Done.
I:Set page: 'action_complete'
I:Set page: 'clear_vars'
I:Set page: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /sdcard/recovery.log

http://forum.xda-developers.com/showthread.php?t=1667929
I think you can adb push the rom zip to your phone and reflash the rom after a full wipe.
Also flash boot image if you are s-on.