Develop Bugs

Issue with CWM and Flashing ROMs

Ok, I can successfully get into CWM, but I can't flash either the OMGB or OMFGB ROMS. I always wipe data/dalvik. It doesn't even try to install, like it can't find the .zip file or something. The funny thing is, I successfully flashed a ROM using the ROM Manager application by downloading CM7 and installing from ROM Manager.
I have tried placing the .zip on the root of the SD card and also in the "CWM download" folder without luck.
Basically, I can flash a ROM with ROM Manager, but not manually using CWM?

you are supposed to find the zip yourself through CWM it will not find it for you
reboot recovery(CWM), wipe data, install zip from sdcard, find .zip in contained folder
if you cannot find it is not .zip format

I am doing exactly as you say. Wipe data/dalvik/cache partition. Flash zip and this is the error I get:
Assert failed: getprop("ro.product.device") == "inc" || getprop("ro.build.product") == "inc"
|| getprop("ro.product.board") == "inc"
E: Error in /sdcard/OMFGB_inc-1.3.1_nightly-08-25.zip
(status7)
Installation aborted.
Anyone ever seen this?

i've had the exact same issue using amon ra style recovery I installed the newest cwm and it flashed no problem. not sure what the problem wad
Sent from my ADR6350 using xda premium

Rossco_Pee said:
I am doing exactly as you say. Wipe data/dalvik/cache partition. Flash zip and this is the error I get:
Assert failed: getprop("ro.product.device") == "inc" || getprop("ro.build.product") == "inc"
|| getprop("ro.product.board") == "inc"
E: Error in /sdcard/OMFGB_inc-1.3.1_nightly-08-25.zip
(status7)
Installation aborted.
Anyone ever seen this?
Click to expand...
Click to collapse
It looks like you are trying to a Droid Incredible Rom on your Droid Incredible 2. ro.build.product = inc is the Droid Incredible
ro.build.product = vivow is the Incredible 2

That makes sense. But I did get those downloads from this forum. I guess it must be the download because I just successfully flashed GAPPS.

Rossco_Pee said:
That makes sense. But I did get those downloads from this forum. I guess it must be the download because I just successfully flashed GAPPS.
Click to expand...
Click to collapse
Are you flashing these files for the inc2?
OMGB_vivow-1.2.2.zip
or
OMFGB_vivow-1.3.1
Also are you checking the md5 to make sure you don't have a corrupt download?

I had the same exact issue same exact ROM. switching recoveries solved it for me
Sent from my ADR6350 using xda premium

As the other post said you're trying to install OM(F)GB for the original Droid Incredible. The code name for the Inc2 is Vivow. That's why the asserts in the updater-script are failing.
Sent from my Incredible 2 using XDA App

check the version of CWM. I read somewhere that one of the 5.0.something did not work well. Sorry I can't remember which one it was.

[Q] sdcard permission and mount issue (KitKat)

Hi,
I recently change my rom from an AOKP JB to Carbon KitKat.
Since that i've a "strange" issue with "sdcard" (all other stuff works fine).
What works:
- sdcard in CWM (both shell + usb)
- sdcard on usb (USB transfer or something like this in English)
What does not work:
- Unable to read or write sdcard under Android (/sdcard, ...), the only thing i can do is with root user in "/mnt/media_rw/sdcard0" folder
So, internal storage (sdcard) is not shown and usable in android, and get only ~2 Gb on ~27 Gb makes me :silly:
What i know :
- sdcard is mounted in "/mnt/media_rw/sdcard0" with 700 perm (only root)
- /sdcard -> /storage/sdcard0 which is empty
- I'm totally lost on kitkat files hierarchy and how it works
I guess, it's a mount/fuse issue between "/mnt/media_rw/sdcard0" and "/storage/sdcard0" and rights problem but i don't know what to do to fix this.
So, any suggestion or help will be really appreciate, thanks
EDIT
Now i'am able to modify ini.endeavoru.common.rc,... but i tried many things and "sdcard" not works. The best i can do is "/sdcard" -> "/mnt/media_rw/sdcard0" and i can read/write on it but android does not see it and USB tranfer not works anymore.
I found this : source.android.com/devices/tech/storage/config-example.html
What i don't understand is for me Hox is "like Nexus 4" but default init files are "like Nexus One" , so i tried "like Nexus 4" but this does not works.
So i think i'm close and if anyone have a link or something about sdcard on android kitkat (how it works) it can be really helpfull.
HTC ONE X (GSM)
CWM 6.0.4.7
Rom : Carbon 4.4.2 KitKat
HbBoot : 1.39 (Unlocked)

I don't know what was wrong but i solved it with cyanogen init files.
Download the tool using wget for unpack/pack boot.img:
Code:
mkdir ~/temp
cd ~/temp
wget android-serialport-api.googlecode.com/files/android_bootimg_tools.tar.gz
Extract :
Code:
tar xvzf android_bootimg_tools.tar.gz
rm android_bootimg_tools.tar.gz
Download cyanogen nightlybuild and extract boot.img in ~/temp folder, then unpack boot.img
Code:
mkdir cboot
~/temp/unpackbootimg -i boot.img -o cboot/
rm boot.img
Extract ramdisk
Code:
mkdir cboot/ramfs
cd ~/temp/cboot/ramfs
gunzip -c ../boot.img-ramdisk.gz | cpio -i
Do the same thing with Carbon KitKat boot.img in "~/temp/boot" and then copy "init.endeavoru..." files from "cboot/ramfs" to "boot/ramfs"
Pack files to boot.img-ramdisk.gz
Code:
cd ~/temp/boot/ramfs
find . | cpio -o -H newc | gzip > ../boot.img-ramdisk.gz
Pack boot.img
Code:
cd ~/temp
./mkbootimg --kernel boot/boot.img-zImage --ramdisk boot/boot.img-ramdisk.gz --base 0×10000000 --pagesize 2048 -o boot.img
Flash boot.img
Code:
adb reboot bootloader
fastboot flash boot boot.img
Restart phone and it should works
Clean
Code:
cd ~/
rm -r temp/

Helooo… help me plz…
My htc one x has twrp recovery but it doesnt mount usb storage in my pc…. And if I install cwm-recovery.... doesnt install kitkat roms….. Help me plz to fix it or to get other recovery which mount usb… ..and install kitkat roms….
Sent from my HTC One X using XDA Premium 4 mobile app

Hi,
You can install KitKat rom with CWM (there is also usb storage).
First you need to change HbBoot to a compatible version. I don't remember all compatible versions for KitKat but the 1.39 works.
I guess you've got the "set_metadata_recursive ...." error when you try to flash your rom ?
If it's the case, download update-binary from here : forum.xda-developers.com/showthread.php?t=2532300
and replace it in both, your rom and gapps and then you will be able to flash.

So…. Help me how which link can I get hboot 1.39..
Becouse my htc one x has
CID-VODAP102… uk…
Hboot 1.36
Sent from my HTC One X using XDA Premium 4 mobile app

I get mine here : d-h.st/users/ClydeB1/?fld_id=8110
but with your CID there is no 1.39 version only 1.36, but maybe you can install kitkat with 1.36.
Try , you will see.
EDIT:
In Carbon KitKat updater-script there is : getprop("ro.bootloader") == "1.33.0000" || getprop("ro.bootloader") == "1.36.0000" || getprop("ro.bootloader") == "1.39.0000"
So you can install it.

duffydake said:
I get mine here : d-h.st/users/ClydeB1/?fld_id=8110
but with your CID there is no 1.39 version only 1.36, but maybe you can install kitkat with 1.36.
Try , you will see.
EDIT:
In Carbon KitKat updater-script there is : getprop("ro.bootloader") == "1.33.0000" || getprop("ro.bootloader") == "1.36.0000" || getprop("ro.bootloader") == "1.39.0000"
So you can install it.
Click to expand...
Click to collapse
hi i tried by using CWM but tells installation aborted....................... help plz

mbwambo said:
hi i tried by using CWM but tells installation aborted....................... help plz
Click to expand...
Click to collapse
You need at least CWM version 6.0.4.4.
Search on internet or maybe here on the forum, there are several tutorial on "how to install kitkat on hox".

Make sure the rom is on the sdcard as i am not sure that UMS works.....but this recovery can install any rom
https://www.dropbox.com/s/xvcapmh8tsw5o3b/twrp-endeavoru.img
And this is the latest test version
https://www.dropbox.com/s/7zxfzbwewzq6hmq/twrp-recovery2.img

Thank…. Mr Hofs… now am using kitkat roms by using TWRP….. but remain one problem which is in failng to mount usb… .in my pc while am in twrp-recovery mode……. Help plz if possible……
Sent from my HTC One X using XDA Premium 4 mobile app

Do you wait long enough ? When you mount the sdcard it can take literally minutes before it pops up. Twrp is under development so keep an eye on the thread.

Ok… thankz… Mr Hofs letvme wait..those threads
Sent from my HTC One X using XDA Premium 4 mobile app

mbwambo said:
hi i tried by using CWM but tells installation aborted....................... help plz
Click to expand...
Click to collapse
You can try updating your recovery to the latest version of CWM such as 6.0.4.6 (AT&T) or 6.0.4.8 (International) depending on which version of HOX you have. This would then allow you to install Kitkat

Tim Harker said:
You can try updating your recovery to the latest version of CWM such as 6.0.4.6 (AT&T) or 6.0.4.8 (International) depending on which version of HOX you have. This would then allow you to install Kitkat
Click to expand...
Click to collapse
Please do not mention AT&T in here. People with the international hox might get that wrong and start flashing it.......wrong. only recommend recoveries from here and this forum only. This is for the international hox not the at&t. Let's not confuse users

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.

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.

[Question] Error E1001: Failed to update system image, ERROR 7

Hi.
This is my first time working with ROMs, wanted to see if I could unpack and repack them and have them work, so I would know if my later changes cause problems. I've noticed if I unzip a ROM, then zip it again, without any changes made, I get this error within a few seconds of starting the flash. If I don't unpack and repack the zip, it flashes fine.
I use the Android Kitchen, to unpack/repack, and signed the zip. Anyone know what's going on?
Did a full wipe with TWRP before flash attempt.
Code:
Starting ADB Sideload feature...
Target: google/occam/mako:5.1.1/LMy48M/2167285:user/release-keys
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Thank you,
Josh

Edit your updater-script
find this line
Code:
.... package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
change to :
Code:
.... package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
Just replace " ||" with ";" and delete line abort("blablabla"):

adislice said:
find this line
Code:
.... package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
change to :
Code:
.... package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat");
Just replace " ||" with ";" and delete line abort("blablabla"):
Click to expand...
Click to collapse
hey man when i deleted that line my phone booted in fastboot mode

I solved this by installing the latest version of TWRP and Oxygen OS.

Can anyone please help me correct error 7 with the following updater-script
The error i get is :
Installing zip file '/external_sd/lineage-15.1
20180524-UNOFFICIAL-Ocm.zip
Checking for Digest file...
Target: htc/ocmdtwl_01405/htc_ocmdtwl:8.0.0/OPR6.
170623.013/1010171.4:user/release-keys
detected filesystem ext4 for /dev/block/bootdevice/
by-name/system
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/lineage-15.
-20180524-UNOFFICIAL-ROm,zip'
Updating partition details...
... done
assert(getprop("ro.product.device") == "htc_ocm" || getprop("ro.build.product") == "htc_ocm" ||
getprop("ro.product.device") == "htc_ocndugl" || getprop("ro.build.product") == "htc_ocndugl" ||
getprop("ro.product.device") == "htc_ocmdtwl" || getprop("ro.build.product") == "htc_ocmdtwl" ||
getprop("ro.product.device") == "ocm" || getprop("ro.build.product") == "ocm" || abort("E3004: This package is for device: htc_ocm,htc_ocndugl,htc_ocmdtwl,ocm; this device is " + getprop("ro.product.device") + ".");
ui_print("Target: htc/ocmdtwl_01405/htc_ocmdtwl:8.0.0/OPR6.170623.013/1010171.4:user/release-keys");
ifelse(is_mounted("/system"), unmount("/system"));
package_extract_dir("install", "/tmp/install");
set_metadata_recursive("/tmp/install", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0644);
set_metadata_recursive("/tmp/install/bin", "uid", 0, "gid", 0, "dmode", 0755, "fmode", 0755);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "backup");
unmount("/system");
show_progress(0.650000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat.br", "system.patch.dat") ||
abort("E1001: Failed to update system image.");
show_progress(0.100000, 0);
ui_print("Patching vendor image unconditionally...");
block_image_update("/dev/block/bootdevice/by-name/vendor", package_extract_file("vendor.transfer.list"), "vendor.new.dat.br", "vendor.patch.dat") ||
abort("E2001: Failed to update vendor image.");
show_progress(0.020000, 10);
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
run_program("/tmp/install/bin/backuptool.sh", "restore");
unmount("/system");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
show_progress(0.200000, 10);
if (getprop("ro.boot.mid") == "2Q4D20000" || getprop("ro.boot.mid") == "2Q4D10000") then
ui_print("This is a DS device - renaming radio props");
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
rename("/vendor/lib64/libril-qc-ltedirectdisc.so", "/system/vendor/lib64/libril-qc-ltedirectdisc.so");
rename("/vendor/lib64/libril-qc-qmi-1.so", "/system/vendor/lib64/libril-qc-qmi-1.so");
rename("/vendor/lib64/libril-qc-radioconfig.so", "/system/vendor/lib64/libril-qc-radioconfig.so");
rename("/vendor/lib64/libril-qcril-hook-oem.so", "/system/vendor/lib64/libril-qcril-hook-oem.so");
unmount("/system");
endif;
set_progress(1.000000);
Any help is appreciated :s

Try using sideload insted of sd
i had the same error and i could do nothing...then I thought my sd maybe giving the error so i tried the sideload mode and believe me..........it worked
option 2:-if u have backed up your rom (or by anyhow if you can) try flashing another (in my case...an older) version of twrp. it also worked for me. would be glad if this helps you.
---------- Post added at 11:30 PM ---------- Previous post was at 11:05 PM ----------
[/COLOR]
SL.Pirate said:
i had the same error and i could do nothing...then I thought my sd maybe giving the error so i tried the sideload mode and believe......me it worked
but...at the moment i am having another problem...i'd appreciate if someone could help. the rom has been installed correctly (I guess) but...when it reboots,it says encryption unsuccessful. ther'es a key sayng reset phone but nothing happens after pressing it.i tried wiping all the partitions and reinstalling the rom and no use.
Click to expand...
Click to collapse
Solved...had some matters with the data partition.

SL.Pirate said:
Solved...had some matters with the data partition.
Click to expand...
Click to collapse
Such as?
I'm stuck at the same place as you were...

For the posterity :
in TWRP go to advanced > terminal, then create /cache/recovery with
mkdir /cache/recovery
solved the problem for me
Source : https://android.stackexchange.com/q...ineage-16-samsung-galaxy-note-2-gt-n7100-t03g

6mon said:
Such as?
I'm stuck at the same place as you were...
Click to expand...
Click to collapse
it said 'ENCRYPTION UNSUCCESSFULL'
if the samething happens to you....go to twrp,select wipe,advanced wipe and select (only) the data partition. then you gotta select repair or change file system select change file system and then select the correct format for the partition.(in and most of the cases...it is the EXT4 format.go ahead and reboot your device.this should probably work.If not...try other formats also from bottom to to. (HINT:-see what other partitions are formatted to).This should probably work if thats the case.

worked for me .thanks alot

It works!
6mon said:
For the posterity :
in TWRP go to advanced > terminal, then create /cache/recovery with
mkdir /cache/recovery
solved the problem for me
Source : https://android.stackexchange.com/q...ineage-16-samsung-galaxy-note-2-gt-n7100-t03g
Click to expand...
Click to collapse
Thank you so much! Before doing this, my Lenovo Vibe K5 Plus (A6020) wasn't able to install any ROM, but it's over! Now I can install custom ROMs with no flaws :good:

Worked for me as well and much easier than editing the update script. Thanks a lot!

If youre still getting error 7 e1001 then try this.
Boot twrp
Tap advanced tab
Tap file manager/explorer
Tap on /system
Tap + icon on the folder in bottom right corner to modify
Tap chmod 755 to enable r/w for system part.
Try to install again.
That is what worked for me

6mon said:
For the posterity :
in TWRP go to advanced > terminal, then create /cache/recovery with
mkdir /cache/recovery
solved the problem for me
Source : https://android.stackexchange.com/q...ineage-16-samsung-galaxy-note-2-gt-n7100-t03g
Click to expand...
Click to collapse
did the trick for me. Whoever has Error 7 / Error 1001 issues, try this first cant hurt!

6mon said:
For the posterity :
in TWRP go to advanced > terminal, then create /cache/recovery with
mkdir /cache/recovery
solved the problem for me
Source : https://android.stackexchange.com/q...ineage-16-samsung-galaxy-note-2-gt-n7100-t03g
Click to expand...
Click to collapse
Posterity works!!! I found your post by googling and it solved my issue, thanks again!

I have the same issue on S4 mini, but /cache/recovery/ dir is present.

Hello
I am having this issue installing /e/ os on samsung J5 J500F.
I tried making directory /cache/recovery and addind read and write rights to /system but it did not work.
I also tried different version of the os and build as well as different version of TWRP.
I tried removing the assert line in the updater script but the zip file generated then in refused by twrp, It gets me the error "invalid zip file format".
I tried making the zip file with winrar or 7zip using either relatie paths or absolute path, but i still get the same error.
Would someone have an idea ?
Thanks !

Sometimes it is caused due to corrupted file. While transferring file through MTP it is likely to corrupt large files. I had the same problem. Then I tried copying file while in TWRP (sure it is also MTP) and it worked.

HatMan22 said:
Sometimes it is caused due to corrupted file. While transferring file through MTP it is likely to corrupt large files. I had the same problem. Then I tried copying file while in TWRP (sure it is also MTP) and it worked.
Click to expand...
Click to collapse
Hello, thank you very much for your advice, I copied all files through TWRP, so it is probably coming from something else.
I tried downloading the file and and also flashing some other builds or different versions but I still get "failed to update system image error"

Gabriel-Roger said:
Hello, thank you very much for your advice, I copied all files through TWRP, so it is probably coming from something else.
I tried downloading the file and and also flashing some other builds or different versions but I still get "failed to update system image error"
Click to expand...
Click to collapse
Do you have latest TWRP installed? Old TWRP may also cause this issue.