Database Develop

[Q] HELP

I wanted to install latest cyanogen rom(SPQ Rom 0.6).
I went to recovery, have psf freedom recovery, and wipe data.
Then when I wanted to install zip, chose the rom and it wouldnt install.(error messege at bottom) Anyway now I can't go past the tattoo startup image before boot image. Can't do usb mass storage.
Is there a way to install new recovery image via fastboot, hboot.
Also tried the reset with phone turned off.
Nothing worked. Doesn't wipe correctly now also, "error mounting /sd-ext/!
Skipping format...
error message is as follow:
assert failed: getprop("ro.product.device") == "bahamas" l l getprop("ro.build.product") == "bahamas l l getprop(ro.product.board") == "bahams"
E:Error in /sdcard/SPQRom-0.6.zip
(Status 7)
Installation aborted.
THREAD CLOSED not development related
ask ur question in the Q & A thread

re:HELP
I am not an expert, but i think it could be from the SD card.
What partitions do you have on it?

Don't have any, because of the cyanogen rom. Do you think I have to format sd card?

If you did not partition the SD ,then in my opinion it is most likely from the recovery.But again that's only my opinion.
Sent from my HTC Tattoo using XDA App

I'm thinking the same, because I flashed that psf freedom recovery when it were in its developing stages. When I wanted to flash new rom with that recovery it messed up my phone.
Is there a way to install new recovery via hboot?

went through command prompt. This is what I have so far.
fastboot
fastboot flash recovery recovery.Tattoo.alpha2b.Mvx.img
<waiting for device>

Solved
I solved my problem by finding my backups of my sd-card om my computer. Luckily I had 1 nan backup and restored to that. Works like a charm again at last.
Also had to flash new recovery via adb, didn't want to work with recovery tattoo(from root tattoo in 1 click).

I have this problem too using the PSF recovery and I dont have any nandroid backups

Status 7 CM7

So I was trying to follow directions at this video http://www.youtube.com/watch?v=mLNv_-sEng4 to install CyanogenMod 7 on Captivate. But it fails after applying CM7. (at 6:44 on that video). It finds the package, opens it, but then errors out, (Staus 7). Heres what I did, and what I downloaded. First I copied "captivate-efsbackup.zip 2011-03-03 159.4 KB" and "update-cm-7-04282011-NIGHTLY-Captivate-signed.zip < 8 hours ago 94.1 MB" from "http://sourceforge.net/projects/teamhacksung/files/captivate/" and downloaded "cm7-captivate-initial-kernel.tar 2011-03-19 3.5 MB" from same website. (on video, file name is "cm7-Captivate-initial-20110304.zip"), I tried twice, and same thing. Heres the status when I try to apply CM7
**************************************
--Installing: /sdcard/update-cm-7-04212011-NIGH
TLY-Captivate-signed.zip
E:no misc partition
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device")== "
captivate" || getprop("ro.build.product") == "ca
ptivate" || getprop("ro.product.board") == "capt
ivate"
E:Error in //sdcard/update-cm-7-04212011-NIGHTLY-
Captivate-signed.zip
(Status 7)
Installation aborted.
**************************************
p.s. First I tried with "update-cm-7-04282011-NIGHTLY-Captivate-signed.zip"

please follow the WRITTEN instructions in the cyanogenmod thread. you are doing it wrong (you never used the initial zip).
please don't open new threads because you are incapable of reading.

oh, my bad... thats where the mistake is, i didnt see the initial, thank you, I will try that later.

one quick questions. instructions say
12. Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
13. Do a factory reset / data wipe!
14. Reboot
15. Install the latest update after a reboot!
on step 14, do I have to boot into the android OS, and then restart into recovery mode, and select updated from sd card, and install the update?

zheka1 said:
one quick questions. instructions say
12. Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
13. Do a factory reset / data wipe!
14. Reboot
15. Install the latest update after a reboot!
on step 14, do I have to boot into the android OS, and then restart into recovery mode, and select updated from sd card, and install the update?
Click to expand...
Click to collapse
yes, you have to botto into android at least once before updating.

There's a sticky in here for these kinds of questions. Do NOT start new threads.

and another one closed. Please do a search before posting.

P1000 stuck at boot after updating CM9

Hi guys,
I think I (soft-)bricked my Galaxy Tab (P1000). I hope you can help me
About a month ago, my tablet had installed the Overcome Rom 4.1, based on Android 2.3.
I then decided to try CM9, so I installed one of the first CM9 official nightly builds. I think I installed it simply through the CMW Recovery.
Yesterday I found that the 9.0.0 stable build was out, so I downloaded it from get.cm.
I used Titanium Backup to backup important app data into the "internal sdcard".
Then I used ROM Manager to "install rom from sdcard", choosing to erase cache only (not data), and to create a nandroid backup of my current rom.
ROM Manager rebooted into CWM recovery and started to nandroid backup and to install the new rom.
But, sadly, at next reboot, the tablet was stuck at the samsung boot screen.
It was also impossible to enter recovery mode with the volume up key. The only working mode was the download mode (activated with volume down key)
Today I tried to flash the CWM boot image (downloaded from the Samsung Galaxy Tab (GSM): Full Update Guide" on CM website) using Odin.
Now I can access to CWM Recovery, but it shows a lot of errors.
E.g.:
entering CMW Recovery
Code:
CWM-based Recovery v.5.0.2.8
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
backup and restore > restore from internal sdcard > 2012-08-10-18-55-42
Code:
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
E:format_volume: no MTD partition "/dev/block/st19"
Error while formatting /system!
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
mounts and storage > mount /sdcard
Code:
Error mounting /sdcard!
mounts and storage > mount USB storage
Code:
E:Unable to write to ums lunfile (No such file or directory)
Now here's my questions:
1. What happened? Did I do something wrong in updating CM9 to the stable version?
2. Will I be able to restore my data and/or my nandroid backup?
I can't mount my sdcard from CMW, but when I choose "restore from internal sdcard" it correctly tells my backup date, so I think the internal sdcard content is still there somewhere...
I'd really appreciate to restore all my apps and data!
3. How can I fix this mess? I'd like to have the CM9 installed and working.
Thank you very much!! :angel:

Ok, I've just realized that the internal sdcard is /emmc and not /sdcard.
So the "mount /sdcard" error is normal.
I can correctly mount /emmc from CWM, but if I try to install a rom from a zip file (either the CM9 old nightly or the stable build, which are both saved on the internal emmc), it says:
Code:
-- Installing: /emmc/cm-9.0.0-p1.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000" || getprop("ro.build.product") == "GT-P1000"
E:Error in /emmc/cm-9.0.0-p1.zip
(Status 7)
Installation aborted.
Code:
-- Installing: /emmc/cm-9-20120713-NIGHTLY-p1.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000" || getprop("ro.build.product") == "GT-P1000"
E:Error in /emmc/cm-9-20120713-NIGHTLY-p1.zip
(Status 7)
Installation aborted.

Just restock and start over again:
From the thread: http://forum.xda-developers.com/showthread.php?t=1385153
How to Flash the above zips :
You need to restock your tab if you are running an old MTD build, (only if /system isn't 406 mb, check it by the command `df system` or use an app (such as root explorer) )
IF you are coming from a FSR (STL/BML) ROM (aka Samsung ROM - anything else than the latest CM9 builds / AOKP builds, i.e. any GB ROM, no need to restock)
IF you are coming from a froyo ROM, you need to flash a stock GB ROM first, follow the guide below :
Restocking :
Follow the team overcome restock guide [http://www.teamovercome.net/p1000/?page_id=17], and completely restock your tab.
Once you've flashed it, reboot into download mode again and flash any kernel with recovery (any non-MTD kernels from humberos.com.br, or this forum, for your tab model)
After you've flashed the kernel, reboot into recovery, and this time, install the zip you just downloaded from CyanogenMod servers.
Install Google Apps if you want (gapps-ics-* from goo.im) [optional]
Reboot and enjoy your tab
Normal install :
You need to have a kernel with CWM Recovery
Get the zip from the above download links
Put the zip on your sdcard, reboot into recovery, and install the zip
It'll reboot a few times during the install, that's normal

Will I lose all data on the /emmc partition (including all my TitaniumBackup files) if I restock?
If the answer is yes, is there a way to copy some files from the emmc to an external sdcard before restocking? (e.g. using CWM, or Odin/Heimdall)
Thanks.
Sent from my HTC Vision using xda app-developers app

sigitm said:
Will I lose all data on the /emmc partition (including all my TitaniumBackup files) if I restock?
Click to expand...
Click to collapse
Only if you install overcome rom (via CWM).
Sent from my GT-P1000 using Tapatalk 2

Restock to 2.3.3. Then flash overcome before flashing cm9.

sigitm said:
Ok, I've just realized that the internal sdcard is /emmc and not /sdcard.
So the "mount /sdcard" error is normal.
I can correctly mount /emmc from CWM, but if I try to install a rom from a zip file (either the CM9 old nightly or the stable build, which are both saved on the internal emmc), it says:
Code:
-- Installing: /emmc/cm-9.0.0-p1.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000" || getprop("ro.build.product") == "GT-P1000"
E:Error in /emmc/cm-9.0.0-p1.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
I have exactly the same scenario as you described, so I'm interested, could you find a solution?
I can restock with Odin using theTeam Overcome Guide, the tab boots ok. So I try to install CM9 again, I can flash the zImage with Heimdall no problem, but when I choose install the CM9 zip from the internal sdcard, I always get the same getprop assert above. I made this loop a few times now (trying to install CM9, restock), but it's always the same.

Weird that never happen to me.
Just to be crazy, can you try flash AOKP build 40 instead?
If it works, then flash cm9.
Someone got that working before.
Sent from my GT-P1000 using xda app-developers app

priyana said:
Weird that never happen to me.
Just to be crazy, can you try flash AOKP build 40 instead?
If it works, then flash cm9.
Someone got that working before.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
restock -> overcome 4.1 -> CM9
This worked for me, thanks!

You mean restock - overcome kernel - overcome 4.1 - cm9 ?
Sent from my GT-P1000 using xda app-developers app

Qqqxxxzzz said:
sigitm said:
Will I lose all data on the /emmc partition (including all my TitaniumBackup files) if I restock?
Click to expand...
Click to collapse
Only if you install overcome rom (via CWM).
Click to expand...
Click to collapse
I restocked but sadly I lost all data on the internal sdcard. :crying:
Then I copied latest CM9 nightly rom to the internal sdcard, installed the Overcome Kernel via Odin, booted into Overcome Clockwork Mod, and successfully installed CM9.

priyana said:
You mean restock - overcome kernel - overcome 4.1 - cm9 ?
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
1. restock as described the overcome guide
2. oneclick rooting
3. overcome 4.1 with odin
4. cm9 with cwm

setalosas said:
1. restock as described the overcome guide
2. oneclick rooting
3. overcome 4.1 with odin
4. cm9 with cwm
Click to expand...
Click to collapse
Sent from my GT-P1000 using xda app-developers app
Sorry, by now I know overcome guide by heart and probably can write it out with my eyes closed.
but...
3. overcome 4.1 with odin
What is that?
I thought you flash overcome 4.0 kernel tar using Odin,
Not overcome 4.1 rom
Overcome rom is flashed using CWM only.
So, You mean restock - overcome kernel - overcome 4.1 - cm9
Rooting is redundant.

priyana said:
3. overcome 4.1 with odin
What is that?
I thought you flash overcome 4.0 kernel tar using Odin,
Not overcome 4.1 rom
Overcome rom is flashed using CWM only.
So, You mean restock - overcome kernel - overcome 4.1 - cm9
Rooting is redundant.
Click to expand...
Click to collapse
No, I didn't flash the overcome 4.0 kernel.
I used odin with the Overcome_7_Series_v4.1.0_Wipe.zip file unzipped, and put the proper files into the pit/pda/phone fields of odin. That's all.

bummer
flashed GT-P1000 with CM9.1 stable version too. Suddenly the device keeps auto shutdown with unknown problems, app crashes such as Google Play (which I itched to remove and updated to the somenumber version) and changed Apollo app back and forth and back again of 1.0 version from the separate developed apk with the original cm9 Apollo. and then after many times flashing and tried to restore the CM9.1 Stable, the device wont let me use CM9 again. On boot scanning sd card, it shuts down weirdly. maybe there's some problem for my device with CM9. sigh.

Getting ICS on the Bell Mobility GT-P1000M

Hi everyone,
I really don't like posting redundant information, but I just had to post something to help my Canadian colleagues...
I have a Samsung GT-P1000M (Bell Mobility Canada version) that I updated to Gingerbread via Kies but then wanted to get to ICS (CM9). I'll be honest I can typically easily filter through web garbage when it comes to knowing what to do but the entire world is so active on Android that I had mass confusion. There's a lot of bad information out there... In my initial attempts I had no issues rooting using SuperOneClick: http://www.androidauthority.com/galaxy-tab-p1000-root-superoneclick-72083/
Then, I installed CWM so that I could try installing the flash CM9 zip file. It would not install due to the assert statement (Status 7), where it was trying to match to a GT-P1000, but mine is an M. So I edited the script inside the zip file and tried again but it ended up going into a continuous loop on Status 7. I tried flashing again but had the same issues.
Anyway, long story short, this is what I would suggest with the M version to get CM9 (ICS). Essentially put on this overcome image so that the GT-P1000M version thinks it's a regular GT-P1000 tablet. There's no real point in rooting as you'll blow everything away anyway. Make sure to back up your stuff:
1) Do what priyana suggests in this post and restock your tablet. This involves starting on Page 6 of this guide. Finding all the files is a bit annoying, but doable. Just try to get them from reasonably trusted sources.
2) Stop following the guide at the end of page 11 to proceed to install CM9. Reboot the tablet into the CWM Recovery by holding the volume up key and power button during boot. Install the CM9 zip file as priyana suggests. Then flash the google apps obtained from goo.im (the whole thing is as easy as installing 2 zip files)
Anyway, I think it was necessary to blow away everything so that the tablet stopped believing it was actually a P1000M. Now ICS is on there and runs beautifully. I know the post is a bit redundant but it is to clear up the P1000M difference. As soon as this thing booted the web worked perfectly, never had to put any network settings in or anything.
Also this gives phone functionality, I just don't know how it will get billed considering I'm on a Tablet Only plan... I guess we'll find out in a few days when my bill comes out. It'll probably be at 25 cents/minute or something. Anyway, thanks everyone!

The overcome files are all well hosted by sos_sifou
http://forum.xda-developers.com/showthread.php?t=1881981
Anything broken, just let him know.
Sent from my GT-P1000 using xda app-developers app

Another Canadian GT-P1000M Result
Just wanted to share my experience trying to put CyanogenMod on a Bell Canada Galaxy Tab (GT-P1000M) for anyone coming across this thread. I had one of these fall into my lap, and being a nexus 5 owner, the Froyo that came stock just wasn't going to cut it.
Step1: Update the 2.3.3
First thing I did was update to 2.3.3 using Samsung Kies software on a Windows machine. Every Root+CWM path I seemed to find was aimed at 2.3 not 2.2. That was painful enough. The only real trick have to make sure to set the device up properly Settings->Wireless and Networl->USB Settings->Kies Mode (or something to that effect, I can't see this menu anymore),
Step2: Root and Custom Recovery
From there I pretty much followed the instructions at wiki.cyanogenmod.org/w/Install_CM_for_p1 for a generic P1000 (skipping the "flash gingerbread" step because I did that with Kies). The CM instructions link you to theunlockr.com/2012/05/07/how-to-root-and-flash-the-clockworkmod-recovery-on-the-galaxy-tab-p1000-running-gingerbread/ for the root and recovery installation step. This was pretty straight forward. All you need is the Odin exe, and the root and recovery tar file.
Now it's rooted and unlocked. You can reboot and make sure the superuser and CWM apps are there to be sure.
Step3: CM9.1
Continuing with the instructions at wiki.cyanogenmod.org/w/Install_CM_for_p1. I put the cm9.1.zip and the gapps zip on the table simply by plugging into my computer. Unplug and reboot into recovery with Volume Up + Power. Wipe. Try to flash the cm9.1 zip and I get this error.
assert failed: getprop("ro.product.device") == "galaxytabb" || getprop("ro.buildp.product") =="galaxytab" ||getprop("ro.product.device") == "GT-P1000" || getpropr("ro.build.product") == "GT-p1000"
E:Error in /sdcard/cm-9.0.0-RC1-p1.zip
(Status 7)
Installation aborted.
Like lucgallant mentions, it seems to be something about this tablet being a GT-P1000M as opposed to just GT-P1000.
Here was my fix:
1. Extract the cm9.1.zip
2. Navigate to \cm-9.1***\META-INF\com\google\android and open the "updater-script" in a text editor.
3. change the part with this:
assert(getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000" || getprop("ro.build.product") == "GT-P1000");
to this:
assert(getprop("ro.product.device") == "galaxytab" || getprop("ro.build.product") == "galaxytab" ||
getprop("ro.product.device") == "GT-P1000M" || getprop("ro.build.product") == "GT-P1000M");
4. Re-zip the folder
Here I ran into snag #1. The zip I created put an extra folder level in (e.g. cm9.1.zip / cm9.1 / META-INF instead of just cm9.1.zip / META-INF). This wouldn't let me flash the zip. Fixed this and managed to start the flash, when I ran into snag #2. Got stuck in a boot loop (one with the CM logo).
Managed to get back the the bootloader, and for the hell of it thought I'd flash the original zip that would fail on the assert message. Sure enough, that worked. So whatever I did to get stuck in the boot loop do something similar to what lucgallant said about convincing your tablet it's a GT-P1000 and not a GT-P1000M (os something). But I didn't have to do any of the overcome image stuff.
So recap:
Files needed
- Odin3 v1.7
- CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar
- cm9.1.zip
- cm9.1_modified.zip (that you modified the updater_script in and make a new zip)
- gapps zip
Step1
- update to 2.3.3 in kies
Step2
- reboot into "download mode" (volume down and power)
- use the odin.exe thing to flash the CF.tar
- reboot into regular mode and make sure superuser and a cwm app are there
- put the gapps.zip, cm9.1.zip and cm9.1modified.zip
Step3
- reboot in recovery (volume up + power)
- wipe and factory reset
- flash the cm9.1.zip and fail on assert (never know, you might get lucky)
- flash the cm9.1.zip and get farther but get stuck in a bootloop
- frantic volume up and power and different times to try to get back into recovery mode
- flash the cm9.1.zip original which will now magically work
- flash the gapps.zip
- reboot
Voila. Worked for me at least.

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