Related
Hello,
i have the Problem that i cant install the update.zip for "UMTS / 3G Modem Support (Huawei)" from recoverysystem on my Folio 100.
It Says:
-- Installing from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
Formatting MISC:...
If anyone have Ideas, plz help me...
Thanks alot...
userxy79
Do you update from the newest Toshiba upgrade. If you did it you can't install nothing, because the newest recovery. To solve this pro blem, go to:
1. FolioMod1.4 Thread
2. Look in first post and find "for somone that update.. go here
..."
3. Follow guide
or
Go to "What's up with dualbooting Android/Ubuntu" thread made by me and find same but better explain guide.
That sounds good... Big Thanks to you. i will watch this
No problem.
Hi guys
I've prepared ready-to-flash nbx03 fw.
What's the difference between stock and that one?
Features:
prerooted,
'rescue-backdoored'
init.d added
write permissions for ext-sdcard enabled,
replaced locked recovery with one from R1A!
So you will have newest R5A with still adb shell enabled in recovery!
Benefits? You will be able to use 'prerooted' firmware in future releases!
Official stock R5A disables shell in recovery - means no more functions
like flashing custom, decrypting etc!
Requirements:
no R5/R5A flashed before, because of recovery locked down.
(= will not work on downgraded from R5/R5A devices)
root
newest AiO
How-to?:
download fw and rename it as 'custom_update_signed.zip',
put custom_update_signed.zip on root of your extSD,
run AiO - choose '3' & '4' - Flash signed zip, choose automatic.
just sit, wait and enjoy
PS. wipe is not required, but recommended.
If after wipe or reboot your device will boot to old firmware (which is still on 2nd /system partition),
then you should use v2 doubleFLASH custom zip - which updates both /system0&1 partitions when flashing
This prevents from such problems!
You can flash 1st regular version of custom zip, or directly v2 with doubleFLASH
Easy as hell
Download:
NEW R5A with 3G! doubleFLASH!: (will update both /system0&1 partitions)
custom_prerooted_doubleFLASH_R5A_nbx03_016-ota-121116077.zip
NEW R5A with 3G!:
custom_prerooted_R5A_nbx03_016-ota-121116077.zip
NEW R5A WiFi only! doubleFLASH!: (will update both /system0&1 partitions)
custom_prerooted_doubleFLASH_R5A_nbx03_001-ota-121116036.zip
old R5 WiFi only custom_prerooted_nbx03_001-ota-120914044_by_condi.zip
-----------------------
mirror on Google Drive
-----------------------
br
condi
condi said:
Hi guys
I've prepared ready-to-flash US nbx03_001-ota-120914044.
What's the difference between stock and that one?
Features:
prerooted,
'rescue-backdoored'
init.d added
write permissions for ext-sdcard enabled,
replaced locked recovery with one from R1!
So you will have newest R5 with still adb shell enabled in recovery!
Benefits? You will be able to use 'prerooted' firmware in future releases!
Official stock R5 disables shell in recovery - means no more functions
like flashing custom, decrypting etc!
Requirements:
R1 firmware currently on device,
no R5 flashed before, because of recovery locked down.
(= will not work on downgraded from R5 devices)
root
AiO
How-to?:
download fw and rename it as 'custom_update_signed.zip',
put custom_update_signed.zip on root of your extSD,
run AiO - choose '3' & '4' - Flash signed zip.
just sit, wait and enjoy
Easy as hell
br
condi
----uploading...
Click to expand...
Click to collapse
Great work once again!!!!
Still no progress with already flashed R5 I take it? Damn.... Still someone had to take the fall, for someone else to RISE
YOU ARE A TREASURE TO THIS COMMUNITY
Stifilz
stifilz said:
Great work once again!!!!
Still no progress with already flashed R5 I take it? Damn.... Still someone had to take the fall, for someone else to RISE
YOU ARE A TREASURE TO THIS COMMUNITY
Stifilz
Click to expand...
Click to collapse
im pretty sure that sooner or later we will figure something out to get r5+'s recoveries back to the game
treasure? noooooo... just a simple man, and his hobby but thanks friend !
condi
condi said:
im pretty sure that sooner or later we will figure something out to get r5+'s recoveries back to the game
treasure? noooooo... just a simple man, and his hobby but thanks friend !
condi
Click to expand...
Click to collapse
You SIR are toooooooooooo modest.
So you can still pre-root install to HC I assume? I have not been able to get back since the R5 recovery installed itself
Well time will tell and we WILL get there! LOL
Is it as simple as a setting turned off somewhere or is it a full part of the recovery.img?
I have not looked in your prerooted file yet..... Can you inject your recovery (the on the fly one) as a permanent solution?
That would be TOPS.
Thanks again
Stifilz
stifilz said:
You SIR are toooooooooooo modest.
So you can still pre-root install to HC I assume? I have not been able to get back since the R5 recovery installed itself
Well time will tell and we WILL get there! LOL
Is it as simple as a setting turned off somewhere or is it a full part of the recovery.img?
I have not looked in your prerooted file yet..... Can you inject your recovery (the on the fly one) as a permanent solution?
That would be TOPS.
Thanks again
Stifilz
Click to expand...
Click to collapse
have you tried oldest 3.2 fw? (not 3.2.1) someone here have written that he downgraded (dont know if thats true).
adb probably is being disabled through kernel, init.rc or somewhere there.
about injecting - for now - unfortunatelly no.
br
condi said:
have you tried oldest 3.2 fw? (not 3.2.1) someone here have written that he downgraded (dont know if thats true).
adb probably is being disabled through kernel, init.rc or somewhere there.
about injecting - for now - unfortunatelly no.
br
Click to expand...
Click to collapse
Will change to US and try.... but doubt it.... oldest I have for NZ is 0035 (3.2.1)... Does Sony Tab S have installer file (like Tab P) i have searched high and low for one. LOL
Stifilz
stifilz said:
Will change to US and try.... but doubt it.... oldest I have for NZ is 0035 (3.2.1)... Does Sony Tab S have installer file (like Tab P) i have searched high and low for one. LOL
Stifilz
Click to expand...
Click to collapse
check P's partition table and... you can always try P installer fw
to flash it you will have only to change region via AiO to P, and ro.product.device and ro.build.product to nbx02!
btw you know whats the difference on -ota- and -installer- fw?
does it overwrites hidden.img no matter lower/higher present version???
maybe that "hidden_full.img" will overwrite r5's hidden! ??
br
condi said:
check P's partition table and... you can always try P installer fw
to flash it you will have only to change region via AiO to P, and ro.product.device and ro.build.product to nbx02!
btw you know whats the difference on -ota- and -installer- fw?
does it overwrites hidden.img no matter lower/higher present version???
maybe that "hidden_full.img" will overwrite r5's hidden! ??
br
Click to expand...
Click to collapse
Hmmm. Change to Tablet P region successfully. (nearly shat myself, seemed like forever to boot LOL)
Changed to nbx02 in build.prop where it was nbx03.
Also mounted the other system partition and changed the build.prop there too.
Still got this error.
Code:
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx02_001-installer-01202.009.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 11110404 -> 110705000
Checking detailed SKU[27550200] is passed
Installing update...
installing nbx updater extensions
script aborted: assert failed: getprop("ro.product.device") == "nbx02" ||
getprop("ro.build.product") == "nbx02"
assert failed: getprop("ro.product.device") == "nbx02" || getprop("ro.buil
d.product") == "nbx02"
E:Error in /tmp/desklunvr/desklunvr.zip
(Status 7)
Installation aborted.
Have a feeling and hoping this will work....... Do I have to change buildinfo.sh? "# autogenerated by buildinfo.sh"
Do we have access to this?
When tabs are returned to Sony they come back as 3.2!!
Stifilz
stifilz said:
Hmmm. Change to Tablet P region successfully. (nearly shat myself, seemed like forever to boot LOL)
Changed to nbx02 in build.prop where it was nbx03.
Also mounted the other system partition and changed the build.prop there too.
Still got this error.
Code:
-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx02_001-installer-01202.009.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 11110404 -> 110705000
Checking detailed SKU[27550200] is passed
Installing update...
installing nbx updater extensions
script aborted: assert failed: getprop("ro.product.device") == "nbx02" ||
getprop("ro.build.product") == "nbx02"
assert failed: getprop("ro.product.device") == "nbx02" || getprop("ro.buil
d.product") == "nbx02"
E:Error in /tmp/desklunvr/desklunvr.zip
(Status 7)
Installation aborted.
Have a feeling and hoping this will work....... Do I have to change buildinfo.sh? "# autogenerated by buildinfo.sh"
Do we have access to this?
When tabs are returned to Sony they come back as 3.2!!
Stifilz
Click to expand...
Click to collapse
check /datapp/vendor/vendor0&1/vendor.prop for nbx values
So if we have R5 then we shouldn't even bother with this?
condi said:
check /datapp/vendor/vendor0&1/vendor.prop for nbx values
Click to expand...
Click to collapse
Quick question - do you need to be on 3.2 before you can flash this? I got a different assert.
Copy system image...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Sony/nbx03_003/nbx-3"3.2/THMAS11001/11001.003:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Sony/nbx03_003/nbx03:3.2.1/THMASU0035/0035.003:user/release-keys"
Click to expand...
Click to collapse
[email protected] said:
So if we have R5 then we shouldn't even bother with this?
Click to expand...
Click to collapse
Correct because we have already lost adb shell in recovery.... so can't flash modded roms like this one.
Stifilz
---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------
Ultimate Chicken said:
Quick question - do you need to be on 3.2 before you can flash this? I got a different assert.
Click to expand...
Click to collapse
Don't worry about that, that was condi and I trying to figure something out. Didn't work BTW.
As in first post you need to be on R1A/R2A. US is the only region with R5 out atm. Apparently the other regions are due out mid DEC....
Stifilz
Must be doing something wrong....
Hi,
I'm trying to flash a UK 4.0.3 R1a tablet with the details in this thread.
The tablet was rooted via the b1nry method (when that method was first discovered).
All appears to work OK but then I get a failed assert.
Told the device to do a full wipe, then rooted using the AiO5.2 - this worked fine.
Then attempted the flash again, still no joy, same error message.
What am I doing wrong ? Should I changed the tablet to US region before attempting the flash ?
Thanks
Ian
---------- Post added at 07:46 PM ---------- Previous post was at 07:40 PM ----------
In answer to my own query - no that doesn't help either, the error this time coming much sooner (whilst verifying update package) :-
Erohibit update as a result of checking version or base sku
Attached should be a pic of the actual error I receive...if that helps at all..
ianfretwell said:
Attached should be a pic of the actual error I receive...if that helps at all..
Click to expand...
Click to collapse
That error is 100000% ok.
Use 'adb devices' and tell me if there is device there - im pretty sure that there will be none.
Probably you have not installed drivers for adb in recovery (yes it needs to be installed aside from regular drivers in normal boot. So enter device manager and there should be new device without driver. You will have to install it manually.
Oh and if you have changed region to US, then go to AiO\files directory and delete _hack_recovery.zip.
Condi - many thanks, you were, of course, absolutely correct and the flash has now succeeded !!
Apologies for being the noob!!
Ian.
condi said:
I've prepared ready-to-flash US nbx03_001-ota-120914044.
So you will have newest R5A with still adb shell enabled in recovery!
Click to expand...
Click to collapse
Does this really contain 4.0.3 release 5a, which is scheduled to be released mid-December 2012? I ask because I am pretty sure the update file nbx03_001-ota-120914044.zip contains 4.0.3 release 5, not release 5a.
I agree with you. That may be tiny mistake. The incremental numba says that it s from US 4.0.3.r5.
Cat McGowan said:
Does this really contain 4.0.3 release 5a, which is scheduled to be released mid-December 2012? I ask because I am pretty sure the update file nbx03_001-ota-120914044.zip contains 4.0.3 release 5, not release 5a.
Click to expand...
Click to collapse
biablo said:
I agree with you. That may be tiny mistake. The incremental numba says that it s from US 4.0.3.r5.
Click to expand...
Click to collapse
yes, just a typo, my bad ive lost count with all that incrementals lol
wifi only rom, right?
I acquired a Chinese-bought Galaxy Tab 10.1 P7500 16gb from Gumtree a few days ago.
I imagine most were put off by the lack of Google Maps, Play, Mail on the device- Just meant I was able to get away with paying as little as £130
Having used custom roms for years on my HTC Desire HD and Galaxy Note 2, I was quickly able to find a Rom here at xda to bring it up to fuller functionality - currently using Stock ICS from Toldo
I've been using a 4.1.2 for on my phones for months, and only now that I'm back to 4.0.4 on my GT does it come to mind what's missing; particularly Google Now.
I've tried a bunch of CM10 and CM 10.1 derivatives for the tab but none (so far) will install. I have a feeling that this is something to do with the fact that my tab was chinese, therefore not the exact model the rom was built for.. despite trying several roms and ensuring that P7500 was mentioned in the description.
log from most recent CM10.1 nightly; although the same errors are found in all other roms I've tried based on android 4.1.2 or later.
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/cm-10.1 - 20130109-NIGHTLY-p4 GSM.zip
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "p4" || getprop("ro.built.product") == "p4"
E: Error in /sdcard/cm-10.1 - 20130109-NIGHTLY-p4 GSM.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I'm either looking for a way around this error to install these roms regardless of the exact model they were built for, or a reccommendation or a rom which wouldn't have this problem.
I hope the length of my post doesn't put anyone off lending a hand. Thanks in advance!
Same problem here
I have the same problem... My model is the Korean SHW-M380K, I was able to succesfully install other ICS gt-p7500 roms but same status 7 error with the jelly bean update... isnt there a way we could use odin to do it?
Semi-Solved
Having done some more googling, this seems to have solved the problem.
androidgadgematic.com/2012/12/fix-custom-rom-installation-status-7.html
Basically, you're going into the zip file to /META-INF/com/google/android/updater-script
This file is contains the instructions for the roms installation.
The first few lines (depending on the ROM) are basically checking that you're installing the rom on the device it was designed for
they look like this
assert(getprop("ro.product.device") == "p4" || getprop("ro.build.product") == "p4");
Click to expand...
Click to collapse
Removing these lines will allow the installation to continue without checking you're installing to the right device.
I tried and failed similar instructions, but this one does seem to get it right- the primary difference being that I'm using the exact programs mentioned in these instructions- Notepad++ and Winzip.
I'd previously tried 7zip, and the zip handling built into windows, but these didn't work.
I'll be experimenting with a few different roms now to see if any will let me use mobile data.
you do not need to tamper with the rom in this regard. it is there to prevent flashing on unsupported devices.
flash recovery (CWM 6.0.2.7):
http://droidbasement.com/galaxy/roms/cm10.1/p4/recovery.tar.md5 via odin.
then you will be able to flash the nightlies (which is currently at 4.2.1) via http://get.cm/?device=p4&type=nightly for GT-P7500 without being blocked.
here is the thread for nightly discussion (which contains info, tips, etc.):
http://forum.xda-developers.com/showthread.php?t=2074202
you must be on the ICS bootloader, or you will incur a 'rolling' screen in both recovery and rom:
http://droidbasement.com/galaxy/roms/cm10.1/p4/bootloader.tar.md5
ICS modem is in the cm10.1/p4 folder as well. both are from P7500XWLP9 release.
Thanks!
pershoot said:
you do not need to tamper with the rom in this regard. it is there to prevent flashing on unsupported devices.
flash recovery (CWM 6.0.2.7):
http://droidbasement.com/galaxy/roms/cm10.1/p4/recovery.tar.md5 via odin.
then you will be able to flash the nightlies (which is currently at 4.2.1) via http://get.cm/?device=p4&type=nightly for GT-P7500 without being blocked.
here is the thread for nightly discussion (which contains info, tips, etc.):
http://forum.xda-developers.com/showthread.php?t=2074202
you must be on the ICS bootloader, or you will incur a 'rolling' screen in both recovery and rom:
http://droidbasement.com/galaxy/roms/cm10.1/p4/bootloader.tar.md5
ICS modem is in the cm10.1/p4 folder as well. both are from P7500XWLP9 release.
Click to expand...
Click to collapse
Thanks so much for this!
I'm not sure whether it was a newer recovery (I was on 5.8.?.? previously), or whether it was the bootloader but I've just been able to update to the newest CM10.1 nightly without removing the first line of the updater script.
The status 7 error has made updating my phone impossible for the last several months. I'm stuck on Task650 last AOKP release because that's the only thing that will install (I was running it when I got the error). Every internet source tells me to unzip the rom, remove the "ASSERT" section from the updater script and then recompress. This still hasn't worked for me and I've tried several different roms from 4.2,4.3 and 4.4. I updated CWM to the latest version successfully but I still get the error with roms and GAPPS. This is with full wipes.
I suspect the problem has something to do with mounting, but playing with those settings hasn't helped. I see mount /sdcard as an option, but toggling that also produces an error. I've tried my best to figure this out, any help would be appreciated.
Maybe it would help you to understand what is going on to cause the status 7 error. The install file, a ClockworkMod flashable zip file, has an asserts line that causes it to look in the build.prop file (build properties) on the phone to make sure that it is not being installed onto the wrong phone. So, for instance, if it wants to install the firmware on the AT&T version of the GSII, it will look for one of the properties in the build.prop file that should say "SGH-I777." I don't remember off hand which property it reads, but I will list all of them in a minute.
There are two ways to correct the status 7 error. One you have mentioned is to remove the asserts clause from the install file. If you do this correctly, the firmware will install. The other way is to correct the entries in your phone's build.prop file to match what the asserts clause is looking for. In my opinion, the second method is the better one.
On my phone, running SHOstock3 v3.0.2, the following lines in build.prop have SGH-I777:
ro.product.model=SGH-I777
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.build.product=SGH-I777
build.prop is in the system directory. Look in the asserts clause of the install file to see what it is looking for. If it is firmware intended for this phone, it should be looking for SGH-I777. If it is looking for something else, please make sure the firmware is intended for the AT&T version of the SGII. Next, use a root file explorer to change the above four entries in your build.prop to the correct values. build.prop is a text file, so just open it, edit it, and save it. Then reboot the phone for the changes to be recognized. Now you will be able to install your new firmware.
Thanks for the detailed response. Since I already removed the assert sections, I didn't expect the build.prop to be the source of the problem. I did go through and check it, the values were correct, showing SGH-i777, I did edit them to SGH-I777 as you said but that still didn't help.
Surprised to see someone have the same exact issue as me. I too was using Task650's last AOKP Rom as my last Rom as well and I too am unable to flash any new Roms.
I updated CWM in hopes that it would help but no luck.
Were can I find the assert clause to edit them in the .zip file of new rom that I'm trying to install?
Edit: Might have found the location although I'm not sure if its the correct one. META-INF>com>google>android>updater-script ?
I compared PAC-Rom's script (rom I want) with Task650's AOKP script and found that AOKP's script has two extra lines that are missing in PAC-Rom's script:
PAC
assert(getprop("ro.product.device") == "i777" ||
getprop("ro.build.product") == "i777" ||
getprop("ro.product.device") == "SGH-I777" ||
getprop("ro.build.product") == "SGH-I777" ||
getprop("ro.product.device") == "SGH-S959G" ||
getprop("ro.build.product") == "SGH-S959G")
AOKP
assert(getprop("ro.product.device") == "i777" ||
getprop("ro.build.product") == "i777" ||
getprop("ro.product.device") == "SGH-I777" ||
getprop("ro.build.product") == "SGH-I777" ||
getprop("ro.product.device") == "SGH-i777" ||
getprop("ro.build.product") == "SGH-i777" ||
getprop("ro.product.device") == "SGH-S959G" ||
getprop("ro.build.product") == "SGH-S959G")
Can I use any of this to flash the rom?
I attempted to copy the script (above lines only) to the PAC script but I dont know how to save it in the .zip file as so..
Try Notepad++; it saves and re-signs zips perfectly.
SteveMurphy said:
Try Notepad++; it saves and re-signs zips perfectly.
Click to expand...
Click to collapse
Thanks for the reply. I downloaded notepad++ but have no clue how to use it, much less how to change the above only.
I'm having same situation.
I tried to flash CWM for my i777, and as I have read through it is only possible with custom kernel. So I rooted my phone, downloaded Mobile Odin because kernels im getting from here are not odin compatible (tar files) and I flashed the kernel with mobile odin like described in one post here on forums. I have working recovery but i'm unable to flash any Rom on my phone, which made it unusable for now.
Im getting same Error , Status 7 but I can see also this on top of error
Warning: No file_contextsset_metadata_recursive: some changes failed
Is there something wrong with recovery or im doing something wrong.
gjizaqin said:
I'm having same situation.
I tried to flash CWM for my i777, and as I have read through it is only possible with custom kernel. So I rooted my phone, downloaded Mobile Odin because kernels im getting from here are not odin compatible (tar files) and I flashed the kernel with mobile odin like described in one post here on forums. I have working recovery but i'm unable to flash any Rom on my phone, which made it unusable for now.
Im getting same Error , Status 7 but I can see also this on top of error
Warning: No file_contextsset_metadata_recursive: some changes failed
Is there something wrong with recovery or im doing something wrong.
Click to expand...
Click to collapse
Before we can answer your question, we need to know exactly what you did. For instance, did you actually try to flash a recovery with Odin, or did you try to flash CWM with rom manager? And more importantly, exactly what did you do to flash a new kernel using mobile odin, and what kernel did you flash?
I had the same issue. I ended up having to use odin to return to stock and go from there.
yurkinator said:
I had the same issue. I ended up having to use odin to return to stock and go from there.
Click to expand...
Click to collapse
Yeap. Pretty much went back to stock, then root, then was able to get PAC installed
Sent from my Nexus 5 using Tapatalk
hi
creepyncrawly said:
Maybe it would help you to understand what is going on to cause the status 7 error. The install file, a ClockworkMod flashable zip file, has an asserts line that causes it to look in the build.prop file (build properties) on the phone to make sure that it is not being installed onto the wrong phone. So, for instance, if it wants to install the firmware on the AT&T version of the GSII, it will look for one of the properties in the build.prop file that should say "SGH-I777." I don't remember off hand which property it reads, but I will list all of them in a minute.
There are two ways to correct the status 7 error. One you have mentioned is to remove the asserts clause from the install file. If you do this correctly, the firmware will install. The other way is to correct the entries in your phone's build.prop file to match what the asserts clause is looking for. In my opinion, the second method is the better one.
On my phone, running SHOstock3 v3.0.2, the following lines in build.prop have SGH-I777:
ro.product.model=SGH-I777
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.build.product=SGH-I777
build.prop is in the system directory. Look in the asserts clause of the install file to see what it is looking for. If it is firmware intended for this phone, it should be looking for SGH-I777. If it is looking for something else, please make sure the firmware is intended for the AT&T version of the SGII. Next, use a root file explorer to change the above four entries in your build.prop to the correct values. build.prop is a text file, so just open it, edit it, and save it. Then reboot the phone for the changes to be recognized. Now you will be able to install your new firmware.
Click to expand...
Click to collapse
is it possible to find them like this
ro.product.model=GT-P5110
ro.product.name=espresso10wifi
ro.product.device=espresso10wifi
ro.build.product=espresso10wifi
i have GT-P5113
R E H said:
is it possible to find them like this
ro.product.model=GT-P5110
ro.product.name=espresso10wifi
ro.product.device=espresso10wifi
ro.build.product=espresso10wifi
i have GT-P5113
Click to expand...
Click to collapse
Tab 2 10.1? I have no experience with your device.
Logic alone makes me think that the above is incorrect, but apparently I understand the status 7 issue only incompletely. I'm afraid I won't be of any help to you.
Kitkat 4.4.4 Installation Aborted in Xperia L with error "status 7"
creepyncrawly said:
Maybe it would help you to understand what is going on to cause the status 7 error. The install file, a ClockworkMod flashable zip file, has an asserts line that causes it to look in the build.prop file (build properties) on the phone to make sure that it is not being installed onto the wrong phone. So, for instance, if it wants to install the firmware on the AT&T version of the GSII, it will look for one of the properties in the build.prop file that should say "SGH-I777." I don't remember off hand which property it reads, but I will list all of them in a minute.
There are two ways to correct the status 7 error. One you have mentioned is to remove the asserts clause from the install file. If you do this correctly, the firmware will install. The other way is to correct the entries in your phone's build.prop file to match what the asserts clause is looking for. In my opinion, the second method is the better one.
On my phone, running SHOstock3 v3.0.2, the following lines in build.prop have SGH-I777:
ro.product.model=SGH-I777
ro.product.name=SGH-I777
ro.product.device=SGH-I777
ro.build.product=SGH-I777
build.prop is in the system directory. Look in the asserts clause of the install file to see what it is looking for. If it is firmware intended for this phone, it should be looking for SGH-I777. If it is looking for something else, please make sure the firmware is intended for the AT&T version of the SGII. Next, use a root file explorer to change the above four entries in your build.prop to the correct values. build.prop is a text file, so just open it, edit it, and save it. Then reboot the phone for the changes to be recognized. Now you will be able to install your new firmware.
Click to expand...
Click to collapse
Hi Experts !!
I was trying to update my Xperia L from V 4.2.2 to Kitkat 4.4.4 .
I rooted the device and bootloader unlocked also.
Installed Fastboot CWM v6.0.3.5 in my mobile.
I had the ROM and GAPP in external memory card.
When i tried installing the ROM from memory card zip file i got the below error and aborted.
from the log :
I: Can't partition non-vfat : auto
I: Can't format unknown volume: /emmc
Actual error while installation as follows:
Finding update package....
Opening update package....
Installing update ....
set_metdata_recurisive : some changes failed
E: error in /external_sd/cm-11-20140727-NIGHTLY-taoshan.zip
(status 7)
Installation aborted.
I'm struck now.. Please help how can i complete the installation and where im going wrong ?
kavinbhaskar said:
Hi Experts !!
I was trying to update my Xperia L from V 4.2.2 to Kitkat 4.4.4 .
Click to expand...
Click to collapse
Best way for you to get answers for your device is to ask in the correct forum; for you it would be http://forum.xda-developers.com/xperia-l/help
Good luck.
Same problem here.......
I was running the stock jellybean rom UK Vodafone unrooted. Then I flashed Jeboo kernel i9100-1a using Odin.
Then I got into CWM recovery and installed SuperSU.1.25 UPDATE.
After all these I rebooted got into CWM and installed CM 11 I9100 nightly. (It worked on my cousins phone)
After a long time the progress bar reaches the end and BAM!
set_metadata_recursive some changes failed
Error in sdcard/directory/"name "zip
(Status 7) Installation Aborted.
The phone is confirmed rooted (Yellow Triangle).
Please Help!!!!!!:crying:
I am not familiar with the i9100 jeboo kernel, and you don't need it for the i777, so my advice is:
reboot to recovery
flash the i777 shift kernel
reboot to recovery
flash an i777 cm11
enjoy i777-specific kit-kat on your sgh-i777
Jilmax said:
I was running the stock jellybean rom UK Vodafone unrooted. Then I flashed Jeboo kernel i9100-1a using Odin.
Then I got into CWM recovery and installed SuperSU.1.25 UPDATE.
After all these I rebooted got into CWM and installed CM 11 I9100 nightly. (It worked on my cousins phone)
After a long time the progress bar reaches the end and BAM!
set_metadata_recursive some changes failed
Error in sdcard/directory/"name "zip
(Status 7) Installation Aborted.
The phone is confirmed rooted (Yellow Triangle).
Please Help!!!!!!:crying:
Click to expand...
Click to collapse
what
i also had the same error on my touchpad but all i had to do was delete those assert lines .i used notepad
An update went wrong, something happened and it aborted. I tried again and got the following error.
/dev/block/platform/sdhci-tegra.3/by-name/APP has been remounted R/W; reflash device to reenable OTA updates
E: Error in /sideload/package.zip
(Status 7)
When I tried to boot i was stuck in a loop of Android is Upgrading, I read up on it and the only way out was a factory reset, I did that and that made things worse, now the tablet is stuck in a loop of Android is starting, cache clearing and factory resets haven't fixed it, Only way out now is to flash the stock image but to do that i need to unlock the bootloader, to do that i need to boot to the OS and tick an option in the dev settings, I tried everything i knew and nothing worked, please help.
@Sebianoti,
Time to start the OTA. You have no other options if your bootloader is locked.
cam30era said:
@Sebianoti,
Time to start the OTA. You have no other options if your bootloader is locked.
Click to expand...
Click to collapse
I have, it's in the post too. When i do that i get an error
/dev/block/platform/sdhci-tegra.3/by-name/APP has been remounted R/W; reflash device to reenable OTA updates
E: Error in /sideload/package.zip
(Status 7)
Sebianoti said:
I have, it's in the post too. When i do that i get an error
/dev/block/platform/sdhci-tegra.3/by-name/APP has been remounted R/W; reflash device to reenable OTA updates
E: Error in /sideload/package.zip
(Status 7)
Click to expand...
Click to collapse
My bad, I fat fingered it. I meant RMA!
cam30era said:
My bad, I fat fingered it. I meant RMA!
Click to expand...
Click to collapse
Easier said than done, I have a north american model and i'm in UK (long story), I already contacted someone at HTC and might be getting a replacement but i still have a dead tablet i'd like to fix, seems that's not possible
Sebianoti said:
Easier said than done, I have a north american model and i'm in UK (long story), I already contacted someone at HTC and might be getting a replacement but i still have a dead tablet i'd like to fix, seems that's not possible
Click to expand...
Click to collapse
Correct