yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] bmurphr1:
So what's the story, we need a guinea pig to flash just the preloader as well as fastboot? Somebody let me know so I can brick this POS and give Amazon a legitimate reason for returning the tablet for a replacement when I haven't even bricked it yet. :D

EDIT: This is the code I'm referring to:

adb push lk.bin /data/local/tmp/
adb push preloader_prod.img /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb shell "dd if=/data/local/tmp/preloader_prod.img of=/dev/block/platform/mtk-msdc.0/mmcblk0boot0"
adb reboot-bootloader
[Fire Original Android Development] blueberry.sky:
Yes, we do need someone to test flashing the preloader+fastboot. That code is correct.

Here are quotes from the two people who tried flashing the bootloader ("lk") only, maratd & kleydejong. You can see that they did not flash the preloader.
[Fire Original Android Development] bmurphr1:
Looks like I'm batting next as to flashing the preloader and fastboot together as mentioned in my code? I know this is a one in a million shot and I'm about to sacrifice my tablet to the Amazon Gods but IDGAF since I have another one coming Sunday via Amazon Prime's quick replacement service.

EDIT: I'm about to flash the preloader and fastboot together in one go...wish me luck.

---------- Post added at 07:20 AM ---------- Previous post was at 07:01 AM ----------

It's a no go flashing the preloader and fastboot...it bricked my device for good. The output said that both operations were successful, but after doing the bootloader-reboot my tablet went dead and is now bricked.

I hope this helps out anybody who's thinking that flashing both will give us the ability to launch TWRP. I don't mind donating this tablet to the Amazon Gods since my replacement arrives on Sunday, so that's why I went ahead and tried the flash mentioned earlier...I figured that was the closest we could get to be able to un-neuter fastboot and allow TWRP to be executed.
[Fire Original Android Development] blueberry.sky:
Damn. Now, for 5.1.1 devices we hang our hopes on getting kexec. I understand we need kexec to do a safestrap bootloader. Guess we do have FlashFire but it's risky without access to our own recovery to fallback on.

Big thanks bmurphr1.
[Fire Original Android Development] bmurphr1:
Not a problem...it didn't make sense to donate at least one fully working tablet back to Amazon when I could fully brick it in hopes that others could fastboot TWRP to flash custom firmwares to their cheap devices. :D
[Fire Original Android Development] blueberry.sky:
Did your Fire have bad pixels or were you just getting a replacement in hopes of getting 5.0.1?
[Fire Original Android Development] bmurphr1:
I wanted a replacement 5.0.1 so I chatted with Amazon and they pre-shipped the replacement tablet before receiving the "broken" one. I was surprised they actually had some on hand considering the backorders on the tablet alone go several days past Christmas, but I guess because I'm a Prime member my replacement was shipped out before everybody else gets their tablet. I have an e-mail confirming the delivery of the replacement tablet no later than December 20th.
[Fire Original Android Development] wuhoatu:
Not working with my son's fire.

adb remount
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found

Any ideas?
[Fire Original Android Development] theholycow01:
Probably drivers. Assuming you're on Windows, what do you see in Device Manager for the Fire?
[Fire Original Android Development] wuhoatu:
Not caused by drivers because all devices are OK. I do think that remount within adb shell windows is not always working. I manage to root with adb remount without running adb shell.
[Fire Original Android Development] jco23:
just wanted to chime and say thanks. I followed the steps from the first post on my son's fire that was rooted on 5.0.1 (which automatically took the OTA to 5.1.1 to lose root). I was able to reapply root successfully, and very easily.
[Fire Original Android Development] xenokc:
deleted
[Fire Original Android Development] Neffy27:
This sounds similar to my initial experience. Read my post #71.
[Fire Original Android Development] xenokc:
Have installed exactly per instructions and having issues. Am able to get to root adb shell just fine. When pushing the files and running the script, it runs fine with no errors. But when it reboots is stuck on 'fire' boot screen (over 30min). Am able to get back into bootloader just fine and repeat steps. Also looked to see if the script did what it said and it did. Still stuck on 'fire' boot screen.

Suggestions?

Edit: I installed via Linux not Windows.
[Fire Original Android Development] bmurphr1:
Looks like Amazon delivered my replacement tablet a day earlier than expected...that's highly surprising considering it's less than a week away from Christmas. I opened up the new tablet already though and found out it's still on 5.0.1 so when I get ready here this evening I'll be able to fastboot TWRP and flash CM12 onto this el cheapo tablet and be rid of FireOS once and for all.
[Fire Original Android Development] rjdh2o:
I'm looking to do the exact same thing. Let us know how it works out.
[Fire Original Android Development] jbraney:
I have a question... Should I find some way to return my tablet (brick it, or do SOMETHING to it), so I can get a new one with 5.0.1 on it and get CM12.1? Or should I wait for a 5.1.1 fix... I don't know if anyone has any leads atm, but I haven't heard anything recently, and that bothers me. If anyone has leads they want to pursue, I'll wait... :P
[Fire Original Android Development] Dr.TheMaster:
You can flash SlimLP via FlashFire on rooted 5.1.1 .. And BTW CM12.1 devs are working on it..

Kindly press thanks if I helped :)
[Fire Original Android Development] jbraney:
Ok... I want to wait specifically for CM12.1, so I'll just wait. However, do you know what leads they are following now? I haven't heard anything on any of the forums since the preloader + fastboot failed... Just trying to follow everything here! :P
[Fire Original Android Development] Dr.TheMaster:
you can see what they are talking about in the main CM12.1 thread :D
[Fire Original Android Development] blueberry.sky:
For CM12.1, they are looking into getting CM to flash properly via FlashFire.

For TWRP recovery & safestrap bootloader devs need to get kexec working. Anyone with experience in kexec or android SMP? Seems there is a SMP problem, cpu-cores not reseting. thread
[Fire Original Android Development] wuhoatu:
I just got my son's Fire rooted and flashfire SlimLP 2.3 and everything working fine. He is happy now.
[Fire Original Android Development] ggow:
[MENTION=7104332]k4y0z[/MENTION]

- CM-12.1 is now flashable from FireOS 5.1.1 using FlashFire
[Fire Original Android Development] k4y0z:
Great, thank you very much!
[Fire Original Android Development] k4y0z:
looks like you didn't boot with root privileges.

Did you boot with

fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue

and no reboot after that?

what did fastboot respond to the commands?

It should look like this:

...
(bootloader) APPEND KERNEL CMDLINE

OKAY [ 0.005s]
finished. total time: 0.005s

resuming boot...
OKAY [ 0.002s]
finished. total time: 0.002s
[Fire Original Android Development] besweeet:
So what are the recommended FlashFire steps? The information seems to be scattered.
[Fire Original Android Development] Pond-life:
Sounds like you made a typo when you did it by hand then

---------- Post added at 12:53 AM ---------- Previous post was at 12:49 AM ----------

As in http://xdaforums.com/amazon-fire/general/how-to-flashfire-app-to-install-rom-t3269839

with the rom of your choice with the gapps they suggest in that rom's thread (though where it doesn't specify the size: minigapps or smaller.)
[Fire Original Android Development] NeeKoNeeKo:
Im having this exact same issue, any ideas?

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
...
(bootloader) APPEND KERNEL CMDLINE

OKAY [ 0.008s]
finished. total time: 0.010s

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>fastboot continue
resuming boot...
OKAY [ 0.004s]
finished. total time: 0.004s

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb wait-for-device && adb shell
root@ford:/ # exit
exit

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb remount
remount succeeded

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb push files\libsupol.so /data/local/tmp/
2026 KB/s (170232 bytes in 0.082s)

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb push files\root_fire.sh /data/local/tmp/
321 KB/s (1976 bytes in 0.006s)

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb push files\su /data/local/tmp/
3679 KB/s (75364 bytes in 0.020s)

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb push files\Superuser.apk /data/local/tmp/
3174 KB/s (5904943 bytes in 1.816s)

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb push files\supolicy /data/local/tmp/
2925 KB/s (29972 bytes in 0.010s)

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb shell chmod 777 /data/local/tmp/root_fire.sh

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb shell /data/local/tmp/root_fire.sh

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
...
(bootloader) APPEND KERNEL CMDLINE

OKAY [ 0.008s]
finished. total time: 0.010s

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>fastboot continue
resuming boot...
OKAY [ 0.004s]
finished. total time: 0.006s

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb wait-for-device && adb remount
remount succeeded

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb shell /system/xbin/su --install

C:\Users\N\Downloads\root_fire_5thGen_2015\root_fire>adb reboot
[Fire Original Android Development] k4y0z:
It seems like the root_fire.sh script may break stuff, when executed more then once.

I'ts probably best to reinstall fire-os and try again:

http://xdaforums.com/amazon-fire/orig-development/howto-how-to-restore-frimware-device-t3238740
[Fire Original Android Development] NeeKoNeeKo:
I dont have a sideload option, pressing vol key + power will take me directly into fastboot mode.. no menu to chose sideload according to that guide, i can see the device in recovery only
[Fire Original Android Development] sd_shadow:
then use other volume button
[Fire Original Android Development] NeeKoNeeKo:
D'oh

Thanks! :D :D
[Fire Original Android Development] Twilla:
I know this is probably the dumbest thing you've ever heard, but .. I can't get it to reboot into bootloader.

When I do the adb reboot-bootloader, it installed drivers on my windows and sounded like the kindle connected and then disconnected, but then the device disappeared from adb, and nothing happened on my kindle. It's just all black until I restart it. I tried to look everywhere if I needed a custom "bootloader"(I thought they already had one?) or something, but I can't find anything about this. I'm sorry, am I doing something wrong?

I know I probably shouldn't be the type to do this sort of thing since I can't even figure that out, but I do like custom roms, so I'm trying to do this. I'd really appreciate if anyone had any idea as to what I'm doing wrong!

I'll keep trying to figure it out... hmm. Sorry, ignore this post I suppose haha. Maybe I'll reset the kindle? Or something? Hmm.

Edit: I just noticed that when I plug this in, ADB interface comes up in device manager for "HTC Dream", but normally it says "Android composite ADB interface" if that matters ><

MT65xx Preloader is the device that connects and instantly disconnects when i reboot-bootloader if that helps as well.
[Fire Original Android Development] sd_shadow:
7in 5th gen fire?
[Fire Original Android Development] Twilla:
8in Kindle Fire HD 5th gen, I believe.

http://www.amazon.com/gp/product/B00S5HFVGI?redirect=true&ref_=kin_comp_dk_th_img
[Fire Original Android Development] sd_shadow:
No Root for The hd10 or hd8

---------- Post added at 09:13 AM ---------- Previous post was at 09:13 AM ----------

http://xdaforums.com/showthread.php?t=3205447

[Help Thread][Amazon Fire HD 8 and HD 10] Ask Any Question, Noob Friendly
[Fire Original Android Development] Twilla:
Well, I feel silly now! Thank you!

I think I'll trade this in, then. 8in was a little big for me anyways, haha.
[Fire Original Android Development] NeeKoNeeKo:
Is there a way to recover a bricked device that is without battery??

Mine doesnt seem to charge.. and i was in the process of sideloading the stock
[Fire Original Android Development] CrazyDelta:
Hi Guys,

I just want to get some assurance that this is the root process (in first post) that I need to follow for my Amazon Fire 7 (5.1.1). I want to install Cyanogenmod 12.1 so am I right to assume I go thru the steps from first post, then install Cyanogen Recovery and then flash Cyanogenmod 12.1? Sorry for sounding noobish, but it has been a long time since I rooted a phone or tablet. Mostly it was a simple tool that I used so this time I am a bit lost here. Your advise would be appreciated.

Thanks.
[Fire Original Android Development] to_b:
Yes, this is the right way to root your device.

Unfortunately it is not possible to install a custom recovery and since 5.1.1 it is no longer possible to fastboot into a custom recovery temporarily.

You have to use FlashFire to install a custom rom (cm-12.1 or slimlp).

Just search in the corresponding threads for "FlashFire".

Place the Files (custom rom, gapps, su-package) on internal storage!
[Fire Original Android Development] Pond-life:
Well there is a tool for root (and more) http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
[Fire Original Android Development] CrazyDelta:
HI, Thanks for that. If that a preferred method? Are there any specific differences/downsides to either method?
[Fire Original Android Development] sflesch:
So, I rooted and added Google Play. For some reason, the device shows under the Android Device Manager, but not as an available device to install on from the apps.

Any ideas? I changed to my wife's account and back to mine with no luck.
[Fire Original Android Development] glate:
related - make sure you use pico or nano gapps or you can have a really bad time
[Fire Original Android Development] sd_shadow:
Stock rom doesn’t show up, no fixing that I know of
[Fire Original Android Development] to_b:
Reminds me of the efuse in the fire tv firmware update:

Maybe [MENTION=3991724]rbox[/MENTION] can tell if this could be the same kind of protection?
[Fire Original Android Development] rbox:
If you tried to flash an old bootloader on a device with an updated one, and afterwards it was bricked, then it was probably downgrade protection.
[Fire Original Android Development] bmurphr1:
rbox hit it on the head....I knew I was going to brick that first Kindle before I ever put those commands in, and I didn't care because I already had the replacement tablet 48 hours away from being delivered to my house. I wanted a Kindle with 5.0.1 because $35 for a Kindle is just a ridiculously awesome price considering the hardware, but FireOS is just barely mediocre for my needs. Being able to run CM12 was my primary reason for purchasing the Kindle in the first place, and once I figured out that the tablet was automatically setup under my Amazon Prime's account information (never seen this one before) and saw the updating screen I pretty much already knew at that point I was getting screwed one way or the other. This taught me a valuable lesson when it comes to Android devices...don't EVER allow them to automatically update themselves on stock firmware.

Right now I'm just using my KFFOWI running CM12 to watch movies at the gym, and I consider it a 'throw-away' tablet meaning if somebody were to try and steal it from me I'd just laugh and hand it to them. My real tablet is a Venue 8 Pro 2GB RAM model w\ Pen + Genuine Keyboard Case running Windows 10, and I use a MS Surface Pro 2 with 8GB of RAM and a 256GB SSD as my work tablet.
[Fire Original Android Development] gwhite5:
Fire tablet recovered with the new lk binary!

Remove this and prevent other people from bricking their Fires!

The preloader doesn't dd successfully (Operation not permitted). I have to keep my Fire on until I can find the new lk.bin or working preloader install instructions. EDIT: nope, I definitely need the stock 5.1.1 lk.bin.

What's wrong with using SP Flash Tool by the way? I thought that was the de facto MTK flash tool?

I should have taken a back up of my lk.bin before doing this. I didn't read further in to the post (where I would have found that nobody has tried it). If anyone can provide the lk.bin, I could resurrect my tablet. It's impossible for me to get a replacement I'm afraid.

I have a device with the product name 'Ford'.
[Fire Original Android Development] k4y0z:
I have updated the post.

Also the new lk should be available in the official update-bin:

http://kindle-fire-updates.s3.amazo...ate-kindle-global-37.5.4.1_user_541112720.bin
[Fire Original Android Development] gwhite5:
Thanks. Somebody uploaded the lk binary anyway, but I didn't know you could download from Amazon the update manually!
[Fire Original Android Development] sd_shadow:
[Index]Amazon Fire 7" - 5th Gen-2015
[Fire Original Android Development] pateken:
i have root the kindle 2015 5.11 and i want install recovery twrp. help me tanks.
[Fire Original Android Development] sd_shadow:
twrp cannot be installed
[Fire Original Android Development] pateken:
There is no procedure to install recovery alternatives on kindle 5.11?
[Fire Original Android Development] pateken:
i have installed slimrom. its ok. but i want install twrp recovery.
[Fire Original Android Development] sd_shadow:
can't be done
[Fire Original Android Development] demlv:
You have the Fire OS 5.11 bootloader, so no TWRP for you. For the earlier 5.01 version of the bootloader, TWRP can be BOOTED on the device and used to install roms/wipe partitions/etc., but it has to be booted from a PC each time you want to use it. TWRP cannot be permanently INSTALLED on this device. :(
[Fire Original Android Development] pateken:
I tried to install TWRP with ROOT Rashr flash tools but the device shuts down.
[Fire Original Android Development] sd_shadow:
twrp cannot be installed on KFFOWI /Ford
[Fire Original Android Development] pbailey212:
You can not install a costom recovery , you have a locked bootloader
[One (M8) Q&A, Help & Troubleshooting] jshamlet:
This seems like one of those "two steps forward, one step back" kind of deals. I have the developer edition Marshmallow build running, and on the upside, it allows you to select what function you want the USB port to support. You can have it charge only, act as a file transfer port, tether, etc. You can even choose whether or not to attach a virtual CD drive (for the sync app)

The only thing is, you can only do one at a time! Lollipop would let me transfer files and maintain a tethered connection at the same time. I'm hoping there is an option to let you tether natively while also supporting file transfers, as I tend to use both simultaneously a lot.

-Seth
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] firsttimee:
need some help! how do u unbrick it?

what can i do to fix it?

can i go take it in anywhere?
[Galaxy S6 Edge+ Q&A, Help & Troubleshooting] arcane613:
That depends on how bricked it is. If you can get to recovery and flash, then you can do it that way.

If you are FRP locked or can't get to recovery then you need download mode. Can you get into download mode? With the device off, try holding volume down+home and then press power. Release all when screen comes on.

If you have to recover via download mode, you need an Odin tar file. Use Odin 3.10.7. I finally found the Odin tar files for 928W8 yesterday. I also have that variant phone. I linked to the firmware HERE. I had to pay for access to downloads on that site though. It still isn't listed on sammobile..

I do have OK5 for Rogers downloaded, and have 10Mbps upload, I could upload it to Google Drive.. I think you can change the CSC, but I haven't tested.. I'm on a custom ROM, I just wanted to have an odin file in case, and also to update my modem..
[One (M9) Accessories] bradleyh10:
Hello,

I've just got an M9 and am happy with it. Thought I'd make the most of the quick charge tech so I brought a QC2.0 charger from amazon:

An Aukey Quick Charge 2.0 42W 3 Ports USB Desktop Charging Station [sorry, can't post links yet]

Reading the reviews, and also other threads on here, that people with M9's using QC charge very fast but mine just isn't.

Right now it's taken just oven an hour to charge to full from 49%. Nothing like what other people are saying.

I've contacted the supplier of the charger and they've just sent me another one but it's exactly the same. How should I continue testing? How would I determine if it is the Phone?

The only issue I can potentially identify is that after around 75%-80% the rate of charge seems to drastically drop off.

Any insight would be great !

Stock ROM [EE - UK]

Android 5.1

Kernal 3.10.49

Thanks
[One (M9) Accessories] deakelem:
Are you stock? if not what rom and kernel are you using?

regarding the drop off after 80% thats perfectly normal for QC, it will be quite rapid up until about 80+% then sort of trickle.
[One (M9) Accessories] bradleyh10:
Stock [EE - UK]

Android 5.1

Kernel: 3.10.49

Pre - 80% its charging about 1%/minute. Which seems much slower than other people describe.

Post - 80% its about 0.3%/minute
[One (M9) Accessories] mike.s:
Did it come with a USB cable, and are you using that one? In order to take full advantage of quick charging, heavier gauge and/or short cables are best. And yes, the closer to 100%, the less difference in charging rate.
[One (M9) Accessories] bradleyh10:
Hello,

Yes it came with a cable which was high quality, which I'm also using.

I did have a thought if it was because I was charging it with the phone turn on, but just did a test with it turned off and the results were very similar
[One (M9) Accessories] 1337jay:
Are you using the QC 2.0 port? Because that thing has only one.

I'm always using official chargers, same for my M9..works very well.
[One (M9) Accessories] bradleyh10:
Hi, Yes using the correct Orange QC port on this charger.

Perhaps you could share what sort of charging times you're getting with your official charger?
[One (M9) Accessories] bradleyh10:
Also worth adding there may be an 'offical' HTC charger but all that should matter is if it's Qualcomm QC2 licence device, which it is and is listed on the Qualcomm website

So I'm back to my original question, how can I tell if its the phone?

It would also be good if anyone with an M9 and QC2 could post their charging times

Thanks
[One (M9) Accessories] Deathmeter:
you could check with the app ampere and see what youre getting with different cables and chargers
[One (M9) Accessories] Deathmeter:
Something else to try would be disabling HTC's car app as it causes issues with charging. Open the car app>go to settings>disable all settings.

Go to phone settings>apps>car>uninstall updates>disable.
[One (M9) Accessories] outrage_uk:
I use a Choetech 60W Quick Charge 2.0 for mains, and a Choetech 51W Quick Charge 2.0 Car Charger for the car. The car one is ideal because it has a blue LED for normal power which changes to green when it's using Quick Charge, to give you an indicator it's working.

I get between 1% and 2% charge a minute depending on how hot the battery is and what is running (Viper 4.0.1 ROM - Android M). Usually around an hour and half for a full charge.

Yours doesn't seem excessively slow - make sure you try when your battery isn't hot and when no apps are running in the background. Maybe useful to run the Ampere app to see what the current battery drain is before you start... ideally should be 200ma or less.

Drop off after 80% is normal, ~1% every 2 minutes.