yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] zach61797:
if i do changes in settings and i send my device into a bootloop will having a back up work? can i just boot it into this recovery and restore?
[Fire Original Android Development] sd_shadow:
i haven't tested restore in twrp
[Fire Original Android Development] zach61797:
ok when you do please let me know thanks
[Fire Original Android Development] csolanol:
Yup, it's working ok. Make the backup to the sdcard. I don't think you have enough free space in the internal memory.
[Fire Original Android Development] zach61797:
ok and this will save me if i bootloop?
[Fire Original Android Development] sd_shadow:
yes, it should.
[Fire Original Android Development] zach61797:
ok thank you
[Fire Original Android Development] Diomorgan:
Sorry to bother, the TWRP is PERFECT even if I must run it with pc.

You say "install xposed framework", but which version?

Got a link to add to your list? Thank you!

Ok, sorry didn't searched deeply, I found this link on xda

http://xdaforums.com/amazon-fire/general/how-to-install-xposed-firmware-custom-t3239343 I think it should work, isn't it?

Ok again no, this should be for NON 2015 models, since it involve FlashFire tha we can't use :(
[Fire Original Android Development] Vlasp:
Actually, I wrote that guide, and I only have the Fire 2015. FlashFire is basically a root application that lets you install some Zip files through the app. Xposed in the post will work with either being flashed through the FlashFire app or TWRP. Good luck!
[Fire Original Android Development] Diomorgan:
Ooooops, didn't noticed.

I installe trought TWRP and rebooted, but now my fire says "installing more recent software", don't know if an update come out today, anyhow it it will broke my root I'll just try again rooting with TWRP and install the xposed you posted.

I only hope that amazon didn't found the root guide and applied a sort of security.

Willl let you know.

Thank you very much. :o
[Fire Original Android Development] sd_shadow:
it does that every time use make changes, root, twrp...
[Fire Original Android Development] Diomorgan:
I whaited and everything is fine, xposed installed and still rooted, superthank you! :o
[Fire Original Android Development] Diomorgan:
Mmmm, unluckily I got problem with exposed frimewroks (OT:it gave me proble even on TABLET Z4, so I'm afraid is an option or plugin that I turn on).

Maybe the problem "could be" I flashed the .zip with TWRP?

Actually I would like to use xposed just to download instagram pics and the multi reboot menu from Gravity, but when I turned on some option in gravity it starte taking a life (15minutes?) to boot and, anyhow, it doesn't modify menu, so I'll try reflashing the unexposedbackup, reflash exposed and uninstall gravity, let's see.

I read somewere that some google apps slow down the tablet, but I don't thin is my situation.

Anyhow, thank you again for the TWRP so I can easyly restore the roted tablet loooooosin a lot of time from .bin to flash supersu! :)
[Fire Original Android Development] macravin:
Is anyone currently working on modified stock builds for this tablet? I think a rom like Kinnology on previous devices is what this slate needs right now. I tried to debloat and add some of the regular android settings to the settings app, but I just ended up breaking things.... ;(
[Fire Original Android Development] csolanol:
Yup, working on SlimLP. At this point it is as stable as cm from ggow plus battery stats fixed. No plans to release it until bluettooth works.
[Fire Original Android Development] jdogrambo:
wat happens if try to flash this
[Fire Original Android Development] sd_shadow:
see post #2
[Fire Original Android Development] jdogrambo:
i seen post 2 but what will happen
[Fire Original Android Development] sd_shadow:
when you do what?

---------- Post added at 06:27 PM ---------- Previous post was at 06:12 PM ----------

if you are asking what is a custom Recovery?

you should do some research on Android partitions, root, roms, and such.

www.rootjunky.com/home has info and videos about this
[Fire Original Android Development] sageDieu:
I'm getting remote:unknown command:

https://i.imgur.com/GnYPHpm.png

Any ideas?
[Fire Original Android Development] Hemphiz:
Try typing boot.img.img
[Fire Original Android Development] sageDieu:
what do you mean? fastboot boot TWRP_Fire_2.8.7.0.img.img?
[Fire Original Android Development] Hemphiz:
It's the only thing I can think of (I had the same problem so had to type the above and it worked and yes. fastboot boot TWRP_Fire_2.8.7.0.img.img
[Fire Original Android Development] sageDieu:
Ah no that didn't help, says no such file or directory which is accurate. For me it loads the file to the tablet, just the boot command doesn't work.
[Fire Original Android Development] 87racer:
same here. remote unknown command, brand new fire, opened box updated, tried to fastboot boot. both twrp and other custom boot images not working so i think it is fastboot related.
[Fire Original Android Development] csolanol:
Both new tablets?.

Looks like amazon patched the bootloader to avoid us booting from temp boot.img.

Someone has to look at software version on the tablet and post it.
[Fire Original Android Development] sageDieu:
Mine is 5.1.1 as mentioned by the other guy in the SlimROM thread. I'd love to pursue getting into this thing, for $35 I don't care if I break it along the way.
[Fire Original Android Development] harisled:
Can't boot TWRP as well on the updated system image (5.1.1) :(
[Fire Original Android Development] demlv:
"opened box updated" is the key. Once updated to 5.1.1 = no joy....at least for now.
[Fire Original Android Development] Nooblet:
ADB isn't finding the device to sideload ROM, anyone else having this problem?
[Fire Original Android Development] csolanol:
Yes, sideload isn't working. Copy your zip files to the SD.
[Fire Original Android Development] Nooblet:
Wellllll about that..... I lack one, guess it's back to stock. Sideload works partially for CM recovery, just won't flash for some reason...
[Fire Original Android Development] csolanol:
Ummm if you have a pendrive you can use otg in twrp.
[Fire Original Android Development] npompei:
So it looks like we are waiting on the 5.1.1 update recovery and or Rom updates correct? Damn thing updated on me when I plugged it in and walked away. Had no clue - ha. So we are in a holding pattern for those on 5.1.1 correct?
[Fire Original Android Development] 87racer:
Yes, holding. Fastboot no longer works for booting custom recoveries...
[Fire Original Android Development] csolanol:
Yup but no good news for now.
[Fire Original Android Development] MAGICMAN516:
So if I just got mine today and if I want to put the cyanogenmod that's on here I shouldn't even try to connect it to wifi and then it won't update then I can get it all installed correct?
[Fire Original Android Development] sd_shadow:
Unless it already has 5.1.1, then it doesn't matter, current twrp/root methods would not work.

I believe some are shipping with 5.1.1 now. (edit) if not they soon will be.

But yes your best bet is to try booting twrp, without booting to stock rom first.
[Fire Original Android Development] MAGICMAN516:
Looks like I'm in luck I booted without connecting to a wifi and I have 5.0.1. I'll have to give this a shot when I have more time then.
[Fire Original Android Development] blueberry.sky:
Sh*t, I'm waiting for another Fire & praying it won't have 5.1.1. I haven't seen any reports of new Fires preloaded with 5.1.1 yet, guess I missed them. Could you point me toward a report?
[Fire Original Android Development] sd_shadow:
i can't remember, so i edited my post same time you asked, to this

"I believe some are shipping with 5.1.1 now. (edit) if not they soon will be."
[Fire Original Android Development] DoLooper:
Does sideload mode work in this TWRP? I tried to use it but device didn't show up anywhere in Win 7 Device Manager so I couldn't install driver. (In other modified TWRPs I've been able to see the device while in sideload mode.) Thanks!
[Fire Original Android Development] sd_shadow:
Twrp Sideload has not worked for me
[Fire Original Android Development] MAGICMAN516:
It works now booting into cm12 got the face. I bought the device when they had the sale for $35.00 with the advertisement option. LOL now I have a cm12 device. Thanks guys.
[Fire Original Android Development] besweeet:
Add me to the list of people who did the OOTB software update.
[Fire Original Android Development] chugger93:
Hate to be a noob...but I'm brainfarting. Ran the fastboot boot command, but says waiting for device. I think I need to be in fastboot mode for this to work. How do I get in fastboot mode?

nm, I suck. figured it out
[Fire Original Android Development] besweeet:
Hold power + volume down, then select the recovery option.
[Fire Original Android Development] shabuboy:
does anyone see any benefit to adding on the first page version 5.1.1 is not rootable at the moment? Or on any of the other main pages with procedures for root, roms, etc.

Just wondering...
[Fire Original Android Development] yaoverstand:
I cannot get my device to boot TWRP. I have the TWRP img file in the same folder as adb/fastboot/cmd.exe, and I copied and pasted the commands just to make sure. This is what my cmd terminal looks like:

Any help would be appreciated!
[Fire Original Android Development] Pond-life:
So the TWRP_Fire_2.8.7.0.img is in the same Mateo directory that cmd is running in, odd. Assuming you aren't on 5.1.1 anyway

Always had it in bootloader rather than recovery myself don't know if that's significant.

adb reboot-bootloader

fastboot boot TWRP_Fire_2.8.7.0.img

Though I do notice your recovery name is different, it's the name in post 2 on thread though the download from 1 gave me the name above. It's not just naming problem is it?
[Fire Original Android Development] csolanol:
Are you launching fastboot from the same path as recovery image is?
[Fire Original Android Development] 87racer:
You don't have the twrp image in the mateo directory, move it there or use the cd command to change directory to the directory where adb is. Make sure you have the name typed perfectly. Alternately shift+right click on the twrp image in explorer and click copy as path. Then type fastboot boot then right click and paste. This will paste the full path to the twrp image.
[Fire Original Android Development] yaoverstand:
I am launching cmd.exe from the same folder as fastboot and adb, but I didn't even catch that it was still saying the Mateo folder. All my adb stuff is in the root directory of c:/.

So I just need to move the TWRP image to the root directory of Mateo?
[Fire Original Android Development] 87racer:
I would just change directory to c:\ with 'cd c:\' then your existing commands will work
[Fire Original Android Development] dgmustard:
You can also type "fastboot boot " (make sure there is a space at the end) and then drag the .IMG file into the command prompt from file explorer and it'll auto-add its file location to the command.

Then just press enter to initiate the command.
[Fire Original Android Development] yaoverstand:
So adb into fastboot, and then cd to c :/ and then fastboot the TWRP img?
[Fire Original Android Development] blueberry.sky:
You can get into fastboot via adb but I find it easier to just power off, hold volume up button + hold power button.
[Fire Original Android Development] 87racer:
Yep, or cd c:\ first, doesnt matter as long as you cd before fastboot command
[Fire Original Android Development] besweeet:
For some reason, your "figured it out" update never showed within the actual post, but only when quoting.
[Fire Original Android Development] sandman512:
Hey guys, Just want to throw this out there since it seems a lot of people are having trouble getting this thing to boot into TWRP. So, I have been using ROOTJUNKY'S SUPERTOOL. Basically, there is a file(I think ADB FASTBOOT), which gives you several options such as install/test drivers, boot into TWRP etc.... I have yet to have any issues with it. It is called SUPERTOOL, here you go http://rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool
[Fire Original Android Development] 87racer:
Anybody tested this on an OTA 5.1.1? I will tonight although I doubt it will work.
[Fire Original Android Development] eggger:
the only thing I managed to do with it is to install google play
[Fire Original Android Development] k4y0z:
I was wondering if the sources for your TWRP-port are available. (I looked through your github, maybe I just overlooked them?)

I would like to enable adb in TWRP, that would be very usefull for debugging.

ATM I'm using cyanogen-recovery for that, but since that's missing a lot of other features it's a PITA to switch back and forth.

Thanks
[Fire Original Android Development] diegocr:
We compiled it with slim source, need to comment first block and uncomment second block on recovery/root/recovery.fstab

https://github.com/diego-cr/device_amazon_ford

Thanks for your modules
[Fire Original Android Development] k4y0z:
Thank you, I'll take a look.

No problem, anytime.

If you need anything else kernel-related just PM me.

Had to take a break from messing with kexec, although I've come pretty far.

Might clean up and upload the sources and seek for help here.

Wasn't yet able to fully boot a new kernel, because the initialization of the CPU cores fails.

I haven't given up though, it would be awesome if it worked!
[Fire Original Android Development] csolanol:
Yeah, feel free to look whatever you want and ask what you need. If we can help we will be very pleased to. I will take a look this weekend too. I didn't realize about the lack of adb support and then we started with the rom, so not enough free time for all.
[Fire Original Android Development] sd_shadow:
RootJunky's Supertool uses same twrp and commands, it's just automated.

There is no reason it would work with 5.1.1 better.
[Fire Original Android Development] tonyf7:
My Fire came in a couple of days ago and I think it had 5.1.1 already on it. Anyone know if a TWRP for 5.1.1 is on the way?
[Fire Original Android Development] sd_shadow:
5.1.1 likely will require a bootstrap like Safestrap.
[MENTION=5749760]ggow[/MENTION] maybe working on a safestrap for ford, when he has time.

---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------

or an unlocked bootloader.
[Fire Original Android Development] tonyf7:
That would be great! Because as of now I'm stuck in this horrible Amazon ecosystem and it sucks.
[Fire Original Android Development] FBis251:
Hey [MENTION=2511007]csolanol[/MENTION] do you have a link to the TWRP sources you used to build the recovery?

Thanks
[Fire Original Android Development] csolanol:
Sure: https://github.com/SlimRoms/bootable_recovery
[Fire Original Android Development] t3chwizard:
This may be a useless question, but is there any way to be able to mount the external or internal SD while in TWRP? I used this one recovery for the Original Kindle Fire with the OtterX partition layout and it allowed me to copy files to the internal memory while in the recovery over MTP. There's also this one recovery I have used on my LG Optimus G Pro called PhilZ which the development has since been discontinued, but nevertheless, and it would allow you to mount the external SD using UMS over USB while in the recovery. Now this might be not possible at the moment because of the locked BL, but I thought it would be worth asking about just to see.
[Fire Original Android Development] diegocr:
On new build can mount sd as usb storage.
[Fire Original Android Development] Pond-life:
Great stuff. And adb as well. :)

Thanks a lot, very useful indeed

Though am finding I can't copy files to the sd card from pc as usb storage.

Edit 2.

Can push them there in adb though so it's all good :D
[Fire Original Android Development] sd_shadow:
great!

small issue, you couldn't use a different name? like TWRP_Fire_2.8.7.0.v2.img ?

Not a big deal, just is going to cause some confusion.
[Fire Original Android Development] diegocr:
TWRP_Fire_2.8.7.0_adb.img
[Fire Original Android Development] sd_shadow:
that should be obvious enough, Thanks
[Fire Original Android Development] Pond-life:
Is it just me that can't delete files from or copy files to the SD card after mounting using explorer?
[Fire Original Android Development] diegocr:
USB storage not working, don't save changes to sd

Use "adb push"

---------- Post added at 09:55 AM ---------- Previous post was at 08:58 AM ----------

Uploaded new version with MTP
[Fire Original Android Development] sweh:
Does this work on the "Fire 7" (the non-HD version)? This was $35 during black friday specials, so I got one to play with. But...

% fastboot boot TWRP_Fire_2.8.7.0_adb.img
downloading 'boot.img'...
OKAY [ 0.256s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.258s

The Fire screen shows the file transferred, but it doesn't boot into the image. Do I need to break/root/something before hand? Is this the Fire 7 so much different to the HD versions.

FWIW, Fire OS 5.1.1 installed yesterday on firstboot..
[Fire Original Android Development] besweeet:
Doing the OOTB update to 5.1.1 is a known bad idea: http://xdaforums.com/amazon-fire/general/psa-information-regarding-firmware-t3264224

I also updated without knowing.
[Fire Original Android Development] 87racer:
We don't have functioning fastboot access if you have 5.1.1 via OTA. You are stuck for now.
[Fire Original Android Development] sweh:
Ah, thanks. I thought this was going to be too easy :)

(*grump* failed to TWRP on my Moto X Pure Marshmallow and now failing with the Fire 7... not my week! :crying:)
[Fire Original Android Development] 87racer:
If it is worth that much you can exchange it with Amazon, hope you get a 5.0.1 tablet and just dont connect to wifi before rooting/flashing.
[Fire Original Android Development] k4y0z:
Just wanted to let you know, adb sideload also works with the adb-TWRP-version now. :)

I believe that didn't work before.

Thanks again!
[Fire Original Android Development] besweeet:
Just to confirm, the updated TWRP recovery is still useless for those of us that are on Fire OS 5.1.1, right?
[Fire Original Android Development] k4y0z:
Check here: http://xdaforums.com/amazon-fire/orig-development/root-t3272362
[Fire Original Android Development] besweeet:
I saw that. Seems promising!
[Fire Original Android Development] diggitydogg:
So this is odd. I went to update to the newest CM on here and when I'm trying to boot the TWRP image it just sits there stuck at USB Transferring... and never goes anywhere. This has always been working without a hitch. I verified that drivers are all set and other fastboot commands are working fine, it just doesn't move the TWRP image over to boot it. I rebooted tablet and computer, downloaded the newest TWRP image from this thread, tried different ports and cables. I'm kind of at a loss at this point. I rarely get stumped like this, and even more rarely ask for help, but I can't seem to find anything that might point me in the right direction.

Any ideas?
[Fire Original Android Development] blueberry.sky:
Also verified the md5 of your TWRP image, correct? That is odd.
[Fire Original Android Development] diggitydogg:
You know, I didn't verify that. It is the same image I have used since I got the Fire on Black Friday and haven't had an issue until today. I'll check them both though (the original one and the new version)
[Fire Original Android Development] blueberry.sky:
. . . Yeah, somehow I overlooked that when asking about md5.

Tho I suppose a random hard drive error could land in the middle of your twrp? If you're really unlucky. Similarly, I would guess it's possible for the Fire's flash chip to develop an error in the middle of fastboot. Should be very very unlikely. But your problem does seem pretty odd. You could try reflashing fastboot. Post #7 of this thread has a copy of the 5.0.0/5.0.1 fastboot (lk.zip) & the command to flash it.

Just kind of low on ideas.
[Fire Original Android Development] fmc000:
Activate fastboot on the tablet, disconnect the cable, launch the twrp boot command and only after that reconnect the cable.
[Fire Original Android Development] Tomes77:
I have the same problem, brand new fire tablet, all fastboot commands are working well, but when i try to boot the TWRP image, the downloading is OKAY [0.xxs] then booting... FAILED (remote: unknown command).

All the ADB drivers are installed, i also try the last hint with reconnect after start boot command.

Any further ideas?
[Fire Original Android Development] Pond-life:
OS version on the Fire? if it's 5.1.1 it won't work. That's first thought.
[Fire Original Android Development] blueberry.sky:
Yep, "FAILED (remote: unknown command)" is the message you get when you're on 5.1.1. FlashFire is the only way currently to flash roms in 5.1.1.
[Fire Original Android Development] Tomes77:
Ok, thank you, i will try..

---------- Post added at 11:29 PM ---------- Previous post was at 11:03 PM ----------

In the Thread SlimLP 5.1.1 there are the same steps and the same TWRP Image to install a new ROM. So it must be work also on 5.1.1

http://xdaforums.com/amazon-fire/orig-development/rom-slimlp-5-1-1-amazon-fire-2015-ford-t3256053
[Fire Original Android Development] FrankieChen:
I had a similar problem with the FIRE not being recognised once it rebooted and struggled for a couple of weeks trying different suggestions. It was a simile "pause" after the reboot command that finally resolved the issue. Maybe worth a try.
[Fire Original Android Development] Pond-life:
The 5.1.1 in that thread name refers to Android 5.1.1 not to Amazon os 5.1.1
[Fire Original Android Development] dhappyman0:
What is FlashFire? Can't seem to find any threads on it for the fire tablet.
[Fire Original Android Development] sd_shadow:
http://xdaforums.com/showthread.php?t=3269839

How to Use FlashFire App to install a Rom
[Fire Original Android Development] demlv:
On my Nexus 6 I usually have to connect my OTG flash drive, then reboot to recovery in order for TWRP to recognize it. Since it is apparently not possible to a) reboot to TWRP with an OTG device connected, or 2) reboot to TWRP from TWRP, I gather that OTG devices are recognized more easily by TWRP on this device. Can anyone share their experience or any tricks needed to get OTG backups/restores working on the Fire with TWRP?
[Fire Original Android Development] thekrakah:
Easiest windows root method I've tested so far. Credit to glitch3yf0x .

Here's also an alternate method to get flashfire on to your Fire device after your gone through the root process.

download flashfire apk to your windows adb directory: flashfire-0.24.apk

Connect your Fire device, be in Fire OS, not fastboot. Run the below commands, flashfire will be loaded, and you can move onto loading your preferred ROM.

adb commands to run from your windows adb directory:

adb kill-server

adb start-server

adb wait-for-device

adb install -r flashfire-0.24.apk

adb kill-server
[Fire Original Android Development] blueberry.sky:
My trick: use microSD! :D

See the OP, post #1.

I know it's hard when important information is buried deep in a thread.
[Fire Original Android Development] MohRez:
Hi

Can you made a Custom Recovery for Galaxy J5 F ( J500F ) like this Sir ??
[Fire Original Android Development] sd_shadow:
Why ask here?

[RECOVERY][TWRP][J500] TWRP 2.8.7.0 for Samsung Galaxy J5
[Fire Original Android Development] demlv:
Got it. I'll stick to the micro SD then. Thanks!

Yes, getting a clear understanding can be difficult when key info. is buried in a thread. It becomes even harder when the information found in the OP itself is seemingly conflicting. Near the top of the OP it clearly reads: "All should work, it has been tested . . . Project became stable . . . all is working as expected."

For purposes of clarity, I respectfully encourage [MENTION=2511007]csolanol[/MENTION], the thread owner, to pick only one of the following statements: "All is working as expected" OR "Don't use USB storage, not working".
[Fire Original Android Development] csolanol:
Done...
[Fire Original Android Development] p0lt:
twrp 3.0.0

TWRP 3.0.0 is out today. Is there a version for the ford yet?
[Fire Original Android Development] sd_shadow:
really?