Related
What are my options for root?
DELETE
Can my device be rooted with the super tool?
AntDeek said:
Can my device be rooted with the super tool?
Click to expand...
Click to collapse
Yes. I rooted my 5.1.1 and installed SlimLP 5.1.1 following the last two videos in this post. Very easy
Giorgi-geo said:
Yes. I rooted my 5.1.1 and installed SlimLP 5.1.1 following the last two videos in this post. Very easy
Click to expand...
Click to collapse
the tutorial does work to root device and install SlimLP rom... but I will say that the UI keeps crashing and make the device unusable for me at the moment. I've read that SlimLP is stable, so i guess i'm a little unlucky that I've encountered this problem. I'm going to restore the device to stock and do it all over again. Anyway, just a word of warning!
DrewFerg11 said:
the tutorial does work to root device and install SlimLP rom... but I will say that the UI keeps crashing and make the device unusable for me at the moment. I've read that SlimLP is stable, so i guess i'm a little unlucky that I've encountered this problem. I'm going to restore the device to stock and do it all over again. Anyway, just a word of warning!
Click to expand...
Click to collapse
You did a clean flash, right? Wipe dalvik cache, cache, data and system.
Are you using Layers? They don't play well with Fire's screen. In fact the dev mentioned discontinuing Layers support. Anyone on 5.1.1 should definitely never use Layers.
I've been on SlimLP since it was released (I upgrade to each new version as it comes out). No crashes at all.
blueberry.sky said:
You did a clean flash, right? Wipe dalvik cache, cache, data and system.
Are you using Layers? They don't play well with Fire's screen. In fact the dev mentioned discontinuing Layers support. Anyone on 5.1.1 should definitely never use Layers.
I've been on SlimLP since it was released (I upgrade to each new version as it comes out). No crashes at all.
Click to expand...
Click to collapse
Yep, I did a clean install, wiped, and stayed away from layers (never used it before anyways). The 'System UI' constantly crashed and therefore made it impossible to do anything, besides restart the device. I was changing the Date/Date Style configurations in Settings.
Settings -> Interface -> Status Bar -> Clock and Date
Messing with the Date Style and Position, and then an alert appeared saying the UI crashed. I was able to restore my device to stock 5.1.1, re-root, and re-flash SlimLP. So far so good.... Whats weird is after the fresh re-flash I did mess with those same settings again, and the UI did crash again. Unlike last time where it would then crash constantly making it unusable, it crashed to the lock screen and then has been fine since (knock on wood). I've been using my device for about an hour now, haven't touched those settings, and everything seems to be fine for the moment :fingers-crossed:.
Can anyone tell me what´s the difference if i get a device with 5.0.1 or with 5.1.1 from amazon? Will the root or flashing of custom rom be somehow more difficult or unable?
If i get a 5.1.1 device, will i have something not working, while it would be working if i would get a 5.0.1 device?
With 5.1.1 you can't load twrp recovery to flash custom roms. Only way to currently flash roms in 5.1.1 is via FlashFire. This is far from ideal. SlimLP seems to work ok via FlashFire but there are reports that you can't flash RR or CM12.1 at the moment. And if your rom gets into a bootloop, you need to start over. Reinstall stock OS > root > install FlashFire > wipe & flash rom.
Currently 5.1.1 devices aren't as capable at flashing custom roms, rooting is simple to the end user on either now.
5.1.1 can't use the tethered twrp and thus far can't use Flashfire to install CM, though has had some success at going to SlimLp and RR roms.
Pond-life said:
Currently 5.1.1 devices aren't as capable at flashing custom roms, rooting is simple to the end user on either now.
5.1.1 can't use the tethered twrp and thus far can't use Flashfire to install CM, though has had some success at going to SlimLp and RR roms.
Click to expand...
Click to collapse
You can now flash CM on 5.1.1 devices. See this post: http://forum.xda-developers.com/showpost.php?p=64456287&postcount=969
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.
Hello,
i need ur help and advice.
since two days i dont have Access to "google play services", since i did an Update for the custom rom i had. (Victara, NIGHTLY CynogenMod or something)
So now my question is what posibilitys i have.
Can i get the Original Rom again? is it posible to have it Rooted while on Original Rom?
I have Bootloader unlocked via the Motorola page.
If i have to go with another Custom Rom, which one should i choose?
Kind regards
push pls
Bedii said:
push pls
Click to expand...
Click to collapse
Here are the full factory firmwares if you need to go back to stock:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Which Gapps did you use? You might have the wrong versions for your ROM.
Delta Gapps:
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Open Gapps:
http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
You should probably clean flash your ROM, and the latest Gapps (make sure you flash MarshMallow Gapps on a MarshMallow ROM).
Gus Ghanem said:
Here are the full factory firmwares if you need to go back to stock:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Which Gapps did you use? You might have the wrong versions for your ROM.
Delta Gapps:
http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Open Gapps:
http://forum.xda-developers.com/android/software/pa-gapps-continuation-t3098071
You should probably clean flash your ROM, and the latest Gapps (make sure you flash MarshMallow Gapps on a MarshMallow ROM).
Click to expand...
Click to collapse
I did use the Standard gapps. the one that said "take this if u are not sure which version u need"
i Installed a new ROM. but it drains a lot of my Batterie... dont know why.
Also i cant really root it. Everytime i try to Update SuperSU# it fails.
Can u tell me a good ROM i could use? or can i go to original somehow while having my Phone rooted?
Bedii said:
I did use the Standard gapps. the one that said "take this if u are not sure which version u need"
i Installed a new ROM. but it drains a lot of my Batterie... dont know why.
Also i cant really root it. Everytime i try to Update SuperSU# it fails.
Can u tell me a good ROM i could use? or can i go to original somehow while having my Phone rooted?
Click to expand...
Click to collapse
If you go back to stock factory firmware, you will lose root, but I'm sure there are ways to root it, but I've never done it on stock, so I don't know what works.
But, CM based ROMs should already have root built-in, under Developer Options, Root Access for Apps and ADB.
I prefer CyanogenMod because it is always actively being developed and updated, and is well supported.
Right now CyanPop looks like a good one, although I've never tried it (should already have root)
http://forum.xda-developers.com/moto-x-2014/development/rom-cyanpop-v4-5-t3277786
Actually that is the version that i have. I installed that and Gappa "ARM" 6.0. Dont know what i choose in the last section anymore.
Since i installed it i have the problem that the Batterie gets empty pretty fast.. and also i get Errors like "Couldnt load E-mail services" or something like that.
Also i cant update SuperSU#, update always fails
I want to clean install it again, not sure tho what gapps i should use.
Gus Ghanem said:
If you go back to stock factory firmware, you will lose root, but I'm sure there are ways to root it, but I've never done it on stock, so I don't know what works.
But, CM based ROMs should already have root built-in, under Developer Options, Root Access for Apps and ADB.
I prefer CyanogenMod because it is always actively being developed and updated, and is well supported.
Right now CyanPop looks like a good one, although I've never tried it (should already have root)
http://forum.xda-developers.com/moto-x-2014/development/rom-cyanpop-v4-5-t3277786
Click to expand...
Click to collapse
Can u help me with that last post?
Bedii said:
Can u help me with that last post?
Click to expand...
Click to collapse
I'm not sure what you would like to do.
There's a new version of TWRP (3.0.0) for Moto X 2014 Victara, you should flash that using fastboot in bootloader mode.
https://dl.twrp.me/victara/
If you want to start over clean, to flash a ROM and Gapps:
THIS WILL WIPE EVERYTHING!
Boot into Recovery, and tap Wipe, then Advanced, then select:
Dalvik/ART cache
System
Data
Cache
Then swipe to wipe them.
Copy over the ROM and Gapps zip files from your computer to your internal storage, if you haven't already.
Tap Install and flash the ROM, then tap clear cache/dalvik
Tap Install again and flash Gapps, then clear cache/dalvik
Reboot system and don't install supersu
Gus Ghanem said:
I'm not sure what you would like to do.
There's a new version of TWRP (3.0.0) for Moto X 2014 Victara, you should flash that using fastboot in bootloader mode.
https://dl.twrp.me/victara/
If you want to start over clean, to flash a ROM and Gapps:
THIS WILL WIPE EVERYTHING!
Boot into Recovery, and tap Wipe, then Advanced, then select:
Dalvik/ART cache
System
Data
Cache
Then swipe to wipe them.
Copy over the ROM and Gapps zip files from your computer to your internal storage, if you haven't already.
Tap Install and flash the ROM, then tap clear cache/dalvik
Tap Install again and flash Gapps, then clear cache/dalvik
Reboot system and don't install supersu
Click to expand...
Click to collapse
i already wiped everything last time, thats why i want to do it again to be clean.
what u said here:
"There's a new version of TWRP (3.0.0) for Moto X 2014 Victara, you should flash that using fastboot in bootloader mode."
is not nessesary if i want the clean install, right?
But i still dont know which Gapps i should get. I get Errors in my Current ROM, and i think its because i choose the wrong Gapps.
Also, the TWRP 3.0.0 u recommended, is it a stable Rom?
Bedii said:
i already wiped everything last time, thats why i want to do it again to be clean.
what u said here:
"There's a new version of TWRP (3.0.0) for Moto X 2014 Victara, you should flash that using fastboot in bootloader mode."
is not nessesary if i want the clean install, right?
But i still dont know which Gapps i should get. I get Errors in my Current ROM, and i think its because i choose the wrong Gapps.
Also, the TWRP 3.0.0 u recommended, is it a stable Rom?
Click to expand...
Click to collapse
TWRP is a custom recovery not a ROM, it allows you to flash ROMs and Gapps.
Right now, the only Gapps that are being constantly updated are Open Gapps and Delta Gapps, they both support MarshMallow, and don't have any serious issues. I use Delta Gapps with CM because they allow you to flash only the apps you want, or replace some of the CM stock apps, if you prefer the Google versions.
Here are the different Open Gapps packages, and the apps they contain:
https://github.com/opengapps/opengapps/wiki/Package-Comparison
If your ROM is MarshMallow then use the Delta Gapps under MarshMallow.
DO NOT MIX GAPPS, use either Delta Gapps, OR Open Gapps, but not both.
Gus Ghanem said:
TWRP is a custom recovery not a ROM, it allows you to flash ROMs and Gapps.
Right now, the only Gapps that are being constantly updated are Open Gapps and Delta Gapps, they both support MarshMallow, and don't have any serious issues. I use Delta Gapps with CM because they allow you to flash only the apps you want, or replace some of the CM stock apps, if you prefer the Google versions.
Here are the different Open Gapps packages, and the apps they contain:
https://github.com/opengapps/opengapps/wiki/Package-Comparison
If your ROM is MarshMallow then use the Delta Gapps under MarshMallow.
DO NOT MIX GAPPS, use either Delta Gapps, OR Open Gapps, but not both.
Click to expand...
Click to collapse
Hey,
i need ur help again.. sry.
I downloaded this now
http://forum.xda-developers.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858
Is this a good, stable version?
Can u link me to the Gapps that i need? i cant figure out what im doing wrong...
Bedii said:
Hey,
i need ur help again.. sry.
I downloaded this now
http://forum.xda-developers.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858
Is this a good, stable version?
Can u link me to the Gapps that i need? i cant figure out what im doing wrong...
Click to expand...
Click to collapse
That looks like stock factory firmware, you don't need Gapps for it. You only flash Gapps with custom ROMs, because they don't include the Google Play Store and Services (Google doesn't allow it). Which model and region is your phone?
Gus Ghanem said:
That looks like stock factory firmware, you don't need Gapps for it. You only flash Gapps with custom ROMs, because they don't include the Google Play Store and Services (Google doesn't allow it). Which model and region is your phone?
Click to expand...
Click to collapse
Serialnumber is TA99300WN5.
Dont know what region the phone is from, im from GER.
U said its a stock recovery, does that mean root is not possible?
Do a clean install of your ROM (cyanpop--which tells you clearly not to install SuperSU) with full wipes as per the ROM instructions. Add 'Open Gapps arm 6.0 full'. Follow the instructions.
Or
Read the various guides in Tony Stark's sticky thread for installing the stock ROM (if you're in Germany then it'll be for an xt1092*) and rooting a stock ROM, make sure you understand them, and then do as they say.
Gus has given you several very straightforward and helpful answers and you need to do some real brainwork to make sure you understand what you're doing. I'm sure you'll manage it and learn from it, as we all have.
* you have to check the model of your phone.
kboya said:
Do a clean install of your ROM (cyanpop--which tells you clearly not to install SuperSU) with full wipes as per the ROM instructions. Add 'Open Gapps arm 6.0 full'. Follow the instructions.
Or
Read the various guides in Tony Stark's sticky thread for installing the stock ROM (if you're in Germany then it'll be for an xt1092*) and rooting a stock ROM, make sure you understand them, and then do as they say.
Gus has given you several very straightforward and helpful answers and you need to do some real brainwork to make sure you understand what you're doing. I'm sure you'll manage it and learn from it, as we all have.
* you have to check the model of your phone.
Click to expand...
Click to collapse
Okay, i did 3 things now..
First i installed this: http://forum.xda-developers.com/moto-x-2014/general/install-image-marshmallow-6-0-xt-1097-t3266858
i just followed that tutorial. But when i started my phone, i couldnt open the most apps, they just closed with the Erro message e.g "Whatsapp closed".
Then i tried to install the stock ROM. i was on Tony Starks sticky, and just followed the tutorial. But after flashing the stock ROM into my device, i couldnt reboot it. It just booted into fastboot.
So i tried the Method one again and installed the ROM again. now i can open APP's, but cant get a mobile connection... so no calls and no SMS
I dont know whats wrong, always diffrent errors with diffrent trys...
You are having problems because you seem to be flashing the stock image for an xt1097 onto what I guess is an xt1092.
I was clear about checking phone models and being sure you understood the different instructions and guides.
Start again and make sure you have the right things. I assume you made no nandroid backups to return to.
kboya said:
You are having problems because you seem to be flashing the stock image for an xt1097 onto what I guess is an xt1092.
I was clear about checking phone models and being sure you understood the different instructions and guides.
Start again and make sure you have the right things. I assume you made no nandroid backups to return to.
Click to expand...
Click to collapse
With the new ROM i can see that i have XT1092. The old one just showed me "Moto x 2014".
This is the one i have atm: http://forum.xda-developers.com/moto-x-2014/development/rom-cyanogenmod-13-t3243768
There was no saying that it is for specific models, so my guess was that it works for all.
I tried to get the Stock Image via this tutorial : http://techbeasts.com/2014/11/11/how-to-restore-moto-x-2014-to-stock-firmware/#
Since i tried that i cant get a mobile connection with various ROM's, just WLAN workds atm. Also on that tutorial i searched if it was restricted to a Model that i dont have, but there seem to be none...
its not that i wasnt looking if it works for my model..
aI dont have a nandroid back up too
Well okay, i downloaded the Android 4.4.4 from Motorolas original site for my Phone. unrootet and than flashed it on my Phone.
Now everything is working fine. I dont like this old version tho. How do i get OTA updates? shouldnt he tell me that updates are available?
Well done! You'll probably not get updates with an unlocked bootloader, but this German site might help: http://www.android-hilfe.de/thema/factory-images-ota-4-4-5-0-5-1-6-0-retdeall-xt1092.703838/
kboya said:
Well done! You'll probably not get updates with an unlocked bootloader, but this German site might help: http://www.android-hilfe.de/thema/factory-images-ota-4-4-5-0-5-1-6-0-retdeall-xt1092.703838/
Click to expand...
Click to collapse
Unlocking the bootloader does not effect getting updates.
Sent from my XT1095 using Tapatalk
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).
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Glendog1 said:
Hello,
I currently have the following:
Phone: OnePlus 3T A3003
Recovery: TWRP 3.1.1-x | blu_spark v37
Rom: RR-N-v5.8.3-20170603-oneplus3-official
I installed all of this after hours of googling last year. I now want to upgrade but I am not finding many helping guides are upgrading (rather than installing from scratch).
I downloaded RR-O-v6.1.0-20180627-oneplus3-official and tried to install it via TWRP (after backing up and wiping some stuff). But I got the an error stating something along the lines of "this rom is for oneplus3/t" and your device is "". Googling lead me to believe I needed to update my recovery. So I downloaded TWRP-3.2.2-0oneplus3.img but I really have no idea if I should be installing this? Last time I installed the blu_spark variant but I have no idea why.
Anyway, my question is:
Given the above, please could someone give me a laymans guide to updating my Custom ROM and which things I should install and in which order.
Thank you!
Click to expand...
Click to collapse
Clean Flash:
1) Latest Official TWRP (Can be done from within old TWRP)
2) Reboot Recovery to new TWRP
3) Wipe
4) Latest Firmware (OB29)
5) ROM
6) OpenGapps Arm64 8.1 Nano or Pico
7) Root Optional
Don't forget to Nandroid first, and it might be a good idea to remove any security measures on your current setup too. (Fingerprint/Pin/Pattern)
Queue up the zips for Firmware/ROM/Gapps and flash in that order together.
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Glendog1 said:
Thank you,
Some follow up questions:
* What should I be wiping during step 3.
* Should I install TWRP 3.2.2, does it matter that I currently have the blu_spark variant? (I don't even know what blu_spark means)
* I am just reading about firmware. I am assuming I need OB29 to work with RR-O-v6.1.0-20180627-oneplus3-official? Is that a simple process?
Click to expand...
Click to collapse
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
DirkGently said:
Just follow the steps. The TWRP you download will be an .img file. In the TWRP Install menu press the button for Image to flash the .img file.
For step 3, from the Wipe menu just swipe to wipe.
Click to expand...
Click to collapse
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Glendog1 said:
Thank you, final question. I note you advised to remove security. I changed from 'Pin' to 'None' and gave me a warning about removing it which I agreed to. It still states my phone is encrypted however, and I still need to enter my PIN when restarting. Will this be a problem?
Thank you,
Click to expand...
Click to collapse
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
DirkGently said:
I believe removing your stored fingerprints removes the boot PIN. Don't stress if you can't do this, it's just an additional precaution.
Click to expand...
Click to collapse
Pin/password and fingerprints are two different things. Fingerprints are just a convenient method of authenticating. Removing them does nothing for the actual security with is pin/password.
The reason for removing the lock screen password before taking a backup is that if you install a new ROM and set a password and then restore your older backup, you can't get past the lock screen password. So, remove the password before taking the backup and then you can restore it later and set a new password.
I find the better option is to not remove the password and then, if you need to restore the backup after having changed passwords, you can delete the passwords of the restored backup in TWRP from Advanced>Terminal with these commands:
Code:
cd /data/system
rm -f gatekeeper.* locksettings.*
Changing the pin/password to none doesn't wipe out the on-boot password. However, when setting up a new password and selecting to not set an on-boot password will remove the current on-boot password for some users, but not for others (it doesn't for me).
Sent from my OnePlus 3T using XDA Labs
Thanks guys.
I followed your instructions @DirkGently and it worked a charm.
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Thanks,
Glendog1 said:
What you recommend for rooting the device and is as simple as flashing a zip file like above?
Click to expand...
Click to collapse
Magisk
Glendog1 said:
Also, is the recovery on a separate partition? So if I mess around flashing firmware/rom/apps and mess up, I'll always be able to boot into the recovery partition and flash again?
Click to expand...
Click to collapse
Yes and yes, but firmware may be tricky and messing up too much may render phone unusable. Messing with ROMs is fine though.
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Glendog1 said:
I have already installed a custom rom, will this be an issue?
Click to expand...
Click to collapse
That's ok of you asking questions, that's what this forum is about.
You should have got no problems if you're running a kernel shipped with custom ROM. Custom kernel is like EX, Mady's Xtended, Franco and so on.
Glendog1 said:
Thanks for the reply.
I note that on the Magisk page it states:
"If you plan to flash a custom kernel, flash it AFTER installing Magisk"
I have already installed a custom rom, will this be an issue?
Sorry for so many question. I get really nervous about this stuff!
Click to expand...
Click to collapse
You don't need to worry about Kernel stuff. RR already includes Caesium Kernel. You chose a good ROM by the way!
Here's a little information about Firmware. The OP3 and OP3T have unified builds. This means that in some cases the same Custom ROM can be used on both. There is some device specific software though so this has to be separated out and treated as independent from the ROM. This is what we refer to as Firmware. When Oneplus release new builds they include the updated Firmware in their Official ROM. If you look at the Firmware thread i linked you to, you'll see that kamilmirza takes the Firmware from the Official OOS builds and makes them available as flashable .zip files that we can use on Custom ROMs. Bookmark his Thread for future use.
There is no need to stress about always being on the latest Firmware for your Custom ROM, just ensure it is the Firmware intended for your device. The version you flashed earlier will probably do you for a while. At the same time, if you do always want to be on the latest, there's no reason not to. There's little to be gained by it though. If you're following the RR thread you'll probably see people mention it when the ROM requires a new Firmware. Again, don't stress about it.
As far as flashing Firmware, you can do it any time. You can do it before flashing an updated build of your ROM, or on it's own in a separate visit to Recovery. It's not particular either way. I would stick with the Open Beta Firmware, which people usually abbreviate to OBXX, i.e OB29. Just remember what you flashed so that you know which version you are using.
Now that you're rocking your Custom ROM you're next questions will be about updating it. This can be done easily and safely by Dirty Flashing. I've done dozens of updated builds since my last clean flash and everything has gone perfectly every single time.
Dirty Flash:
1) Download new ROM build (and Firmware if applicable) to Internal Storage.
2) Boot into Recovery
3) Nandroid Backup
4) From Install Menu, flash Firmware (if applicable), and ROM.
5) Wipe Dalvik & Cache when prompted. (BillGoss will tell you it's not necessary. It doesn't hurt either way, so up to you!)
6) Reboot phone.
For a Dirty Flash, you do not need to use the 'Wipe' Menu at all.
I always take a new Nandroid before flashing an updated build. I will have had a whole week on the previous build so i know i'm not backing up a bug and the backup will be as recent as possible if a problem occurs. Once i boot back into the phone i delete the old Backup. The new one is there if i need it. Always have that one recent Backup, just in case. As i've said, RR is great and i'm yet to run into a problem with it. From now on you can Dirty Flash the updated weekly builds with little to worry about and with a Backup to fall back to if anything goes wrong.
I don't mention Magisk because i don't use it, and i don't advise others use it. Unless you need Root access for something specific, don't bother. Half the threads on XDA are about problems with Magisk. Avoid the added complication if you can. Now this statement will trigger the Magisk fans, but nobody has ever had a bug or failure with something that they did not flash in the first place. Keep it as simple as possible.