Develop Bugs

Stock update probs

i flashed a stock rom from shipped rom collection.. and when i updated the update was found and then it downloded and when it was installing it gave me error
Code:
We have determined that your phone may be running a modified version of its system software.
For your protection, we cannot update your phone.
Please revert back to the official HTc system software to update your phone.
if you did not modify your system software or would like help reverting your system,
please contact us via the support section at www.htc.com
why is this so?

Are you using clockworkmod? Because you must stock recovery!

vbhtt said:
Are you using clockworkmod? Because you must stock recovery!
Click to expand...
Click to collapse
ya using cwm how to gget that stock recovery?

http://forum.xda-developers.com/showthread.php?t=1431969
This Should have the option of 'return to stock recovery'

vbhtt said:
http://forum.xda-developers.com/showthread.php?t=1431969
This Should have the option of 'return to stock recovery'
Click to expand...
Click to collapse
bro i know i tried it .. the download is unavailable..
do yu have it with you? can you upload it to mediafire and sense the link?

vbhtt said:
http://forum.xda-developers.com/showthread.php?t=1431969
This Should have the option of 'return to stock recovery'
Click to expand...
Click to collapse
i flashed the recovery.img from the rom.zip got the recovery back will try update now.. i feel like a SMART ASS haha nywys thanks vbhtt

vbhtt said:
Are you using clockworkmod? Because you must stock recovery!
Click to expand...
Click to collapse
not working still getting the same eror

mhrsolanki2020 said:
not working still getting the same eror
Click to expand...
Click to collapse
You will have to return to the original System image and recovery for the update to work. The update does a system file verification before it will run.
SAMPLE
Code:
# Script Version: G2.4
mount("yaffs2", "MTD", "system", "/system");
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999");
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PG7624000") == "t");,
assert(check_mid("simple", "PG7624000") == "t");
);
assert(getprop("ro.product.device") == "marvel" ||
getprop("ro.build.product") == "marvel");
ui_print("Copying fotaBoot to /data/system for customize reload...");
mount("yaffs2", "MTD", "userdata", "/data");
package_extract_file("fotaBoot", "/data/system/fotaBoot");
ui_print("Verifying current system...");
show_progress(0.100000, 0);
assert(apply_patch_check("/system/app/AccountSyncManager.apk", "0c905b041013e66457dd8e9e3abc5a98a7aaff37", "cc881deb5a9e22c6034d4533aa16d8e59abf6124"));
set_progress(0.000434);
assert(apply_patch_check("/system/app/AccountSyncManager.odex", "54e29e187f645bf4cca610039c0cea19264db3a9", "82d14a73106da8fc8857ddf346f10803eaace65e"));
set_progress(0.000864);
assert(apply_patch_check("/system/app/AdobeReader.apk", "4b631cd33caf62c028025431193c90e74ac2f843", "b4495167bce02c3888bfbd11500b471408a2cd1e"));
set_progress(0.002245);
assert(apply_patch_check("/system/app/AppSharing.apk", "68f72c802abfae89a352e05c84fec8131f297ec2", "1af6b59cba8d4ea078cb5d92d58b4269cd482d23"));
set_progress(0.002364);
assert(apply_patch_check("/system/app/AppSharing.odex", "cdac67b3837582c59f05974100c27214d49d5c60", "dd965ebcb73fc62140ad74e192c52908884315fd"));

Tera Tike said:
You will have to return to the original System image and recovery for the update to work. The update does a system file verification before it will run.
SAMPLE
Code:
# Script Version: G2.4
mount("yaffs2", "MTD", "system", "/system");
assert(check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999");
ifelse( is_ship_bootloader(getprop("ro.bootloader")) == "t" ,
assert(check_mid("full", "PG7624000") == "t");,
assert(check_mid("simple", "PG7624000") == "t");
);
assert(getprop("ro.product.device") == "marvel" ||
getprop("ro.build.product") == "marvel");
ui_print("Copying fotaBoot to /data/system for customize reload...");
mount("yaffs2", "MTD", "userdata", "/data");
package_extract_file("fotaBoot", "/data/system/fotaBoot");
ui_print("Verifying current system...");
show_progress(0.100000, 0);
assert(apply_patch_check("/system/app/AccountSyncManager.apk", "0c905b041013e66457dd8e9e3abc5a98a7aaff37", "cc881deb5a9e22c6034d4533aa16d8e59abf6124"));
set_progress(0.000434);
assert(apply_patch_check("/system/app/AccountSyncManager.odex", "54e29e187f645bf4cca610039c0cea19264db3a9", "82d14a73106da8fc8857ddf346f10803eaace65e"));
set_progress(0.000864);
assert(apply_patch_check("/system/app/AdobeReader.apk", "4b631cd33caf62c028025431193c90e74ac2f843", "b4495167bce02c3888bfbd11500b471408a2cd1e"));
set_progress(0.002245);
assert(apply_patch_check("/system/app/AppSharing.apk", "68f72c802abfae89a352e05c84fec8131f297ec2", "1af6b59cba8d4ea078cb5d92d58b4269cd482d23"));
set_progress(0.002364);
assert(apply_patch_check("/system/app/AppSharing.odex", "cdac67b3837582c59f05974100c27214d49d5c60", "dd965ebcb73fc62140ad74e192c52908884315fd"));
Click to expand...
Click to collapse
ya i know.. i flashes boot.img system.img and recovery.img from the rom.zip i extracted from ruu

The downloaded file must be on the sd card. It must be something like OTA_update...........zip check if its flashable. Check if you can do something with that. You may have to search for it.

vbhtt said:
The downloaded file must be on the sd card. It must be something like OTA_update...........zip check if its flashable. Check if you can do something with that. You may have to search for it.
Click to expand...
Click to collapse
The only file I. Found is com.android.vending.updater-20120221-061703.tar.gz

It should be in the download folder. You downloaded it ota right? I suggest you search manually and not use the search function of your file manager

vbhtt said:
It should be in the download folder. You downloaded it ota right? I suggest you search manually and not use the search function of your file manager
Click to expand...
Click to collapse
yeah bro.. i searched it everywhere on sd card .. no where not even in download folder..

Have you enabled show hidden files in your file manager? Filenames that start with a '.' are generally hidden
Sent from my iPod touch using Tapatalk

vbhtt said:
Have you enabled show hidden files in your file manager? Filenames that start with a '.' are generally hidden
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
yeap saw.. nothing there.

Maybe the system deleted it after if found out? Do you get a notification that an update is available in the status bar?
Sent from my iPod touch using Tapatalk

vbhtt said:
Maybe the system deleted it after if found out? Do you get a notification that an update is available in the status bar?
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
yep i do... and when i select it.. it starts downloading... and then nothing the same error comes..

Just after it downloads, it asks whether you want to install it right? Click no and then search for it.
Sent from my iPod touch using Tapatalk

vbhtt said:
Just after it downloads, it asks whether you want to install it right? Click no and then search for it.
Sent from my iPod touch using Tapatalk
Click to expand...
Click to collapse
it doesnt asks me nyting as such it just starts itself up

Did you try unrooting?
Factory data reset?
Try the 'fastboot oem lock' command
Cant think of anything else...
Sent from my iPod touch using Tapatalk

Assert failed: getprop("ro.bootloader" during flashing of LiquidSmooth 2.37 T999

Assert failed: getprop("ro.bootloader" during flashing of LiquidSmooth 2.37 T999
Assert failed: getprop("ro.bootloader" showed up when I tried to flash LiquidSmooth 2.37 4.3.1 onto my T-Mobile T999. Any help please?
http://forum.xda-developers.com/showthread.php?t=2313175 < same thing with mine except I'm running stock on 4.3 right now.

Did you receive and install the Stock OTA update to 4.3 ? The process to resolve your issue depends on that answer.

yes I was on stock and everything was normal when I updated and installed to stock 4.3.

xTheOne23 said:
yes I was on stock and everything was normal when I updated and installed to stock 4.3.
Click to expand...
Click to collapse
In that case, first make sure you have the latest version of the custom recovery of your choice. If its not then update it and try. If it is latest then read on.
Best if you take the rom zip and open it on pc with winzip or similar. Then go to
/Meta-Inf/com/google/android/ folder. There you will see a file called updater script. Open it with Wordpad and NOT NOTEPAD! Inside first few lines, you will see something like
Code:
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2");
show_progress(0.500000, 0);
There, delete the part before
show_progress(0.500000, 0);
Close the file and save it back to the zip. Put the zip on your External sd card and flash via recovery.

Perseus71 said:
In that case, first make sure you have the latest version of the custom recovery of your choice. If its not then update it and try. If it is latest then read on.
Best if you take the rom zip and open it on pc with winzip or similar. Then go to
/Meta-Inf/com/google/android/ folder. There you will see a file called updater script. Open it with Wordpad and NOT NOTEPAD! Inside first few lines, you will see something like
Code:
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2");
show_progress(0.500000, 0);
There, delete the part before
show_progress(0.500000, 0);
Close the file and save it back to the zip. Put the zip on your External sd card and flash via recovery.
Click to expand...
Click to collapse
What do you mean by version of custom recoery? Sorry, I'm a noob. And when you say delete the part before, 'show_progress((0.500000, 0);, do i delete everything before it lesving only that ?

Yes you delete all the Assert statement before that. But before you do that, please check the Version of your Custom Recovery.
When you boot to Custom Recovery, CWM or TWRP, you will see its version at the top.

Perseus71 said:
Yes you delete all the Assert statement before that. But before you do that, please check the Version of your Custom Recovery.
When you boot to Custom Recovery, CWM or TWRP, you will see its version at the top.
Click to expand...
Click to collapse
My CWM version is 6.0.4.5.

Yes that's the correct version. You should try removing the Asserts.

installation aborted
i cant install., i did what u said in the post.. installation aborted.
this is what my updater script file looks like.
assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
assert(getprop("ro.bootloader") == "T999UVDLJA" ||
getprop("ro.bootloader") == "T999UVDLJC" ||
getprop("ro.bootloader") == "T999UVDMD5" ||
getprop("ro.bootloader") == "T999UVUEMJC" ||
getprop("ro.bootloader") == "T999VVLDLL1" ||
getprop("ro.bootloader") == "T999LUVAMB7" ||
getprop("ro.bootloader") == "T999VVLDMF2");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
show_progress(0.500000, 0);
i deleted the part before show_progress

Did you try adding your bootloader to the updater script? Is the phone running the latest release of twrp?

Modem update from CWM

Modem update from CWM simply doesn't work!
I tried already everything! Result is: Script runs without error but no change, the baseband version is still the old.
My last update script (no errors, but doesn't work) is following:
Code:
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" ||
getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" ||
getprop("ro.product.device") == "i9195" || getprop("ro.build.product") == "i9195" ||
getprop("ro.product.device") == "GT-I9195" || getprop("ro.build.product") == "GT-I9195");
ui_print("------------------------------------------------------");
ui_print("I9195 modem update by LackoGyerek");
show_progress(0.150000, 0);
package_extract_dir("tools", "/tmp");
set_perm(0, 0, 0777, "/tmp/busybox");
run_program("/tmp/busybox", "mkfs.vfat", "/dev/block/platform/msm_sdcc.1/by-name/modem");
run_program("/tmp/busybox", "mkdir", "-p", "/tmp/modem");
run_program("/tmp/busybox", "mount", "-w", "-t", "auto", "/dev/block/platform/msm_sdcc.1/by-name/modem", "/tmp/modem");
package_extract_dir("modem", "/tmp/modem");
set_perm_recursive(0, 1000, 0771, 0771, "/tmp/modem/image");
run_program("/tmp/busybox", "umount", "/tmp/modem");
ui_print("Installation complete!");
show_progress(1.000000, 0);
ui_print("------------------------------------------------------");
The update package above uses the unpacked NON-HLOS.bin content. Can be easily unpacked with DiskInternals Linux Reader tool.
Already tried with/without formatting of modem partition.
Also tried the edify command
Code:
package_extract_file("NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
Method below was checked too:
Code:
busybox dd if=./NON-HLOS.bin of=/dev/block/platform/msm_sdcc.1/by-name/modem
Result of dd command:
Code:
97923+1 records in
97923+1 records out
50136832 bytes (47.8MB) copied, 6.765573 seconds, 7.1MB/s
And finally this method:
Code:
package_extract_dir("modem","/tmp");
write_raw_image("/tmp/NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
delete("/tmp/NON-HLOS.bin");
All above with the same result: No error during flash, but baseband version not changed.
Any idea, how to update modem via recovery?

If you check the contents of the flashed NON-HLOS.bin you should find that it has indeed been changed.
The version listed in about device doesn't update unless you flash with Odin twice

Whosat said:
If you check the contents of the flashed NON-HLOS.bin you should find that it has indeed been changed.
The version listed in about device doesn't update unless you flash with Odin twice
Click to expand...
Click to collapse
Trust me, I checked it!
Followíng command used to check:
Code:
busybox dd if=/dev/block/platform/msm_sdcc.1/by-name/modem | strings | grep "I9195"
The above always returned the old baseband version string.
And yes, the Odin solution works also for me but I'm searching for a CWM flash solution. No luck yet...

News: I've found this XDA thread, where user says:
The only Write operation permitted on a flash memory device is to
change a bit from a one to a zero. If the reverse operation is needed, then
the block must be erased (to reset all bits to the one state).
Click to expand...
Click to collapse
Maybe this is the solution. Before flashing modem, the whole modem partition must be erased.

Guys, it's really interesting. It seems, that modem partition on our device is write protected. We simply can't erase/format it or write anything to it from recovery (or we don't know the correct way).
I did the following: Went to TWRP recovery, which has built in command line terminal. My goal was to format modem partition. Normally this can be done using following command:
Code:
busybox mkfs.vfat -v /dev/block/platform/msm_sdcc.1/by-name/modem
Cmd executed successfully, but modem partition was NOT formatted.
After restart of phone I checked the mobile data functionality, everything worked and still works without problem.

This is the script form a GT-I9500 CWM-flashable modem.
Code:
ui_print("----Samsung Galaxy S4----");
ui_print("-----GT-I9500-ONLY-----");
ui_print("-----Android 4.2.2------");
ui_print("------STOCK Modem-----");
ui_print("-created-by-DjeMBeY-XDA-");
show_progress(0.150000, 0);
assert(package_extract_file("Djembey/modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p13"),
delete("/tmp/modem.bin"));
ui_print("Installation complete!");
show_progress(1.000000, 0);
Seems like it uses write_raw_image straight to the partition.

Whosat said:
This is the script form a GT-I9500 CWM-flashable modem.
Code:
ui_print("----Samsung Galaxy S4----");
ui_print("-----GT-I9500-ONLY-----");
ui_print("-----Android 4.2.2------");
ui_print("------STOCK Modem-----");
ui_print("-created-by-DjeMBeY-XDA-");
show_progress(0.150000, 0);
assert(package_extract_file("Djembey/modem.bin", "/tmp/modem.bin"),
write_raw_image("/tmp/modem.bin", "/dev/block/mmcblk0p13"),
delete("/tmp/modem.bin"));
ui_print("Installation complete!");
show_progress(1.000000, 0);
Seems like it uses write_raw_image straight to the partition.
Click to expand...
Click to collapse
Yes, I saw that. Already tried but as the other methods: Script executes successfully, but modem is not updated.
You can also try if you want, here is my example.
The script in my package is following:
Code:
package_extract_dir("modem","/tmp");
[B]write_raw_image[/B]("/tmp/NON-HLOS.bin", "/dev/block/platform/msm_sdcc.1/by-name/modem");
delete("/tmp/NON-HLOS.bin");
Note: assert() command is not necessary.

Help with unpacking system apps

Hello everybody .. Hiw i can unpack lollipop system.dat file??

@Skin1980

@S3V3N

Akhayev said:
@Skin1980
Click to expand...
Click to collapse
system.dat? Explain better pls

Skin1980 said:
system.dat? Explain better pls
Click to expand...
Click to collapse
I am sorry .. I downloaded cm12 that based on lollipop and when i opened the rom theres a file named system.new.dat and all the apps inside this file and i wants to port some apps from this file but i cant open it cos its .dat file

Akhayev said:
I am sorry .. I downloaded cm12 that based on lollipop and when i opened the rom theres a file named system.new.dat and all the apps inside this file and i wants to port some apps from this file but i cant open it cos its .dat file
Click to expand...
Click to collapse
try to mount it

Skin1980 said:
try to mount it
Click to expand...
Click to collapse
7zip cannot extract a system.new.dat file and DAEMON tools cannot mount it. I'm hoping ROM devs release their ROMs with the standard format but if they don't, I'm sure someone from the community will easily find a way to extract them.

CM12 system.new.dat apps
Hi,
I had downloaded CM12 just now. There are no apks but only 1-img and 1-dat files in which "system.new.dat" file contains the stuff. Please provide a way to extract apks from system.new.dat file.

Unpack
Anyone figure how to do this?

I would like to know this as well.

I don't know for stock, I'm searching how to do it, but for cm12, you can compile from source directly, there is a thread in development section.

I'm stuck too.
Habaddon said:
I don't know for stock, I'm searching how to do it, but for cm12, you can compile from source directly, there is a thread in development section.
Click to expand...
Click to collapse
This is a chicken and egg problem for me. I want to build a ROM but first want to extract the device firmware for my ROM. (I don't have access to the Nexus 4 phone to install a ROM on and then extract the firmware.)
I've been Googling for a solution without luck.
Followed a clue. I uncommented a debug print statement in simg2img. No luck.
Code:
$ file system.new.dat
system.new.dat: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
$ simg2img.py system.new.dat system.new.raw
424620032
'\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00'
Not a compressed ext4 file!!
Any ideas?

Yeah, I tried that too, it doesn't work. I ask a dev, in fact, it is simple. All you need to do is mount the img.
mkdir system
sudo mount system.img system
Click to expand...
Click to collapse

Still stuck
Habaddon said:
Yeah, I tried that too, it doesn't work. I ask a dev, in fact, it is simple. All you need to do is mount the img.
Click to expand...
Click to collapse
I'm still confused.
I suspect that the system.new.dat is not a simple image file and is most probably signed in some way. I don't know why the file command says that it is an ext4 filesystem while simg2img.py, with the debug statement which prints the first bytes uncommented, prints only nulls.
BTW, I asked my relative who owns the device to try flashing this ROM and it didn't work because of a known problem whereby rooting was lost. He will try a new ROM.
Plan B will be to pull the firmware via adb but I'm certainly curious about the new Lollipop way of packaging the ROM.
Code:
$ ls -l cm-12-20141123-UNOFFICIAL-mako.zip
-rw-r--r-- 1 zippy zippy 238444354 Dec 6 08:20 cm-12-20141123-UNOFFICIAL-mako.zip
$ unzip cm-12-20141123-UNOFFICIAL-mako.zip
Archive: cm-12-20141123-UNOFFICIAL-mako.zip
signed by SignApk
extracting: system.patch.dat
inflating: META-INF/com/android/metadata
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: META-INF/org/cyanogenmod/releasekey
inflating: boot.img
inflating: file_contexts
inflating: [COLOR="Red"]system.new.dat[/COLOR]
inflating: system.transfer.list
inflating: system/bin/backuptool.functions
inflating: system/bin/backuptool.sh
inflating: system/bin/otasigcheck.sh
inflating: META-INF/com/android/otacert
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
$ ls -l system.new.dat
-rw-rw-r-- 1 zippy zippy 424620032 Feb 29 2008 system.new.dat
$ file system.new.dat
system.new.dat: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
$ rm -rf # remove the extracted system directory from above
$ mkdir system
$ sudo mount system.new.dat system
[sudo] password for zippy:
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
$ dmesg | tail -2
[89035.798766] loop: module loaded
[89035.906824] EXT4-fs (loop0): bad geometry: block count 215040 exceeds size of device (103667 blocks)

I wonder why nobody put up a way to modify this?
I kept looking for the solution from the day lollipop releases, but without any success.
:crying:

Investigating ...
I know more now.
Below is the update-script which calls functions in the update-binary. I highlighted the code in question. This is obviously not a simple filesystem in the system.new.dat. I've hacked at it with ext4.fsck and resize2fs with no luck.
Code:
assert(getprop("ro.product.device") == "mako" || getprop("ro.build.product") == "mako" || abort("This package is for device: mako; this device is " + getprop("ro.product.device") + "."););
ifelse(is_mounted("/system"), unmount("/system"));
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");
if is_mounted("/data") then
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
else
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data", "");
package_extract_file("system/bin/otasigcheck.sh", "/tmp/otasigcheck.sh");
package_extract_file("META-INF/org/cyanogenmod/releasekey", "/tmp/releasekey");
set_metadata("/tmp/otasigcheck.sh", "uid", 0, "gid", 0, "mode", 0755);
run_program("/tmp/otasigcheck.sh") != "31744" || abort("Can't install this package on top of incompatible data. Please try another package or run a factory reset");
unmount("/data");
endif;
show_progress(0.750000, 0);
[COLOR="red"]block_image_update("/dev/block/platform/msm_sdcc.1/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");[/COLOR]
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
delete("/system/bin/otasigcheck.sh");
unmount("/system");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system", "");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_metadata("/tmp/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755);
set_metadata("/tmp/backuptool.functions", "uid", 0, "gid", 0, "mode", 0644);
run_program("/tmp/backuptool.sh", "restore");
delete("/system/bin/backuptool.sh");
delete("/system/bin/backuptool.functions");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");
show_progress(0.200000, 10);
Next, one can look in the source code and try to figure out what it is doing.
Or maybe the next step is to see if there is a host build (i.e. Ubuntu, Fedora, etc) of the binary-update which can be run from the command line into a file which can be mounted.
I'm sure that there is an easy way but finding it is difficult!

Ext2Explorer, Diskinternals Linux Reader can mount, read and extract those system images. But I m not sure if they are fully compatible because in both of these apps which I tried priv-app and some other folders are shown empty. I don't know if normaly there are files in these folders or not.

I've been struggling with these system.new.dat block images since lollipop came out since I need to convert roms to flash onto F2FS system partitions. I searched high and low for a way to mount that image outside of twrp with no luck. So I just used twrp instead... Luckily I've an extra device at my disposal atm. These are the steps I take:
Clean flash a lollipop rom that has a system.new.dat image in twrp.
Reboot system.
When device finishes booting use hardware power button to power down without messing with the rom itself yet so it stays fresh. (It's ok to confirm power down on touch screen.)
In twrp make a backup of only the system partition.
Boot back to system and use the method you prefer to move the file system.ext4.win from /TWRP/BACKUPS/-ur-device-serial/-ur-backup-date on to your pc and rename it system.tar so you can unpack it. (Of course make sure you have the proper decompression tools, which every OS usually does now.)
Now you have the complete fresh contents of /system as you would in a traditional rom zip. You can now do with that as you please. :silly:

Well googling i found this solution http://forum.xda-developers.com/nexus-7/general/guide-unpack-dat-t2970707 @adomol:
I've been struggling with these system.new.dat block images since lollipop came out. I searched high and low for a way to mount that image outside of twrp with no luck. So I just used twrp instead... These are the steps I take:
1.Clean flash a lollipop rom that has a system.new.dat image in twrp.
2.Reboot system.
3.When device finishes booting use hardware power button to power down without messing with the rom itself yet so it stays fresh. (It's ok to confirm power down on touch screen.)
4.In twrp make a backup of only the system partition.
5.Boot back to system and use the method you prefer to move the file system.ext4.win from:
/TWRP/BACKUPS/-ur-device-serial/-ur-backup-date
to your pc and rename it system.tar so you can unpack it. (Of course make sure you have the proper decompression tools, which every OS usually does now.)
Now you have the complete fresh contents of /system as you would in a traditional rom zip. You can do with that as you please, or just throw it into a rom kitchen.
all credits to @adomol

adomol said:
I've been struggling with these system.new.dat block images since lollipop came out since I need to convert roms to flash onto F2FS system partitions. I searched high and low for a way to mount that image outside of twrp with no luck. So I just used twrp instead... Luckily I've an extra device at my disposal atm. These are the steps I take:
Clean flash a lollipop rom that has a system.new.dat image in twrp.
Reboot system.
When device finishes booting use hardware power button to power down without messing with the rom itself yet so it stays fresh. (It's ok to confirm power down on touch screen.)
In twrp make a backup of only the system partition.
Boot back to system and use the method you prefer to move the file system.ext4.win from /TWRP/BACKUPS/-ur-device-serial/-ur-backup-date on to your pc and rename it system.tar so you can unpack it. (Of course make sure you have the proper decompression tools, which every OS usually does now.)
Now you have the complete fresh contents of /system as you would in a traditional rom zip. You can now do with that as you please. :silly:
Click to expand...
Click to collapse
-droidberg- said:
Well googling i found this solution http://forum.xda-developers.com/nexus-7/general/guide-unpack-dat-t2970707 @adomol:
I've been struggling with these system.new.dat block images since lollipop came out. I searched high and low for a way to mount that image outside of twrp with no luck. So I just used twrp instead... These are the steps I take:
1.Clean flash a lollipop rom that has a system.new.dat image in twrp.
2.Reboot system.
3.When device finishes booting use hardware power button to power down without messing with the rom itself yet so it stays fresh. (It's ok to confirm power down on touch screen.)
4.In twrp make a backup of only the system partition.
5.Boot back to system and use the method you prefer to move the file system.ext4.win from:
/TWRP/BACKUPS/-ur-device-serial/-ur-backup-date
to your pc and rename it system.tar so you can unpack it. (Of course make sure you have the proper decompression tools, which every OS usually does now.)
Now you have the complete fresh contents of /system as you would in a traditional rom zip. You can do with that as you please, or just throw it into a rom kitchen.
all credits to @adomol
Click to expand...
Click to collapse
But this won't work when trying to port because you need to swap kernel's (for going between same-device, different-carrier)

Nokia N1 Chinese version 5.1.1 update!!!

Here is the download link
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-china2015/A5CN701_update.zip
This upgrade includes the android upgrade, version update of the pre-installed apps and function improvement
- Android system upgrade to v5.1.1
- New "Navigation Icons" app
- New "App Notifications" app
- Update "Z-Launcher" to v1.2.5-Beta
- Update "The Store" to v3.31
- Update "Auto Start Manager" to v1.6
- Update "Sound Recorder" to v1.23
- Update "Clock" to v4.2
- Add "power level" information on lockscreen
- Add "close all" function in recent apps list
- Improve bluetooth connection stability
此版本包含系统更新、软件新增、功能改进，更新内容包括：
- Android系统更新 [版本号 5.1.1]
- 新增"虚拟键"程序
- 新增"通知开关"程序
- 更新"Z-Launcher"程序 [版本号 1.2.5-Beta]
- 更新"应用商店"程序 [版本号 3.31]
- 更新"自启动管理"程序 [版本号 1.6]
- 更新"录音"程序 [版本号 1.23]
- 更新"时钟"程序 [版本号 4.2]
- "锁屏界面"新增"电池电量显示"功能
- "最近任务界面"新增"关闭全部应用程序"功能
- 改善蓝牙连接稳定性
此版本包含系統更新、應用新增、功能改進，更新內容包括：
- Android系統更新 [5.1.1]
- 新增"虛擬鍵"程式
- 新增"通知開關"程式
- 更新"Z-Launcher" [1.2.5-Beta版]
- 更新"應用商店"程式 [3.31版]
- 更新"自啟動管理"程式 [1.6版]
- 更新"錄音程式"程式 [1.23版]
- 更新"時鐘"程式 [4.2版]
- "鎖屏畫面"新增"電池電量"資訊
- "最近任務功能"中新增"關閉全部應用程式"功能
- 修正藍牙連線穩定度

No root

Xkernels said:
Here is the download link
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-china2015/A5CN701_update.zip
Click to expand...
Click to collapse
Nokia N1 Chinese version lists:
HTML:
A5CN114 Easter eggs
A5CN204 316M
A5CN20C 17.4M
A5CN21B 21.6M
A5CN30B 14.9M
A5CN315 18.6M
A5CN403 32.3M
A5CN410 312M
A5CN507 348M
A5CN51C 19.9M
A5CN701 471M
A5CNA13 67.98M
A5CNB19 479.01M
download link such as:
HTML:
Patch:http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-china2015/patch/A5CNXXX_update.zip
Full:http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-china2015/A5CNXXX_update.zip
Nokia N1 Taiwan version lists:
HTML:
A5FM51C 16.8M
A5FM508 625.59M
A5FM91E 848.38M
A5FMB19 816.04M
download link such as:
HTML:
Patch:http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-tw2015/patch/A5FMXXX_update.zip
Full:http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-tw2015/A5FMXXX_update.zip
Nokia N1 United Kingdom version lists:
HTML:
A5WU51C 613.44M
download link such as:
HTML:
Patch:http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-uk2015/patch/A5WUXXX_update.zip
Full:http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-uk2015/A5WUXXX_update.zip

Remain root on this update, isn't it?

yes

Seems that the bootloader is locked by this update. My N1 cannot be rooted by this method anymore: http://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965

OMG. Don't update to 5.1.1. In this firmware, Can not root by the temp CWM like before.

kokkok said:
OMG. Don't update to 5.1.1. In this firmware, Can not root by the temp CWM like before.
Click to expand...
Click to collapse
Yep. But I will factory reset it and manually update to previous firmware to root again. Let's wait and see.
Btw, Nokia N1 is just awesome!

How can manual rollback to previous firmware, pls show it to me. Many thanks

kokkok said:
How can manual rollback to previous firmware, pls show it to me. Many thanks
Click to expand...
Click to collapse
delete the row marked red in "A5CN507_update.zip\META-INF\com\google\android\updater-script"
(!less_than_int(1430978494, getprop("ro.build.date.utc"))) || abort("Can't install this package (Thu May 7 14:01:34 CST 2015) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "Nokia_N1" || abort("This package is for "Nokia_N1" devices; this is a "" + getprop("ro.product.device") + "".");
package_extract_file("ifwi.zip", "/tmp/ifwi.zip");
ui_print("Verifing BOM token ...");
flash_bom_token("/tmp/ifwi.zip") || abort("BOM flashing failed");
ui_print("Updating IFWI ...");
flash_ifwi("/tmp/ifwi.zip");
show_progress(0.750000, 0);
block_image_update("/dev/block/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing fastboot image ...");
package_extract_file("droidboot.img", "/dev/block/by-name/fastboot");
ui_print("Writing silentlake image ...");
then adb reboot recovery>adb sideload

aquaminh said:
Seems that the bootloader is locked by this update. My N1 cannot be rooted by this method anymore: http://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
Click to expand...
Click to collapse
C:\platform-tools>adb reboot bootloader
C:\platform-tools>fastboot oem get-bootinfo
...
FAILED (remote: unknown OEM command)
finished. total time: 1.687s
BOOTLOADER Version - unkown?

Xkernels said:
delete the row marked red in "A5CN507_update.zip\META-INF\com\google\android\updater-script"
(!less_than_int(1430978494, getprop("ro.build.date.utc"))) || abort("Can't install this package (Thu May 7 14:01:34 CST 2015) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "Nokia_N1" || abort("This package is for "Nokia_N1" devices; this is a "" + getprop("ro.product.device") + "".");
package_extract_file("ifwi.zip", "/tmp/ifwi.zip");
ui_print("Verifing BOM token ...");
flash_bom_token("/tmp/ifwi.zip") || abort("BOM flashing failed");
ui_print("Updating IFWI ...");
flash_ifwi("/tmp/ifwi.zip");
show_progress(0.750000, 0);
block_image_update("/dev/block/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing fastboot image ...");
package_extract_file("droidboot.img", "/dev/block/by-name/fastboot");
ui_print("Writing silentlake image ...");
then adb reboot recovery>adb sideload
Click to expand...
Click to collapse
Many thanks but I can not download the previous firmware such as 510C because browser reported the server refuses. Any other link address?

Xkernels said:
delete the row marked red in "A5CN507_update.zip\META-INF\com\google\android\updater-script"
(!less_than_int(1430978494, getprop("ro.build.date.utc"))) || abort("Can't install this package (Thu May 7 14:01:34 CST 2015) over newer build (" + getprop("ro.build.date") + ").");
getprop("ro.product.device") == "Nokia_N1" || abort("This package is for "Nokia_N1" devices; this is a "" + getprop("ro.product.device") + "".");
package_extract_file("ifwi.zip", "/tmp/ifwi.zip");
ui_print("Verifing BOM token ...");
flash_bom_token("/tmp/ifwi.zip") || abort("BOM flashing failed");
ui_print("Updating IFWI ...");
flash_ifwi("/tmp/ifwi.zip");
show_progress(0.750000, 0);
block_image_update("/dev/block/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/by-name/boot");
show_progress(0.200000, 10);
ui_print("Writing fastboot image ...");
package_extract_file("droidboot.img", "/dev/block/by-name/fastboot");
ui_print("Writing silentlake image ...");
then adb reboot recovery>adb sideload
Click to expand...
Click to collapse
Would you show me the steps to sideload this firmware? I am now at the latest 5.1.1. My adb and usb driver were installed already. Sorry I am newbie about rooting and flashing firmware.

aquaminh said:
Seems that the bootloader is locked by this update. My N1 cannot be rooted by this method anymore: http://forum.xda-developers.com/nokia-n1/general/play-store-howto-t3118965
Click to expand...
Click to collapse
aquaminh said:
Would you show me the steps to sideload this firmware? I am now at the latest 5.1.1. My adb and usb driver were installed already. Sorry I am newbie about rooting and flashing firmware.
Click to expand...
Click to collapse
A5CN51C is a patch with 19.9M,you should download full version A5CN507.
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-china2015/A5CN507_update.zip
run command prompt in the adb tools path,such as:
C:\platform-tools\adb reboot recovery
then N1 reboot to recovery mode
select the adb sideload mode
C:\platform-tools\adb sideload\A5CN507_update.zip(copy A5CN507_update.zip to platform-tools folders)
then begin to flash.

Still waiting for a way to unlock the bootloader, so that i can root and install Google Play. Or root then wait for the update 5.1.1 for the Taiwanese version then flash it!

Xkernels said:
A5CN51C is a patch with 19.9M,you should download full version A5CN507.
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-china2015/A5CN507_update.zip
run command prompt in the adb tools path,such as:
C:\platform-tools\adb reboot recovery
then N1 reboot to recovery mode
select the adb sideload mode
C:\platform-tools\adb sideload\A5CN507_update.zip(copy A5CN507_update.zip to platform-tools folders)
then begin to flash.
Click to expand...
Click to collapse
Thank a lot, I will try now. Hope everything will fine

Xkernels said:
A5CN51C is a patch with 19.9M,you should download full version A5CN507.
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-china2015/A5CN507_update.zip
run command prompt in the adb tools path,such as:
C:\platform-tools\adb reboot recovery
then N1 reboot to recovery mode
select the adb sideload mode
C:\platform-tools\adb sideload\A5CN507_update.zip(copy A5CN507_update.zip to platform-tools folders)
then begin to flash.
Click to expand...
Click to collapse
colorado48 said:
Still waiting for a way to unlock the bootloader, so that i can root and install Google Play. Or root then wait for the update 5.1.1 for the Taiwanese version then flash it!
Click to expand...
Click to collapse
kokkok said:
Thank a lot, I will try now. Hope everything will fine
Click to expand...
Click to collapse
DO NOT update to 5.1.1 if you want to keep the bootloader unlocked. I've been trying so many times to unlock it but it still doesn't work.

aquaminh said:
DO NOT update to 5.1.1 if you want to keep the bootloader unlocked. I've been trying so many times to unlock it but it still doesn't work.
Click to expand...
Click to collapse
Finally, you are an expert or noob about rooting and unlocking firmware? Are you successfully rollback to previous firmware and reroot N1 which updated to 5.1.1????

kokkok said:
Finally, you are an expert or noob about rooting and unlocking firmware? Are you successfully rollback to previous firmware and reroot N1 which updated to 5.1.1????
Click to expand...
Click to collapse
Xkernels said:
A5CN51C is a patch with 19.9M,you should download full version A5CN507.
http://ota-service.oss.fc811.com/upload/Nokia/moorefield/Nokia_N1/N1-china2015/A5CN507_update.zip
run command prompt in the adb tools path,such as:
C:\platform-tools\adb reboot recovery
then N1 reboot to recovery mode
select the adb sideload mode
C:\platform-tools\adb sideload\A5CN507_update.zip(copy A5CN507_update.zip to platform-tools folders)
then begin to flash.
Click to expand...
Click to collapse
No it doesn't work. Every previous tricks for rooting N1 were written while its bootloader is open. Now it's locked with the new update so maybe we have to wait for the new trick from the developers.

Bad news. Don't know why Nokia relock the bootloader.