Hello, I recently (and successfully) installed Blackrose and fastboot flashed the need partition sizes to install an ICS rom. I have since decided that I want to go back to CM7 for the time being. I booted my phone onto fastboot and tried to flash the stock hboot .nb0 file (The one that came with the blackrose folder, it is labeled stock) and I get this error: "FAILED (remote: image update error)"
I was wondering if anyone can shed any light on how I can be able to go back to the stock partition size so I can restore my CM7 backup. I assume it will not work with sizes needed for ICS. Thank you VERY much.
A recent thread
http://forum.xda-developers.com/showthread.php?t=1460035
Sent from my Transformer TF101 using Tapatalk
i gave some options on br thread
can you see phone listed after typing fastboot devices
you must copy it from binary folder in br folder to your fastboot path--ie the sdk tools folder for me
then cd to that folder in command window
in binary folder hboot_stock.nb0
i try to updated my htc one to sense 6.0 when it installed the updated it will stuck at half and showing the red triangle.
tried factory reset and wipe cache but not worked.
seems like it cannot find soundhound_freemium.apk ... but try search google nothing come out.
is some know how to do solve this annoying problem? i am a totally noob. thanks guys!:laugh:
here is the message
and find the message below:
finding update packing...
opening update packing..
verifying current system...
check/date/preload/soundhound_freemium.apk failed, error No such file or directory
installation aborted.
write host_mode:0 done
zj2252 said:
i try to updated my htc one to sense 6.0 when it installed the updated it will stuck at half and showing the red triangle.
tried factory reset and wipe cache but not worked.
seems like it cannot find soundhound_freemium.apk ... but try search google nothing come out.
is some know how to do solve this annoying problem? i am a totally noob. thanks guys!:laugh:
here is the message
and find the message below:
finding update packing...
opening update packing..
verifying current system...
check/date/preload/soundhound_freemium.apk failed, error No such file or directory
installation aborted.
write host_mode:0 done
Click to expand...
Click to collapse
post the output of fastboot getvar all except imei and serialno
you have unlocked bootloader. This process wipe /data including all HTC preloaded apps in /data/preload/. The ota updates sometime applies patches to these preloaded app. If they are missing, youmust put them back in that folder and set the right permission.
Solved
alray said:
post the output of fastboot getvar all except imei and serialno
you have unlocked bootloader. This process wipe /data including all HTC preloaded apps in /data/preload/. The ota updates sometime applies patches to these preloaded app. If they are missing, youmust put them back in that folder and set the right permission.
Click to expand...
Click to collapse
1. Hi, first You Phone needs to stay Rooted
2.you need to have your phone S-on
3.You would have to get your Current Phone's OTA in Zip Downloaded
4.Get es Explorer
5.Decompress The OTA.zip Somewhere on your Pc then Browse through it,You will see a folder Data/Preload
6.Copy everything and paste it in your Phone anywhere you want it
7.Now use the es explore To create the same folder in 0/Data Create new folder Preload there then paste the Whole thing there
8.Now from the es Explorer Change the Permission of every file and apps ( Check on everything)
I almost forgot u must be on original stock recovery of your Phone for the update to run
9.Paste The new Ota update in your downloads then Check for updates then you would get Update completed Intall now.
10.Install it now And you are Done
Sense looks very awesome let me now if there is anything else
I ran into this exact problem and just reflashed the stock ruu with s off and ran all the ota updates again and it worked.
Good luck!
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.
I want to install new Roms on my phone.
I followed the guides in the forum and unlocked the bootloader, and installed TWRP. However, when I try to install the new roms like Resurrection Rom v6 or AospExtended v5.8 I get the following error:
Code:
E3004: This package is for device: titan, titan_umts, titan_udstv, titan_umtsd, titan_retaildsds, XT1068, XT1064, XT1063, XT1069; This device is .
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/sdcard/RR-o-V6.2.0-20180911-titan-Final.zip' .....[/COLOR]
I get a similar error for ASOP package too. except it complains about the bootloader:
Code:
E3004: This package supports booltloader(s): 0x4882, 0x4883,0x4886,0x4887; This device has bootloader
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/sdcard/RR-o-V6.2.0-20180911-titan-Final.zip' .....[/COLOR]
.
My device model is: XT1068
And in the fastboot screen it says: 48.86
I would appreciate it if someone could guide me on how to resolve the issue.
mraabs said:
I want to install new Roms on my phone.
I followed the guides in the forum and unlocked the bootloader, and installed TWRP. However, when I try to install the new roms like Resurrection Rom v6 or AospExtended v5.8 I get the following error:
I get a similar error for ASOP package too. except it complains about the bootloader:
.
My device model is: XT1068
And in the fastboot screen it says: 48.86
I would appreciate it if someone could guide me on how to resolve the issue.
Click to expand...
Click to collapse
You should've searched on YouTube. Unzip your rom using winrar, I don't remember the path but you have to remove the first two assert lines of the script with notepad++ and save it back and rezip the ROM.
Search on YouTube "how to fix error 7 in twrp". And follow his steps.
I just replace the default bootloader version present in script with the bootloader version it gave the error and it works.
Edit.
Or for avoiding any errors after rezipping the ROM. Just open the ROM zip through winrar and navigate to the script directory and hold n drag it outside and then delete the script present in that zip file and after editing the script using notepad++ hold n drag it back to the same directory. This way you'll not have to unzip and rezip.
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