I have seen in several places across the web the leaked OTA JB update for the bell Galaxy S3 i747 model. I have found several tutorials all of which end with the same thing the download mode choosing the file then I receive a message in red stating E:Error in /tmp/sideload/package.zip (status 6). Looking through the comments I found that I am not the only one to receive this message but a thorough google search has resulted in no solutions whatsoever.
How can I fix this error 6?
riesnich said:
I have seen in several places across the web the leaked OTA JB update for the bell Galaxy S3 i747 model. I have found several tutorials all of which end with the same thing the download mode choosing the file then I receive a message in red stating E:Error in /tmp/sideload/package.zip (status 6). Looking through the comments I found that I am not the only one to receive this message but a thorough google search has resulted in no solutions whatsoever.
How can I fix this error 6?
Click to expand...
Click to collapse
Had that problem. Go to my profile, and check my bell gs3 thread (should be newest) and download the OTA, it's a different version and does not have the error. If you already have the latest firmware shouldn't be an issue, just flash away. Hope this helps.
Related
OK, so I've got a Samsung Tab 7 (GT-P1000T). Running firmware 2.2, kernel 2.6. I'm trying to upgrade to CyanogenMod, looks like the closest I'll be able to get to ICS for the Tab as it's not supported. I've used Doomlord's zergrush root to get the device rooted, but now I'm having issues with CM.
I'm trying to use the p1 builds as they appear to be the correct one for this device. I've tried CM10 nightly and CM9 official to no success. At first there is an assert error because it's only looking for P1000, so I've tried changing the assert to look for P1000T and also just deleting the assert line. In both instances it reports that it is installing the update and then aborting the update with no indications as to why.
I'm hoping someone has had some experience with this or can point me in the right direction. I'm not having any luck with google. (Also, sorry if I've posted in the wrong part of the forum).
I recently rooted and flashed my Samsung Galaxy S3 SCH-S960L (TracFone Variation, Sprint Based) with CyanogenMod 10.2-20131102-SNAPSHOT-M1-d2mtr which is for the MetroPCS version of CyanogenMod. Along with it saying MetroPCS, I also had an issue where the landscape orientation would be inverted which is quite a nuisance. Over on CyanogenMod's website someone suggested flashing the Sprint ClockworkMod (Which I was already using but for MetroPCS) and flashing the Sprint version of CyanogenMod. Now, upon flashing the ROM I get the error of
Code:
ClockworkMod Recovery v6.0.4.3
/storage/sdcard1: Checking
/storage/sdcard1: Mounted
--Installing" /storage/sdcard1/cm-10.1.3-d2spr.zip
Finding update package...
Opening update package...
Installing update...
assert failed: get prop("ro.bootloader") == "L710VPBLJ7" || get prop("ro.bootloader")
(Log is not directly copied, some symbols may be inaccurate)
From there is just continues with similar lines of error.
Can anyone provide a fix to using my phone? I have to use the MetroPCS/Sprint versions of CWM and CM since the TracFone version of the Galaxy S3 has little support. At the moment my device is a brick and I would really like to use CyanogenMod but without that orientation issue and it saying "MetroPCS"
Any support is appreciated.
With best regards,
SirBenjamin
SirBenjamin said:
I recently rooted and flashed my Samsung Galaxy S3 SCH-S960L (TracFone Variation, Sprint Based) with CyanogenMod 10.2-20131102-SNAPSHOT-M1-d2mtr which is for the MetroPCS version of CyanogenMod. Along with it saying MetroPCS, I also had an issue where the landscape orientation would be inverted which is quite a nuisance. Over on CyanogenMod's website someone suggested flashing the Sprint ClockworkMod (Which I was already using but for MetroPCS) and flashing the Sprint version of CyanogenMod. Now, upon flashing the ROM I get the error of
Code:
ClockworkMod Recovery v6.0.4.3
/storage/sdcard1: Checking
/storage/sdcard1: Mounted
--Installing" /storage/sdcard1/cm-10.1.3-d2spr.zip
Finding update package...
Opening update package...
Installing update...
assert failed: get prop("ro.bootloader") == "L710VPBLJ7" || get prop("ro.bootloader")
(Log is not directly copied, some symbols may be inaccurate)
From there is just continues with similar lines of error.
Can anyone provide a fix to using my phone? I have to use the MetroPCS/Sprint versions of CWM and CM since the TracFone version of the Galaxy S3 has little support. At the moment my device is a brick and I would really like to use CyanogenMod but without that orientation issue and it saying "MetroPCS"
Any support is appreciated.
With best regards,
SirBenjamin
Click to expand...
Click to collapse
http://review.cyanogenmod.org/#/c/54652/ got it merged in, come tomorrow just flash the latest d2spr nightly and it should flash in d2spr recovery for you.
it works
shabbypenguin said:
http://review.cyanogenmod.org/#/c/54652/ got it merged in, come tomorrow just flash the latest d2spr nightly and it should flash in d2spr recovery for you.
Click to expand...
Click to collapse
I got it to work(this is bilyan from IRC) missed CM on my s3
wickedclown691 said:
I got it to work(this is bilyan from IRC) missed CM on my s3
Click to expand...
Click to collapse
glad to hear it
APN
make sure you back up your apn. After I installed d2spr I couldnt connect with data. I had to restore APN settings.
Hi all,
I posted this in the S3 specific forum but not getting a lot of traction there. Just picked up a refurbished AT&T Galaxy S3 (i747) and it appears to have the T-Mobile (T999) bootloader for some reason.
Here's what I've found model and version-wise...
System settings - About device:
Model number SGH-I747
Android version 4.1.2 (stock Touchwiz)
Build number I747ZSEMC1
Info app from Play store:
Boot loader version T999UVDMD5
Finger print samsung/d2vl/d2can:4.1.1/JRO03l/I747ZSEMC:user/release-keys
Product d2vl
Model SGH-I747
Download Mode shows T999 bootloader.
Putting a T-Mobile sim in registers on the network and for some reason I get H+, which I didn't think was possible with the I747 AT&T model. Don't have an AT&T sim to test with at the moment.
I've tried flashing the I747 4.1.2 bootloader but I get different error messages depending on which recovery I use to flash it.
Stock recovery:
Verifying update package...
E:signature verification failed
Installation aborted
Clockworkmod:
E:Error in (file path and name)
(Status 7)
Installation aborted.
TWRP:
E:Error executing updater binary in zip (file path and name)
Updating partition details...
Failed
I've also tried using the Cyanogenmod installer under Windows and it says that it installed successfully but Touchwiz is still there. I noticed a red triangle during the process as well so I suspected it wasn't working.
My primary concern right now is how can I fix this bootloader issue so I can get a more recent rom on it? Any suggestions?
Anyone have any ideas at all? I've tried flashing a number of bootloaders in Odin and continue to get errors like "FAIL! (Auth)" and "SECURE CHECK FAIL : aboot." I can't flash anything in recovery it seems.
I can still get into stock Touchwiz and CWM recovery and Download Mode, but I can't seem to get ANYTHING to flash properly on this device.
Edit: It seems to always fail on aboot.mbn, which I'm reading can be caused by a locked bootloader. Anything I can do about that?
I was able to flash AOKP 4.4, I'm assuming because it didn't mess with the bootloader any. Baseband version is still showing as T999UVDMD5. If I try to flash something like Cyanogenmod I get a bootloader error and it fails.
Everything in build.prop shows SGH-I747 and d2att as the device model. I don't understand why it has a T-Mobile bootloader. Anyone know how to fix this?
I have the exact opposite problem. It's an SGH-T999 that ids itself as an i747 in download mode. I can flash some things with Odin, but not full ROM tars ... I did flash Philz recovery and use it to flash other roms as zips ... but having trouble doing other things with it. And since I lost the IMEI and need it to talk over RMNET to fix that ... I think it's this i747 firmware that's messing me up.
I wouldn't even worry about it now that AOKP 4.4.2 flashed okay, but the camera doesn't work and I can't seem to find a working solution. One thing after another...
Hi all, its been a while since i posted but i am royally stuck, using various threads and guides i got my m8 vodafone uk back to stock, everything as it should be.
however i am seeing 3 very small OTA updates pending, the trouble is i cant for the life of me get them to download, each time i try i get an error saying "Download failed" "An error occurred while downloading the software updates."
all three of the updates info say that they are to prepare my device for the upcoming marshmallow update
any help would be greatly appreciated
Bump. This is happening to me too and I can't find any information on it. I just un rooted my phone and can't apply the update
First off I want to preempt by saying I have searched for answers to the best of my abilities and haven't found a solution that has worked. However I might have missed one. I will attempt to be as thorough as i can here.
I have a rooted unlocked pixel 2xl, Magisk no twrp. I have attempted to sideload the Ota but it fails before it gets off the ground. I get a verification error and the Ota fails to load.
Dumb question #1) do i need to unroot to sideload the ota with the setup I have.?I thought unrooting was only necessary with partitioned recovery like TWRP.
I have the latest tools, the latest OTA for my model phone, a hope a prayer, but little else.
"E: footer is wrong
update package verification took 0.0 s (results 1)
E: signature verification failed
E: error 21
installation aborted.
"
What am I missing? Any help would be appreciated.
filthysanches said:
First off I want to preempt by saying I have searched for answers to the best of my abilities and haven't found a solution that has worked. However I might have missed one. I will attempt to be as thorough as i can here.
I have a rooted unlocked pixel 2xl, Magisk no twrp. I have attempted to sideload the Ota but it fails before it gets off the ground. I get a verification error and the Ota fails to load.
Dumb question #1) do i need to unroot to sideload the ota with the setup I have.?I thought unrooting was only necessary with partitioned recovery like TWRP.
I have the latest tools, the latest OTA for my model phone, a hope a prayer, but little else.
"E: footer is wrong
update package verification took 0.0 s (results 1)
E: signature verification failed
E: error 21
installation aborted.
"
What am I missing? Any help would be appreciated.
Click to expand...
Click to collapse
Let me start with, you're in the wrong section, with the wrong phone for the section. Actually, I'm starting and ending with that. I wish you luck though.
See and that's why your senior member thanks
filthysanches said:
First off I want to preempt by saying I have searched for answers to the best of my abilities and haven't found a solution that has worked. However I might have missed one. I will attempt to be as thorough as i can here.
I have a rooted unlocked pixel 2xl, Magisk no twrp. I have attempted to sideload the Ota but it fails before it gets off the ground. I get a verification error and the Ota fails to load.
Dumb question #1) do i need to unroot to sideload the ota with the setup I have.?I thought unrooting was only necessary with partitioned recovery like TWRP.
I have the latest tools, the latest OTA for my model phone, a hope a prayer, but little else.
"E: footer is wrong
update package verification took 0.0 s (results 1)
E: signature verification failed
E: error 21
installation aborted.
"
What am I missing? Any help would be appreciated.
Click to expand...
Click to collapse
- fastboot flash stock boot.img (current running version, inside factory image.zip)
- boot to stock recovery and sideload the OTA.zip
after that you need boot/flash twrp and root the phone if you want to have root again.
Yeah I was hoping to avoid all that as I would need to free my tether as well. Allot of steps for an update, but it's looking like I might not have a choice.
filthysanches said:
First off I want to preempt by saying I have searched for answers to the best of my abilities and haven't found a solution that has worked. However I might have missed one. I will attempt to be as thorough as i can here.
I have a rooted unlocked pixel 2xl, Magisk no twrp. I have attempted to sideload the Ota but it fails before it gets off the ground. I get a verification error and the Ota fails to load.
Dumb question #1) do i need to unroot to sideload the ota with the setup I have.?I thought unrooting was only necessary with partitioned recovery like TWRP.
I have the latest tools, the latest OTA for my model phone, a hope a prayer, but little else.
"E: footer is wrong
update package verification took 0.0 s (results 1)
E: signature verification failed
E: error 21
installation aborted.
"
What am I missing? Any help would be appreciated.
Click to expand...
Click to collapse
u prolly were answered already but if ur unlocked u should be updating through fastboot..
o and this is a dev section plus not the xl forum lol
Yeah I was informed. I'm not sure how I wandered my way here but you know mistakes and all that. I'll be more careful next time. I figured a mod would have struck me down by now.
Thanks
filthysanches said:
Yeah I was informed. I'm not sure how I wandered my way here but you know mistakes and all that. I'll be more careful next time. I figured a mod would have struck me down by now.
Thanks
Click to expand...
Click to collapse
If you're using xda labs, first running after install on my pixel 2, the app automatically took me to the pixel 2 xl forums when I clicked my device. Honest mistake. Don't let these ethugs bother ya. Did you get your xl fixed?
filthysanches said:
First off I want to preempt by saying I have searched for answers to the best of my abilities and haven't found a solution that has worked. However I might have missed one. I will attempt to be as thorough as i can here.
I have a rooted unlocked pixel 2xl, Magisk no twrp. I have attempted to sideload the Ota but it fails before it gets off the ground. I get a verification error and the Ota fails to load.
Dumb question #1) do i need to unroot to sideload the ota with the setup I have.?I thought unrooting was only necessary with partitioned recovery like TWRP.
I have the latest tools, the latest OTA for my model phone, a hope a prayer, but little else.
"E: footer is wrong
update package verification took 0.0 s (results 1)
E: signature verification failed
E: error 21
installation aborted.
"
What am I missing? Any help would be appreciated.
Click to expand...
Click to collapse
on my pixel 2 I had the same issues. Had to manually change the slot from b to a and fastboot some stuff. hope it helps
Sent from my Pixel 2 using Tapatalk
filthysanches said:
First off I want to preempt by saying I have searched for answers to the best of my abilities and haven't found a solution that has worked. However I might have missed one. I will attempt to be as thorough as i can here.
I have a rooted unlocked pixel 2xl, Magisk no twrp. I have attempted to sideload the Ota but it fails before it gets off the ground. I get a verification error and the Ota fails to load.
Dumb question #1) do i need to unroot to sideload the ota with the setup I have.?I thought unrooting was only necessary with partitioned recovery like TWRP.
I have the latest tools, the latest OTA for my model phone, a hope a prayer, but little else.
"E: footer is wrong
update package verification took 0.0 s (results 1)
E: signature verification failed
E: error 21
installation aborted.
"
What am I missing? Any help would be appreciated.unless you are able to format data don't flash custom recovery and allow the device to boot to stock recovery and reset from there. I still say factory images not ota for stock
Click to expand...
Click to collapse
Your better off flashing factory images via fastboot