yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] jbraney:
I have bricked many devices, usually there is a way to unbrick them, but if you have tried all conventional means, then for now at least, it probably is... Sorry!
[Fire Original Android Development] Pond-life:
Was that with the lk alone or the second idea with the preloader too?
[Fire Original Android Development] kleydejong:
Just the lk alone, not the preloader.
[Fire Original Android Development] flyapart:
Great! Noob question warning -- I can get the root prompt but can't seem to install SuperSU. Can you tell us what commands you used from the terminal to do this? Also which file you used to install it (apk vs zip) and where they need to be placed? Thanks!!!
[Fire Original Android Development] jkchr1s:
Excellent find, congrats. This is even simpler than the 5.0/5.0.1 method.
[Fire Original Android Development] pappasmurfsharem:
I just opened the root.bat from the other method in the 5.0.1 page and pasted the cmds manually in a cmd prompt

seems to have worked as I can use a terminal emulator and enter 'su' and get Superuser prompt

I believe it is/was more or less this

You will need the root_fire.zip from the other thread, and then open a command window in the folder where you extract those files.
[Fire Original Android Development] aramil:
Confirming this works :good:
[Fire Original Android Development] pappasmurfsharem:
to add to this, since the only real reason I wanted root was to use a different launcher.

install Terminal Emulator after you root using the method above.

install whatever launchers you wants

then in the terminal shell

then when you click the "Home Button" it will prompt you to use a differnet launcher
[Fire Original Android Development] maratd:
Correct. As in, it's a brick. Nothing shown on screen no matter what I do. Behavior is similar to what was described in another thread when someone mentioned they tried to downgrade. Nothing on screen, but it keeps connecting/disconnecting on the computer.
[Fire Original Android Development] DoLooper:
I'm not very knowledgeable about all you're doing, but you know bibikalka provided the old bootloaders here: http://xdaforums.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594

Could they be installed with fastboot boot or adb sideload?
[Fire Original Android Development] blueberry.sky:
Someone tried installing the old 5.0.1 fastboot (bootloader). Resulted in a hard brick (unrecoverable brick, as far as we know).

But flashing the preloader + fastboot might work.

Files attached to post #7:
[Fire Original Android Development] Pond-life:
Best to push the launcher into system isn't it?

Still need to block future OTAs though as they could easily revert the launcher and block this new way in on the next OTA?
[Fire Original Android Development] pappasmurfsharem:
I didn't need to do so.

just disabled the firelauncher. and it appears to have worked.

to be fair I also did

pm enable com.google.android.launcher for google now.

but when I clicked home MY ADW launcher also showed up so I'm not certain if that step was necessary
[Fire Original Android Development] blueberry.sky:
Yes, we always need to block OTA.
[Fire Original Android Development] jbraney:
Has anybody tried flashing pre-loader + fastboot yet? I don't know how to do this at the moment, but I would love to hear if somebody else was successful...
[Fire Original Android Development] revdirty:
For the less savvy people like myself, is someone compiling a handy .bat file and folder with everything u need to do this . something similar to the zip file for installing the google playstore via adb. that would be fantasitc! Getting root to change the launcher would be wonderful
[Fire Original Android Development] pappasmurfsharem:
If youy wnt to just change the launcher. I don't think you technically need root

Just follow the first post

Make sure you have an alternate launcher downloaded and installed from the store

Then when at the root shell

Type

This should disable the fire launcher so that when you press home you'll get prompted to select a new launcher

Then also disable OTA
[Fire Original Android Development] revdirty:
Well I do want to do more then just change the launcher.. adblock and other root only apps
[Fire Original Android Development] jbraney:
The biggest reason I need root is to manage the small file size. I have a 64GB SD card in there, but every time an app updates, it removes itself to the main partition, making me dangerously low on space until I re-move it... EXTREMELY annoying. Not to mention I download a lot of movies and music onto this thing from third parties, and would like the default download location to be on the SD. I can't do any of this without root... :(

---------- Post added at 07:58 PM ---------- Previous post was at 07:52 PM ----------

Can anybody simply explain how to make the tablet keep the root access gained in step 1?

I have SuperSu installed from the playstore, but that doesn't work...
[Fire Original Android Development] pappasmurfsharem:
I explained it a few posts back ?

If you saw that but are slightly confused/worried

PM me and I'll get you sorted
[Fire Original Android Development] DoLooper:
Can you please give me the link to the "5.0.1 page" with the root_fire.zip? (Guess I'm blind or something) :eek: Thanks!
[Fire Original Android Development] pappasmurfsharem:
Goto android development forum (currently we're in original android development"

Then "Amazon fire 5th gen 2015 root"

Under the video in the first post is a link

You will need the proper adb drivers installed first but the video covers that
[Fire Original Android Development] DoLooper:
Yep. :D Will be a day or two.

For rooted stock:

- Install custom launcher

- Disable Fire launcher

- scripts to switch between custom and Fire launchers

(run from shortcut on launcher home screen)

- Move custom launcher to system/priv-apps (for widgets)

- Disable OTA

Not sure about doing an su install script since right now it relies on sh scripts written by someone else.
[Fire Original Android Development] Pond-life:
The ota stopped hide commands working on 5.1.1, don't think disable worked either, so root was needed.

You could use a different launcher you just couldn't make it default.

Hide works once in root shell on 5.1.1?

---------- Post added at 01:18 AM ---------- Previous post was at 01:15 AM ----------

This is the one they refer to

http://xdaforums.com/amazon-fire/development/wip-achieving-root-thread-t3238152

Suspect there would be much writing in there today if it hadn't been locked over a naming dispute.
[Fire Original Android Development] revdirty:
Guess ill be waiting, im not very comfortable with cmdline stuff.. anything beyond the basic pinging an ip or following on screen prompts (ala.. press 1 to ___ press 2 to ____) and im lost..I hope i can get this done, i have 2 of em and need them finished for my sons xmas gifts
[Fire Original Android Development] Tomsgt:
http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695

enjoy
[Fire Original Android Development] pappasmurfsharem:
In theory they should as you are root when in the adb shell

However I didn't actually run them until after I installed SuperSU

---------- Post added at 07:24 PM ---------- Previous post was at 07:22 PM ----------

PM me
[Fire Original Android Development] DoLooper:
Ha! I've been playing with these for a month, thinking I'd tinker "just one more day!" You've got it covered, all right. Thanks!
[Fire Original Android Development] DoLooper:
Ad blocking on rooted 5.1.1

Could someone please test this command to block ads on rooted stock 5.1.1 and see if it survives a reboot (and an Amazon ad download!)? Thanks!

adb -d shell "su -c 'pm disable com.amazon.kindle.kso/com.amazon.kindle.kso.lockscreen.LockscreenUpdateService'" >nul 2>&1
[Fire Original Android Development] Pond-life:
Tomsgt updated the batch file now.
[Fire Original Android Development] SalemGDU:
Rootjunkys Supertool WORKS for the most part even on 5.1.1 BUT it will not I repeat will not allow you to boot into recovery........ I have one fire on 5.0.1 rooted and TWRP backup ads removed and google working. The other is on 5.1.1 cannot root or load recovery but the tool or >>.bat<< file will let you remove ads and install PLAY services...
[Fire Original Android Development] Pond-life:
It should root on 5.1.1 with the latest root junky supertool.
[Fire Original Android Development] kr338r:
had already rooted before update, just wanted to say thanks for the work!
[Fire Original Android Development] Neffy27:
When I get to "adb shell remount", just replies with "error:device not found". Any ideas? I can leave the shell and get adb to show device after a adb get-state. Driver issue maybe?

EDIT

This worked for me.

THANK YOU ALL!
[Fire Original Android Development] blueberry.sky:
Anyone try flashing the preloader + fastboot yet?
[Fire Original Android Development] Pond-life:
No one has mentioned it, so probably not. Think it got a bit lost in the thread
[Fire Original Android Development] besweeet:
Or people saw a few Fire's being bricked by an attempted bootloader downgrade and got scared away.
[Fire Original Android Development] hobbit19:
hd8

5.1.1

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\User>cd c:/

c:\>cd adb

c:\adb>adb reboot-bootloader

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

c:\adb>fastboot oem append-cmdline "androidboot.unlocked_kernel=true"

...

FAILED (remote: unknown command)

finished. total time: 0.023s

c:\adb>fastboot oem append-cmdline "androidboot.unlocked_kernel=true"

...

FAILED (remote: unknown command)

finished. total time: 0.024s

c:\adb>fastboot oem append-cmdline "androidboot.unlocked_kernel=true"

...

FAILED (remote: unknown command)

finished. total time: 0.024s

c:\adb>fastboot oem append-cmdline

...

FAILED (remote: unknown command)

finished. total time: 0.018s

c:\adb>
[Fire Original Android Development] Pond-life:
Probably a bit of both

---------- Post added at 08:41 PM ---------- Previous post was at 08:31 PM ----------

Did the tablet reboot to fastboot mode even? I don't see the usual comments there.

Does adb devices show it?

And fastboot devices?
[Fire Original Android Development] blueberry.sky:
*Two Fires.

Unfortunate that that a 2nd person tried it. Only one needed to test it. K4y0z warned of the risk in bold red text. This is for someone who wants to help with development & doesn't mind having to return their Fire if it get's bricked. I've read that amazon will even ship out a replacement before they have received the old one back. To save time waiting for the replacement.
[Fire Original Android Development] Pond-life:
Guess they were both checking at about the same time.

Are they finally back in stock then?
[Fire Original Android Development] blueberry.sky:
It would be good to post before trying to flash the preloader+fastboot so others know to hold off trying it until you report back.

They are shipping Fires as fast as they can make them. There is still a backorder if you order a new one now but I would hope replacements skip the line. I got the impression that they do.
[Fire Original Android Development] Pond-life:
Mines on 5.1.1 the safe bibikalka way.

Saw a couple of people say they were offered refurb or wait for them to come into stock, but probably depends who you get hold of at Amazon
[Fire Original Android Development] howzitnow:
My 11/26 fires needed to be replaced... Both of them?. I got bumped to the end of the line. Re-ship date was 12/28 but I got an email today that said they'd now ship12/22.
[Fire Original Android Development] blueberry.sky:
What was the problem with them? Did you ship them back yet?
[Fire Original Android Development] randomblame:
hmmm I've got a 5.1.1 ford here to test, those who bricked on the bootloader downgrade didn't flash the old preloader? Can I get a link to that and instructions?
[Fire Original Android Development] Dr.TheMaster:
hi.. so from what I have read so far in the comments.. there is no way to boot into TWRP or any custom recovery after 5.1.1.. even if we have root access.. that means that we cannot install custom ROMs for now.. am I correct? and is there any hope that the devs can solve this? thanks in advance
[Fire Original Android Development] randomblame:
fastboot was neutered with the 5.1.1 ota it is still there but the boot command is gone so you can not boot to twrp not sure if the flash command still exists perhaps we could have someone dump us a cm12

system.img and run fastboot flash system?
[Fire Original Android Development] blueberry.sky:
Yes, they only flashed fastboot. No one has tried flashing the preloader+fastboot yet. Your Fire 5.1.1 was OTA updated or came preinstalled, correct? If so, see k4y0z instructions in post #7. link

edit

Links to the two attempts without the preloader.

Post # 17 flash fastboot only #1.

Post #37 flash fastboot only #2.
[Fire Original Android Development] 4t701:
Use FlashFire

[emoji106]
[Fire Original Android Development] Dr.TheMaster:
And will that work without a problem? Can you confirm that please? That sounds amazing..

Kindly press thanks if I helped :)
[Fire Original Android Development] blueberry.sky:
Be aware that using FlashFire is a bit risky when we don't have our own recovery to fallback to. If do some tweak to your rom that results in a boot loop you might get stuck. Tho I would guess you should be able to use amazon's recovery to flash 5.1.1 then start over (root> block OTA> FlashFire> rom).
[Fire Original Android Development] jbraney:
Have you tested it to see if it will properly work?

---------- Post added at 07:16 PM ---------- Previous post was at 07:15 PM ----------

Well if someone tries this, please put up their progress here or on a new thread... I think we all want to see this work, and would love to get updates!
[Fire Original Android Development] blueberry.sky:
I read in other threads that people have tested using FlashFire to go from stock to custom roms & even back to stock. I recall reports that SlimLP & RR worked ok but at least one attempt at CM12.1 failed. I believe at least one person used FlashFire in 5.1.1 successfully.

Just don't ask me which threads this was in. :laugh: I've been trying to keep up on almost every Fire thread. But you can always search the fire forum for "FlashFire".
[Fire Original Android Development] randomblame:
got root sideloaded flashfire and it seems to work then boots to amazon fw

* strike that CM12.1 failed to work but Slim-ford-5.1.1.build.2.2b-20151210.zip flashed and is booting :)

If you want to flash a custom rom and you have 5.1.1 with a useless fastboot you can still run flashfire and flash slim. Here's the order of operations:

Root your device

sideload flashfire

install esfile to open flashfire

copy slim to /sdcard

in flashfire flash the zip
[Fire Original Android Development] jbraney:
Just flash it? Do you need to do any system resets or cache wipes like you do in TWRP? Or do I just copy to SDcard and flash the zip...
[Fire Original Android Development] randomblame:
I didn't bother wiping
[Fire Original Android Development] jbraney:
Hey, you really look like you know what you're doing. Check out my comment on the Supertool page... I might have an idea. Just read it, it's not that long!
[Fire Original Android Development] 4t701:
[emoji67]

-you *probably* need to do a FULL wipe (unless you're only flashing an update to your rom or are flashing some other random .zip)

-Flash your ROM, Gapps.zip, and your SuperSU.zip (if you need/want root access)

-check 'automount' on all ROM/.zips you flash

-leave EverRoot disabled

-FLASH!

-should only take a couple minutes if everything works

BE AWARE IF YOU ARE ON 5.1.1 YOU HAVE NO ACCESS TO TWRP SHOULD SOMETHING GO WRONG!

-Good luck!

#########################

I have not done this on 5.1.1. I'm on 5.0.1 but have suuccessfully flashed SlimLP, Cm12.1, and Resurrection Remix Rom using this procedure. I have also switched(flashed) back and forth between these roms using FlashFire several (too many to count) times.

[emoji41]
[Fire Original Android Development] jbraney:
Ok... I would like more clarification. RandomBlame has 5.1.1, and was able to flash the Slim Rom with only the Zip, no reseting, or anything... I want to go ahead and do this, but if someone can please clarify here, I would be grateful. I really do not want to brick this thing atm...
[Fire Original Android Development] 4t701:
Remember kids:

"A clean flash is a safer flash. Just remember to always have a current backup."

[emoji106]

Also what's the point in NOT doing a FULL wipe? Unless you don't have a backup or something I see no reason.
[Fire Original Android Development] randomblame:
sure if you have a recovery partition. I didn't wipe because I wanted to retain what was in /data and /cache This IS a dirty flash using flashfire and not a recovery environment. all sorts of bad things can happen.
[Fire Original Android Development] howzitnow:
They both had dead pixels. I havent sent them back yet. Amazon said to keep them until the replacements come and that there would be a return label for the broken ones in the box. At least there's something for the kids to open on Christmas. The night before 5.1.1 was rooted I set the dead pixel one up with root and Google play figuring we'd keep them instead of the new ones as its pretty much assured the replacements will have 5.1.1. Now that there's root on that, I'll probably go back to the original plan and send dead pixel ones back.
[Fire Original Android Development] randomblame:
Sure if you have a recovery partition. I didn't wipe because I wanted to retain what was in /data and /cache it was experimental. Using flashfire instead of a recovery environment is not as safe and not as clean, all sorts of bad things can happen. I didnt wipe and it worked perfectly for me, if you wipe and it bootloops you have no easy way to recover. Just sayin... android is smarter than it used to be these days you can get away with a dirty flash and sometimes its useful.
[Fire Original Android Development] 4t701:
You can make and restore backups from FF.
[Fire Original Android Development] randomblame:
not if your device doesnt boot.
[Fire Original Android Development] pbailey212:
If you use flash fire, make sure you use pico gapps. If the gapps/ROM together are too large for the system partition, it will freeze up and you won't have a recovery to fall back on. I highly don't recommend using flash fire on 5.1.1. It's really risky.
[Fire Original Android Development] randomblame:
That could be recoverable through adb which would be set up already from rooting the device before flash fire - unless you wipe data - another reason I didn't wipe when testing :)
[Fire Original Android Development] randomblame:
Wiping EVERYTHING in flashfire now just to make sure I break my tab instead of someone else's

*and its good to go. I'd recommend dirty flashing thru flashfire then after you have a good boot to your new custom rom wipe everything. This way you have should still have adb in case something goes wrong.
[Fire Original Android Development] rjdh2o:
Is anyone running Cyanogen Mod or any other Roms on this yet?
[Fire Original Android Development] jbraney:
Randomblame got slimROM to work, but when he tried CM12.1, it failed... Its still highly risky. Just have patience and let the experts work it out... They are making extremely fast progress! :)
[Fire Original Android Development] theophile2:
If you make a backup in flashfire and then try to flash something and it doesn't boot, you can reflash the stock firmware with the stock recovery, reinstall flashfire, and then restore the backup.
[Fire Original Android Development] k4y0z:
This has only been tested on the Fire 7" 2015 edition.

the hd8 fastboot doesn't seem to support the command "oem append-cmdline".
[Fire Original Android Development] blueberry.sky:
:victory:

Might have found someone who has 5.1.1 & is willing to try flashing the preloader + fastboot. No problem returning it if bricked.
[Fire Original Android Development] bmurphr1:
I'm willing to sacrifice my tablet as well since I already have the replacement on the way. I want a tablet with 5.0.1 firmware installed on it so fastboot is un-neutered and already have a replacement showing up on Sunday.

Whoever wants me to attempt to un-screw my 5.1.1 tablet give me the directions on how to setup the flash and if the tablet is bricked, then it doesn't matter.

EDIT: I just saw the instructions on the first page and I'm ready to attempt to push lk.bin and preloader_prod.img on to my 5.1.1 Kindle to see if we can regain fastboot access to the device. Are there any objections at this point? I'm going to give this post a few hours and if somebody gives me the go-ahead (that knows what they're doing) then I'll perform the procedure to see if the tablet is bricked or we get fastboot back so that we can boot cyanogen recovery or TWRP.
[Fire Original Android Development] dgmustard:
Do NOT follow those steps unless you want to be the 3rd Fire that is bricked from the process.

A user on page 2 already tried it and bricked his Fire. Another user (page 4) then ran the test (likely didn't see the other post) and also bricked his Fire.

Please read the entire thread before running commands when there is no known method (unless you know what you are doing).

EDIT: That may have come across stronger that intended but was trying to make sure you didn't brick your Fire (so we have more testers).

EDIT 2: I was wrong, sorry. I didn't realize that post had been updated. I am glad I posted this though as now its been confirmed that those are the steps you should take. Your post said that you would run the steps in an hour if no one commented and I would have hated for those steps to be the wrong ones...
[Fire Original Android Development] bmurphr1:
I'm following multiple threads at the moment and have no idea which is the latest "lets try this move" so forgive me for not being as on top of things as the rest of you seem to be.

I have a span of about 5 days to brick this tablet before it has to be shipped back to Amazon, so right now I'm a guinea pig for whoever needs me to be.

(In case you haven't figured it out yet, I already have another "replacement" tablet that's arriving Sunday so that I'll be able to keep it on 5.0.1 and have to mail this tablet back once I receive the replacement so I have a window of a few days to do any sort of testing that needs to be done to the Fire 2015. Whether we get fastboot un-neutered or not before then, this tablet is being shipped back by Tuesday at the latest.)
[Fire Original Android Development] tuckerwagner:
It's my understanding that neither of those people flashed the preloader.
[Fire Original Android Development] Pond-life:
That is the case. Maybe he should have followed his own advice and read the entire thread
[Fire Original Android Development] jbraney:
That guy doesn't know what he was talking about. Yes, two people DID brick their devices already, but they didn't flash BOTH the fastboot AND the preloader. That is what nobody has tested yet, and what we need. Go ahead. I don't know how exactly it's done, but I DO know nobody has done it yet and posted about it...

Not trying to insult anybody, just don't want us to lose a good opportunity, especially if you are 100% willing to brick since you already have a replacement coming...
[Fire Original Android Development] blueberry.sky:
I have to say it's a little amusing that you say read the thread. As others have pointed out the 2 attempts so far have been flashing fastboot only.

No one has tried flashing the preloader+fastboot yet.

Links to the two attempts without the preloader.

Post # 17 attempt 1.

Post #37 attempt 2.