I've been trying to upgrade my LeEco S3 to version 5.8.019S. Each time I do it, it gets almost half way through the upgrade process and then says "Failed to update! Cause: Installation failed.". See here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried resetting to factory defaults and clearing data... Nothing works.
Any help is greatly appreciated!
Re-enable any apps you disabled?
abel408 said:
I've been trying to upgrade my LeEco S3 to version 5.8.019S. Each time I do it, it gets almost half way through the upgrade process and then says "Failed to update! Cause: Installation failed.". See here:
I've tried resetting to factory defaults and clearing data... Nothing works.
Any help is greatly appreciated!
Click to expand...
Click to collapse
was your phone rooted?
unroot your phone.
disabled OEM unlock in Developer settings
smokin901 said:
was your phone rooted?
unroot your phone.
disabled OEM unlock in Developer settings
Click to expand...
Click to collapse
It was rooted, but now it's fully stock. OEM unlock is disabled and all apps are back on the system.
If system partition has been modified (rooted or even accessed in read/write mode by TWRP) then updates will not work.
wpbear said:
If system partition has been modified (rooted or even accessed in read/write mode by TWRP) then updates will not work.
Click to expand...
Click to collapse
So the very act of doing fastboot boot twrp.img and subsequent "Keep Read Only" in TWRP modifies the system partition? How so?
I've got some stock TWRP images of 18S and 19S (generated using a temporary boot into TWRP - rather than flashing recovery - and keeping system read-only). I suppose, though, that since restoring them to the system partition would require modifying it in the first place, that breaks OTAs?
I've also got the 19S OTA zip. Not sure what would need to be modified to flash it, though.
rczrider said:
So the very act of doing fastboot boot twrp.img and subsequent "Keep Read Only" in TWRP modifies the system partition? How so?
I've got some stock TWRP images of 18S and 19S (generated using a temporary boot into TWRP - rather than flashing recovery - and keeping system read-only). I suppose, though, that since restoring them to the system partition would require modifying it in the first place, that breaks OTAs?
I've also got the 19S OTA zip. Not sure what would need to be modified to flash it, though.
Click to expand...
Click to collapse
You need to modify part which verifies the installation.
Post installation script from ota
Sent from my Le X526 using Tapatalk
smokin901 said:
You need to modify part which verifies the installation.
Post installation script from ota
Click to expand...
Click to collapse
META-INF/com/google/android/updater-script ?
Code:
get_device_compatible("le_s2_na") == "OK" || abort("This package is for \"le_s2_na\" devices; this is a \"" + getprop("ro.product.device") + "\".");
ui_print("Start to check root...");
ifelse(root_check() == "root", abort("The phone has root!
"), ui_print("The phone is OK, start to OTA update.
"));
ui_print("Source: LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801810091S/39:user/release-keys");
ui_print("Target: LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801910272S/61:user/release-keys");
ui_print("Verifying current system...");
getprop("ro.build.fingerprint") == "LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801810091S/39:user/release-keys" ||
getprop("ro.build.fingerprint") == "LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801910272S/61:user/release-keys" ||
abort("Package expects build fingerprint of LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801810091S/39:user/release-keys or LeEco/Le2_NA/le_s2_na:6.0.1/IFXNAOP5801910272S/61:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/boot:11091240:76343e8329de11d0279fc48e2e1cc2ea3a70e391:11091240:22302e5527893ac327ff04fa478d19532c1d1c05") || abort("\"EMMC:/dev/block/bootdevice/by-name/boot:11091240:76343e8329de11d0279fc48e2e1cc2ea3a70e391:11091240:22302e5527893ac327ff04fa478d19532c1d1c05\" has unexpected contents.");
# ---- radio update verification ----
ui_print("Verifying radio-update...");
apply_patch_check("EMMC:/dev/block/bootdevice/by-name/modem:79092224:580467b7ef83c3f71ad6991e3624b77a1379c8fa:79092224:55c73357a7923ba6ce7099c2c3a4bccdba049ed6") || abort("\"EMMC:/dev/block/bootdevice/by-name/modem:79092224:580467b7ef83c3f71ad6991e3624b77a1379c8fa:79092224:55c73357a7923ba6ce7099c2c3a4bccdba049ed6\" has unexpected contents.");
apply_patch_space(79092224) || abort("Not enough free space on /system to apply patches.");
if (range_sha1("/dev/block/bootdevice/by-name/system", "134,1,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,878904,884736,884738,884993,884995,885503,917503,917504,917506,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "165a725a008e94b0fde64d19bd4ead3d310134d1" || block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")) then
ui_print("Verified system image...");
else
abort("system partition has unexpected contents");
endif;
# ---- start making changes here ----
ui_print("Patching system image after verification.");
show_progress(0.900000, 0);
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
ui_print("Verifying the updated system image...");
if range_sha1("/dev/block/bootdevice/by-name/system", "136,0,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,882859,884736,884738,884993,884995,885503,917503,917504,917506,918014,923428,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "127f8d73efdc54efcd9ed606b81300f0c4a5c6a0" then
if range_sha1("/dev/block/bootdevice/by-name/system", "142,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,882859,883371,884224,884736,884738,884993,884995,885503,917503,917504,917506,918014,923428,923940,949760,950272,950274,950786,982528,983040,983042,983554,1015296,1015808,1015810,1016318,1040310,1040311") == "9192c3ab8d6affd1d695787c2ec307d8f235a74c" then
ui_print("Verified the updated system image.");
else
abort("system partition has unexpected non-zero contents after OTA update");
endif;
else
abort("system partition has unexpected contents after OTA update");
endif;
ui_print("Patching boot image...");
show_progress(0.100000, 10);
apply_patch("EMMC:/dev/block/bootdevice/by-name/boot:11091240:76343e8329de11d0279fc48e2e1cc2ea3a70e391:11091240:22302e5527893ac327ff04fa478d19532c1d1c05",
"-", 22302e5527893ac327ff04fa478d19532c1d1c05, 11091240,
76343e8329de11d0279fc48e2e1cc2ea3a70e391, package_extract_file("patch/boot.img.p"));
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("patch/firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("patch/firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("patch/firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("patch/firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlib");
package_extract_file("patch/firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymaster");
package_extract_file("patch/firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
package_extract_file("patch/firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("patch/firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("patch/firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("patch/firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("patch/firmware-update/cmnlib.mbn", "/dev/block/bootdevice/by-name/cmnlibbak");
package_extract_file("patch/firmware-update/keymaster.mbn", "/dev/block/bootdevice/by-name/keymasterbak");
package_extract_file("patch/firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
package_extract_file("patch/firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1bak");
), "");
msm.boot_update("finalize");
package_extract_file("patch/firmware-update/devinfo.bin", "/dev/block/bootdevice/by-name/devinfo");
package_extract_file("patch/firmware-update/adspso.bin", "/dev/block/bootdevice/by-name/dsp");
apply_patch("EMMC:/dev/block/bootdevice/by-name/modem:79092224:580467b7ef83c3f71ad6991e3624b77a1379c8fa:79092224:55c73357a7923ba6ce7099c2c3a4bccdba049ed6",
"-", 55c73357a7923ba6ce7099c2c3a4bccdba049ed6, 79092224,
580467b7ef83c3f71ad6991e3624b77a1379c8fa, package_extract_file("patch/firmware-update/NON-HLOS.bin.p"));
package_extract_file("patch/firmware-update/misc.img", "/dev/block/bootdevice/by-name/misc");
package_extract_file("patch/firmware-update/splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("patch/firmware-update/oemconfig.img", "/dev/block/bootdevice/by-name/OEMCONFIG");
package_extract_file("patch/firmware-update/ddr.bin", "/dev/block/bootdevice/by-name/DDR");
set_progress(1.000000);
rczrider said:
META-INF/com/google/android/updater-script ?
Click to expand...
Click to collapse
check what is the output of
fastboot oem device-info
from the script this is the part you should remove
Code:
if range_sha1("/dev/block/bootdevice/by-name/system", "136,0,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,882859,884736,884738,884993,884995,885503,917503,917504,917506,918014,923428,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "127f8d73efdc54efcd9ed606b81300f0c4a5c6a0" then
if range_sha1("/dev/block/bootdevice/by-name/system", "136,0,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,882859,884736,884738,884993,884995,885503,917503,917504,917506,918014,923428,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "127f8d73efdc54efcd9ed606b81300f0c4a5c6a0" thenif (range_sha1("/dev/block/bootdevice/by-name/system", "134,1,32770,33025,33027,33535,65535,65536,65538,66046,98303,98304,98306,98561,98563,99071,131071,131072,131074,131582,163839,163840,163842,164097,164099,164607,196607,196608,196610,197118,229375,229376,229378,229633,229635,230143,262143,262144,262146,262654,294911,294912,294914,295169,295171,295679,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,491519,491520,491522,492030,524287,524288,524290,524798,557055,557056,557058,557566,589823,589824,589826,590334,622591,622592,622594,623102,655359,655360,655362,655870,688127,688128,688130,688638,720895,720896,720898,721406,753663,753664,753666,754174,786431,786432,786434,786942,819199,819200,819202,819457,819459,819967,851967,851968,851970,852478,878904,884736,884738,884993,884995,885503,917503,917504,917506,950272,950274,983040,983042,1015808,1015810,1016318,1040310,1040311,1048512") == "165a725a008e94b0fde64d19bd4ead3d310134d1" || block_image_verify("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat")) then
ui_print("Verified system image...");
else
abort("system partition has unexpected contents");
endif;
else abort("system partition has unexpected contents after OTA update");
endif;
do this if and only if you have not modified any of the apps that comes with stock rom..
is there a stock rom zip available for S3. like it is available for S2(Indian Version).
smokin901 said:
check what is the output of
fastboot oem device-info
Click to expand...
Click to collapse
Code:
(bootloader) Device product name: []
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.031s]
If I run fastboot oem unlock-go, it changes to:
Code:
(bootloader) Device unlocked: true
But of course that doesn't stick after a reboot.
smokin901 said:
from the script this is the part you should remove
do this if and only if you have not modified any of the apps that comes with stock rom..
Click to expand...
Click to collapse
Thanks! I've already updated my S3, but I should have another one here early next week that I can test it out on. If anyone else on 18S wants to give it a shot, it can be downloaded here: https://mega.nz/#F!SE9hlbxa!Q2ZTtBaW16Qccb77BT1Pxw
Just rename "IFXNAOP5801910272S-edited.zip" to "update.zip", place in the root of your internal storage, go to Settings > System update > settings (3 dots at top right) > Local update
smokin901 said:
is there a stock rom zip available for S3. like it is available for S2(Indian Version).
Click to expand...
Click to collapse
Not that I'm aware of. Unfortunately.
Im in the same boat. trying to get my previously TWRP/rooted now on stock recovery and rom - S3 to update but is giving me the failure notice.
I dont quite understand the above, can you dummy it down for me?
Thanks
Rico
iamrico00 said:
Im in the same boat. trying to get my previously TWRP/rooted now on stock recovery and rom - S3 to update but is giving me the failure notice.
I dont quite understand the above, can you dummy it down for me?
Thanks
Rico
Click to expand...
Click to collapse
which part do you need help with?
I downloaded the file and placed it in the root directory on the phone. Went to update and clicked the 3 dots to do a manual update. It went to the update screen and it still says failed.
Do you have a recovery? I flashed one for the s3 I found on some website. Can you upload that? I doubt it's the issue but it may be.
Thanks Rico
I know why OTAs are not working, if you try and flash the OTA update zip with TWRP it will say that the update is for the S2_na and that the device is the S2.
in other words, the unrooting and stocking process stated here for our S3 converts our phones in S2s, which means, OTAs will never install.
Solution here is, wait for a Stock S3 Rom.
Ok. So how do I return to stock so I can get OTA update?
Rico
CpaoV said:
I know why OTAs are not working, if you try and flash the OTA update zip with TWRP it will say that the update is for the S2_na and that the device is the S2.
in other words, the unrooting and stocking process stated here for our S3 converts our phones in S2s, which means, OTAs will never install.
Solution here is, wait for a Stock S3 Rom.
Click to expand...
Click to collapse
Your probably using the wrong version of TWRP...Only the Chinese version works right, not the new official one for S2,and anyways unless you take out a part of update script,and I have not figured it all out as yet no update will work on S3 if you have used twrp in any way on the phone it seems
britdude said:
Your probably using the wrong version of TWRP...Only the Chinese version works right, not the new official one for S2,and anyways unless you take out a part of update script,and I have not figured it all out as yet no update will work on S3 if you have used twrp in any way on the phone it seems
Click to expand...
Click to collapse
I tried with both versions of TWRP, I tried with stock recovery as well, I cleaned all my phone and flashed everything back manually, and yet, it still gives error when trying to update either via OTA or via Zip.
So, it's either a bad update file or my phone was permanently banned from OTAs until a full clean stock ROM is available.
Currently, I gave up, this 19S is pretty good actuallt, today I just got 6.5 hrs SOT (Lots of multitasking between Chats and Media, PoGo, Shooter games, youtube, downloading stuff) and it's fluent enough, now I kinda don't wanna ruin that.
---------- Post added at 07:00 PM ---------- Previous post was at 06:57 PM ----------
---------- Post added at 07:00 PM ---------- Previous post was at 07:00 PM ----------
Not a bad update, like I have said, once we use twrp ,OTA's will fail..
I am looking into what can be changed in OTA file to get it to install
Just restating what many of you have already said. I never had TWRP installed, but did use the "fastboot boot twrp.img" command to install SU and root my phone. I never touched the stock recovery, and the OTA failed even after a factory reset.
Of course this update isn't really a huge one, but I would like to have compared the camera changes and possibly use the stock apps, such as remote, if they fixed the permissions (constantly asking for location and access to contacts seemed fishy to me).
This does however pose a bigger problem when and if a new 7.0 Nougat update is released and those of us who can't OTA are stuck on 19s indefinitely.
I wonder if those with the Pro3 are having the same issue. At least the Pro3 has the option of installing available custom roms.
You Relocked Bootloader ?
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.
Hi all,
I recently flashed an android for the first time, so go easy on me!
I flashed my galaxy note gt-n7000 with the CM10 preview #3 (dated 20th August 2012) with success... but!
When I try to install preview #4 of CM10 (24-08-1012), I always get an error message coming from the updater-script.
It says:
assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" ||
getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" ||
getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" ||
getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
I already figured out that my note's name/product/device has been changed to I9100 (S2 build), so I simply opened /system/build.prop and changed it back to GT-N7000. (settings -> about phone -> model is showing GT-N7000 as it should now). Although, I didn't change ro.build.product because the build.prop said it isn't used anymore :s
Still, while running the zip from cwm (6.0.x.x) I still get the same message and it aborts with status 7.
One thing to take notice: I can't install from SD card, it says it's unable to mount the /sdcard when I try to update from external sd card in cwm. I'm trying to install from internal sd...
I already tried installing another rom without success.
I'm in the dark here, so please light up the way :crying: :fingers-crossed:
selman555 said:
Hi all,
I recently flashed an android for the first time, so go easy on me!
I flashed my galaxy note gt-n7000 with the CM10 preview #3 (dated 20th August 2012) with success... but!
When I try to install preview #4 of CM10 (24-08-1012), I always get an error message coming from the updater-script.
It says:
assert failed: getprop("ro.product.device") == "galaxynote" || getprop("ro.build.product") == "galaxynote" ||
getprop("ro.product.device") == "n7000" || getprop("ro.build.product") == "n7000" ||
getprop("ro.product.device") == "N7000" || getprop("ro.build.product") == "N7000" ||
getprop("ro.product.device") == "GT-N7000" || getprop("ro.build.product") == "GT-N7000"
I already figured out that my note's name/product/device has been changed to I9100 (S2 build), so I simply opened /system/build.prop and changed it back to GT-N7000. (settings -> about phone -> model is showing GT-N7000 as it should now). Although, I didn't change ro.build.product because the build.prop said it isn't used anymore :s
Still, while running the zip from cwm (6.0.x.x) I still get the same message and it aborts with status 7.
One thing to take notice: I can't install from SD card, it says it's unable to mount the /sdcard when I try to update from external sd card in cwm. I'm trying to install from internal sd...
I already tried installing another rom without success.
I'm in the dark here, so please light up the way :crying: :fingers-crossed:
Click to expand...
Click to collapse
Just flash a cm10 safe kernel first before flashing rom, reboot the recovery and then flash away.
Sent From My GT-N7000 Using XDA Premium.
You missed something
sahilarora2003 said:
Just flash a cm10 safe kernel first before flashing rom, reboot the recovery and then flash away.
Sent From My GT-N7000 Using XDA Premium.
Click to expand...
Click to collapse
Sorry, but I think you missed the fact that I am already on the unofficial cm10 preview 3 rom. Meaning I already have a cm10 safe kernel?
Perhaps I am missing something too?
buildprop flash,
Or format in mounts system then reflash a rom. Thats where it is saved. I think you are on a save kernel so I think it should not be an issue.
Edit: Just to be sure you can flash a safe kernel, reboot in recovery and then do above. All at your own risk
Sent from my GT-N7000 using Tapatalk 2
Are you sure?
baz77 said:
buildprop flash,
Or format in mounts system then reflash a rom. Thats where it is saved. I think you are on a save kernel so I think it should not be an issue.
Edit: Just to be sure you can flash a safe kernel, reboot in recovery and then do above. All at your own risk
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
You're suggesting formatting /system and then reflashing another rom (without rebooting in between)?
Could that be the solution? The build.prop file can be found there, how will the updater-script be able to find the parameters it needs if the /system folder was formatted?
Sorry if it's an obvious question (which I think it is), but I'm not yet an android savvy. I've had some experience with linux tho...
Any help is appreciated!
well funny thing is, it will work, try it
Sent from my GT-N7000 using Tapatalk 2
No good!
baz77 said:
well funny thing is, it will work, try it
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I'm not panicking, but still, I formated /system and tried flashing cm10 preview #4, but it still gives me the aser failed error.
My build.prop is GONE and still it says it can't assert... what gives?
ok then I am suspecting recovery and kernel, Can you flash a different safe kernel, and then reflash the rom?
edit, appears my case, when I had it, it must have been different. I did change kernel in similar case and it worked
Sent from my GT-N7000 using Tapatalk 2
Trying parandroid now
baz77 said:
ok then I am suspecting recovery and kernel, Can you flash a different safe kernel, and then reflash the rom?
edit, appears my case, when I had it, it must have been different. I did change kernel in similar case and it worked
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I installed cwm 5.8 now, It seems I can't mount /emmc but i'm gonna give it a go...
Got the solution.
Downgrade to GB, root the device and upgrade to cm10 in recovery.
It will work.
Another problem...
sahilarora2003 said:
Got the solution.
Downgrade to GB, root the device and upgrade to cm10 in recovery.
It will work.
Click to expand...
Click to collapse
I tried to install speedmod K3-13, which landed me on cwm 5.8.1.8. I can't get back to 6.0.x because this version screws up the mount /emmc and /sdcard! When I choose install from /sdcard, the content that is displayed is actually my internal storage.
I can't put anything on my internal storage, because my rom doesn't work anymore and I can't connect to my pc...
I've seen the posts about downgrading to GB, but I can't because of the sdcard & emmc screwup..
Some tips & tricks would be helpful. :fingers-crossed:
good one, remember to reboot recovery after flashing kernel.
last resort try flashing a gb rom from pc odin with or without regular pitfile. Flashing takes some time so be patient. If it get stuck about an hour at factorysys you might have case of superbrick, but I am not expecting that.
Sent from my GT-N7000 using Tapatalk 2
I'll try
baz77 said:
good one, remember to reboot recovery after flashing kernel.
last resort try flashing a gb rom from pc odin with or without regular pitfile. Flashing takes some time so be patient. If it get stuck about an hour at factorysys you might have case of superbrick, but I am not expecting that.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Way to put my mind at ease
Do you have a link to where I can find the correct gb for odin?
selman555 said:
I tried to install speedmod K3-13, which landed me on cwm 5.8.1.8. I can't get back to 6.0.x because this version screws up the mount /emmc and /sdcard! When I choose install from /sdcard, the content that is displayed is actually my internal storage.
I can't put anything on my internal storage, because my rom doesn't work anymore and I can't connect to my pc...
I've seen the posts about downgrading to GB, but I can't because of the sdcard & emmc screwup..
Some tips & tricks would be helpful. :fingers-crossed:
Click to expand...
Click to collapse
Download prerooted GB rom from my sig.
Reboot in Download mode.
Open PC Odin on your PC
Connect your phone to pc via usb cable
Select GB file under PDA tab
Hit Start
Wait for the completion.
Thanks!
sahilarora2003 said:
Download prerooted GB rom from my sig.
Reboot in Download mode.
Open PC Odin on your PC
Connect your phone to pc via usb cable
Select GB file under PDA tab
Hit Start
Wait for the completion.
Click to expand...
Click to collapse
Alright, very good!
So afterwards, I can just reflash through cwm to cm10?
That would be awesome!
selman555 said:
Alright, very good!
So afterwards, I can just reflash through cwm to cm10?
That would be awesome!
Click to expand...
Click to collapse
Yes you can. Just reboot into recovery and flash rom+gapps, do all 3 wipes(Cache/Dalvik/Data) and reboot woaah you are on cm10 now Cheers
Fingers crossed for now...
sahilarora2003 said:
Yes you can. Just reboot into recovery and flash rom+gapps, do all 3 wipes(Cache/Dalvik/Data) and reboot woaah you are on cm10 now Cheers
Click to expand...
Click to collapse
I was on CM10 preview 3, but I just had to go to 4!!!
Especially the fact that the g-sensor didn't work bothered me!
The GB download is very slow though, i'm downloading at 80~800kb/s. It's taking for ages.
Perhaps you should find another mirror for you sig...
I'll let you know how it went
Going great!
sahilarora2003 said:
Yes you can. Just reboot into recovery and flash rom+gapps, do all 3 wipes(Cache/Dalvik/Data) and reboot woaah you are on cm10 now Cheers
Click to expand...
Click to collapse
I've gotten past the factorysys.img and it's now writing nand...
Would it be safe to go to paranoid android from here?
Should be, but follow the procedure from paranoid android thread to the letter. Its in first post of the thread, or in the thread.
selman555 said:
I've gotten past the factorysys.img and it's now writing nand...
Would it be safe to go to paranoid android from here?
Click to expand...
Click to collapse
Yes. Just reboot into recovery and flash rom+gapps and do all three wipes. Time to reboot now.
Sent From My GT-N7000 Using XDA Premium.
I have been searching threads left and right for about 40 hours in total looking for answers. I have tried everything. The problem is: I am stuck in twrp with no os, no previously saved roms, and no way to load files onto my kindle.
If I could either of these two to work, I would be in business.
A) When i try to use 'adb sideload' it gives me an error. If I could sideload the file I'd be okay.
B) When i plug my kindle into my pc, I can find it in device manager, but even when i mount it it wont show up as a storage device
Extra info: a factory fastboot cable will be at my disposal shortly. i am temperately tech-savy
EDIT
My new problem, whenever i try to flash any rom i get the following error:
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
PLEASE HELP
I found out that old adb versions dont support adb sideload. Also look at Stunts thread. http://forum.xda-developers.com/showthread.php?t=2459498
Also found this
Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done."
ughhh
south956 said:
I found out that old adb versions dont support adb sideload. Also look at Stunts thread. http://forum.xda-developers.com/showthread.php?t=2459498
Also found this
Wiped /sdcard, can't reboot from recovery: You thought you had the ROM file on the sdcard, but you didn't, and wiped everything, so without a ROM image, you can't boot into system.
Solution: Put the ROM file where your ADB binary is (usually inside platform-tools folder in Android SDK directory) and rename it rom.zip. On the device, boot into TWRP, select Advanced, then ADB Sideload. Connect device to PC. From here, run "adb" and hit Enter to check for your binary version, if it's anything lower than 1.0.3.0, you need to update the binaries by re-installing the latest Android SDK. Once the device is in sideloading mode and is connected to the PC, type "adb sideload rom.zip" and hit Enter. Now you'll find the ROM on the sdcard, flash, and you're done."
Click to expand...
Click to collapse
i know how to use the sideload it just doesnt work. and on the link you gave me, everything worked until i am flashing the rom, i get this error
updating partition details...
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
epdating partition details...
PLEASE HELP
18lo said:
i know how to use the sideload it just doesnt work. and on the link you gave me, everything worked until i am flashing the rom, i get this error
updating partition details...
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
epdating partition details...
PLEASE HELP
Click to expand...
Click to collapse
Use this tutorial to push a ROM onto TWRP. You be good in no time http://forum.xda-developers.com/showthread.php?t=2459498
not the point
LinearEquation said:
Use this tutorial to push a ROM onto TWRP. You be good in no time http://forum.xda-developers.com/showthread.php?t=2459498
Click to expand...
Click to collapse
thats not the point i know what to do there its just flashing the rom thats the problem. i get the error
everything worked until i am flashing the rom, i get this error
updating partition details...
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
epdating partition details...
PLEASE HELP
Ok what tablet is it exactly and what rom are you flashing? Thread?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
ok
south956 said:
Ok what tablet is it exactly and what rom are you flashing? Thread?
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
Click to expand...
Click to collapse
it is a kindle fire hd 7'' and i am flashing cm 10.1 when i did a practice flash of the gapps it worked fine.
then when i tried a kindle os i got a slightly different error. im confused, is it something wrong with the file?
What twrp version are you using
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
im not sure
south956 said:
What twrp version are you using
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
Click to expand...
Click to collapse
2.6.0.0
Try 2.6.3.1
Also if anything you might have to system restore everything, get KFFAide and twrp should allow you to boot into fastboot to restore back to 7.2.3 stock os. You will only need regular usb cable.
Also you nesd to get a higher adb version to fully use adb sideload and maybe higher twrp too.
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
okay, how should i install it
south956 said:
Try 2.6.3.1
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
Click to expand...
Click to collapse
how do i install it
You have to sideload it. [email protected]#! Have you tried updating adb too?
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
Wait do adb commands work when youre connected?
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
eh
south956 said:
You have to sideload it. [email protected]#! Have you tried updating adb too?
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
---------- Post added at 10:12 PM ---------- Previous post was at 10:10 PM ----------
Wait do adb commands work when youre connected?
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
Click to expand...
Click to collapse
adb works when it is plugged in, yeah. but when i do adb shell i get something like: #<6n]
Ok use su instead of sh, and push twrp file on sdcard..... What do you get
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------
Wait you dont need to add su or sh commands just use cmd in administrator mode to adb push
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
south956 said:
Ok use su instead of sh, and push twrp file on sdcard..... What do you get
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------
Wait you dont need to add su or sh commands just use cmd in administrator mode to adb push
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
Click to expand...
Click to collapse
it failed when i try to install. i will try tomorrow
Ok ill search up to see how i can help
For your own custom Sig : http://forum.xda-developers.com/showthread.php?t=1922304
18lo said:
2.6.0.0
Click to expand...
Click to collapse
Have you inspected the zip? Not long ago when goo.img was updating their servers, zips looked like they were downloading but it was just a mere shell.
As suggested, you will want to update TWRP. Can you show me where and which file you're using? Cm has a dynamite 4.3 JB 10.2 for the KFHD7 as well.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
---------- Post added at 01:24 AM ---------- Previous post was at 01:16 AM ----------
18lo said:
thats not the point i know what to do there its just flashing the rom thats the problem. i get the error
everything worked until i am flashing the rom, i get this error
updating partition details...
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
epdating partition details...
PLEASE HELP
Click to expand...
Click to collapse
Why not re-download the ROM and see if that helps. Try using the crackflasher mirror offered in Hascodes CM threads. http://forum.xda-developers.com/showthread.php?t=2388352 use mirror 2. Here is current TWRP thread http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
LinearEquation said:
Have you inspected the zip? Not long ago when goo.img was updating their servers, zips looked like they were downloading but it was just a mere shell.
As suggested, you will want to update TWRP. Can you show me where and which file you're using? Cm has a dynamite 4.3 JB 10.2 for the KFHD7 as well.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
---------- Post added at 01:24 AM ---------- Previous post was at 01:16 AM ----------
Why not re-download the ROM and see if that helps. Try using the crackflasher mirror offered in Hascodes CM threads. http://forum.xda-developers.com/showthread.php?t=2388352 use mirror 2. Here is current TWRP thread http://forum.xda-developers.com/showthread.php?t=2128848
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Click to expand...
Click to collapse
Will this work on a 7"?
18lo said:
it failed when i try to install. i will try tomorrow
Click to expand...
Click to collapse
Well gee, looks like it says on the tutorial that it's for an 8.9. I'm guessing no. Here, let me search for you http://forum.xda-developers.com/showthread.php?t=2388341 I suggest you read up and learn some things before you ruin your Kindle. Oh, the search engine works great to.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
LinearEquation said:
Well gee, looks like it says on the tutorial that it's for an 8.9. I'm guessing no. Here, let me search for you http://forum.xda-developers.com/showthread.php?t=2388341 I suggest you read up and learn some things before you ruin your Kindle. Oh, the search engine works great to.
Sent from my Amazon Kindle Fire HD running CM 10.2 using xda app-developers
Click to expand...
Click to collapse
when i use that file i get the same error
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.