Related
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?
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Linx78 said:
i was running cm12 with no probs on htc one m9
then by mistake i installed the new update and it was cm13.
after the phone rebooted i got google play error saying i need to update google play.
downloaded the latest gapps6 but when trying to install in recovery mode from internal phone memory (as sd card for some reason is not mounted anymore) it gives an error E: FAILED TO MAP
is there a way to go back to cm12 or fix these faults on cm13?
Click to expand...
Click to collapse
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
dladz said:
Install gapps immediately after rom installation, do not allow a full boot..
There is also an issue with the SD and the way it's read, this is an android M issue.
Click to expand...
Click to collapse
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Linx78 said:
that's the problem, i didn't realize it's cm13 (thought it's another cm12 nightly) till rebooted the phone...
now it won't allow me to install anything at all giving that e: map... error.
Click to expand...
Click to collapse
Ask in the forum mate, where u got the rom from.
dladz said:
Ask in the forum mate, where u got the rom from.
Click to expand...
Click to collapse
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Linx78 said:
i'm really sorry if i posted in wrong place... (please direct me in the wright way)
the rom itself was downloaded automaticaly on the phone as an update and i pressed the option update, so the phone rebooted itself into recovery installed it and then i rebooted the phone myself not even looking what was installed... the rest you already know...
Click to expand...
Click to collapse
You will have to have downloaded the rom from xda surely? The Rom you downloaded initially I assume was cm 12.1, then you updated to cm 13, that thread is in the original android development section, I'm sure you can find your way there as you've been there before. The thread is now called cm13 I believe..
Also make sure you're on the latest TWRP recovery, I'm guessing you are but it'd be nice to be sure.
Might also be worth downloading G apps from the cm13 thread then rebooting to recovery, flashing the rom again and installing gapps whilst once complete, don't allow a reboot.
Wiping cache and dalvic will be fine, don't perform a full wipe just incase you can't install the rom again.
If you get stuck, you can push files to your phone using recovery and the push command..
Not 100% but I think storage works via TWRP, could be wrong about that and I've not tested it with cm13.
Either way you have a way back..
---------- Post added at 06:55 PM ---------- Previous post was at 06:55 PM ----------
Install from your internal memory not your SD card. Get the necessary files on your internal memory instead.
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Linx78 said:
thank you very much, will try there.
yes, you are right, got rom from xda and i'm on latest recovery, but no matter what i do, even after wiping cashe still getting the bloody
E: failed to map file
Installation aborted
Click to expand...
Click to collapse
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Linx78 said:
i can't post anything there... not enough posts...
did i brick my phone now? or is there a way to clean install? recovery mode won't work...
Click to expand...
Click to collapse
No it'a not bricked..
Are you installing from internal or external memory?
Connect your phone to your computer and go to recovery, then mount storage in recovery, copy G apps to internal memory.
Make more posts in here, i think you need ten
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
dladz said:
Sorted. Avoid it til it'a fixed like me unless you want to be a Guinea pig.
Click to expand...
Click to collapse
sorry, i did copy everything onto internall memory, still no luck...
also the cm13 updated the recovery aswell, and i can't even do a factory reset...
please is there a way to go back to cm12.1?
once again i can't install anything in recovery mode.
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
that wasn't my post, some else posted here too...
i'm stuck, adb won't install anything too
LLegion said:
I tried it and found Android 6.0 is having issues with my PC, not recognizing my SD Card, not even the Internal SD !!! :S I know it is pure Super fast but i cant live without connecting my phone to PC.
Also I tried to flas Gapps just after installing MM (not reboot and with Aroma) and the installation freezes, so im stuck with pure Android no Google Apps, so I did return to Lollipop VipeOne 3.5.0 with a full backup made with TWRP.
Click to expand...
Click to collapse
i wanted to ask how to go back to cm12.1 from cm13?
i don't have any backups, nor my recovery is allowing to install anything as per post above...
adb method is not working either, just says waiting for the device when rebooted to download and nothing else.
also my firmware is 2.10..... is that an issue?
dladz said:
Hang on you just said you reverted back to viper?
You should be able to install things now?
At this point I'm not too sure mate.. Sorry, perhaps install recovery again, might not be the right thing to do though, ask in the viper thread, you might have enough posts now.
Click to expand...
Click to collapse
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Linx78 said:
i also tried install recovery through adb, didn't work, just says waiting for the device and nothing happens
Click to expand...
Click to collapse
Nah i'm on 2.10 that's fine.
At this point it appear to be an issue with CM13 rather than anything else, I'm not up to speed with Android 6.0 so I think it would be best if you asked in the thread, you've made over 10 posts now so i'm assuming you can post there.
See what they say, let them know what you've done so far, someone will have either been through it or will know what to do.
Sorry i can't be of more help mate.
PS: Just thought of something, if you have connectivity to your computer / laptop, update your recovery if you haven't already, chances are it's an issue with cm13 but might be worth a try.
I had similar problem - Google Services crashing after unintentional update to CM13.
I realized that I need to install new GApps to fix the issue but GApps installation in recovery was constantly failing.
I used to have some recovery there, I even don't know which one, but during update to CM13 the recovery has been changed to some kind of CM recovery.
After installing TPRW recovery (ir forked for me from the TPRW Manager App from play store) I was able to install Nano GApps.
It solved the issue with Google Services crashing, now I got some Wizard crashing. The issue with crashing wizard is solved by going to privacy setting and allowing the wizard all rights. Later I realized that many other applications were crashing on start as well. I solved it for each of them by uninstalling and installing from Play Store again.
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message "android.process.media has stopped".
I've used the following installation procedure:
1. Starting with the stock Samsung Android v4.4.2, I used Odin v3.1.2, to root the device, by installing
CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md
2. I used Odin to install picassowifi TWRP v2.8.7.0. I didn't use the latest v3.1.1-0, because it reboots the
device while making Nandroid backups. Available here
https://eu.dl.twrp.me/picassowifi/
3. I copied several versions of Lineage OS amd Gapps (see below) to the device's SD card
4. I used TWRP to wipe the cache/dalvic/data/system each time, using the Wipe->Advanced option
5. I used TWRP to install the Lineage OS amd Gapps as an atomic operation on the device
6. After installation, I rebooted from TWRP:
- without rooting: I get the message "Google Services Framework keeps stopping"
- with rooting, by installing SuperSU: The device enters into a boot loop, displaying the sliding Lineage logo
I followed the same procedure to update my Samsung Galaxy S4 Mini, and it worked flawlessly.
I tried the following Lineage OS versions, available here:
https://download.exynos5420.com/LineageOS-14.1/n2awifi/
lineage-14.1-20170506-UNOFFICIAL-n2awifi.zip
lineage-14.1-20170715-UNOFFICIAL-n2awifi.zip
I also tried the folowing Lineage OS versions, available here:
https://download.lineageos.org/n2awifi
lineage-14.1-20170608-nightly-n2awifi-signed.zip
lineage-14.1-20170713-nightly-n2awifi-signed.zip
I tried the following versions of Gapps, available here (32-bit arm, Android v7.1, stock variant):
http://opengapps.org/?api=7.1&variant=stock
open_gapps-arm-7.1-stock-20170505.ziip
open_gapps-arm-7.1-stock-20170711
I tried several combinations of these 2 packages. With all the combinations I tried, I got the results summarised above.
This post suggests installing Lineage OS alone without Gapps, and then install Webview Implementation, if not installed:
http://www.lineageosrom.com/2017/02/how-to-fix-google-play-services-error.html
When I tried this and reboot, I get the messages "android.process.media" has stopped, followed by the message "clock has stopped". When I click away these messages, and click on next on the Lineage OS screen, the device enters into a boot loop displaying the sliding Lineage logo. This agrees with the Lineage recommendation, that both packages need to be installed at the same time:
https://wiki.lineageos.org/devices/n2awifi/install
Can anyone please help? I really don't want to go back to Android v4.4.2 on my SM-T520.
Hello so to get rid of the error I would suggest downloading samsung kies 1 not 2 or 3 and flashing completely back to stock then try rooting and flashing rom should get rid of system errors and force closes. Kies will ask you for model and serial number. Serial is found on back of the tablet. As another suggestion I would try resurrection remix by cosmox. It is very stable everything works. I just posted a link in that thread with a link to download samsung kies for a 64 bit windows and other relevant files if you need. Let me know if you need any other help. Also closer inspection of your links. I think for sm-t520 u should be using twrp Picassowifi, not n2awifi so idk if that will work or not. Not sure about that part though because they may have made it work on Picasso.
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
paintball,
I've found a solution, that I thought I'd post here in case anyone else has the same problem.
I wiped the cache/dalvic after each step of the installation:
Wipe-> Advanced -> wipe cache / data / dalvic / system
Install -> flash Lineage -> wipe cache/dalvic
Install -> flash Gapps -> wipe cache/dalvic
Reboot -> don't install SuRoot
I got a Music closed error during the first boot, which hasn't appeared since.
Afterwards, I used Odin to install CF-Auto-Root. The device rebooted twice after this step, but now appears to be OK.
A final problem I had was that it couldn't find my wifi SSID. I solved this by setting wifi region to Europe.
ppmoore said:
Thanks paintball.
I confirm that I had used picassowifi TWRP. I've edited the original post to indicate this.
I've also tried what you suggested - I reinstalled the original stock Samsung firmware using Odin, and used TWRP to again install Lineage. Same result, still displaying the same Google Service errors.
I'll look at the Resurrection remix.
Paul
Click to expand...
Click to collapse
I suggested using Samsung kies which I'm positive works, not Odin, but I'm glad you got it fixed.
ppmoore said:
Hello,
[Sorry: can't edit title]
I've been trying to install Lineage 14.1 on my Samsung Galaxy Tab Pro (SM-T520), and haven't been successful.
I keep getting the message "Google Services Framework keeps stopping", sometimes alternating with the message
<snip>
Click to expand...
Click to collapse
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
I have tried several permutations of Lineage OS nightlies along with various flavors of OpenGApps, with and without root, wiping cache/dalvik/data/system, wiping only some, wiping none.
I also cannot restore the backup of the running LOS that I had up (I did take a backup before going back to the original setup). When I try, I get the same results as above--as if I had backed-up an un-instantiated setup.
Any thoughts?
eckster said:
I'm having a similar issue. Mine differs in the following ways.
I was able to successfully install and run LineageOS with OpenGApps full, but reverted to a nandroid backup because I needed some information from the original install. Since then, I have been unable to get past the initial couple of screens for setting things up--and this with the constant "Google Services Framework keeps stopping" error.
I have tried most of the "fixes" I've found but to no avail. I notice that, (1) when I go to the drop-down menu and setup WiFi, as soon as the device connects to the Internet, I go to the Lineage bootup animation and get stuck there. If I hard boot from there, I can get in up to the point where I connect to the Internet (not just router, but actually get through to the Internet) and (2) I cannot enable Developer options--when I try, no matter how many times I click on the Build number, I get no indication of the options being enabled.
Any thoughts?
Click to expand...
Click to collapse
Hi Eckster,
I have exactly the same problem on a LG G2 with LOS 14.1. It ran July version perfectly but I didn't make a backup and now I'm stuck. Did you ever manage to fix this?
Thanks,
Kevin
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
how did you format the partitions? I can only find "format data".. thx
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
:thumbsup: I was on lineage 14, all was well. I tried an old stock rom NK2, that was fine. I tried to restore lineage backup via twrp, got this problem with the framework crashing. No amount of re-flashing twrp nor lineage, gapps, modem, bootloader, etc nothing worked; always crashed right after boot to lock screen. Finally twrp "format data" - yes. Now lineage boots to welcome, no crash; restore backup - after copying it back to internal - and all is good.
I'm glad it works but why is it needed in this case to remake the filesystem on data - does it work by removing some bad file or does it work by rebuilding the ext4 and security context? this is with latest twrp twrp-3.2.1-0-klte.
Hi,
don't know if you solved it eventually, or maybe helpful for other people with the same problem. I had the same problem, spent 6 days digging around on the internet why the framework keeps stopping and crashing.
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Say whatever you need to whatever deity you prefer and wait for the tablet to boot.
I hope to be of some help to other people having the same problem
Code:
Sent from my SM-S920L using Tapatalk
grammar
detlef25 said:
Managed to solve it. I formatted all partitions _including_ data (which means you'll also loose all zips you wanted to install so make sure that adb is working). Then rebooted into the recovery. Installed as usual, worked.
Click to expand...
Click to collapse
Was going crazy trying to figure out why LineageOS was encountering so many ANRs. The first time I flashed Lineage it worked beautifully but every time after that it just went nuts. This fixed it for me, thanks dude!
Note to others who may end up here, after formating data I had to install a stock ROM, then wipe and install Lineage. Lineage wouldn't install due to Updater process ended with ERROR: 7 which was because there was some bit of information that was on the data partition that showed the install script that the phone was actually a Note II. Formating data blows that info away but installing stock puts it back on.
LievenVanh said:
I eventually found out that:
- TWRP 3.0.2.0 is WAY more stable than 3.1.1.0 (which never succeeded in installing gapps without crashing)
- Wiping system, data, dalvik recovery and internal storage is not the only thing that needs to be done. You also need to use the 'FORMAT DATA" button (everything will be wiped from your tablet, so, as always, backups )
- After that, install the lineageOS binary, after the installation, wipe dalvik/cache, go back and install the appropriate GApps package, wipe dalvik/cache and reboot
Click to expand...
Click to collapse
Coming into this thread after a few hours of struggle with an old GS4 I can say that this method instantly worked for me as well.
Thanks!
Thanks for the help to resolve my issue of installation. Do you have a solution for Zoom , where my audio (cannot hear other speakers) and video is missing. Did enable access for Mic, Camera etc in App permission.
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
hamudistan said:
Look at this thread: https://forum.xda-developers.com/ga...-t520-unofficial-lineage-14-1-t3538770/page86 -- last two posts
Click to expand...
Click to collapse
That solution didn't work. My Zoom audio still not working.
Hello,
It all began that i just wanted to restart my Oneplus3 unlocked with lineage 15.
But then back in Lineage15 i wasnt able to use my pin anymore + it restarted after few seconds...
Afterwards i ended up in a lineage bootloop.
Ok, then i thought then i do a fresh flash with new lineage 16.
I tried to flash but it said i need to install new modem firmware for Lineage16.
I downdloaded the new 9.0.5 modem + firmware and flashed it from here : https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
Then i tried to flash LOS16 again but it failed due to some errors on unable to mount some partitions (cache , system, etc).
So i thought i need to wipe or reformat them, as some people suggested to switch from ext4 to fat and back to reinit the partition.
I did this for at least system and internal storage. ( i learned that it was a dumb idea )
Afterwards i was not able to push anything anymore through MTP in TWRP, but i was still able to sideload or push images via adb.
Afterwards i tried to flash LOS16 or LOS15 via TWRP again but it always ends up to a "unable to mount /system (invalid argument" error at some point of the installation.
I thought: Okey maybe i go back to stock as i messed up the internal file system somehow, and go back to LOS afterwards.
So i flashed the stock recovery for nougat which i got from here: https://www.****************/2017/0...th-latest-oxygen-os-firmware-complete-unroot/
Then i tried to flash various stock Oxygen roms with the stock recovery, by using wipe + system reset + adb sideload:
4.02, 4.51, 5.08, 9.0.5
4.02 and 9.0.5 didnt run until the end.
Flashing 5.08 works but ends up in a black screen when starting it.
Flashing 4.51 works but when i start it i run into a bootloop ( 2 Dots circuling forever )
I also tried to use the 4.51 version to flash LOS again but it did not work out
I just tried again to flash 4.51 but it also didnt work out anymore. :\
So, what do you think i could do to get a working OS on my system again?
Did i do something on the installation of LOS or Oxygen ?
Can i use a backup from a friends Oneplus3_T to get a working system partition / full OS again?
Should i unbrick the phone by using one of various guides to go back to fully stock? I am kind of afraid of this, as some people describe some final brick in the threads which may be caused by modem firmware problems (Sahara issue). https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/ or https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Thank you so much, i kind of getting mad about it
@julledd
Backup from 3T seems like a bad idea.
You may have a hardware issue.
Your best bet is to use one of the tools available in the various unbrick guides. If one doesn't work, try another.
Best of luck!
Hi thx for your help!
i tried different unbrick tools (9.0.5 / 3.1.2 / 4.0.5) and after several attempts i get it flashed to the phone. But in the end it still ends up in a bootloop, either at the android logo or the circuling dots. Via Sideload i am also not able to flash a new OS. It always breaks somewhen >50%.
In very rare cases i am then able to go to the OS, but when i go to "About Phone" to unlock it for TWRP, it freezes before showing anything. I guess there is internally something broken which forbids it to show the internal state of the phone. Every boot is different, and i cannot see any system in this failure of my phone.
Do you have any more hint?
I am already at a point where i want to exchange the main PCB.. Is this possible for the Oneplus3? Can i also exchange it with a Oneplus3T PCB?
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.