Database Develop

[Q] root problem

my moto g 2014 titan_retaildsds in not compatible with chainfire auto root zip titan_retaildsds and its not rooting please can anyone help me????:crying:

syash01 said:
my moto g 2014 titan_retaildsds in not compatible with chainfire auto root zip titan_retaildsds and its not rooting please can anyone help me????:crying:
Click to expand...
Click to collapse
1. Follow Motorola's instructions to
unlock the bootlader.
2. Flash TWRP 2.8.5 with fastboot.
3. Flash latest SuperSU with TWRP.
4. Enjoy

syash01 said:
my moto g 2014 titan_retaildsds in not compatible with chainfire auto root zip titan_retaildsds and its not rooting please can anyone help me????:crying:
Click to expand...
Click to collapse
Well, flashing with TWRP only worked for me on KitKat, it stopped working for 5.02, but what I did was used auto root for Lollipop, I was told this is the only supported method for this device on Lollipop, are you still on 4.4.4 or did you receive the OTA 5.02?
And as you are trying Auto Root, are you sure you are choosing the correct one for your device, it took me an hour or so to ensure that it was the correct one, I analysed all the tags and compared them with my version, there was a few for my device so I had to make sure everything matched.
This is the one I used, it works but best check if it fits your device: download(dot)chainfire(dot)eu/603/CF-Root/CF-Auto-Root/CF-Auto-Root-titanumtsds-titanretaildsds-xt1068.zip
You need to add the http protocol and replace (dot) with .
It won't let me post links.

TchTlk said:
Well, flashing with TWRP only worked for me on KitKat, it stopped working for 5.02
Click to expand...
Click to collapse
How so?

doppelhelix said:
How so?
Click to expand...
Click to collapse
After the flash was successful with TWRP, I launched the SU app and it said something along the lines of 'SuperUser is not installed correctly' I used the exact same method as I did on KitKat, I then learned that this is no longer the way of rooting the device on Lollipop, I installed TWRP for nothing.

After rooting via TWRP 2.8.5.0 try to change the mode with SELinux Mode Changer: https://play.google.com/store/apps/details?id=com.mrbimc.selinux&hl=de

TchTlk said:
I then learned that this is no longer the way of rooting the device on Lollipop, I installed TWRP for nothing.
Click to expand...
Click to collapse
?
There was and is only one correct way to install SuperSU regardless of lollipop or kitkat
· Flash TWRP 2.8.5 with fastboot.
· Flash latest SuperSU with TWRP.
Wolfcity said:
change the mode with SELinux Mode Changer:
Click to expand...
Click to collapse
Chainfire himself is strictly against changing SELinux. That's why he had to invest so much time and even bought a Moto G (2014) so he can fix any error resulting of enforced SELinux. SuperSU 2.45 was the result of his investigation into the XT106x.

doppelhelix said:
?
There was and is only one correct way to install SuperSU regardless of lollipop or kitkat
CR Auto Root is the only method that worked for me since the lollipop update, I tried the SU zip with TWRP, i t was successful, however the SU app just displayed an error message saying that if wasn't installed correctly.
I did exactly the same thing as before, the only thing that changed was the new update.
Click to expand...
Click to collapse

TchTlk said:
.
I did exactly the same thing as before, the only thing that changed was the new update.
Click to expand...
Click to collapse
Maybe your twrp version was outdated?

doppelhelix said:
?
There was and is only one correct way to install SuperSU regardless of lollipop or kitkat
· Flash TWRP 2.8.5 with fastboot.
· Flash latest SuperSU with TWRP.
Chainfire himself is strictly against changing SELinux. That's why he had to invest so much time and even bought a Moto G (2014) so he can fix any error resulting of enforced SELinux. SuperSU 2.45 was the result of his investigation into the XT106x.
Click to expand...
Click to collapse
Thx for that info. Didn´t heard that and if Chainfire said so it´s better to follow that.
And btt,flashing TWRP 2.8.4.0 or 2.8.5.0 with latest superSU (2.46 at the moment) should work with 5.0.2 without any other variations.

[RECOVERY][UNLOCKED BL] TWRP 3.5.0_9-1

Code:
/*
* I am not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* in the products you find here before flashing it!
* YOU are choosing to make these modifications.
*/
Prerequisites for Installation
- Must have an unlocked bootloader
Installation
- Use Flashify OR:
- Go into fastboot mode
- Install using the following command where <recovery-image> is the relevant file for your device
Code:
fastboot flash recovery <recovery-image>
*** Please do NOT create any mirrors ***
Downloads
All TWRP Builds for Apollo and Thor
Source Code
- Kernel Source
XDA:DevDB Information
TWRP, Tool/Utility for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
Version Information
Status: Stable
Stable Release Date: 2016-02-25

Many thank to your great work.
Can Flash it via Flashtify ?
Sent from my LG-D855 using XDA Free mobile app

NeverSmile said:
Many thank to your great work.
Can Flash it via Flashtify ?
Sent from my LG-D855 using XDA Free mobile app
Click to expand...
Click to collapse
Yes you can, as long as your bootloader is unlocked

I assume it's ok to flash this via TWRP 2.8.7.0 (to the recovery Partition of course)?

Cl4ncy said:
I assume it's ok to flash this via TWRP 2.8.7.0 (to the recovery Partition of course)?
Click to expand...
Click to collapse
Should be fine
Sent from my Nexus 6 using Tapatalk

ggow said:
Should be fine
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked fine.
The screenshot function still creates a 0 bytes file in Pictures\Screenshots though, which can be deleted via TWRP only.

Question:
First run after installation there was a page regarding the option to mount System as read-only with a checkbox whether that page should not re-appear. I did NOT enable (i.e. left it disabled) that checkbox, but I've not seen that page again (regardless if I re-booted into recovery via the extended shutdown menu, or by pressing Vol+&Power at start). Is that option somewhere in the settings? And is it to be considered a bug that the page did not re-appear?

Cl4ncy said:
Question:
First run after installation there was a page regarding the option to mount System as read-only with a checkbox whether that page should not re-appear. I did NOT enable (i.e. left it disabled) that checkbox, but I've not seen that page again (regardless if I re-booted into recovery via the extended shutdown menu, or by pressing Vol+&Power at start). Is that option somewhere in the settings? And is it to be considered a bug that the page did not re-appear?
Click to expand...
Click to collapse
It's not a bug, usually appears on first run only and should not impact TWRP's ongoing use.

NeverSmile said:
Many thank to your great work.
Can Flash it via Flashtify ?
Click to expand...
Click to collapse
ggow said:
Yes you can, as long as your bootloader is unlocked
Click to expand...
Click to collapse
Worked like a charm. Nice visual upgrade over 2.8.7.0. Summary of other changes here.

New Build is Up
- Dated 29 March 2016
- Fix slow performance especially when flashing open-gapps-6.x packages
- I would urge everyone to update their recovery partition before upgrading to future builds of CM-13.0

ggow said:
- Dated 29 March 2016
- Fix slow performance especially when flashing open-gapps-6.x packages
- I would urge everyone to update their recovery partition before upgrading to future builds of CM-13.0
Click to expand...
Click to collapse
Updated via Flashify on a pair of Thors; no issues.

Please help me. my hdx7 has locked bootloader. I made a mistake, flashed your TWRP3.0 .........Now, HDX7 cant work,cant connect computer ,cant in recovery.
only display "kindle fire". how can i repair it? plz.....

chaefei said:
Please help me. my hdx7 has locked bootloader. I made a mistake, flashed your TWRP3.0 .........Now, HDX7 cant work,cant connect computer ,cant in recovery.
only display "kindle fire". how can i repair it? plz.....
Click to expand...
Click to collapse
How did you attempt to flash TWRP (Safestrap, Flashify, FireFlash)? In the end it really doesn't matter. If your HDX won't progress past the gray Kindle Fire screen it is probably toast. Do you know what version of FireOS was last on the device (3.x, 4.x)?

Davey126 said:
How did you attempt to flash TWRP (Safestrap, Flashify, FireFlash)? In the end it really doesn't matter. If your HDX won't progress past the gray Kindle Fire screen it is probably toast. Do you know what version of FireOS was last on the device (3.x, 4.x)?
Click to expand...
Click to collapse
my hdx7 had been flashed twrp2.8, and flashed cm11. Today, I flashed cm12,but i found hdx7 cant work. So i think it maybe because twrp2.8 is old version.
i used twrp2.8 to flash new twrp3.0........

chaefei said:
my hdx7 had been flashed twrp2.8, and flashed cm11. Today, I flashed cm12,but i found hdx7 cant work. So i think it maybe because twrp2.8 is old version.
i used twrp2.8 to flash new twrp3.0........
Click to expand...
Click to collapse
You failed to read the documentation. CM12 also requires an unlocked bootloader as clearly stated in the OP. That's why it didn't flash with TWRP 2.8. There is no "maybe". Played with fire and got burned.
Since you had TWRP 2.8 installed the last version of FireOS was likely 3.1.x. There is an outside chance your device can be recovered following instructions in the following thread. Good luck.
http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197

Davey126 said:
You failed to read the documentation. CM12 also requires an unlocked bootloader as clearly stated in the OP. That's why it didn't flash with TWRP 2.8. There is no "maybe". Played with fire and got burned.
Since you had TWRP 2.8 installed the last version of FireOS was likely 3.1.x. There is an outside chance your device can be recovered following instructions in the following thread. Good luck.
http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197
Click to expand...
Click to collapse
thank you very much

chaefei said:
thank you very much
Click to expand...
Click to collapse
Before you try @Davey126's suggestion - assuming you're on Fire OS 3.1.x - you should just give the bootloader unlock a try. Zero risk, it either unlocks or fails.

Cl4ncy said:
Before you try @Davey126's suggestion - assuming you're on Fire OS 3.1.x - you should just give the bootloader unlock a try. Zero risk, it either unlocks or fails.
Click to expand...
Click to collapse
because my hdx7 is second-hand device，i don't know whether it is lock or not.
Before flashed twrp3.0 , it had been flashed twrp 2.8、 cm11. is it means unlock？

chaefei said:
because my hdx7 is second-hand device，i don't know whether it is lock or not.
Before flashed twrp3.0 , it had been flashed twrp 2.8、 cm11. is it means unlock？
Click to expand...
Click to collapse
Well, to be as clear as possible about this. You had the real TWRP installed, i.e. TWRP 2.8.7.0, NOT Safestrap based on TWRP?
If you had the real TWRP installed you were on Fire OS v3.1.x - v3.2.3.2, which are unlockable versions. Even with Safestrap v3.7x it could be worth a try to unlock.
Again: You can't mess up anything by trying. It either unlocks or fails. And you can try the one-click-solution. Be sure to grab the PDA drivers if you suffer from the good ol' device not found problem.

Cl4ncy said:
Well, to be as clear as possible about this. You had the real TWRP installed, i.e. TWRP 2.8.7.0, NOT Safestrap based on TWRP?
If you had the real TWRP installed you were on Fire OS v3.1.x - v3.2.3.2, which are unlockable versions. Even with Safestrap v3.7x it could be worth a try to unlock.
Again: You can't mess up anything by trying. It either unlocks or fails. And you can try the one-click-solution. Be sure to grab the PDA drivers if you suffer from the good ol' device not found problem.
Click to expand...
Click to collapse
thanks. i will try .
i want use fastboot method. But when i connect hdx to computer, the computer have nothing response.....

how to restore update capibilities

I inadvertently disabled ota updates via a root script the script says to restore update capability to flash update.bin provided my amazon's website, but I can't find this update.bin nor do I know how to flash it, can someone help me, I want to update to 5.1.2

MtDewFella said:
I inadvertently disabled ota updates via a root script the script says to restore update capability to flash update.bin provided my amazon's website, but I can't find this update.bin nor do I know how to flash it, can someone help me, I want to update to 5.1.2
Click to expand...
Click to collapse
http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

What version of FireOS do you have now? If it's 5.0.1 then you really do not want to update, at least not through normal means.
Does 5.1.2 bring anything useful?

I have version 5.1.1, I want version 5.1.2. I followed the link above and tried to sideload the update.bin but I get an error in adb.
Edit: Nobody Mentioned I had to be in recovery mode before issuing the adb sideload command, you guys shouldn't assume we all know these things. Anywho, I got the update to sideload.

MtDewFella said:
I have version 5.1.1, I want version 5.1.2. I followed the link above and tried to sideload the update.bin but I get an error in adb.
Edit: Nobody Mentioned I had to be in recovery mode before issuing the adb sideload command, you guys shouldn't assume we all know these things. Anywho, I got the update to sideload.
Click to expand...
Click to collapse
my directions are very clear about that
Sent from my KFFOWI using XDA Labs

MtDewFella said:
I have version 5.1.1, I want version 5.1.2. I followed the link above and tried to sideload the update.bin but I get an error in adb.
Edit: Nobody Mentioned I had to be in recovery mode before issuing the adb sideload command, you guys shouldn't assume we all know these things. Anywho, I got the update to sideload.
Click to expand...
Click to collapse
No assumptions - you missed the instruction. Recheck your sources.

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).

[Kindle/Fire/Ford] Lost SuperSU after installing Custom ROM

Hi,
I have a Fire 7" which originally had 5.3.1.0 OS. Rooted it with RootJunkys tools (KingFire, then Super SU)
Installed the Resurrection Remix Rom with Flashfire.
Yet, apparently i forgot to tick the option to preserve SuperSU.
And now i have the Custom ROM up and running, but i do not have Super SU any more.
Trying to run KingFire again - fails (ran it 5-6 times) - works until 25-30% and says "Root Failed, no strategy now"
Tried to upload and run SuperSU apk, but it says - it requires root.
What can i do in this case to get back root ?
Thanks. Vladimir

vlast3k said:
Hi,
I have a Fire 7" which originally had 5.3.1.0 OS. Rooted it with RootJunkys tools (KingFire, then Super SU)
Installed the Resurrection Remix Rom with Flashfire.
Yet, apparently i forgot to tick the option to preserve SuperSU.
And now i have the Custom ROM up and running, but i do not have Super SU any more.
Trying to run KingFire again - fails (ran it 5-6 times) - works until 25-30% and says "Root Failed, no strategy now"
Tried to upload and run SuperSU apk, but it says - it requires root.
What can i do in this case to get back root ?
Thanks. Vladimir
Click to expand...
Click to collapse
- reload FireOS 5.3.1.0 (no lower) using stock recovery menu
- you will need to root, block OTA, etc as if tablet was new ...
- if you opt for a custom ROM suggest going with CM 12.1 (robust, stable)
- regardless of choice be sure to follow instructions in ROM OP

Davey126 said:
- reload FireOS 5.3.1.0 (no lower) using stock recovery menu
- you will need to root, block OTA, etc as if tablet was new ...
- if you opt for a custom ROM suggest going with CM 12.1 (robust, stable)
- regardless of choice be sure to follow instructions in ROM OP
Click to expand...
Click to collapse
Thank you!. I was just wondering which of the roms to use best, but i will then stick to CM12.1

vlast3k said:
Thank you!. I was just wondering which of the roms to use best, but i will then stick to CM12.1
Click to expand...
Click to collapse
All custom ROMs for this device have their virtues. I am recommending CM 12.1 at present as it has a large user base (community support) and has proven stable through the most recent release. Nexus is also popular but is having issues with Google Play Services at the moment.