Database Develop

[Q] Cyanogen Mod 6 won't install on N1

I've updated the radio and the latest stable version of Cyanogenmod 6 won't install. I've tried ROMmanager and Manual install via recovery and always end up with a Status 7, aborted install. What am I doing wrong? I am running FRF91 ROM right now with the latest Radio with no problem, but would at least like to check out Cyanogenmod6 to see what it offers over the Stock Froyo ROM.
Here are the steps I take:
Enter Recovery Mode.
BOOTLOADER
RECOVERY
Which takes me to ClockworkMod Recovery v2.5.0.7
WIPE DATA/FACTORY RESET
WIPE CACHE PARTITION
INSTALL ZIP FROM SDCARD
CHOOSE ZIP FROM SDCARD
Then I navigate to and select:
update-cm-6.0.0-N1-signed.zip
The install starts running, and then I get this error message:
assert failed: getprop("ro.bootloader") == "0.333.2012" ||getprop("ro.bootloader") == "0.333.2012"
E: Error in sdcard/update-cm-6.0.0-N1-signed.zip
(Status 7)
Installation aborted
Then I have to restore my ROM back to FRF91.
Any help will be much appreciated

Looks like you have a new HBOOT.
Here's a guide for downgrading:
http://forum.xda-developers.com/showthread.php?t=726258

HBOOT
I'll take your word for it and try the steps you pointed me to and see if it works. Thanks in advance!

It Works
I followed your instructions and it worked! Thanks.

[Q] Issues moving from Darky 10.1-3 to CM7.1

Well, I was trying to move from Darky 10.1-3 to CM7.1 oona GT-i9000 and whatever method I have tried I couldn't do so.
1. When I tried flashing CM7.1 directly from Dark Core Recovery (threads show it's supposed to work) I have first encountered some sort of a boot-loop. I see console flashes quick and then it reboots. I have entered CWM recovery mode and reflashed and now the phone starts, with the USIM card inside I have no reception and com.android.phone continuously crashes. Was unable to do much with that.
2. As method 1 failed I have downloaded EZBase's Froyo bootloader and flashed it. There from CWM Recover I have tried flashing but it failed and I'm getting the following:
assert failed: getprop("ro.product.device") == "galaxys" || getprp("ro.beuild.product") == "galaxys"
and it keeps repeating itself, just instead of "galaxys" it says "GT-I9000" and other possible names for an i9000.
Any advice anyone ?

Did you Wipe? (wipe data/factory reset + wipe cache partition)
Also you might have ext4 lagfix enabled. Go to CWM and disable it.
Then try again.

I normally flash the CM7 initial kernel using odin and then only use CWM to flash CM7 nightly or stable.

[Q] problem with malez recovery

i am trying to install a custom rom on my Liquid acer S100
so i installed malez custom recovery 0.6.2 (the easy installer method)
i can boot to the recovery menu but everything i try to do fails
whenever i select anything it says aborted
flash aborted
wipe aborted
POWER OFF aborted
even Coppy recovery.log to sdcard aborted
please help my phone is useless that way
i am now using 2.2 rom which i flashed using a .bin flashtool. its even slower than my old 2.1 which i cant restore right now
btw, i rooted it visa superoneclick
and i think it was successful cuz i can use root explorer r/w mode
at the last step of installation (after OS boot)
i see this message at the adb log
rm failed -for read-only file system
is that whats causing the problem ??

hsn.ahmed said:
i am trying to install a custom rom on my Liquid acer S100
so i installed malez custom recovery 0.6.2 (the easy installer method)
i can boot to the recovery menu but everything i try to do fails
whenever i select anything it says aborted
flash aborted
wipe aborted
POWER OFF aborted
even Coppy recovery.log to sdcard aborted
please help my phone is useless that way
i am now using 2.2 rom which i flashed using a .bin flashtool. its even slower than my old 2.1 which i cant restore right now
btw, i rooted it visa superoneclick
and i think it was successful cuz i can use root explorer r/w mode
at the last step of installation (after OS boot)
i see this message at the adb log
rm failed -for read-only file system
is that whats causing the problem ??
Click to expand...
Click to collapse
Try factory resetting and than the exe recovery and root from within recovery. It took me 2 times to get it working error free.
Sent from my SGH-I997 using XDA Premium App

-I cant get malez recovery to work on my brother phone. after install acer liquid drivers and all dat. phone conect to pc, mount sdcard but nothing happens

[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.

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.