Database Develop

can I flash CM12.1 over SLIMLP via FlashFire ?

Hi .. since the latest update of CM12.1 supports flashing from FireOS 5.1.1 via FlashFire.. is it possible to flash it from SlimLP via flashfire? knowing that I flashed it over FireOS 5.1.1 with wiping everything via FlashFire except internal SD card.... thanks in advance

Yes, it should work fine.
Wipe dalvik cache, cache, data and system. Then flash the rom.

blueberry.sky said:
Yes, it should work fine.
Wipe dalvik cache, cache, data and system. Then flash the rom.
Click to expand...
Click to collapse
Can anyone confirm this worked out ok on amazon fire? When you say "Then flash the rom." you mean the xposed zip? Or are you talking about a fresh install of a rom with xposed bundled into it?

KLit75 said:
Can anyone confirm this worked out ok on amazon fire? When you say "Then flash the rom." you mean the xposed zip? Or are you talking about a fresh install of a rom with xposed bundled into it?
Click to expand...
Click to collapse
Since this was originally posted, many people have now used flashfire with each of the roms. Search around to see confirmation that it works.
Rom = CM12.1 . Since the OP was asking about CM12.1.
How did you read anything about xposed here? The original question made zero mention of xposed.

blueberry.sky said:
Since this was originally posted, many people have now used flashfire with each of the roms. Search around to see confirmation that it works.
Rom = CM12.1 . Since the OP was asking about CM12.1.
How did you read anything about xposed here? The original question made zero mention of xposed.
Click to expand...
Click to collapse
Youre correct. Not sure how i posted here. Remember i began a title asking about xposed and a thread popped up that mustve seemed relevant. My best guess, i got distracted and posted in the wrong place.
-I've tried xposed with flasfire on 12.1, ressurection, and fire nexus. All worked fine. Since then i got 5.0.1 so I can try mods with more confidence.

Dirty flash possible, when going from SlimLP to CM12.1
blueberry.sky said:
Yes, it should work fine.
Wipe dalvik cache, cache, data and system. Then flash the rom.
Click to expand...
Click to collapse
I'd like to change from SlimLP to CM12.1.
(Reason is: Anki Overdrive does not work 100% with SlimLP. The app can be startet and works fine until the track should be scanned. Unfortunately the cars do not start scanning after pushing "Scan Track". Now I'm going to give CM12.1 a shot as Anki should work with Fire-Tablets. At the moment I can't use it as host.).
Probably I'll use TWRP to flash the CM12.1 ROM (SuperSU and Gapps). My Question is:
Can I keep data, and just wipe system, cache and dalvik before flashing CM12.1?

oliman99 said:
I'd like to change from SlimLP to CM12.1.
(Reason is: Anki Overdrive does not work 100% with SlimLP. The app can be startet and works fine until the track should be scanned. Unfortunately the cars do not start scanning after pushing "Scan Track". Now I'm going to give CM12.1 a shot as Anki should work with Fire-Tablets. At the moment I can't use it as host.).
Probably I'll use TWRP to flash the CM12.1 ROM (SuperSU and Gapps). My Question is:
Can I keep data, and just wipe system, cache and dalvik before flashing CM12.1?
Click to expand...
Click to collapse
- I don't recommend the use of FlashFire with CM-12.1 until issue with random soft-bricks and/or loss of access to stock recovery partition are better understood
- If you have TWRP option then layering CM over SlimLP should present no issues.
- Whether data partition contents can be preserved is unknown. In theory should be ok; make a backup first.
- If you decide to risk FlashFire recommend sideloading FireOS as an intermediary step

5.1.1 cannot use TWRP. Only option is FlashFire in order to install custom ROMs.
For what I know, the issue with CM12 bricking the device is because people did not place the "wipe" in the top of the order. Read and follow the instructions careful.
But the answers to all your questions and more are at: http://forum.xda-developers.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441

shabuboy said:
5.1.1 cannot use TWRP. Only option is FlashFire in order to install custom ROMs.
For what I know, the issue with CM12 bricking the device is because people did not place the "wipe" in the top of the order. Read and follow the instructions careful.
But the answers to all your questions and more are at: http://forum.xda-developers.com/amazon-fire/help/help-thread-question-noob-friendly-t3205441
Click to expand...
Click to collapse
Position of wipe in the operations sequence is certainly important (for any ROM) but not the magic bullet. See: http://forum.xda-developers.com/amazon-fire/help/amazon-fire-stuck-cm-logo-t3347629/post66102825

Xposed on SlimLP?

Has anyone managed to get it working? I just tried to install via FlashFire and wound up getting an animation loop on the SlimLP boot logo. I applied the 5.1.1 firmware through the "apply update through adb" option in the recovery, can anyone confirm Xposed even working on SlimLP?

I'd like to know this also. Have not tried it yet.

I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.

Thanks! Think I found an easier solution than installing Xposed for what zip needed though (just needed YouTube to play in the background). That will come in handy if I want it later for any reason though.

Yes, xposed works fine. Big thanks to csolanol!
You must use the xposed compatible SlimLP 0.13 build + the correct xposed version (see the howto xposed thread in Fire General forum).

Anybody had success with getting .013 build running successfully with eXposed.. I've tried the ' Slim-ford-5.1.1.beta.0.13-UNOFFICIAL-20151221-0949.zip ' build from root junkies tutorial i think in section 4 or something if i remember vaguely, but with no luck... The Flash just proceeds as expected then reboots while opening/loading .zip.. But the standard release 'non-eXposed' runs without any problems.

Need to include more information. You're flashing with twrp or flashfire? If you used flashfire, what are you coming from? Stock 5.1.1 or another rom.
Do you mean after flashing the rom your Fire will not boot / start up?
I flashed SlimLP 0.13 via twrp without a problem on two different Fires. Xposed runs fine.

thanks for your reply, I'm flashing with flashFire from a r00ted fresh clean stock fire-os 5.1.1 on Amazon Fire 7" 5th Gen. i execute flash after selecting wipe all partitions except sd and then load .zip via ota then push button to commence flash, it proceeds to blank screen and then flashing screen and begins to attempt rom install i see rom info and 'char pic' of rom then it self terminates and reboots to existing r00ted fire-os, i do this exact same process with the rom not currently supporting Xposed from rootjunkie download site, and everything completes successfully spending a slightly longer period at the rom install/upload stage completing successfully with slimlp running nice... minus a few almost irrelevant bugs i noticed...
Twrp via adb doesn't work with 5.1.1 right? only works on 5.0.1&2? .. unless im mistaken.. any ideas?

Yep, we can't use twrp on 5.1.1.
So you select to wipe, system data, 3rd party apps, dalvik cache, cache partition, correct? I'm afraid I have no suggestions.

exactly that's correct , then i select rom, then i select gapps. then press flash button and it halts on the next screen as it begins to flash rom and quits to a reboot .. everything still unchanged as it was.. i have tried this process installing from stock os fire 5.1.1 & slimlp 5.1.1 with unsuccessful results.. but hey at least i have a SlimLp non-Xposed edition installed that beats Fire-BS#"*t any day. guess I'll have to wait for a new build to be released. bummer.
---------- Post added at 12:32 ---------- Previous post was at 12:25 ----------
in the future i guess more concentration is needed on the 5.1.1 Xposed edition skimlp rom to be flashed from 5.1.1 stock, for the true android custom eXperience .. i have also seen a fw roll back to 5.0.1or5.0.2 is not possible from any 5.1.1 os. never mind.

What I find is odd is that you've selected to wipe first. Flashfire should be wiping before trying & failing to flash SlimLP 0.13, leaving your Fire wiped & unable to boot back into the stock FireOS (you would then need to restore FireOS 5.1.1 via adb sideload in the amazon recovery). FlashFire is in beta & I think it's currently a bit buggy.

Bib_x said:
I think you have to use the slim-rom version from the 4th post. The original slim rom is not running with xposed beacause of some ART optimizations... Read the slim rom thread. There you can find something about it.
Click to expand...
Click to collapse
Sorry, I feel I joined the conversation mid-way but, which SlimROM thread are you talking about?

There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.

Bib_x said:
There is only one SlimLP-Thread in android development section.
Newest SLim-Version for Fire is without Art-Optimizations, so you can use xposed now with the latest slimlp 0.14.
With the older SlimLP 2.3 there was Art-Optimization inside - so there no xposed was working.
Click to expand...
Click to collapse
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge

marcolorenzo said:
Thanks for the reply. I actually don't have a Fire and came across this thread after a lot of googling. I'm running SlimLP 0.12 I think on a Note Edge. I absolutely love this ROM. Seriously, I was close to selling the phone for scraps until I flashed this ROM. Now I think I will never buy another phone unless there is SlimROM support already
Anyway, I've been looking everywhere for a solution to get Xposed running. I found people saying that SELinux needs to be set to Permissive which I have done but still no luck. Are you saying that it's impossible with SlimLP versions before 0.14? Somehow, I doubt that would come to the Note Edge
Click to expand...
Click to collapse
Maybe try looking in the Note Edge forum not the Amazon Fire one?

Pond-life said:
Maybe try looking in the Note Edge forum not the Amazon Fire one?
Click to expand...
Click to collapse
Maybe you shouldn't presume, with no information, that people are imbeciles? Don't you think I would've have done that at the beginning? Anyway, I may be wrong but I presumed that whether or not Xposed worked was more dependent on the ROM and not the phone? So if people here, who are discussing Xposed on SlimROM can help me, why not ask?

Bib_x is correct, i confirm Xposed working on slimlp build 0.14 beautifully for Fire 7 5th Gen.. be wary of modules you install other wise you'll have to start everything from scratch when you reach a boot hang because of a not yet compatible module.. you have no custom recovery remember so no quick fix, can always fresh install everything lol., which is good training lol.

Has anybody seen this "incompatible data" error when installing rom using Flashfire?

Has anybody seen this "incompatible data" error when installing rom using Flashfire?
I recently purchased a fire 7 which came with fireOS 5.1.4 on it which I downgraded to 5.1.2 (verified version in settings). I used KingRoot to get root and have verified that apps require root are working. I installed Flashfire and everything appears to work fine until I select flash. I can see it does the wipes fine, but when it tries to install cyanogenmod I receive an error that says "can't install package on top of incompatible data."
Has anybody seen this issue before in flashfire? I've been looking for some time now and I seem to be alone.
Things I have tried so far (which have not changed the error is see when flashfire is flashing CM and GAPPS):
Reset device to factory defaults (in settings and through recovery; loaded into 5.1.2 like it was new however it still had root)
Sideloaded Fireos 5.1.2 again and rerooted using kingroot.
Used a different version of CM.
Used different versions of Flashfire (0.5 and 0.51)
Went through the process start to finish again using the Supertool
I've been stuck on this for the last 5 hours... Any hints would be appreciated.
Update: I've had success at flashing the Fire Nexus ROM by ggow (http://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/). I have tried to flash the latest CM and the stable release from November without success. I suppose I might be satisfied with the nexus rom. It seems sexy enough.

LazyTurtle said:
I recently purchased a fire 7 which came with fireOS 5.1.4 on it which I downgraded to 5.1.2 (verified version in settings). I used KingRoot to get root and have verified that apps require root are working. I installed Flashfire and everything appears to work fine until I select flash. I can see it does the wipes fine, but when it tries to install cyanogenmod I receive an error that says "can't install package on top of incompatible data."
Has anybody seen this issue before in flashfire? I've been looking for some time now and I seem to be alone.
Things I have tried so far (which have not changed the error is see when flashfire is flashing CM and GAPPS):
Reset device to factory defaults (in settings and through recovery; loaded into 5.1.2 like it was new however it still had root)
Sideloaded Fireos 5.1.2 again and rerooted using kingroot.
Used a different version of CM.
Used different versions of Flashfire (0.5 and 0.51)
Went through the process start to finish again using the Supertool
I've been stuck on this for the last 5 hours... Any hints would be appreciated.
Update: I've had success at flashing the Fire Nexus ROM by ggow (http://forum.xda-developers.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/). I have tried to flash the latest CM and the stable release from November without success. I suppose I might be satisfied with the nexus rom. It seems sexy enough.
Click to expand...
Click to collapse
Quick post to verify you are including a wipe action in FlashFire 0.51 with System, User Data, Dalvik and Cache ticked positioned *above* the rom flash action.

Same problem
Davey126 said:
Quick post to verify you are including a wipe action in FlashFire 0.51 with System, User Data, Dalvik and Cache ticked positioned *above* the rom flash action.
Click to expand...
Click to collapse
I am not OP, but I am having a similar problem after a failed ROM installation. I can verify that when I tried the steps listed, it did not work. The Nexus build, while quite nice, doesn't support loading apps onto the SD card yet, so it's not a long term solution for me.

SimonHova said:
I am not OP, but I am having a similar problem after a failed ROM installation. I can verify that when I tried the steps listed, it did not work. The Nexus build, while quite nice, doesn't support loading apps onto the SD card yet, so it's not a long term solution for me.
Click to expand...
Click to collapse
Lollipop based support for installing/migrating apps to SD cards is sketchy regardless of rom. Recommend using a tool that leverages 'symbolic links' which is both reliable and robust. Link2SD is one example.

I am having this exact same problem.
I've successfully downgraded from 5.1.3 to 5.1.2.
ROOT
Now using fireflash I am using the newest CM12 build and Google apps but get the same problem.
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Very frustrating....
Havent tried the Nexus rom yet, but any suggestions as the best alternative to CM as i also do not like the fireOS at all.

ratbrain said:
Can't install this package on top of incompatible data. Please try another package or run a factory reset.
Click to expand...
Click to collapse
Did you add a wipe action (system/data/dalvik/cache) *above* the installation action in FlashFire? Pretty important going to/from FireOS.

Davey126 said:
Did you add a wipe action (system/data/dalvik/cache) *above* the installation action in FlashFire? Pretty important going to/from FireOS.
Click to expand...
Click to collapse
Yes. made sure to drag wipe action to top of the queue.
THis puts my fire into boot loop/ amazon logo stuck status

ratbrain said:
Yes. made sure to drag wipe action to top of the queue.
THis puts my fire into boot loop/ amazon logo stuck status
Click to expand...
Click to collapse
Obviously CM is not flashing correctly. You will need to reload FireOS 5.1.2 (or 5.3.1) via stock recovery to recover your device.
CM flash failures are not common suggesting a procedural or image integrity problem. Be sure to verify CM file md5 on the device. Use the SuperTool to root and perform other house keeping tasks. Grab the latest FlashFire build from APKMirror or another trusted source. Accept all defaults...some early guidance advised flipping various FF options which is no longer needed. You'll also want to flash GAaps (nano) concurrent with ROM; adding later is problematic. No need for SuperSU; can add later.

Davey126 said:
Obviously CM is not flashing correctly. You will need to reload FireOS 5.1.2 (or 5.3.1) via stock recovery to recover your device.
CM flash failures are not common suggesting a procedural or image integrity problem. Be sure to verify CM file md5 on the device. Use the SuperTool to root and perform other house keeping tasks. Grab the latest FlashFire build from APKMirror or another trusted source. Accept all defaults...some early guidance advised flipping various FF options which is no longer needed. You'll also want to flash GAaps (nano) concurrent with ROM; adding later is problematic. No need for SuperSU; can add later.
Click to expand...
Click to collapse
I've confirmed the files.
Using latest CM 12 ROM
Using FlashFire 0.53
Only difference Ive used is PICO Gapps.
All after restoring back to 5.1.2
Then ROOT with SuperTool
Note: per the OP, I am also successful in loading the NEXUS ROM. However, the CM Rom always ends up with the error.

ratbrain said:
I've confirmed the files.
Using latest CM 12 ROM
Using FlashFire 0.53
Only difference Ive used is PICO Gapps.
All after restoring back to 5.1.2
Then ROOT with SuperTool
Note: per the OP, I am also successful in loading the NEXUS ROM. However, the CM Rom always ends up with the error.
Click to expand...
Click to collapse
If you're happy with Nexus stick with it. It is my favorite rom for Amazon tablets and the one I prefer as my daily driver. I run CM on this device (5th gen Fire) as it is secondary and contains some nice usability enhancements that take time to apply on Nexus.
As for CM have to see what shakes out over time. Others are not reporting issues; send 3-4 reports of successful installations in the past 24 hours. At least one was on a 5.1.2 base (bootloader/kernel).

DualBootPatcher

I was looking into multi-boot on my xt1060. Not important, just a project. Looking around, I saw a pretty cool project here on XDA called DualBootPatcher and started digging around into whether or not it would work for our device. Maybe not even the xt1060, but any variant of the device. Turns out, as of January 8th 2016, our device (all) is supported by DualBootPatcher: https://github.com/hankching/DualBootPatcher-1/wiki/[Devices]-Motorola and https://forum.xda-developers.com/android/development/list-support-devices-dualbootpatcher-t3278937
Anyone used it? I have an unlocked bootloader and I'm running 5.1, however my device has never been OTA'd past 4.4.2. I think it'd be pretty nifty to dual boot into a non-stock ROM for testing or just to give it a try before you fully commit. I'm also kind of impatient and make weekly backups, so I plan on giving it a shot tonight and will report back how it goes.

Tried
I did try this app on Kitkat 4.4.4. I installed Xperience 7.1 and Gapps Nano, I installed it on data partition, but the phone won't turn on, it only vibrates 5 times.
What I did to restore is installing the utilities.zip from TWRP and changing back to my primary rom.

Sidd24 said:
I did try this app on Kitkat 4.4.4. I installed Xperience 7.1 and Gapps Nano, I installed it on data partition, but the phone won't turn on, it only vibrates 5 times.
What I did to restore is installing the utilities.zip from TWRP and changing back to my primary rom.
Click to expand...
Click to collapse
Same result. Damn. I might keep digging into it if I can find the time.

Problem with lockup / display not turning on across various roms, rooted droid

I successfully rooted my droid (that came with lollipop), using this guide
https://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684
installed twrp backed up the stock OS and installed resurrection remix lollipop rom. I did not install any different modems or radios as I planned to stay on lollipop.
Everything worked great yet after a day or two the display/phone would appear to lock up. I can press power, the display doesn't come on and when (usually) moving the the volume up/down I do hear sounds. Sometimes at this point it will reboot by itself, other times I have to reboot it.
When it comes up it goes through the android is upgrading thing, and sometimes works fine after, sometimes not, regardless eventually this problem repeats.
Thinking it was perhaps RR I tried straight Cyanogenmod, and eventually the rooted stock OS, both have this same problem.
I've tried using it with very minimal installed in the way of apps, same issue.
I've tried saving the log to SD to peer at later, but going through it I don't really see anything obvious to show what the problem is.
I"m wondering if there's a problem with the phone itself (it's a refurb) and am considering unrooting it and returning it.
Anyone seen this or thoughts on what might be the issue?
p.s.
if you happen to have a good link handy to an unrooting guide you might shoot it my way thanks.
thanks in advance!

What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
There are ways to grab logs after a reboot, but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.

thanks for the reply
ChazzMatt said:
What versions of the other ROMs did you use? Lollipop also, or Marshmallow? Nougat? For rooted stock ROM did you upgrade to Marshmallow? None of the Lollipop ROMs are supported anymore, so hard to answer for those.
Click to expand...
Click to collapse
I tried the last released CM lollipop snapshot, as well as the last nightly.
For RR it was last released, "ROM OS Version: 5.1.x Lollipop"
ChazzMatt said:
There are ways to grab logs after a reboot,
Click to expand...
Click to collapse
Yeh I've been saving it to the SD so I can view it after a reboot, I've looked at 4 or 5 of them after the problem occurred and at least to me nothing really stood out
ChazzMatt said:
but here's another suggestion...
I use Auto Reboot app (needs root) to schedule a reboot my phone every day while I'm asleep.
This seems to keep the cobwebs cleared out, so the phone runs better. I know you want to find the issue, but maybe it's an accumulation of apps not releasing RAM orb something. This might help prevent that.
Click to expand...
Click to collapse
Yeh I expect it might periodically need a reboot but if it's just unpredictiably locking up or rebooting on its own it's not very usable.
I think I'm just going to have to try to unroot and return, maybe I'll go with a LG V20 as I don't want to have pay to re-root another one of these and possibly have same issue. Also the whole pay to have some app do something secret to my phone does leave me a bit uneasy.
Kind of a bummer as I'm actually pretty impressed with this device, fast, good battery, takes nice photos, only drawbacks for me are no removable SD and lack of LED notification, but I was willing to live without those given how good everything else was.
thanks

Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Android Version: 7.1.2
Current Rom: AOKP
Kernel: 3.10.107-Stock-bhb27-nougat-kerneL

MrN00b said:
Same here,
I tried with different Roms 7.X, still blocking and display not turning on.
I'd appreciate some help.
Thanks!
Click to expand...
Click to collapse
FWIW and in case it helps you or someone else, I seem to have fixed mine finally, here's what I did.
First I installed latest twrp (mod 4) https://androidfilehost.com/?w=files&flid=39562 (there's a thread on this twrp if you want tor read on it). That in itself didn't fix the issue but did finally let me format and got rid of an 'mkfs.f2fs: invalid option -- r, ERROR=1' type error I used to get.
I installed this stock zip from twrp as described in thread:
https://forum.xda-developers.com/droid-turbo/development/rom-su4tl-49-100-stock-t3390041
It would never actually boot it would shut my phone off not long after showing the boot screen, and I'm not sure if doing that was necessary or not.
Taking some suggestions from here:
https://forum.xda-developers.com/droid-turbo/help/help-request-custom-rom-phone-unlocked-t3767070
I dug up the last official CM 13 snapshot:
https://www.google.com/search?q=cm-13.0-20161221-SNAPSHOT-ZNH5YAO3Y5-quark.zip
sha1: 9a219dd487c27e51b0c5c4922812838f394099c5
Wipe and installed with no gapps and voilà it would boot consistently. Without reinstalling I tried installing pico gapps and it would still boot though it took maybe 15 mins initially.
I want Nougat so I wiped and installed lineage-14.1-20180612-UNOFFICIAL-quark.zip from https://forum.xda-developers.com/moto-maxx/development/rom-t3494646 again no gapps and it also booted fine, whereas previously it would hang on booting. Without reinstalling ROM I tried installing opengapps nano and it would just hang.
I could then no longer get it to boot again, so I reinstalled CM13 no gapps, which booted fine, wipe and install lineage-14.1-20180612-UNOFFICIAL-quark.zip no gapps, and now it boots fine though currently it's taking a while.
I should perhaps note I took twrp backups inbetween steps whenever I had a working boot, (ex before installing gapps), but once the phone went back to hanging on boot, those restores didn't help. Only reflashing CM13 seemed to clear things up.
My ultimate goal is a LOS ish Nougat/Oreo ROM with no gapps using microg, and running tmobile, I'll see what I end up with.