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
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.
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.
Hello,
I've got an X526 phone that overnight lost its signal.
I tried the different solutions found on the forum.
- Erase Modem
fastboot erase modemst1
fastboot erase modemst2
- Installation of the Indian 21s rom stock then flash of the bootloader+modem 21s and 19s file.
- Attempt to install CUOCO ROM but it is impossible because it is for the X527 "s2"and not the X526 "s2_ww".
Do you have any other suggestions? or other way to install CUOCO ROM?
Thanks
there is a way to skip the device model verification. But Roms are specifically made to use the particular hardware in the device. The rom may not install and you might get other errors while installing if the rom is not compatible with the device, or you will struck in bootloop or you may experience UI crashes. If you are okay with that, follow this
Prerequisites: Download and install notepad++ on your pc
Download compatible Rom
Extract it with winrar or 7zip
Browse to "Rom/META-INF\com\google\android" and locate this file "updater-script"
Open that file with "Notepad++"
put "#" before this line: assert(getprop("ro.product.device") i.e., #assert(getprop("ro.product.device")
and do the same for lines start with "getprop("ro.product.device")" # getprop("ro.product.device")
........it must be first 2 or three lines depending on the model......
save it and close notepad++
navigate to the parent folder (which contains all files like "meta INF and install" folders and other files)
right click and click "add to archive" and save it as "Zip file"
Copy & flash through TWRP
you wont get Error 7 but you might get other errors while installing if the rom is not compatible with the device
Good Luck
Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks
I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.
timsch75 said:
I just tried to install the zip file without signature verification, and it failed to unpack the image
Updater process ended with ERROR: 1
Error installing zip file '/external_sd/twrp-installer-3.5.0_9-0-lake.zip'
I've downloaded this a couple of times with the same result.
Click to expand...
Click to collapse
Did you go in to TWRP Advanced and try to sideload TWRP ?
timsch75 said:
Hello. Newbie here trying to install TWRP onto my G7+ (xt1965-T, moto not Revlry). I've been following the twrp.me instructions, among others. I've got the bootloader unlocked, adb & fastboot devices both return what they should, I've copied the twrp-3.5.0_9-0-lake IMG & ZIP files to my platform-tools folder and am running powershell from there. I copied the zip file to the internal memory of the phone as well as the ASC file with basic copy/paste commands in windows.
I temporarily boot the TWRP image and try to install the zip file, only to have it fail signature verification. I tried it without sig verification but still failed on some error. I've searched, but I haven't been able to find anything to get me past this.
Confusion comes with conflicting instructions. I see here that there is a method that differs from the instructions linked above, AFIAK.
There is a note on the bottom of the 1st instructions stating " If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest firmware for your device and reflash the boot image." I did ignorantly initially type the command fastboot flash recovery TWRPxxx.img. Would this have anything to do with my issues?
Are there multiple ways to achieve installation of TWRP & something like LineageOS and I'm just getting confused between instructions for each?
Thanks
Click to expand...
Click to collapse
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.
chuck8812 said:
I fought this same model G7+ (XT1965-T) for several days, trying to install LineageOS for microG. Here are the instructions I used here ....I used the same recovery image (twrp-3.5.0_9-0-lake .img) as you. Download the copy-partitions-20200903_1329.zip from here. To sideload copy-partitions zip in TWRP go to Advanced tab, ADB sideload tab, then I sideloaded lineage-17.1-20210202-microG-lake.zip here.
Click to expand...
Click to collapse
I've regressed. I had previously been ably to temporarily boot into TWRP with the fastboot boot x.img command, at least in windows, but for some reason now it hangs up and will not show the TWRP screen. I had this same issue in Linux, but it worked in Windows, but now it fails the same in both. I run the command above and it shows the typical splash screen that it would if booting the stock android system, but goes no further. Previously, it would flash this , but then go to the TWRP screen. I can't get any feedback from adding the verbose flag to the fastboot command. Any way to track down this problem?
effin 'ell I hate regressions, 'specially the ones that come out of nowhere.
p.s. I don't know what happened with the previous blank post. I was trying to reply in Windows, but it wouldn't let me enter text. I rebooted into Linux for this post, and I see that something got posted previously. I'd delete it if I could.... gremlins