Related
I am rooted and have an unlocked bootloader but have stock rom and stock kernals and stock radios.... everything else stock.
I get the "new update available" OTA click to restart and the phone restarts. I get the android with a blue spinning something in his back with the progress bar moving. at about 25% it always changes to the android on his back with a red triangle exclamation point. Nothing happens from here.
I can do a battery pull and get the phone to start fine again.
I've seen these problems in other posts, but theres always something thats not the same as my phone for example the person flashed a rom or kernal. I have not.
any help?
kegman913 said:
I am rooted and have an unlocked bootloader but have stock rom and stock kernals and stock radios.... everything else stock.
<snip>
I've seen these problems in other posts, but theres always something thats not the same as my phone for example the person flashed a rom or kernal. I have not.
Click to expand...
Click to collapse
Can't help, I'm in the same boat. Trying to think of anything I've done that could be interfering:
Adfree (changes /etc/hosts)
SecureSettings plugin (installs a helper app)
SQLite Installer for root (failed to get this to work; tried to do it manually, forget if I got it )
Maybe there's something else I did that could be interfering too, I forget. At this point I'm wondering if its time to give up on stock and go CM9?
So you rooted your phone, and installed a custom bootloader then kept everything else stock?
My best guess is the custom bootloader is interfering with some permissions being requested by the update. I would go back 100% stock (un-root and reflash the original bootloader) then apply the update with everything locked down just like Big Red likes it.
Make sure you always backup when playing with bootloaders and rooting!
Hope this helps!
i just unlocked the bootloader, this isn't considered a custom bootloader is it? basically, I never did anything custom to it
Did you change your fonts or changed anything with the UI? How about modifying the build.prop?
If you try it again and see the android guy laying down press volume up + power to show the menu. It should list where the OTA failed. (you might have to press that combo a few times)
Report back.
i'll try it a second time when I get home, but volume up and power do nothing, hitting them together, in sucession, holding them both down, holding volume up, down and power do nothing either.......weird
nope, does nothing, maybe the other guy with this prob can confirm?
Hmmm weird. I'm pretty sure you can get the stock recovery to display with a button combo.
You might have to flash the stock image to get the OTA to apply. Something had to have been changed in /system.
Read Efrant's guide on how to do so. http://forum.xda-developers.com/showpost.php?p=25477039&postcount=1
i read somewhere that it might be due to clockwork recovery being the default recovery. how do I change this?
kegman913 said:
i read somewhere that it might be due to clockwork recovery being the default recovery. how do I change this?
Click to expand...
Click to collapse
You need to flash the stock recovery image. Download the factory image for the build that you are on, extract the recovery.img file, reboot your phone into fastboot, and in a command prompt, type: fastboot flash recovery recovery.img
Have a read of the guide that El Daddy linked to. It may explain some things for you.
Red Triangle - Error info
I'm also having this problem with trying to update.
I have an unlocked bootloader but its still the standard one (I didn't do anything other than unlock it) and I'm rooted but didn't flash any ROMs so it is still stock 4.0.2.
I tried a factory reset, stupidly without making sure everything was backed up, and it didn't change anything, I still get the red triangle, in case anyone was thinking of trying that.
I got to the recovery menu (holding power and pressing volume up) and after Installing the update... and Verifying current system...
Here is the entire error message:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
E: Error in /cache/12f767e7a5d0.incremental.zip
(status 7)
Installation aborted
From there, I have no choice but to choose to reboot. Hope this info helps someone come up with a solution.
umataro42 said:
I'm also having this problem with trying to update.
I have an unlocked bootloader but its still the standard one (I didn't do anything other than unlock it) and I'm rooted but didn't flash any ROMs so it is still stock 4.0.2.
I tried a factory reset, stupidly without making sure everything was backed up, and it didn't change anything, I still get the red triangle, in case anyone was thinking of trying that.
I got to the recovery menu (holding power and pressing volume up) and after Installing the update... and Verifying current system...
Here is the entire error message:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
E: Error in /cache/12f767e7a5d0.incremental.zip
(status 7)
Installation aborted
From there, I have no choice but to choose to reboot. Hope this info helps someone come up with a solution.
Click to expand...
Click to collapse
Did you use Stericson Busybox installer?
I also get thus error any help would be great
drummynator said:
Did you use Stericson Busybox installer?
Click to expand...
Click to collapse
I think so. If I have it installed, does it automatically get used?
Should I try uninstalling it?
umataro42 said:
I think so. If I have it installed, does it automatically get used?
Should I try uninstalling it?
Click to expand...
Click to collapse
Well, I have it installed too and I did try to uninstall it, but it still didn't work.
Sent from my Galaxy Nexus using Tapatalk 2
Does anyone know where the downloaded update is stored?
Does anybody know where the downloaded updated is stored?
If they do can I please put the location.
I am willing to try to install the updated downloaded file using clock work mod recovery.
Why don't you guys just have a read of this. It tells you how to install it manually (really easy), and what you need to do to have it install automatically.
P.S. For those talking about busybox, it has nothing to do with it...
efrant said:
Why don't you guys just have a read of this. It tells you how to install it manually (really easy), and what you need to do to have it install automatically.
P.S. For those talking about busybox, it has nothing to do with it...
Click to expand...
Click to collapse
I have looked at that and tried Method 1, but the same thing happened. I've also tried toggling asserts. Still no luck. I used the mysid IMM76K from ICL53F.
drummynator said:
I have looked at that and tried Method 1, but the same thing happened. I've also tried toggling asserts. Still no luck. I used the mysid IMM76K from ICL53F.
Click to expand...
Click to collapse
The guide also tells you what the requirements are for it to work, namely that all the original system files need to be there.
The recovery will tell you which file is not stock. In your case, you got:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
Which means that your /system/bin/gzip file is not the original one that came with your ROM. Just replace it with the stock one, as per the instructions in the link posted above.
efrant said:
The guide also tells you what the requirements are for it to work, namely that all the original system files need to be there.
The recovery will tell you which file is not stock. In your case, you got:
assert failed: apply_patch_check("system/bin/gizp", "51086995a674ab78fd63b49aa7207df466624897", "5ba3b3ecd509cf6cee37b2f27110310a1f55045")
Which means that your /system/bin/gzip file is not the original one that came with your ROM. Just replace it with the stock one, as per the instructions in the link posted above.
Click to expand...
Click to collapse
That looks like the error I got when I did the VolumeUp/Power combination and attempt the update.
/system/bin/gzip is a symlink for the busybox executable. Is there a way to put back stock files for everything that busybox replaced in one go? I have a feeling if I were to figure out how to get the stock gzip back, and try to do the update, that I'd find another system file was replaced by busybox.
I am a frequent experience Android user and have been flashing Roms since like forever.
Owning gs4 been nice installing Roms all the time however recently when I went to install new gpe ROM (new kernel seemed prime to have) coming from HDrom rls20 I downloaded currupt zip. When I tried installing currupt zip (not knowing yet it was currupt) it gave me red errors not allowing me to proceed.. Then, I turned off device got fresh dload and made sure md5 sum was legit and it was tried again of course first factory data reset with advanced system wipe the ROM proceeded to aroma installer this time.. Attempting to install I chose all my settings and it went to progress bar to install and skipped any system extraction and went straight to Apks.. Batch completed and I hadn't a ROM installed for it took it 5seconds.. I have had this problem in the past before and I sold it they returned it (didn't like condition) and bingo I was able to install Roms again (this was way back in the day with this same gs4) I'm assuming system partition not mounting because also when I tried installing that currupt file it was saying in red unable to mount system and stuff. Luckily I downloaded NK2 firmware (took 8hs) and am fine on stock but I'm hoping someone has a clue to point me in right direction.. I saw forum of somebody with similar issue their fix was pushing zip via computer adb commands then installing. I'll have to give it a try but sticking to stock for a bit. BTW this happens with every ROM just skips system files in fact cyanogenmod just hhung at installation wouldn't fail or complete. I used TWRP LATEST. Please help developers I'm sure this ones a no brainer for y'all. Except seems like issue only I've encountered for this isn't a popular thing at all on google.
SOLVED
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Stoowyguy said:
Thanks to somebody in gs3 forums all i had to do was push adb the rom and wow it worked installed system YAY IM HAAPPPYY
Click to expand...
Click to collapse
What does it mean to "push adb" a phone's rom? Doesn't Odin automatically flash the selected rom?
Hello Everyone!
I am trying desperately to update my Zenfone 2 ZE551ML to Android M without much success, hence this is my last resort.
First I tried to simply download the image from the Asus website and install it via stock recovery, but whatever I did, it just resulted in 'Error'. Looking at the logs, I got the error message that:
"Only Android 5.0(newer than 20160504 version) or Android 6.0.1 (older version) can upgrade to this version"
while mine was VWW-2.20.40.194, which is a 20160801 release.
I found several complaints about this happening over the different forums, but no apparent solution other than trying to flash a raw image. That might have made sense as I got a couple of OTA updates for the 5.0 versions, so I flashed it, but still, I got the same error.
Sideloading via ADB did not bring me any closer to the solution.
I found somewhere that I could work around it by simply deleting this check:
Code:
((getprop("ro.build.version.release") == "5.0") && (greater_than_int(getprop("ro.build.date.utc"), 1462294000))) || ((getprop("ro.build.version.release") == "6.0.1") && (!less_than_int(1477290703, getprop("ro.build.date.utc")))) || abort("Only Android 5.0(newer than 20160504 version) or Android 6.0.1 (older version) can upgrade to this version");
from the zip META-INF\com\google\android\updater-script, but when flashing that, I got a signature error.
I signed the zip with SignApk, but then I got this:
E: footer is wrong
E: signature verification failed
I also renamed the zip on the internal storage to MOFD_SDUPDATE.zip to have the recovery find it az an update zip and flash it from there, but no 'Apply update from internal storage' or similar appeared.
Has anyone managed to work around any of these issues? Or any ideas how to update it?
Thanks!
zakoo2 said:
Hello Everyone!
I am trying desperately to update my Zenfone 2 ZE551ML to Android M without much success, hence this is my last resort.
First I tried to simply download the image from the Asus website and install it via stock recovery, but whatever I did, it just resulted in 'Error'. Looking at the logs, I got the error message that:
"Only Android 5.0(newer than 20160504 version) or Android 6.0.1 (older version) can upgrade to this version"
while mine was VWW-2.20.40.194, which is a 20160801 release.
I found several complaints about this happening over the different forums, but no apparent solution other than trying to flash a raw image. That might have made sense as I got a couple of OTA updates for the 5.0 versions, so I flashed it, but still, I got the same error.
Sideloading via ADB did not bring me any closer to the solution.
I found somewhere that I could work around it by simply deleting this check:
Code:
((getprop("ro.build.version.release") == "5.0") && (greater_than_int(getprop("ro.build.date.utc"), 1462294000))) || ((getprop("ro.build.version.release") == "6.0.1") && (!less_than_int(1477290703, getprop("ro.build.date.utc")))) || abort("Only Android 5.0(newer than 20160504 version) or Android 6.0.1 (older version) can upgrade to this version");
from the zip META-INF\com\google\android\updater-script, but when flashing that, I got a signature error.
I signed the zip with SignApk, but then I got this:
E: footer is wrong
E: signature verification failed
I also renamed the zip on the internal storage to MOFD_SDUPDATE.zip to have the recovery find it az an update zip and flash it from there, but no 'Apply update from internal storage' or similar appeared.
Has anyone managed to work around any of these issues? Or any ideas how to update it?
Thanks!
Click to expand...
Click to collapse
I reply to you with a view to help others too
**** If you dont have a stock LP back up .....****
Coming from rooted any 5 LP rom
1) You first check which firmware you are on or the base the custom rom was built on.
Once you determine 1)
You download the stock recovery for 1)
Unroot device -- go into root settings - select full unroot.
You then fastboot flash above stock recovery -- Then sideload the full asus firmware that is related to the stock recovery you flashed -- eg, on 551 Z00A CM 13 was at a guess built on .165LP(you will have to check yourself,my memory fades here)
Then when flashed , go to settings and factory reset.
Then put asus firmware eg , .184 LP or upwards for 551 on internal and reboot.
Upon reboot , you will get notification to update .
Do the same on 551 with .134 M and reboot .
**** If you do have a stock LP back up .....****
Simply , unroot , flash stock recovery for the build your are on -- sideload full stock same firmware, by-pass set up quickly and factory reset, set it up -- input (on 551) asus firmware of .184 or upwards on internal and reboot, set it up -- do the same with M.134 (on 551) on internal and reboot
timbernot said:
I reply to you with a view to help others too
**** If you dont have a stock LP back up .....****
Coming from rooted any 5 LP rom
1) You first check which firmware you are on or the base the custom rom was built on.
Once you determine 1)
You download the stock recovery for 1)
Unroot device -- go into root settings - select full unroot.
You then fastboot flash above stock recovery -- Then sideload the full asus firmware that is related to the stock recovery you flashed -- eg, on 551 Z00A CM 13 was at a guess built on .165LP(you will have to check yourself,my memory fades here)
Then when flashed , go to settings and factory reset.
Then put asus firmware eg , .184 LP or upwards for 551 on internal and reboot.
Upon reboot , you will get notification to update .
Do the same on 551 with .134 M and reboot .
**** If you do have a stock LP back up .....****
Simply , unroot , flash stock recovery for the build your are on -- sideload full stock same firmware and factory reset,set it up -- input (on 551) asus firmware of .184 or upwards on internal and reboot, set it up -- do the same with M.134 (on 551) on internal and reboot
Click to expand...
Click to collapse
I did not have CM as base, I had official Asus firmware, so I didn't need to flash the stock recovery as it was already on. So I was trying to upgrade from stock to stock. I even flashed the minimum recommended LP by Asus (WW-2.20.40.184) to upgrade to MM (and this flashing succeeded), but still, I couldn't upgrade to MM.
zakoo2 said:
I did not have CM as base, I had official Asus firmware, so I didn't need to flash the stock recovery as it was already on. So I was trying to upgrade from stock to stock. I even flashed the minimum recommended LP by Asus (WW-2.20.40.184) to upgrade to MM (and this flashing succeeded), but still, I couldn't upgrade to MM.
Click to expand...
Click to collapse
Did you put asus M on internal and reboot ?
timbernot said:
Did you put asus M on internal and reboot ?
Click to expand...
Click to collapse
yes, multiple times I tried that, even with different M releases, every time the same error.
zakoo2 said:
yes, multiple times I tried that, even with different M releases, every time the same error.
Click to expand...
Click to collapse
I want you to check my downgrade thread in my signature "watch the video there too"
Not purposely to downgrade but to flow backwards and forwards through any specific firmware you like - ALL from SD card too - pay attention to how the files are written on SD card too
.
What you should first do
Is try a factory reset in .184LP
if that fails , you either dont have a fully functioning stock rom to update from or something is a miss .
***Warning*** , whatever you flashed in build.prop earlier may brick your phone when you reset within settings and i take NO responsibility for .
There really wasnt any need for what you attempted earlier
timbernot said:
I want you to check my downgrade thread in my signature "watch the video there too"
Not purposely to downgrade but to flow backwards and forwards through any specific firmware you like - ALL from SD card too - pay attention to how the files are written on SD card too
.
What you should first do
Is try a factory reset in .184LP
if that fails , you either dont have a fully functioning stock rom to update from or something is a miss .
***Warning*** , whatever you flashed in build.prop earlier may brick your phone when you reset within settings and i take NO responsibility for .
There really wasnt any need for what you attempted earlier
Click to expand...
Click to collapse
again - if I try to install any M release from SD card, it fails with the error msg in the OP. If I put an LP rom there, it works.
I can and also have before factory reset the phone without issues, so it's not at fault here. Also tried multiple versions of LP.
I haven't touched the build.prop, not sure why you would assume I did. And there was need for everything I attempted, as nothing before that worked.
zakoo2 said:
again - if I try to install any M release from SD card, it fails with the error msg in the OP. If I put an LP rom there, it works.
I can and also have before factory reset the phone without issues, so it's not at fault here. Also tried multiple versions of LP.
I haven't touched the build.prop, not sure why you would assume I did. And there was need for everything I attempted, as nothing before that worked.
Click to expand...
Click to collapse
Well everything should just work if you can factory reset within settings , can you reset now though ? this moment
timbernot said:
Well everything should just work if you can factory reset within settings , can you reset now though ? this moment
Click to expand...
Click to collapse
I did the first time you suggested. It works - the factory reset.
@zakoo2
I know your on 2.20.40.194 now
Can you put
UL-WW-2.20.40.196-user.zip.zip with the extra ( .zip ) on external sd and reboot ?
If you get success with that ^^
Try the same for this >
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551ML/UL-Z00A-WW-4.21.40.134-user.zip
night
timbernot said:
@zakoo2
I know your on 2.20.40.194 now
Can you put
UL-WW-2.20.40.196-user.zip.zip with the extra ( .zip ) on external sd and reboot ?
Click to expand...
Click to collapse
I put the WW-4.21.40.184-user.zip.zip on the sdcard and ... and it worked. I'm speechless...
Is this really the bug I spent 8 hours on and went to hell and back to fix?? I'm flipping out right now...
Regardless, thank you very much for your help, you probably saved me from at least 8 hours more frustration.
Have a nice evening, sir!
zakoo2 said:
I put the WW-4.21.40.184-user.zip.zip on the sdcard and ... and it worked. I'm speechless...
Is this really the bug I spent 8 hours on and went to hell and back to fix?? I'm flipping out right now...
Regardless, thank you very much for your help, you probably saved me from at least 8 hours more frustration.
Have a nice evening, sir!
Click to expand...
Click to collapse
Marvelous stuff
happy days
ps , if you ever use downgrade version 52.20.40.196 it relocks bootloader , just the same as upgrading to M
If you ever stuck in future just ask
I have been working on the sister models of this phone also. Provide feedback. Let people know how it is working. I run the att model. I saw no one was building for this model anymore either so i used some time and energy to build it so that it could be enjoyed by other fans of lineage 14.1. Hit the thanks button and enjoy. Dirty flash the updates not the initial flash of this rom but the updates to it. As of 9-3-18 i will be switching to Ubuntu 18.04 Bionic Beaver, that being said i do not know if i will have to change anything or do anything different to keep pushing these updates out but i will most definitely try to keep them coming.
4-10-18
https://www.androidfilehost.com/?fid=818070582850507325
4-13-18
https://www.androidfilehost.com/?fid=962187416754474764
4-18-18 rooted
https://www.androidfilehost.com/?fid=746010030569969739
4-26-18
https://www.androidfilehost.com/?fid=818070582850510217
5-3-18
https://www.androidfilehost.com/?fid=890278863836283433
5-13-18
https://www.androidfilehost.com/?fid=746163614322264306
5-20-18
https://www.androidfilehost.com/?fid=674106145207488031
5-31-18
https://www.androidfilehost.com/?fid=962339331458995668
7-28-18
https://www.androidfilehost.com/?fid=5862345805528060622
9-3-18
https://www.androidfilehost.com/?fid=1322778262903996428
10-07-18
https://www.androidfilehost.com/?fid=1322778262904022305
12-8-18
https://www.androidfilehost.com/?fid=11410963190603868846
12-16-18
https://www.androidfilehost.com/?fid=11410963190603876375
12-23-18
https://www.androidfilehost.com/?fid=11410963190603881247
2-24-19
https://www.androidfilehost.com/?fid=1395089523397901092
3-25-19
https://www.androidfilehost.com/?fid=1395089523397925386
5-6-19
http://download1647.mediafire.com/4...p6/lineage-14.1-20190507-UNOFFICIAL-d2spr.zip
10-13-19
https://www.androidfilehost.com/?fid=1899786940962607769
recommend clean flash as it was built on a different computer
setprop persist.lineage.nofool true in terminal emulator with root privs (type su first grant permission then setprop persist.lineage.nofool true) gets rid of persistant notification
Bluetooth dialtone when playing music fix
Settings > Battery > tap in 3-dot menu at top right tap on Battery optimisation. To show all apps and services here, select the ‘All apps’ options under the dropdown. Tap on both of the Bluetooth services and change them to Don't optimise.
Nice bro. I recently retired my s3, but I've seen a few ppl hunting down new builds. I'll direct them here for ya.
I tried to flash on my GS3 (Virgin Mobile) but received an error:
"Can't install this package on top of incompatible data. Please try another package or runa factory reset
Updater process ended with ERROR: 7"
Do I need to do factory reset?
My GS3's running on official Lineage OS (latest nightly 20171224), and with TWRP 3.2.1-0.
Tremoloworks said:
I tried to flash on my GS3 (Virgin Mobile) but received an error:
"Can't install this package on top of incompatible data. Please try another package or runa factory reset
Updater process ended with ERROR: 7"
Do I need to do factory reset?
My GS3's running on official Lineage OS (latest nightly 20171224), and with TWRP 3.2.1-0.
Click to expand...
Click to collapse
If you're running official lineage, you have to wipe everything. Especially system. You can't install an unofficial build on top of an official build. Signature mismatch, among other things.
Wipe data, system, cache, and dalvik/art cache. In other words, clean flash.
Tremoloworks said:
I tried to flash on my GS3 (Virgin Mobile) but received an error:
"Can't install this package on top of incompatible data. Please try another package or runa factory reset
Updater process ended with ERROR: 7"
Do I need to do factory reset?
My GS3's running on official Lineage OS (latest nightly 20171224), and with TWRP 3.2.1-0.
Click to expand...
Click to collapse
Wipe data factory reset wipe cache and dalvik install zip install gapps and install update su zip. How is it working? I don't have the sprint version so I cannot test
madbat99 said:
If you're running official lineage, you have to wipe everything. Especially system. You can't install an unofficial build on top of an official build. Signature mismatch, among other things.
Wipe data, system, cache, and dalvik/art cache. In other words, clean flash.
Click to expand...
Click to collapse
Joker1716 said:
Wipe data factory reset wipe cache and dalvik install zip install gapps and install update su zip. How is it working? I don't have the sprint version so I cannot test
Click to expand...
Click to collapse
Thanks, I did factory reset and wipe system then flash, it's installed successfully. And it's working alright!
I'm about to upload the update in a few minutes
Machine glitched out. I had to start over. Update will be a while.
It's been a long day update on the way my apologies for the delay oh hey its pre rooted also.
update posted
Hey man thanks for the hard work. I tried installing the latest update and cellular network stopped functioning. Tried doing a hard reset for network settings. Is there anything I can do without reverting to a full flash? I am with Sprint.
If data isn't working now and was before the update you could dirty flash the previous rom with working data. You should keep a copy of all the apn information so it could be put in manually after an update behaves like that. A lot of problems people are having with the data is also caused by device profiles under setting not being set correctly, and i believe there is a code like *#*#4636#*#* into the dialer that takes you to the testing menu. I am limited on finding solutions for the sprint version because I only have the att version without a sim but I will help if I can.
update posted
Could not you compile for the D2refreshspr, SGS3 Triband?
Osorio1798 said:
Could not you compile for the D2refreshspr, SGS3 Triband?
Click to expand...
Click to collapse
I don't think the device tree is available anymore for it. Plus, the last time the common tree for refresh was made was quite a while back. ROMs have passed it by. Meaning there would be a lot of bug squashing and testing and tons of work. There was never an official build for that one (d2refreshspr) so there isn't much to go on.
So it's not just a sync and build like d2spr.
So my guess... Not likely. It's just not worth the hours of work, especially if one doesn't even own the device.
Unless you have the common tree modified for the triband?
Osorio1798 said:
Could not you compile for the D2refreshspr, SGS3 Triband?
Click to expand...
Click to collapse
I'm going to attempt it no promises I'll give it a few hours of my time
madbat99 said:
I don't think the device tree is available anymore for it. Plus, the last time the common tree for refresh was made was quite a while back. ROMs have passed it by. Meaning there would be a lot of bug squashing and testing and tons of work. There was never an official build for that one (d2refreshspr) so there isn't much to go on.
So it's not just a sync and build like d2spr.
So my guess... Not likely. It's just not worth the hours of work, especially if one doesn't even own the device.
Unless you have the common tree modified for the triband?
Click to expand...
Click to collapse
Most of the tree is already there with the d2 so it's not as much work as it may seem. I'm gonna see what I can't do with it.
Joker1716 said:
I'm going to attempt it no promises I'll give it a few hours of my time
Click to expand...
Click to collapse
But I'm not going to debug it you have the phone you can debug I cannot help in that regard whatsoever but I will try to at least build it
Osorio1798 said:
Could not you compile for the D2refreshspr, SGS3 Triband?
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...rom-lineage-14-1-d2refreshspr-5-7-18-t3786850
There it is.
@Osorio1798 hey bro, he built it.
Hello, guys. I just ran into an error I had never seen before while flashing a new firmware on my T320. After searching around, I found more people have reported it as well on many devices and I've tried most solutions, to no avail.
When installing a zip for a lineage 16 rom, I got an error 7 message, which implies a mismatch between the rom and the device being flashed. I'm sure they should be a match, so I proceeded with the most common solution (when you know it's a match), which is to remove the device-checking code from within the zip. That didn't work, I got a "invalid zip file format" error.
I haven't tried many different roms after this in order to exclude the possibility this being actually a incompatibility issue but I'm worried because, when first flashing, I wiped the device quite carelessly. I'm afraid I might have "over-wiped" something important. I have TWRP installed, version 3.1.1.0, and did the wiping using it's built in tools.
Is there something I should never wipe, risking breaking it beyond repair? Is there a special procedure to perform or option to choose when zipping the rom back after removing the device-checking code?
Thanks for any advice,
Horácio.
horaciosalles said:
Hello, guys. I just ran into an error I had never seen before while flashing a new firmware on my T320. After searching around, I found more people have reported it as well on many devices and I've tried most solutions, to no avail.
When installing a zip for a lineage 16 rom, I got an error 7 message, which implies a mismatch between the rom and the device being flashed. I'm sure they should be a match, so I proceeded with the most common solution (when you know it's a match), which is to remove the device-checking code from within the zip. That didn't work, I got a "invalid zip file format" error.
I haven't tried many different roms after this in order to exclude the possibility this being actually a incompatibility issue but I'm worried because, when first flashing, I wiped the device quite carelessly. I'm afraid I might have "over-wiped" something important. I have TWRP installed, version 3.1.1.0, and did the wiping using it's built in tools.
Is there something I should never wipe, risking breaking it beyond repair? Is there a special procedure to perform or option to choose when zipping the rom back after removing the device-checking code?
Thanks for any advice,
Horácio.
Click to expand...
Click to collapse
A Slimroms file just made it through, so it's not destroyed, it's a matter of compatibility, somehow.
update the TWRP to 3.3.1.0
I have the same problem with T320 and was using TWRP 3.3.1.0, lineage-16.0-20191211-UNOFFICIAL-mondrianwifi.zip . I was able to install RR-N-v5.8.10-20190128-mondrianwifi-Unofficial.zip.
Any idea why?
Thanks
thro14 said:
I have the same problem with T320 and was using TWRP 3.3.1.0, lineage-16.0-20191211-UNOFFICIAL-mondrianwifi.zip . I was able to install RR-N-v5.8.10-20190128-mondrianwifi-Unofficial.zip.
Any idea why?
Thanks[/Q]
I got it working now. I downloaded 16.0 again. In TWRP- Factory reset, Advance wipe-chose Dalvick, Data, System & Cache.
This time I did not "Format Data". Not sure which did it (download or not format data).. Hope it helps.
Click to expand...
Click to collapse
having this same problem says "this package is for mandrainwifi , this device is . "
Trevorlay said:
having this same problem says "this package is for mandrainwifi , this device is . "
Click to expand...
Click to collapse
Make sure you have the latest twrp. If it still doesn't work, you could try messing with wiping/not wiping.