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.
Related
Installing update...
assert failed: getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" ||
getprop("ro.product.board") == "SCH-I800"
E:Error in/sdcard/KhasMek.DJ11.Kleanmod.v3.zip
(Status 7)
Installaiton Aborted
Can,t install rom, does anybody have some simmilar?
bombarder said:
Installing update...
assert failed: getprop("ro.product.device") == "SCH-I800" || getprop("ro.build.product") == "SCH-I800" ||
getprop("ro.product.board") == "SCH-I800"
E:Error in/sdcard/KhasMek.DJ11.Kleanmod.v3.zip
(Status 7)
Installaiton Aborted
Can,t install rom, does anybody have some simmilar?
Click to expand...
Click to collapse
Yes just search in this forum. I had the same problem too. Basically here is what to do
1- download and flash the full firmware JJ4 with pit and partition cheched (this will resolve the csc errors)
Your tab might still get stuck on the boot logo. Turn it off then go to download mode
2- Flash Gingerbread 2.3.3 following Chainfire instructions
Your tab should reboot normally.
Good luck
Sent from my GT-P1000 using XDA Premium App
I, sorry for noob qestion, but I have cdma device I800, this method for gsm device isn,t it?
bombarder said:
I, sorry for noob qestion, but I have cdma device I800, this method for gsm device isn,t it?
Click to expand...
Click to collapse
Yes gsm tab
Sent from my GT-P1000 using XDA Premium App
if I flashed it could it damage my device?I read somewhere about posibility damaging
bombarder said:
I, sorry for noob qestion, but I have cdma device I800, this method for gsm device isn,t it?
Click to expand...
Click to collapse
I actually had the same issue, and have been scouring the forums for days. Unfortunately, I wasn't able to find a solution. I tried following the instructions listed for Unbricking the Galaxy Tab and it worked for about a day.
After that it began generating errors. First my widgets disappeared saying there was a problem, second reboot wifi generated errors and wouldn't turn on, and third reboot was the Verizon Logo. When it was on the VZW logo, it would vibrate once, pause, and vibrate three times. Wash. Rinse. Repeat.
So, if this is what you were dealing with, this is what I did to resolve it. (Warning: I am not a developer, and take no responsibility for what happens should you choose to repeat my steps.)
1.) I noticed it was still on CWM3, tried to reflash Khasmek's Voodoo plus v.5. -Booted into Recovery
-Wiped Data, Cache
-Flashed
Got me out of the vzw loop. Went to boot loop.
2.) Flashed rom (tried K-lean v3 and Khasmeks Aosp and Simply Aosp.
-Copy rom to SD card.
-Boot into Recovery
-Update from Zip on SD
-Flash
Fail. Still a status 7 on install of any given rom. Still displaying CWM 3.0 after kernel flash.
3.) Heimdall with original files.
-Go look it up.
Booted, but a function died on every reboot (Camera, Wifi, Widgets, etc). Noticed that system only displayed 512 RAM. May have flashed incorrect files.
-Verified. Idiot. Downloaded and Repeated with correct files.
Still had same issue with rebooting and losing a function every time.
Still displaying CWM3.0
4.) Got frustrated. Drank a little. Remembered I had a recovery from March.
-Boot into recovery
-Backup and Restore
-Restore
Bingo. Everything seems to be functioning correctly and has been for a few days. Have rebooted multiple times, no issues. Also, CWM is 2.5 again.
Hope that helps.
Hello,
I was trying to install the Paranoid Android ROM (http://forum.xda-developers.com/showthread.php?t=2203301).
I did everything as always but unfortunately I receive an error:
Code:
CWM-based Recovery v.5.5.0.4 :: CF-v.1.5
-- Installing: /sdcard/pa_i9053-3.15-23MAR2013-gokussjx.zip
Finding update package...
Opening update package...
[COLOR="DarkRed"]Installing update...
assert failed: getprop("ro.product.device") == "m3" || getprop("ro.built.product") == "m3" ||
getprop("ro.product.device") == "i9305" || getprop("ro.built.product") == "i9305" ||
getprop("ro.product.device") == "GT-I9305" || getprop("ro.built.product") == "GT-I9305"
E:Error in /sdcard/pa_i9053-3.15-23MAR2013-gokussjx.zip
(Status 7)
Installation aborted[/COLOR]
Im not a software developer for mobile phones but I guess it is trying to tell me, that the ROM which I'm trying to install isnt working on my device.
But I am absolutely sure that I got an I9305 as you can see on the attached screenshot.
Any ideas?
I have also redownloaded the ZIP and tried it multiple times but always ended up with the same error.
I really would appreciate any help!
Celaniry said:
Hello,
I was trying to install the Paranoid Android ROM (http://forum.xda-developers.com/showthread.php?t=2203301).
I did everything as always but unfortunately I receive an error:
Code:
CWM-based Recovery v.5.5.0.4 :: CF-v.1.5
-- Installing: /sdcard/pa_i9053-3.15-23MAR2013-gokussjx.zip
Finding update package...
Opening update package...
[COLOR="DarkRed"]Installing update...
assert failed: getprop("ro.product.device") == "m3" || getprop("ro.built.product") == "m3" ||
getprop("ro.product.device") == "i9305" || getprop("ro.built.product") == "i9305" ||
getprop("ro.product.device") == "GT-I9305" || getprop("ro.built.product") == "GT-I9305"
E:Error in /sdcard/pa_i9053-3.15-23MAR2013-gokussjx.zip
(Status 7)
Installation aborted[/COLOR]
Im not a software developer for mobile phones but I guess it is trying to tell me, that the ROM which I'm trying to install isnt working on my device.
But I am absolutely sure that I got an I9305 as you can see on the attached screenshot.
Any ideas?
I have also redownloaded the ZIP and tried it multiple times but always ended up with the same error.
I really would appreciate any help!
Click to expand...
Click to collapse
Try to install the latest CWM!
Sent from my GT-I9305 using xda premium
update your recovery. I suggest philz
Awesome! This ROM really rocks!
Is there any way to disable the 3 button-elements as my phone already has real buttons?
yes, Google it
Celaniry said:
Awesome! This ROM really rocks!
Is there any way to disable the 3 button-elements as my phone already has real buttons?
Click to expand...
Click to collapse
If you go into the settings where you set tablet, phablet or stock ui mode you can go deeper into those settings from there. Can't remember what they're called right now. In stock ui you can reduce the soft buttons percentage to 0.
Hope this will help you.
Sent from my GT-I9305 using xda premium
"semi bricked" i9305 using Odin Mobile App
Hi guys,
I decided to flash Paranoid Android 4.2.2 onto my SIII i9305 and was successful using the Odin Mobile App after several other failed options.
I was about 5 minutes into enjoying the new ROM and I thought wait a second have I installed the Google Apps to the phone (NB I had placed the gapps on the external SD card along with the ROM.
In a moment of utter stupidity I opened up the Odin Mobile App again and selected flash gapps. Then when the phone was rebooting it just stuck on the recovery screen and when I selected "apply update from external storage" and chose the ROM (pa_i9305-3.65-9JUL2013-gokussjx.zip). It then displayed
E: failed to verify whole-file signature
E: signature verification failed
I cannot get beyond the recovery screen at all and when I select reboot system now the "Samsung Galaxy S3 GT i9305" screen appears 3 times and then returns back to the recovery screen.
I have no idea what to do and have googled possible solutions and come up with one that looks like a possible fix: iandroidblog.com/how-to-unroot-galaxy-s3-lte-i9305/
Waiting for my girlfriend to bring home her PC from work so I can let you know how it goes but in the interim does anyone have any ideas?
Cheers!
Try to get into download mode and flash a stock image using odin.
After that, you can root and flash CWM/TWRP again and flash your favorite custom ROM.
Edit: Make sure to wipe/factory reset when going back to Stock from AOSP/AOKP as the layout is totally different and may cause boot loops in itself (from my own experience)
latest version
PA i9305 3.99 RC2
The latest version incl. Modem and working Kernel.
BACON - i9305 trouble
tried to install PA today,on my i9305, but got error, not suported deveice, pakage for BACON a00001, this is m0
Is it possible to have PA on my device?
No i install CW, but i really would like PA.
Thanks!
Link to Paranoid ROM
Can anybody pleaase help me?
I cant find a paranoid rom that lets me install it.WHen install i get error. So therfore please give me a link for rom, and for gaps for the rom.
Thanks so much in advance!!!
Torsoen
torsoen said:
Can anybody pleaase help me?
I cant find a paranoid rom that lets me install it.WHen install i get error. So therfore please give me a link for rom, and for gaps for the rom.
Thanks so much in advance!!!
Torsoen
Click to expand...
Click to collapse
what error?
NOW I know these "Phone unable to boot" things are common, but please listen, you will make my day if my phone gets fixed
The phone is locked on Telstra (The reason I tried to root it, to unlock it)
I recently used the Samsung Galaxy SIII Toolkit located at SkipSoft [dot] net (Can't post links, new to forums).
When I started it up it said that there was an auto update that supported 4.1.2 but only donators could access that and I couldn't find the update anywhere on the internet, so I proceeded into the version without 4.1.2, and (Silly me) decided to use the non-4G version of 4.1.2 root (Since the 4G section didn't support it yet) and this may have been what broke my phone, the root process included using Odin and other means of rooting and I wasn't able to make it to the end since when the phone rebooted to hopefully be rooted, it wouldn't boot up ( ;_; ) So I decided to retry the root process (Silly me, again) and it only made it worse and my phone was stuck on the "Downloading...Do not turn off the target !!", and I couldnt go anywhere else even if I took out the battery and put it back in, tried going into recovery. So, since it was in the Download mode I was ablt to use Odin to load things onto the phone so I loaded CWM-based recovery v5.5.0.4 : : CF-v1.5 and used ADB to push a compatible Cyanogen mod zip to the recovery, when I thought that I'd done it, nope, errors, errors everywhere. So at this point I'm completely stuck on what to do so I came here to where all you extremely smart and amazing people do magic with phones. I'm going to list the error that shows up when I try to install (It's a big error, I have to type it)
-- Installing: /sdcard/cm-10.1 - 20130501 - NIGHTLY - i9305.zip
Finding update package...
Opening update package...
Installing update... (Commence huge error)
assert failed: getprop("ro.product.device") == "
m3" || getprop("ro.build.product") == "m3" ||
getprop("ro.product.device") == "m3xx" || g
etprop("ro.build.product") == "m3xx" || g
etprop("ro.product.device") == "i9305" || getpro
p("ro.build.product") == "i9305" || getpr
op('ro.product.device") == "GT-I9305" || getprop
("ro.build.product") == "GT-I9305"
E:Error in /sdcard/cm-10.1 - 20130501 - NIGHTLY - i9305.zip
(Stautus 7)
Installation aborted.
Ok, so I know I probably did not have to list the whole error, but I do want to get it fixed, my great friend gave me this phone for FREE in great condition.
Thankyou in advance for people who help fix the problem :fingers-crossed:
Read this, then use it...
http://forum.xda-developers.com/showthread.php?t=1942150
This will then give you a working rooted phone to adapt as you please...
Raistlin1158 said:
Read this, then use it...
http://forum.xda-developers.com/showthread.php?t=1942150
This will then give you a working rooted phone to adapt as you please...
Click to expand...
Click to collapse
Thank you, let's hope this works
(Loving how fast the community can reply )
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.
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.