Database Develop

[Q] ROM installing

I installed VivoKat Rom beta#6 but now i wont a perform clean install to stable#1 but after installing i see in log:
minzip:extracted file "/system/xbin/su"
minzip:extracted file "/system/xbin/vim"
about to run program [/tmp/backuptool.sh] with 2 args
/tmp/backuptool,sh: cd: line 99: can't cd to /tmp/addon.d/
md5sum: can't open *sh':no such file or directory
find: /tmp/addon.d/:No such file or directory
find: /tmp/addon.d/:No such file or directory
find: /tmp/addon.d/:No such file or directory
cp" can't stat '/tmp/addon,d/*': No such file or directory
script result was [/system]
install from sdcard conmplete
and 2nd
in recovery when i wipe dalvik cashe, in log shows
e:unknown volume for patsh [/sd-ext]
and when booting in system up it shows stable#1 but some bags from older beta versions, who is solved in stable#1.
Can someone tel any solutions?

S-OFF solved problem with ROM kernel
for RUU running to get s-off need to be locked phone, or ruu shows error.

dont know idiom about Roms
hi guys,
this is my first post,sorry if my question is very easy for you.
now the custom rom is running on my phone but I want to flash new Rom (but RUU) and turn my phone to orginal time that I bought it.
I want to khow that:"RUU" and "stock " and "Official" are the same?
and all 3 words means RUU ?(I know what is RUU)
because I see the name of thread that wrote "RUU "and "stock" together,and some of them just wrote "RUU"or just wrote "stock",I want to know difference between them.
and I want to know all words that means "custom rom" too...tnx.

Official: 100% HTC.
RUU: Make your phone Official.
Stock: ROM is like Official, but you can still keep root privileges.
So yes, they are basically the same but with few variations.
Sent from my Nexus 5

[Q] LG P880 Error 7 and Error 6. X3 or P880?

Hi everyone.
I'm new to Android(And I hate it). I jumped to Android from Apple iOS few days ago.
My LG P880 has 4.1.2 JB installed which is very laggy.
I tried to install 4.4.2 many times but It gives error statuses 7 and 6.
Error:
assert failed: getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880"
E:Error in /external_sd
i already have the latest version of CWM, i flashed it through rom manager.
I used this method too. but useless...
Step 1.Open the ROM.zip with winrar
Step 2.Found \META-INF\com\google\android\updater-script ,use Notepad open
Step 3.delete assert(getprop("ro.product.device") == "p880" ||
getprop("ro.build.product") == "p880");
Please tell me what to do now..
Why the ROMS are recognizing my device as X3 but not P880?

saqibjdn said:
Hi everyone.
I'm new to Android(And I hate it). I jumped to Android from Apple iOS few days ago.
My LG P880 has 4.1.2 JB installed which is very laggy.
I tried to install 4.4.2 many times but It gives error statuses 7 and 6.
Error:
assert failed: getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880"
E:Error in /external_sd
i already have the latest version of CWM, i flashed it through rom manager.
I used this method too. but useless...
Step 1.Open the ROM.zip with winrar
Step 2.Found \META-INF\com\google\android\updater-script ,use Notepad open
Step 3.delete assert(getprop("ro.product.device") == "p880" ||
getprop("ro.build.product") == "p880");
Please tell me what to do now..
Why the ROMS are recognizing my device as X3 but not P880?
Click to expand...
Click to collapse
do tell which cwm version you have? if it's not 6.0.4.5, flash it manually

Flying_Bear said:
do tell which cwm version you have? if it's not 6.0.4.5, flash it manually
Click to expand...
Click to collapse
I used "recovery-clockwork-6.0.4.5-p880"
How to install manually on my damn "LG 4X HD P880 X3".

saqibjdn said:
I used "recovery-clockwork-6.0.4.5-p880"
How to install manually on my damn "LG 4X HD P880 X3".
Click to expand...
Click to collapse
I believe that @Flying_Bear meant "By not using rom manager", but manually selecting a zip to be flashed after having booted your phone in recovery mode (Power on + Vol down).
Anyhow, let me say that your approach to the problem is not inviting for people to help you. You can be disappointed by the device, but your disappointment can be interpreted as arrogance, and people don't like very much arrogant people asking for help.
Relax and try to enjoy it all the same.

Use phillztouch modified cwm or latest twrp, clearly something is wrong with the one you are using now

[SOLVED] error status 6 and error 7/ X3/P880 model issue.
wow wow wow.. Thanks God.... Finally I installed 4.4.2 Carbon rom on my Phone.
Thank you so much guys for helping me out...
Love you all...
I installed philz_touch_6.12.8-p880 and it worked..
Whoever is facing error 7 or error 6 kindly use this method.
1. Install ADB
2. Unlock bootloader.
3. Root device.
4. Install TWRP first.
5. Go to recovery mode using volume down+Power. and Install "philz_touch_6.12.8-p880"
6. Now Power off phone and Restatrt using Volume up + Power button.
7. Format Factory data, wipe delvik from "advance" menu. Install CUSTOM ROM from sd card option. Install GAPPs and restart your phone.

X3\p880 Naming problem
Sorry if I'm hijacking this thread.
I've got a p880 stuck in a bootloop after installing a custom recovery. Can't remember which one.
The phone is rooted has 4.1.2 on it.
I've tried booting to recovery and wiping the cache and doing a factory reset.
I'm posting here because I tried sideloading 10.2. It fails with error message saying that the phone is an X3 not a p880.
I also tried sideloading phils_touch as mentioned above but get the same error message: the software is for the p880 not the X3.
Can anybody point me in the right direction?
Thanks
Brendan

bpjh56 said:
Sorry if I'm hijacking this thread.
I've got a p880 stuck in a bootloop after installing a custom recovery. Can't remember which one.
The phone is rooted has 4.1.2 on it.
I've tried booting to recovery and wiping the cache and doing a factory reset.
I'm posting here because I tried sideloading 10.2. It fails with error message saying that the phone is an X3 not a p880.
I also tried sideloading phils_touch as mentioned above but get the same error message: the software is for the p880 not the X3.
Can anybody point me in the right direction?
Thanks
Brendan
Click to expand...
Click to collapse
Just one question, have you unlocked the bootloader?
Greetings from my Nexus 7 2013 Flo!

Thanks for the reply.
I've managed to get the phone to work.
Found a software upgrade combination (vol up, connect usb I think), then used LG Mobile support tool. I think I'm back at stock,unrooted firmware!
Ran adb reboot oem-unlock to unlock bootloader.
Tried again to run adb sideload cm-11. Transfers file to phone ok but installation fails with usual firmware is for p880 this phone is an X3.
Tried to root with o4xr but it fails also.
Have checked usb debugging and unknown sources.

bpjh56 said:
Thanks for the reply.
I've managed to get the phone to work.
Found a software upgrade combination (vol up, connect usb I think), then used LG Mobile support tool. I think I'm back at stock,unrooted firmware!
Ran adb reboot oem-unlock to unlock bootloader.
Tried again to run adb sideload cm-11. Transfers file to phone ok but installation fails with usual firmware is for p880 this phone is an X3.
Tried to root with o4xr but it fails also.
Have checked usb debugging and unknown sources.
Click to expand...
Click to collapse
There's a way to get around this.
You have to look in the zip file you want to flash and search for a text file.
In this text file (something with update as far as I remember) there's a line called getprop="X3" (in your case.
Delete this line and you should be good to go.
Sent from my LG-P880 using XDA Premium 4 mobile app

I've unpacked the cm-11 archive using 7zip.
Found a text file called updater-script.
The file starts;
assert(getprop("ro.product.device") == "p880" || getprop("ro.build.product") == "p880" || abort("This package is for \"p880\" devices; this is a \"" + getprop("ro.product.device") + "\".")
If I delete all of this, save and remake the archive using 7zip it fails with "Verifying Update Package...installation aborted"
I tried changing it to:
assert(getprop("ro.product.device") == "x3" || getprop("ro.build.product") == "x3" || abort("This package is for \"x3\" devices; this is a \"" + getprop("ro.product.device") + "\".")
Same error.

bpjh56 said:
If I delete all of this, save and remake the archive using 7zip it fails with "Verifying Update Package...installation aborted"
Click to expand...
Click to collapse
Use winrar, edit the file from within the archive and just save the changes without changing compression parameters
Check the encoding used with your text manager, use notepad++
In any case your problem is the recovery. Download twrp 2.7 from omni rom's thread
extract zip file there's an recovery.img file
open terminal and execute:
adb reboot oem-unlock
fastboot flash recovery c:/path/to/recovery.img (or drag the file inside the temrinal window)
fastboot reboot

Do you mean delete the first section or change p880 references to x3?
You're right about the recovery.
I installed cyanogen rom manager from play store and installed cm recovery from there. The idea was to try and upgrade from the sdcard.
Now the recovery does not work at all.
Pushing vol down and power I just get a red error message. Same goes for vol up and add usb cable.
Phone still works though.
Will your recovery procedure fix the bootloader?
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Actually I can't flash the recovery image because adb no longer detects my phone.
Not correct, After normal booting of phone it adb does detect it

bpjh56 said:
Do you mean delete the first section or change p880 references to x3?
You're right about the recovery.
I installed cyanogen rom manager from play store and installed cm recovery from there. The idea was to try and upgrade from the sdcard.
Now the recovery does not work at all.
Pushing vol down and power I just get a red error message. Same goes for vol up and add usb cable.
Phone still works though.
Will your recovery procedure fix the bootloader?
---------- Post added at 01:09 AM ---------- Previous post was at 01:00 AM ----------
Actually I can't flash the recovery image because adb no longer detects my phone.
Not correct, After normal booting of phone it adb does detect it
Click to expand...
Click to collapse
Did you get the recovery working yet? The red error message upon trying to boot into recovery usually indicates the bootloader isn't properly unlocked. Could you check the secret menu or S/W upgrade mode to see if it's actually unlocked? If that's not the case, restore everything again with the LGMobile Support Tool, unlock the bootloader, check if it's unlocked, flash a custom recovery and try to flash your ROM using that recovery. In that case you shouldn't have to worry about changing updater scripts. Good luck!
Sent from my LG-P880 using xda app-developers app

Used 3845#*880#
Bootloader reported as locked. This after using adb reboot oem-unlock.
If I reinstall using the LG Mobile tool how do I unlock the bootloader?
Will reinstall also repair the bootlaoder?

I''ve reinstalled the firmware using the LG Support tool.
This has fixed the bootloader.
The bootloader is reporting as being locked though after I run adb reboot oem-unlock.

[Q] Cannot update to sense 6 (HTC One m7)

I am not able to install the official HTC sense 6 update on my m7. It downloads fine and gets checked. When I press "install now" it reboots into recovery , then an error occurs. TWRP makes this log :
E:Mount /system Success!
script aborted: assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" ,
"22222222" , "33333333" , "44444444" , "55555555" , "66666666" ,
"77777777" , "88888888" , "99999999" , "HTC__001" , "HTC__Y13" ,
"HTC__E11" , "HTC__102" , "HTC__203" , "HTC__405" , "HTC__304" ,
"HTC__A07" , "HTC__032" , "HTC__J15" , "HTC__016") == "t"
assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" , "22222222" , "33333333" , "44444444" , "55555555" , "66666666" , "77777777" , "88888888" , "99999999" , "HTC__001" , "HTC__Y13" , "HTC__E11" , "HTC__102" , "HTC__203" , "HTC__405" , "HTC__304" , "HTC__A07" , "HTC__032" , "HTC__J15" , "HTC__016") == "t"
E:Error executing updater binary in zip '/sdcard/Download/OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404.zip'
Error flashing zip '/sdcard/Download/OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404.zip'
Updating partition details...
Iata backup size is 2353MB, size: 26206MB, used: 19726MB, free: 6306MB, in data/media: 17372MB.
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: 'main2'
I:Set page: 'advanced'
I:Set page: 'confirm_action'
I:Set page: 'action_page'
I:Copying file /tmp/recovery.log to /data/media/0/recovery.log
the same when I try to manually find and install the OTA in recovery. The phone is stock, rooted, s-off, cid 11111111. the only thing I tried to mess with was changing the system file wpa_supplicant with a different version from CM11 (in order to allow the phone to recognize ad-hoc wlan), but that seems to be irrelevant, because at the time I didn't know that you have to be S-OFF so that any of the changes in root stay permanent....
So the phone basically is all stock if i'm not mistaken???
bootloader shows:
TAMPERED
UNLOCKED
m7_UL PVT SHIP S-OFF RH
CID 11111111.................before it was HTC__002
HBOOT- 1.65.0000
RADIO- 4A.25.3263.21
OpenDSP-v32.120.274.0909
OS- 4.19.401.11
eMMC-boot 2048MB
Feb 26 2014,12:32:09.0
I have no idea why it won't update.
Again: I received the update even before I had S-OFF and CID11111111 . It won't install even after changing those.
I'm clearly at loss here... I want the stock update to also update the firmware not only for the ROM.
pls give me a hint , I'm a total noob
F***KIN HELL, WHERE THE HECK WAS I SUPPOSED TO KNOW I NEEDED A STOCK RECOVERY .....WHY HASNT ANYONE MENTION IT AT ALL.....just found it on after reading 40+ pages of the UPDATES thread ....a random page 719.... BRILLIANT

As far as I know, you need stock recovery (and maybe a locked bootloader too) to install a OEM OTA update.

cool so I flashed the stock recovery and the update started ...... and it's now stuck on a red triangle with an exclamation mark in the middle....I\m screwed right

mengo_ said:
cool so I flashed the stock recovery and the update started ...... and it's now stuck on a red triangle with an exclamation mark in the middle....I\m screwed right
Click to expand...
Click to collapse
Did the progress bar actually moved? If not, hold the power button and device will forcefully restart

yes it moved for a while ...and then changed to the triangle around halfway through.....restarted ....everything is the same sense v 5.5 , stock recovery

mengo_ said:
yes it moved for a while ...and then changed to the triangle around halfway through.....restarted ....everything is the same sense v 5.5 , stock recovery
Click to expand...
Click to collapse
So there is an error, you have to try to get the OTA applying again adn see the error on the recovery. If you don't see anything, try playing with the volume buttons till something show up on the recovery screen.

SaHiLzZ said:
So there is an error, you have to try to get the OTA applying again adn see the error on the recovery. If you don't see anything, try playing with the volume buttons till something show up on the recovery screen.
Click to expand...
Click to collapse
isnt a log created somewhere with the stock recovery?

mengo_ said:
yes it moved for a while ...and then changed to the triangle around halfway through.....restarted ....everything is the same sense v 5.5 , stock recovery
Click to expand...
Click to collapse
press volume up for 3-4 sec then power button up to home button light blinks then leave them it will show note that text
& again it's same problem unlocking boot loader cause delete preload apps that interfering with OTA update correct that
from HTC One

mengo_ said:
isnt a log created somewhere with the stock recovery?
Click to expand...
Click to collapse
No..

ok.. stock recovery says
mount SDCARD failed 1 times, 2, 3,4, 5, times
can not mount SD card (no such device)
write host_mode:0 done
...strange, if I understand right what it is.... when I restart and boot system everything seems normal...
.....
maybe because i restarted to recovery midway through boot up .... trying again....
ok disregard the above.. you man prob. got it right I'm impressed it actually says right after update fails:
Finding update package...
Opening update package....
Verifying update package...
Installing update
Verifying current system...
Check /data/preload/soundhound_freemium.apk failed, error No such file or Directory ()
Installation aborted
write Host_mode:0 done

mengo_ said:
Finding update package...
Opening update package....
Verifying update package...
Installing update
Verifying current system...
Check /data/preload/soundhound_freemium.apk failed, error No such file or Directory ()
Installation aborted
write Host_mode:0 done
Click to expand...
Click to collapse
So it is missing this file.. because of bootloader unlock.. Look around the forum, I am sure somone has shared it already.

SaHiLzZ said:
So it is missing this file.. because of bootloader unlock.. Look around the forum, I am sure somone has shared it already.
Click to expand...
Click to collapse
got it.... thank you guys !!.... one last question . any idea where exactly to put data/preloaded/ ?

mengo_ said:
got it.... thank you guys !!.... one last question . any idea where exactly to put data/preloaded/ ?
Click to expand...
Click to collapse
sdcard is actually /data/media/
I will suggest using a es file explorer, and create that folder under /data/ ... You may need the device rooted for that..

I'll just try placing them in device/data/preload ....
. I haven't made any nandroid backups and I couldn't really find the preloaded apks for 4.19.401.11
Closest thing I found is 4.19.401.5 preload.....
no idea what will happen .
coming from samsung to htc things are complicated as hell. and there aren't clear and consistent guides what to do ....
IT WORKED !!.... now to make a proper backup and put the custom recovery and unlock and remove all the bloat ware

My HTC one is on viperone 6.2.1, please tell me how to upgrade stock sense 6.0. Thanks

chucdv said:
My HTC one is on viperone 6.2.1, please tell me how to upgrade stock sense 6.0. Thanks
Click to expand...
Click to collapse
find a stock Rom ruu exe / zip Or guru reset Rom or nandroid backup install them properly then update to sense 6
from HTC One

Same Problem
I recently got a HTC One off of CL, and Im having issues. I set it up but it tells me right away "Unauthorized Device" This app is not compatible with your device. I can get into Settings but thats it. I tried downloading the latest update but during installation it stops and goes to a red triangle with an exclamation mark in it. Any help would be appreciated

Installed TWRP on Xperia Z3C but installation throws error because of empty /system

Hey all,
I've unlocked the bootloader using the Sony guide (using fastboot with a specific unlock code), after that I managed to install TWRP. However, the command I executed, was
Code:
fastboot flash boot my_recovery.img
instead of
Code:
fastboot flash recovery my_recovery.img
I cant tell if this made a difference, but the TWRP loads up fine however the original Android firmware is not available through startup (it always boots to TWRP). This isnt a problem by itself, since I wanted to install a 14.1 lineageOS build on it anyway.
However, during the installation process of my lineageos.zip im getting the error:
Code:
Updater process ended with ERROR: 7
Error installing zip file /external_sd/lineage-14.blabla.zip
After some digging I noticed this was because of an incorrect match with my `build.prop` file. I tried a fix on the zip-file by editing the `META-INF/com/google/android/updater-script` file but it still fails the installation. Then I noticed the complete `/system/` directory is empty on my phone. I'm assuming it needs to use some of the data in here to start installing the ROM (idk why though).
I hope someone on these forums can point me in the right direction on what to do now, so I can start installing some custom firmware.
Thanks in advance

Flamedog said:
Hey all,
I've unlocked the bootloader using the Sony guide (using fastboot with a specific unlock code), after that I managed to install TWRP. However, the command I executed, was
Code:
fastboot flash boot my_recovery.img
instead of
Code:
fastboot flash recovery my_recovery.img
I cant tell if this made a difference, but the TWRP loads up fine however the original Android firmware is not available through startup (it always boots to TWRP). This isnt a problem by itself, since I wanted to install a 14.1 lineageOS build on it anyway.
However, during the installation process of my lineageos.zip im getting the error:
Code:
Updater process ended with ERROR: 7
Error installing zip file /external_sd/lineage-14.blabla.zip
After some digging I noticed this was because of an incorrect match with my `build.prop` file. I tried a fix on the zip-file by editing the `META-INF/com/google/android/updater-script` file but it still fails the installation. Then I noticed the complete `/system/` directory is empty on my phone. I'm assuming it needs to use some of the data in here to start installing the ROM (idk why though).
I hope someone on these forums can point me in the right direction on what to do now, so I can start installing some custom firmware.
Thanks in advance
Click to expand...
Click to collapse
The system folder was empty because you didn't mount it.
Second flash recovery to the recovery partition and then hold the volume down and power while booting the phone which will actually boot to the recovery partition.
Essentialy what you did is you overwrote the kernel of your current ROM and replaced it with TWRP,hence the thing it doesn't want to load Android and as well it cannot replace the boot partition when you are trying to install the ROM since you are using it and it cannot overwrite it.
So just flash the recovery using that fastboot command,boot into it the way I said and try to flash the ROM.
It should work.

Dinkec27 said:
The system folder was empty because you didn't mount it.
Second flash recovery to the recovery partition and then hold the volume down and power while booting the phone which will actually boot to the recovery partition.
Essentialy what you did is you overwrote the kernel of your current ROM and replaced it with TWRP,hence the thing it doesn't want to load Android and as well it cannot replace the boot partition when you are trying to install the ROM since you are using it and it cannot overwrite it.
So just flash the recovery using that fastboot command,boot into it the way I said and try to flash the ROM.
It should work.
Click to expand...
Click to collapse
Hey thanks for replying, I tried flashing again using the recovery partition/folder now. I rebooted the phone into TWRP using volume down + power button, but sadly it threw the exact same error. Some file is missing which is used to determine my device specs, as is shown in the output:
Code:
E3004: This package is for device: aries,z3c,D5803,D5833; this devices is .
It tries to paste my device identifier in this error but there is nothing in front of the dot. My device is the D5803.
Also I cant tell for sure if it booted into recovery folder because the boot folder still holds the TWRP from the previous "fastboot flash boot file.img" command. Can i somehow re-flash the "boot" partition so it doesnt contain TWRP anymore just to be sure?

Flamedog said:
Hey thanks for replying, I tried flashing again using the recovery partition/folder now. I rebooted the phone into TWRP using volume down + power button, but sadly it threw the exact same error. Some file is missing which is used to determine my device specs, as is shown in the output:
Code:
E3004: This package is for device: aries,z3c,D5803,D5833; this devices is .
It tries to paste my device identifier in this error but there is nothing in front of the dot. My device is the D5803.
Also I cant tell for sure if it booted into recovery folder because the boot folder still holds the TWRP from the previous "fastboot flash boot file.img" command. Can i somehow re-flash the "boot" partition so it doesnt contain TWRP anymore just to be sure?
Click to expand...
Click to collapse
You can by reflashing stock firmware or whatever you were running before.
As for the error,did you 100 percent remove the getprop lines at the beginning of the updater script?

Dinkec27 said:
You can by reflashing stock firmware or whatever you were running before.
As for the error,did you 100 percent remove the getprop lines at the beginning of the updater script?
Click to expand...
Click to collapse
Alright i got it to install the ROM now, thanks! I accidentally compiled the zip with a map inside it, so lineagemod.zip would contain lineagemod.zip/lineagemod/META-INF/com/...
In fact I think the TWRP on "boot" partition wouldnt have mattered while installing the ROM, if I zipped it correctly previously. However it needed to go to "recovery" partition anyway in order to keep it working i guess

Flamedog said:
Alright i got it to install the ROM now, thanks! I accidentally compiled the zip with a map inside it, so lineagemod.zip would contain lineagemod.zip/lineagemod/META-INF/com/...
In fact I think the TWRP on "boot" partition wouldnt have mattered while installing the ROM, if I zipped it correctly previously. However it needed to go to "recovery" partition anyway in order to keep it working i guess
Click to expand...
Click to collapse
Yeah. Good that everything works now.

I still have the problem ...
Hi all,
the errors described are exactly the same on my z3c!
I deleted the first line in the script as described above.
"/system" is mounted. But trying to install fails because
"/system" is not found? Which step did I miss?
Lem Ning
---
twrp 3.0.2-1
lineage-14.1-20170106-UNOFFICIAL-z3c.zip

Firstly, install back stock KK firmware.
After that, you can install another MM/N firmware.
I dont know how it be, but from MM firmware, cant install another MM firmware via TWRP

Just to be sure ...
xtbtvd12399 said:
Firstly, install back stock KK firmware.
After that, you can install another MM/N firmware.
I dont know how it be, but from MM firmware, cant install another MM firmware via TWRP
Click to expand...
Click to collapse
Thanks for your quick answer. What ist meant by "MM/N firmware"? And
what is "stock KK firmware"?

lemning said:
Thanks for your quick answer. What ist meant by "MM/N firmware"? And
what is "stock KK firmware"?
Click to expand...
Click to collapse
Stock Kitkat firmware. Marshmallow/Nougat firmware

Version Number of KK of Z3compact?
Hi,
wich is the version number? The lowest verion for my phone seems to be 23.1.A.1.28 / Android 5.0.2.
Will the migration to lineage os 14.1 work?
Thanks for your answers!

lemning said:
Hi,
wich is the version number? The lowest verion for my phone seems to be 23.1.A.1.28 / Android 5.0.2.
Will the migration to lineage os 14.1 work?
Thanks for your answers!
Click to expand...
Click to collapse
Here is stock Z3C stock rom.
Your phone arent Z3 compact?
I dont know about Lolilpop, never try it before

unzip the ROM, modify the file 'user-script' in META-INF/com/google/android,
remove the top several lines, it would be like these:
Code:
(getprop("ro.product.device") == "D5803" || getprop("ro.build.product") == "D5803" ||
getprop("ro.product.device") == "D5833" || getprop("ro.build.product") == "D5833" ||
getprop("ro.product.device") == "z3c" || getprop("ro.build.product") == "z3c" ||
getprop("ro.product.device") == "aries" || getprop("ro.build.product") == "aries") || abort("This package is for \"D5803,D5833,z3c,aries\" devices
this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Target: 1506639044");
ifelse(is_mounted("/system"), unmount("/system"));
save this file, and then re-zip all files.
reflash the ROM, it would be okay!
Good luck!
ref: https://www.quora.com/How-do-I-fix-Error-7-in-TWRP

In my case the Error is like: E3004: This package is for device: z3c; this device is aries.
In the UPDATER-SCRIPT it says: assert(getprop("ro.product.device") == "z3c" (no other devices are listed here)
Arent "aries" and "z3c" identical? Does that mean I can just delete that line in the UPDATER-SCRIPT and install the os?

Easy fix:
Get a recent TWRP for Z3 Compact, for example:
[RECOVERY][UNOFFICIAL] TWRP 3.2.3-0 for aries [01-09-2018]
Introduction Hi to all dear Z3c users. This is my first TWRP build, I used omni minimal TWRP source and kernel from Sony git. I hope you enjoy this. How to install Fist of all you MUST flash lastest 23.5.A.1.291 firmware with FlashTool at least...
forum.xda-developers.com
Download Android Image Kitchen from here:
[TOOL] Android Image Kitchen - Unpack/Repack Kernel Ramdisk [Win/Android/Linux/Mac]
Android Image Kitchen -- Unpack/Repack Kernel+Recovery Images, and Edit the ramdisk. Windows ports of the necessary Linux utils for Android image (kernel/recovery) mod work: mkbootimg, unpackbootimg: https://github.com/osm0sis/mkbootimg...
forum.xda-developers.com
Extract the folder "Android Image Kitchen" and also copy your TWRP img (for example recovery.img) into it's directory
Drag'n'drop the TWRP img onto unpackimg.bat and wait until the script succeeds
Go to the newly created directory ramdisk and edit the file default.prop:
Replace
ro.build.product=aries
ro.product.device=aries
ro.omni.device=aries
with
ro.build.product=z3c
ro.product.device=z3c
ro.omni.device=z3c
Save file
Go back and double-click repackimg.bat
Wait until it finishes
Flash the image-new.img on your phone; error should be gone for every ROM image as long as you don't update TWRP
So you don't have to edit every single ROM update.

klaus-peter said:
In my case the Error is like: E3004: This package is for device: z3c; this device is aries.
In the UPDATER-SCRIPT it says: assert(getprop("ro.product.device") == "z3c" (no other devices are listed here)
Arent "aries" and "z3c" identical? Does that mean I can just delete that line in the UPDATER-SCRIPT and install the os?
Click to expand...
Click to collapse
Yes and yes, I used to do it this way in the last years but found a better way now, see above.

Huawei GT3 ROM Help [NO OS]

Hi, I saw some threads saying some stuff about the Huawei GT3, but they didnt helped me so Im posting this thread.
I have a huge Problem with my phone.
(Im a Newbie btw)
I wanted to root my phone so I installed TWRP and rebooted (TWRP works btw), now it said "Encryption unsuccessfull"
I looked up on YouTube to look how to fix this and ended up deleting my complete OS
Now I downloaded the Firmware of my Phone and looked how to install it with TWRP and ADB.
When I try to install the "update.zip" File with TWRP it says something like this :
[2017-11-14 08:00:21 623] E:unknown command [errno]
dload_format_userdata,line=527: dload_format_userdata ok!
script aborted: update_huawei_pkg_from_ota_zip: update package from zip failed
update_huawei_pkg_from_ota_zip: update package from zip failed
Updater process ended with ERROR: 7
I:Legacy property environment disabled.
I:Install took 0 second(s).
Error installing zip file '/data/update.zip'
I also tried to delete the "assert" parts in the updater-script file but it also didnt work.
Now I heard about the "dload" Method but I have some questions about that
1. Where is the dload folder exactly
2. When I try to move the folder cointaining the "update.zip" to as expample root It says not enough space on device (which Is not true) or something like this :
Running command: 'mv "/data/update.zip" "/root"'
mv: write error: No space left on device
mv "/data/update.zip" "/root" process ended with ERROR: 1
Do I maybe have the wrong ROM or something?
Please help me . (or try )

Check the dload guide in my signature. You will know everything. Let me know if any questions or doubts, will help. Dont worry twrp error is normal as these zips shouldn't be flashed with twrp

shashank1320 said:
Check the dload guide in my signature. You will know everything. Let me know if any questions or doubts, will help. Dont worry twrp error is normal as these zips shouldn't be flashed with twrp
Click to expand...
Click to collapse
Hi! Thanks for your reply!
I bought myself a Micro-SD card and extraced the ZIP like in your tutorial, and its working!
Its installing right now!
But I wanted to say something..first thank you very much and second the Russian Website you provided gave me the wrong package, this was the right one :
skyneel.com/huawei-gt3-nougat

niclasdriver said:
Hi! Thanks for your reply!
I bought myself a Micro-SD card and extraced the ZIP like in your tutorial, and its working!
Its installing right now!
But I wanted to say something..first thank you very much and second the Russian Website you provided gave me the wrong package, this was the right one :
skyneel.com/huawei-gt3-nougat
Click to expand...
Click to collapse
There are many ways to get firmware but the best part it worked and successful. Enjoy buddy.