Database Develop

Gear Live Stock Firmware Image - 24JUL14 & Bootable Root ADB image

Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.

Thank you Adam and I suppose I can speak for every Live owner here when I say we really do appreciate it. I can't wait to start tinkering with it and lets hope we can get that WatchFace API soon. I'm dying for a more sophisticated looking face with a more blue and silver brushed metal look to it. Can't find one anywhere. Thanks again Adam. What would we do without u?
---------- Post added at 09:03 PM ---------- Previous post was at 09:01 PM ----------
Oh and if you add any more green text to your display... just go head on and Follow The White Rabbit....

Sweet Adam, you made a lot of progress since Friday

thanks for all this work! Now to start working on port for Gear 1... Haven't messed with this stuff since HD2 days....Ugh.
Chris

I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.

Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Contacting now.

Dees_Troy said:
I'd like to get someone to test some TWRP images for me. Need someone that's set up to use adb and fastboot and has basic working knowledge of how to use them. Find me in #twrp on Freenode.
Click to expand...
Click to collapse
Incase you missed the link on iirc, http://pastebin.com/5rUD9X0t

Annnnnd this is why i ditched Samsung after the SGSII, Im so glad I got the G Watch instead.
Seems to be a Thing now that Samsung is playing hard to beat with factory images and source, Devs should jump on some form of anti Sammy bandwagon because although this is sure a great feat in hacking but for people here who Crack flash and test stuff for devs on their devices this is a pain and slows down evolution.
if sammy continue with his imagine all the ideas they can't steal from the clever devs here at XDA, I say screw them and buy devices from companies who truly keep android open source

Can this be used in Odin?

Krunk_Kracker said:
Can this be used in Odin?
Click to expand...
Click to collapse
No, it is a fastboot image

How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!

Joe0113 said:
How do I actually use this!? Sorry for the noobness haha. I understand I have to unlock my bootloader first, but how do I actually obtain root after I do that? TIA!
Click to expand...
Click to collapse
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.

Boot into TWRP
Mount the system
Use the TWRP terminal emulator
rm /system/app/SuperSU.apk
OK so these are the instructions I was given to root. I am currently sitting in TWRP, system was mounted, when I hit reboot system, it told me I wasnt rooted, so I swiped to root...rebooted back to recovery...clicked terminal command which opened up a directory telling me to choose a starting folder :|
this is where im lost.. Also how do I type anything into the terminal commands once I get it open since theres no keyboard lol
Manually removed it using the file manager though its called superuser.apk and it works..Guess im rooted given I can use the rebooter that Adam posted!

KMyers said:
Hello,
As these are ADB/Fastboot packages, you will need do the following
1) Setup the Android SDK (for ADB and Fastboot)
2) Unlock the bootloader
3) Use the "fastboot boot <filename.img>" (replace this with the location of the extracted content from the zip file)
I honestly would recommend against trying this unless you are a bit seasoned as breakage is possible.
Click to expand...
Click to collapse
Do we have to do each individual img? I downloaded the file, extracted it and theres 23 img files lol. I have yet to do anything with a .tar file also
Im debating on returning to stock and taking the watch back to wait for the 360,

Instructions on returning to Stock??
Could someone please post some instructions on returning to Stock? I flash the Octa Rom and did not make a back up and then tried returning to stock by flashing the system.img and it would not boot. I have returned to stock with Nexus devices in the past but looking at the stock firmware image files here I'm not getting how this works. PLEASE HELP

AdamOutler said:
Hi guys, I just managed to pull the stock firmware image off the Sprat, with the assistance of @Dees_Troy. We've been working on this for a few days. Lots of highs and lots of lows. Lots of hardware glitches, device overheating, reading kernel logs to troubleshoot problems... And you know what? All of it could have been avoided if Samsung had released a stock image.
Without any further ado, though, you can find a factory image for this device here: https://builds.casual-dev.com/index.php?dir=random/sprat/
Here is the first custom kernel created for this device. It's mostly dees troy's work, he compiled it and made it operate, but I had to reimage it a few times to make it operate properly. If you absolutely need root for checking something out right now, you can fastboot boot this image and get it.
If you'd like to pull your OWN firwmare including the EFS(serial info) for the device, you can use this command in adb root shell after booting the above image.
Code:
cd /dev/block/platform/msm_sdcc.1/by-name;
f=`ls`;
for f in $x;
do
dd if=$f of=/data/local/tmp/$f.img;
done;
rm /data/local/tmp/userdata.img
exit;
adb pull /data/local/tmp/
the contents of the entire device will come to your computer
now clean up the temp folder.
Code:
adb shell rm /data/local/tmp/*
You now have the firmware above + EFS data.
[rant]
I mean seriously.. Samsung, WTF? I've been working on this for 5 straight days now.
Why did I have to go through the process of keeping this Quad-core watch cool while i tinkered with UART, and continuously rebooted it?
Why did I have to wade knee deep in your kernel problems to get this done?
Is it becoming apparent that Samsung doesn't want people messing with their "open devices"? I mean, I can think of no other reason they haven't released a stock image for a device which can be destroyed with a bad flash.
[/rant]
Either way, we finally have a stock image and that means Dees_Troy can release a TWRP, ROM devs can begin working with the system, and those in need of stock firmware now have access to it. Pretty good news if you ask me.
Click to expand...
Click to collapse
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?

Tomsgt said:
Hi adam i have a Gear Live with Build KMV78Y and when i fastboot boot rootADB.img my device freezes at the bootloader screen and never reboots. i have to adb reboot to get out of it. which is the funny part since i am still on the bootloader screen but adb works. any idea of what is going on here thanks.
Tom
Edit Never Mind i got it just wasnt expecting it to work this way. pretty funny temp root. why not make it perminant root?
Click to expand...
Click to collapse
Hiyas Tom..did you really get your Gear?!?!?!

Tower1972 said:
Hiyas Tom..did you really get your Gear?!?!?!
Click to expand...
Click to collapse
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up

Tomsgt said:
yes got it today and working on the Restore Tool like my LG G Watch restore tool. right now its tested and working just cleaning it up
Click to expand...
Click to collapse
That's the best news I've heard all day!

Tower1972 said:
That's the best news I've heard all day!
Click to expand...
Click to collapse
Samsung Gear Live Tool is up click here and enjoy

[Help Thread][7" Kindle Fire HD](2nd Gen 2012) Ask Any Question, Noob Friendly

[SIZE=+2]This thread has been created
for
Questions & Answers/Troubleshooting[/SIZE]​[SIZE=+2]Specific to[/SIZE]
7" Kindle Fire HD - 2012​
Please feel free to share issues, questions and offer help. Noob questions are welcomed.
It is always best to use the Thanks button , in lieu of simply posting "Thank you".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please keep discussion focused, on questions pertaining to this Device
List of supporters@sd_shadow
...
...
...​To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @.
If you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible of posting there, you may post here. Thank you!
Supporters: If you want to be put on or off the list, just make a request here in the thread!
Before posting anything, I strongly advise you to read
Forum Rules
[GUIDE] - XDA New User Guide - Getting started on XDA
XDA Tour
Fire Index: Which Amazon (Kindle) Fire Do I have? There are several Amazon Fires. Be sure you know which one you have
[Index] Amazon 7" Kindle Fire HD, 8.9" Kindle Fire HD, Kindle Fire 2
Frequently Asked Questions - 2nd Generation Kindle Fires
[REF]All Things About Kindle Fire HD 7"
Please look for a similar [HELP THREAD] when visiting another device forum.
If you would like to create a similar [Help Thread] please Click Here.
​

[SIZE=+3]Frequently Asked Questions[/SIZE]
[SIZE=+2]Kindle Fire HD 7 (2012)[/SIZE]​
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. [/SIZE]
[SIZE=+1]Q1: How do I tell if i have a Kindle Fire HD 7 (2012)?[/SIZE]Kindle Fire HD 7" (2012) has Power and volume buttons on the sides, Front-facing HD camera.​
[SIZE=+1]Q2: What is the ........................................................................................................?[/SIZE]Replace this block of text with a short answer for the above question. If the answer is complicated or otherwise lengthy, avoid the temptation to provide a full answer here. If the answer is truly that involved, this should be answered in another thread outside of this document. The answer then should provide a brief summary or overview and direct the reader to the document providing a full coverage of the topic.​[SIZE=+1]Q3: Why does the ........................................................................................................?[/SIZE]Replace this block of text with a short answer for the above question. If the answer is complicated or otherwise lengthy, avoid the temptation to provide a full answer here. If the answer is truly that involved, this should be answered in another thread outside of this document. The answer then should provide a brief summary or overview and direct the reader to the document providing a full coverage of the topic.​*​Forum Rules | New Users Guide | XDA Tour | Report Posts​A special thanks to everyone who contributed to the production of this FAQ​

Index
Kindle Fire HD 7" - Power and volume buttons on the sides, Front-facing HD camera
Model #:
Serial #
D025------Kindle Fire HD 7" 16GB
D059------Kindle Fire HD 7" 32GB
Codename: Tate
Software: Amazon:7.5.1 - Based on Android OS 4.0.3

Glad you're here to help. Like 6 weeks ago I attempted to return to stock. It was my understanding that I needed to downgrade twrp to flash the image (which I did easily . In the other thread it specified to wipe system first (REALLY wish I had thought that one through). Now I can't push ANYTHING to the SD card. No adb, no USB mtp.
I've tried updating drivers on 3 different computers, (windows 7, Windows 10, and yosemite) Tried unbreakable tool and kfhd restore tool.
All I can do is manually boot to twrp.
I realize there's probably more details needed but I'm strapped for time (on break) I was just ? to see your thread.
Any attempts to help will be profoundly appreciated! Thanks.

KLit75 said:
Glad you're here to help. Like 6 weeks ago I attempted to return to stock. It was my understanding that I needed to downgrade twrp to flash the image (which I did easily . In the other thread it specified to wipe system first (REALLY wish I had thought that one through). Now I can't push ANYTHING to the SD card. No adb, no USB mtp.
I've tried updating drivers on 3 different computers, (windows 7, Windows 10, and yosemite) Tried unbreakable tool and kfhd restore tool.
All I can do is manually boot to twrp.
I realize there's probably more details needed but I'm strapped for time (on break) I was just to see your thread.
Any attempts to help will be profoundly appreciated! Thanks.
Click to expand...
Click to collapse
Can you still get to twrp?

sd_shadow said:
Can you still get to twrp?
Click to expand...
Click to collapse
Yes. That's all I can do. Not home but believe I'm running v 2.7.0.0
---------- Post added at 12:48 PM ---------- Previous post was at 12:40 PM ----------
I've had time to think about it and I doubt hashcode would make a mistake like telling people to wipe system. And if he were mistaken there would be a LOT of people in my situation. So I believe what sets me apart is that my recovery is too old. The right drivers aren't present and I can't use adb as a result.
I CAN get this into Factbook both with a factory cable and with a regular one (the latter only works on Mac it seems). However, on Windows the restore tools both say Fastboot is not recognized command. I believe I tried flashing the updated twrp with Fastboot on mac but for some reason it didn't work.

KLit75 said:
Yes. That's all I can do. Not home but believe I'm running v 2.7.0.0
---------- Post added at 12:48 PM ---------- Previous post was at 12:40 PM ----------
I've had time to think about it and I doubt hashcode would make a mistake like telling people to wipe system. And if he were mistaken there would be a LOT of people in my situation.
Click to expand...
Click to collapse
Wiping system is necessary to install a new system stock or custom
So I believe what sets me apart is that my recovery is too old.
Click to expand...
Click to collapse
possibly do you know the full file name of current recovery?
The right drivers aren't present and I can't use adb as a result.
Click to expand...
Click to collapse
What error(s) are you getting?
I CAN get this into Factbook both with a factory cable and with a regular one (the latter only works on Mac it seems). However, on Windows the restore tools both say Fastboot is not recognized command. I believe I tried flashing the updated twrp with Fastboot on mac but for some reason it didn't work.
Click to expand...
Click to collapse
"Fastboot is not recognized command." is a window issue not Kindle issue

Good info. Unfortunately I'm at work. But hopefully to nite I'll get what you're asking for. Really appreciate the help!

@sd_shadow
The current recovery is TWRP v2.7.0.0
I provided all the info I can think of at the moment. It's been about a month since I tried anything so my memory is a bit fuzzy. If you need anything specific please let me know. Bascially all I want to do is push any rom (custom or stock to this). I have the second bootloader and twrp working. I think MAYBE a newer version of TWRP may solve the driver issue. But I know I tried flashing twrp through fastboot and it din't work. I believe it just hung with no error listed.
Thought I might be on to something. I went into device manager and noticed the option to install legacy drivers. Both android and kindle show up so I got excited but it was short llived... Both attempts yielded they got installed but may not work. Sure enough they didn't. ��
Updated when in twrp over USB I can see kindle and now 3 android composite add interface. But they have a yellow triangle on them.
If I try to connect over add it says list of attached devices but show nothing. I tried mounting system but that does nothing
Clicking on Android in device manager I get this device cannot starts code 10

I spent a few hours trying different things and this seems to be my best bet (or at least the next thing I try). Can't do it tonight though because the windows pc I have is running adb 15 second installer and I don't have everything I need to complete it. If you or anyone else knows an easier way please share. Otherwise I'll setup sdk tools when I have a chance. Hopefully some time tomorrow. I'd prefer to do it on my mac because this pc isnt the best and really slowed me down tonight.
http://www.jayceooi.com/how-to-install-kindle-fire-adb-usb-driver/

KLit75 said:
I spent a few hours trying different things and this seems to be my best bet (or at least the next thing I try). Can't do it tonight though because the windows pc I have is running adb 15 second installer and I don't have everything I need to complete it. If you or anyone else knows an easier way please share. Otherwise I'll setup sdk tools when I have a chance. Hopefully some time tomorrow. I'd prefer to do it on my mac because this pc isnt the best and really slowed me down tonight.
http://www.jayceooi.com/how-to-install-kindle-fire-adb-usb-driver/
Click to expand...
Click to collapse
You have used the preferred driver from here Kindle_Fire_HD_ADB_Drivers.zip
What is your windows version?
Twrp should connect to the Mac, without issue, using mount usb or mtp.

sd_shadow said:
You have used the preferred driver from here Kindle_Fire_HD_ADB_Drivers.zip
What is your windows version?
Twrp should connect to the Mac, without issue, using mount usb or mtp.
Click to expand...
Click to collapse
Windows 10
I have NOOO idea how but I connected with mac. I swear to you I've tried connecting over adb before(MTP still didn't work btw). But I ran some basic commands with twrp mounted to SYSTEM, ran "adb devices" and it shows up. (I had tried SEVERAL variations of this before tonight)
Except instead of saying tate like it used to it had a string of letters/numbers then just said "recovery". Might be what it said before when in TWRP. I used to mostly use MTP when transferring files.
I was able to push the only amazon stockish files I could get 7.41 rooted+su from Hashcode. I also pushed updated TWRP and open apps for CM 12.1. Unfortunately adb push hung on that last one and then adb was gone. Couldn't connect. I bit the bullet and just flashed amazon and it worked. Just did this like 5 minutes ago so haven't tested root, recovery or anything else. I was intending on buying a kids case for this and letting my toddler son use it. We have prime and a lot of books i can access. So I might stay here but would like to get a newer version. Is there an easy way to get a later version of stock? I hate to give up root but he definitely doesn't need it and I've acquired several newer faster devices since I bought this a few years back.
Thanks a lot btw! I had sort of given up on this then I saw your thread. Just having someone to answer questions was enough to keep trying.

KLit75 said:
Windows 10
I have NOOO idea how but I connected with mac. I swear to you I've tried connecting over adb before(MTP still didn't work btw). But I ran some basic commands with twrp mounted to SYSTEM, ran "adb devices" and it shows up. (I had tried SEVERAL variations of this before tonight)
Except instead of saying tate like it used to it had a string of letters/numbers then just said "recovery". Might be what it said before when in TWRP. I used to mostly use MTP when transferring files.
I was able to push the only amazon stockish files I could get 7.41 rooted+su from Hashcode. I also pushed updated TWRP and open apps for CM 12.1. Unfortunately adb push hung on that last one and then adb was gone. Couldn't connect. I bit the bullet and just flashed amazon and it worked. Just did this like 5 minutes ago so haven't tested root, recovery or anything else. I was intending on buying a kids case for this and letting my toddler son use it. We have prime and a lot of books i can access. So I might stay here but would like to get a newer version. Is there an easy way to get a later version of stock? I hate to give up root but he definitely doesn't need it and I've acquired several newer faster devices since I bought this a few years back.
Thanks a lot btw! I had sort of given up on this then I saw your thread. Just having someone to answer questions was enough to keep trying.
Click to expand...
Click to collapse
With Win 8, 8.1 & 10, Disabling Driver Signature Enforcement is likely needed.
For those with Windows 8.1 or 10
Watch [Video] How to disable driver signature enforcement - Windows 8.1 & 8
or How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
and try
Open the charm bar and go into Settings and at the bottom click on Change PC Settings.
Go to the update and Recovery on left then Recovery
Advanced Startup > restart now
Choose the Troubleshoot option followed by Advanced options.
Choose Startup settings then on next screen click on ‘restart’.
Select option
Disable driver signature enforcement
Windows 8.1 will now reboot and you can go ahead and use the Kindle_Fire_HD_ADB_Drivers.zip
more here https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/all​.

I signed up for free time and so far the only difference I see between 7.41 and a newer version would be inability to download prime titles. Of course this is my only amazon product running stock so I have nothing to compare it to. It's strange that the newest version on Hashcode's thread disappeared but older versions are still available. Usually it's the opposite.

KLit75 said:
I signed up for free time and so far the only difference I see between 7.41 and a newer version would be inability to download prime titles. Of course this is my only amazon product running stock so I have nothing to compare it to. It's strange that the newest version on Hashcode's thread disappeared but older versions are still available. Usually it's the opposite.
Click to expand...
Click to collapse
Download Information for OS 7.4.3:
http://goo.im/devs/Hashcode/tate/kfh...n-os-7.4.3.zip
md5sum: 45e687e8e85975348f81f5cbfc8358ac
The reason file is gone is the goo.im site is gone, I will look for a different source

found it on @Tomsgt 's site
kfhd7-amazon-os-7.4.3.zip
http://rootjunkysdl.com/?device=Kindle Fire HD 7in

sd_shadow said:
found it on @Tomsgt 's site
kfhd7-amazon-os-7.4.3.zip
http://rootjunkysdl.com/?device=Kindle Fire HD 7in
Click to expand...
Click to collapse
Thanks. Think I did stumble upon that when I first thought about return to stock. But I'm not sure...
That page shows stock. I think the version I have, 7.4.1, is a modded version of stock. I also see recovery. Zip which is what I need to go full stock. But I don't know if flashing that in twrp will get me to stock.
After struggling just to push a file I don't want to take any chances. If there's a clear way of doing it I'm all in. I think this device will be eligible for the OS 5 update so that'd be my motivation to sacrifice root.
A little off topic--free time is pretty cool if you have prime but adding locally stored videos is a hassle (haven't been able to do it) I'm sure amazon did this deliberately but there must be a workaround.
I was able to download prime videos. Unlike on my android phone, they need to be added to the library first.

Can anyone recommend a fastboot recovery cable for a 2012 kindle fire HD 7 (tate)?

FBis251 said:
Can anyone recommend a fastboot recovery cable for a 2012 kindle fire HD 7 (tate)?
Click to expand...
Click to collapse
Several links in my
What is a Fastboot Cable and Low Battery Options
written for Motorola Devices, but same cable.

I have added a
What is a Fastboot Cable? post to my Fire Index: Which Amazon (Kindle) Fire Do I have?

Bricked Fire 5th gen/bootloop

Hello,
I think i just bricked my Amazon Fire 5th generation.
I Installed CM12.1 using the flashfire method. Because I cant get amazon prime instant video to work, I decided to go back to stock.
I head over to this thread: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
As I can remember, I first wiped everything then installing the newest firmware 5.2.2 via sideload. Before I flashed to CM12.1, I came from fireos 5.2.2.
Now, my device is stuck in an bootloop. The screen is black all the time and I cant get the device back to work. If the device is connected to my pc, it showed up in device manager from time to time with unkown device, after some seconds it disapears and MT65xx Preloader shows up. Again after some seconds this disappears again and after some seconds the same happens over and over.
I cant force the device to stop that because it dosent do anything if i try to shut it down or trying to get into fastboot or recovery.
Is there any way to get the fire back to work?

Did you have amazon FireOS version 5.0.1 or 5.1.1?
If you had 5.1.1 then flashing 5.0.1 will brick it. And will cause your preloader to endlessly cycle as you describe. That "5.2.2" file Awesomeslayerg links to in his thread is 5.0.1, he really should have changed that post since anyone on 5.1.1 following his instructions will be hard bricked.
hAtE NeVeR dIeS said:
If the device is connected to my pc, it showed up in device manager from time to time with unkown device, after some seconds it disapears and MT65xx Preloader shows up. Again after some seconds this disappears again and after some seconds the same happens over and over.
Click to expand...
Click to collapse
I'm sorry to say, the preloader cycling like that shows that you have a hard brick (unrecoverable).

blueberry.sky said:
Did you have amazon FireOS version 5.0.1 or 5.1.1?
Could you have had 5.1.1 but accidentally flashed 5.0.1? That will cause your preloader to endlessly cycle as you describe.
I'm sorry to say, the preloader cycling like that shows that you have a hard brick (unrecoverable).
Click to expand...
Click to collapse
Before I flashed to CM12.1, I came from fireos 5.2.2. So I flashed Firmware 5.2.2 back.
Well, looks like I have to send the tab to amazon...

"5.2.2" is just the file name. We normally refer to it as FireOS 5.0.1, that is name amazon uses & system update menu displays. And it causes less confusion. I don't know why Awesomeslayerg uses "5.2.2" instead of 5.0.1.
hAtE NeVeR dIeS said:
I Installed CM12.1 using the flashfire method.
Click to expand...
Click to collapse
Did you ever try twrp? FlashFire is in beta & can be buggy. If you have 5.0.1 then you should really use twrp.

I downloaded the file linked in the post. Maybe It happens because I wiped everything before flashing the firmware and not after.

Not my fault for your guys mistakes. I'm also dome with the fire development as this community has a lack of common sense.

Awesomeslayerg said:
Not my fault for your guys mistakes. I'm also dome with the fire development as this community has a lack of common sense.
Click to expand...
Click to collapse
No problem dude. Things can happen so everything is alright. I am totally aware of that you are not responsible for damages that happen to the devices. Amazon is sending a new one. If i have to pay for this, its my problem not yours. You dont have to apologise.
But it will be great if you edit your thread and write in there, that the firmware you postet isnt fpr the 5.1.1. bootloader to prevent other users from making such a mistake.

hAtE NeVeR dIeS said:
Hello,
I think i just bricked my Amazon Fire 5th generation.
I Installed CM12.1 using the flashfire method. Because I cant get amazon prime instant video to work, I decided to go back to stock.
I head over to this thread: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
As I can remember, I first wiped everything then installing the newest firmware 5.2.2 via sideload. Before I flashed to CM12.1, I came from fireos 5.2.2.
Now, my device is stuck in an bootloop. The screen is black all the time and I cant get the device back to work. If the device is connected to my pc, it showed up in device manager from time to time with unkown device, after some seconds it disapears and MT65xx Preloader shows up. Again after some seconds this disappears again and after some seconds the same happens over and over.
I cant force the device to stop that because it dosent do anything if i try to shut it down or trying to get into fastboot or recovery.
Is there any way to get the fire back to work?
Click to expand...
Click to collapse
I
think many people have this problem and I am of those

I'm a new member but can't post links, so:
Go to YouTube > search: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet by Rootjunky.
It really helped me out when I bricked my fire 5th Gen.

stewie2806 said:
I'm a new member but can't post links, so:
Go to YouTube > search: How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet by Rootjunky.
It really helped me out when I bricked my fire 5th Gen.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=63943805
[Videos] Tutorials on how to root, flash roms and more on the Amazon Fire 5th gen.
Sent from my KFFOWI using Tapatalk

sd_shadow said:
http://forum.xda-developers.com/showthread.php?p=63943805
[Videos] Tutorials on how to root, flash roms and more on the Amazon Fire 5th gen.
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
thank you sir

I am looking into using SP Tools to restore the stock rom onto a bricked 5th gen. The stock roms do not have the scatter file needed to use SP Tools however there is a tool to create a scatter file but I don't have a working stock tablet to read. In addition if we can create a scatter file maybe 5.0.1 can be flashed via SP Tools onto a device that was previously 5.1.1. I would be willing to test this out if someone could create a scatter file from a stock Kindle fire 5th gen. Here is the link for the MTK tool that will create a scatter file. http://androidmtk.com/create-scatter-file-for-mtk-devices

FireBill said:
I am looking into using SP Tools to restore the stock rom onto a bricked 5th gen. The stock roms do not have the scatter file needed to use SP Tools however there is a tool to create a scatter file but I don't have a working stock tablet to read. In addition if we can create a scatter file maybe 5.0.1 can be flashed via SP Tools onto a device that was previously 5.1.1. I would be willing to test this out if someone could create a scatter file from a stock Kindle fire 5th gen. Here is the link for the MTK tool that will create a scatter file. http://androidmtk.com/create-scatter-file-for-mtk-devices
Click to expand...
Click to collapse
Won't let me create a scatter file on 5.0.1 stock, see attachment.

Didn't fare any better with the scatter file using CM rather than stock. Busybox is installed, SD card has 30GB free space, adbd insecure enabled. Sorry, not much else I know to try.

percussionking said:
Didn't fare any better with the scatter file using CM rather than stock. Busybox is installed, SD card has 30GB free space, adbd insecure enabled. Sorry, not much else I know to try.
Click to expand...
Click to collapse
Thanks, I appreciate you trying. It's always worth a shot

Can someone trying creating scatter file for 5.1.1? Maybe it works...hopefully it works.
Sent from my Moto G 2014 using Tapatalk

@lost_droid21
http://forum.xda-developers.com/showpost.php?p=65262531&postcount=13
same thing on 5.1.1

Kramar111 said:
@ost_droid21
http://forum.xda-developers.com/showpost.php?p=65262531&postcount=13
same thing on 5.1.1
Click to expand...
Click to collapse
It's not reading the MT8127 I also tried with the CM 12.1 however the software should read a firmware.info file and use that to create a scatter file. Problem is I don't see that in any of the update files. What we actually need is the OEM firmware file and not the updates and we probably won't ever see that! If we could try another backup from a rom manager that would provide a scatter or firmware.info file we may be on to something.

FireBill said:
It's not reading the MT8127 I also tried with the CM 12.1 however the software should read a firmware.info file and use that to create a scatter file. Problem is I don't see that in any of the update files. What we actually need is the OEM firmware file and not the updates and we probably won't ever see that! If we could try another backup from a rom manager that would provide a scatter or firmware.info file we may be on to something.
Click to expand...
Click to collapse
Thanks for trying that. It seems to be worse than I thought. I know it's probably going to be unlikely that we find a way to unlock the boot loader. So I guess we really need a OEM firmware file. Can anyone pitch in on that?
Sent from my Moto G 2014 using Tapatalk

I also bricked my Fire
Hi All,
I also bricked my fire while trying to downgrade to 5.0.1. Has anyone flashed ROM using any tool on bricked fire?

Root Acer Iconia One 8 B1-850?

Hello XDA,
I just purchased a new Acer Iconia One 8 B1-850 and was wondering if I could root it.
I see many posts on B1-810 and similar, but nothing for the B1-850.

CoreyGamingTV said:
Hello XDA,
I just purchased a new Acer Iconia One 8 B1-850 and was wondering if I could root it.
I see many posts on B1-810 and similar, but nothing for the B1-850.
Click to expand...
Click to collapse
same here
i want to root to enable the multi user option by updating the build.prop file, i've been able to connect with ADB but the device isn't visible in windows or mac (tried both) when you reboot into boot loader, in fact it doesn't appear to boot into boot loader it just seems to power off (when using ADB reboot command or choosing boot loader from the recovery menu) so i wonder if its locked out somehow??

Need it too. Did anyone find a way to root B1-850?
Thanks!

dtalas said:
Need it too. Did anyone find a way to root B1-850?
Thanks!
Click to expand...
Click to collapse
I too just purchased a B1-850 tablet, but I've figured out how to root it. Really quite simple. Just use Kingroot:
1.) Navigate to https://kingroot.net/ from your tablet
2.) Download the APK for android
3.) Install said APK (this requires you to have allowed installation from unkown sources in the "Security" panel of the settings menu)
4.) Load up the app and follow its instructions
5.) Reboot and try it out
For good measure, I would also unlock the "Developer Options" panel and allow USB debugging (adb access) and such; I did this before proceeding. You'll have to search for instructions on that yourself, its well documented.
This all worked for me this morning! Really looking forward to unlocking the potential of this cheapy tablet.

Kingroot worked first try, just swap their super user program with supersu. I am having trouble installing the xposed framework though if anyone has any tips.

I was able to root, now I need to install a custom recovery. CWM says this model is not in the supported list. Has anyone been able to install a recovery? I need NANDROID backup functionality.

I made a thread walking you through how to do it on this tablet in the guides area but just use flash fire for recovery and xposed install

Did the B1-850 hardware updated in anyway? I was able to root it in June 2016, but after a screen repair and factory reset and fresh rom from acer, king root and all others can't work. I'm stuck without any root options. Any idea?

Same here
Dylfaus said:
Did the B1-850 hardware updated in anyway? I was able to root it in June 2016, but after a screen repair and factory reset and fresh rom from acer, king root and all others can't work. I'm stuck without any root options. Any idea?
Click to expand...
Click to collapse
There was recently new firmware released for this tablet (08/24/16, Build #: AV0L0.RV09RC04.WW.GEN1), and a handful of updates (08/25/16, 08/26/16) from Acer. I have this same tablet, and I'm unable to root after flashing to the firmware released on the 24th, and latest firmware (Build #: AV0L0.RV0BRC02.WW.GEN1) as well. Hopefully someone can find a fix, as the few different methods I've attempted simply will not work with the latest firmware from Acer.

On KingRoot Please click submit search if enough people do they will find a root until then just hold tight.

jared407 said:
On KingRoot Please click submit search if enough people do they will find a root until then just hold tight.
Click to expand...
Click to collapse
I have done this a bunch, sadly still no love. It's annoying me not being able to root a relatively cheaper tablet, as these tend to get rooted first since they get in more people's hands faster. Oh well, just have to have patience.

Thanks, I was having problems, two different rooters failed and I wondered if it was the recent software update! The image version on my B1-850 is the same as you have quoted! Please post if you find a solution, some apps that need deleting are annoying.
---------- Post added at 06:23 PM ---------- Previous post was at 06:13 PM ----------
random4t4x14 said:
There was recently new firmware released for this tablet (08/24/16, Build #: AV0L0.RV09RC04.WW.GEN1), and a handful of updates (08/25/16, 08/26/16) from Acer. I have this same tablet, and I'm unable to root after flashing to the firmware released on the 24th, and latest firmware (Build #: AV0L0.RV0BRC02.WW.GEN1) as well. Hopefully someone can find a fix, as the few different methods I've attempted simply will not work with the latest firmware from Acer.
Click to expand...
Click to collapse
I was having a problem rooting my device and wondered if it was the recent software update, and my image version is as you have quoted! I f you manage to root your device please post!

knockout350 said:
I made a thread walking you through how to do it on this tablet in the guides area but just use flash fire for recovery and xposed install
Click to expand...
Click to collapse
Which recovery do you install with flash fire; I don't see a link to it in your other thread?

Success!
The latest release of KingRoot is able to root the latest firmware for this tablet. I saw there was a new release of KingRoot back on the 23rd, and it's working as it should. I grabbed the working version here -> http://forum.xda-developers.com/devdb/project/dl/?id=21707

hi guys. any idea how to recover b1-850 from bootloop?

I no its a little late but i rooted mine with the kingoroot one click root apk. Ive installed xposed framework and customized like crazy everything from fonts to boot animation. Cant find a custom recovery tho.

I cannot root it with any of the tools I have tried (Kingo ROOT, KingRoot, etc). Anyone know any method that works?

Acer B1-850. Is this device even rootable?
This device has made an idiot of me. If I can be of any assistance finding a root exploit for this device let me know. I will gladly write a detailed procedure of the process. I made the mistake of assuming since it was an entry level, inexpensive device, the path to root would be simple. Three months later none of the common "one-click" programs has found an exploit. I have a copy of stock rom for recovery so testing is not a problem for me. It's a matter of pride at this point. So much so I found one on sale for $60 and bought it just for this purpose. I have followed every link I can find associated with this device to a dead end. Any help will be appreciated.

pdnorman said:
This device has made an idiot of me. If I can be of any assistance finding a root exploit for this device let me know. I will gladly write a detailed procedure of the process. I made the mistake of assuming since it was an entry level, inexpensive device, the path to root would be simple. Three months later none of the common "one-click" programs has found an exploit. I have a copy of stock rom for recovery so testing is not a problem for me. It's a matter of pride at this point. So much so I found one on sale for $60 and bought it just for this purpose. I have followed every link I can find associated with this device to a dead end. Any help will be appreciated.
Click to expand...
Click to collapse
Same here, still no root for me. Usually these cheapo tablets are not as locked down.

Still waiting!?
I have given up getting assistance from xda on this device. Its as political here as anywhere else. I don't drive a Samsung so nobody wants to help with root. I've heard every excuse from locked bootloader (unlockable in dev options) to what one dev actually told me,"There's little interest in spending energy on an inexpensive device." I understand, but why misrepresent the site by implying all android devices are treated the same? Hell on the Iconia One 8 thread, it says that the B1-850 does not have a MTK SoC, but instead has an Intel Atom chip. Then they send you to another thread where, of course, there is no B1-850 listed! That's because it uses a MTK8163 SoC. In both tablets.

Help Please!!

Hello and Thank you for viewing my post!
I am New to Android Devices and the "Rooting" Process. I am a regular Apple user and use a Jailbroken iPhone and Use a Mac as well but have Windows Mirroring Capabilities on my Mac.
I just bought the Kindle Fire HD 8 (6th Generation) (2016) and it came with os 5.1.1 installed but once i connected to wifi it automatically updated me to 5.3.1.1.
I do not like the OS it includes as there are too many annoyances present (Ads, Unwanted OEM Applications, Etc.) and would like to Root my device and Run a "Real" Android OS and in other words, convert my Kindle Fire HD 8 into a Android Tablet as many do but i am unable to root because i am on 5.3.1.1.
If someone could please help walk me through the steps i need to take to root and all the tools ill need to do so, as well as ways to avoid bricking the device in the process.
Thank you in advance!
-Elijah

ElijahJ777 said:
Hello and Thank you for viewing my post!
I am New to Android Devices and the "Rooting" Process. I am a regular Apple user and use a Jailbroken iPhone and Use a Mac as well but have Windows Mirroring Capabilities on my Mac.
I just bought the Kindle Fire HD 8 (6th Generation) (2016) and it came with os 5.1.1 installed but once i connected to wifi it automatically updated me to 5.3.1.1.
I do not like the OS it includes as there are too many annoyances present (Ads, Unwanted OEM Applications, Etc.) and would like to Root my device and Run a "Real" Android OS and in other words, convert my Kindle Fire HD 8 into a Android Tablet as many do but i am unable to root because i am on 5.3.1.1.
If someone could please help walk me through the steps i need to take to root and all the tools ill need to do so, as well as ways to avoid bricking the device in the process.
Thank you in advance!
-Elijah
Click to expand...
Click to collapse
You can flash an older stock version with fastboot. You may need a fastboot cable to do it though.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
You can flash an older stock version with fastboot. You may need a fastboot cable to do it though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Ive heard rollingback from 5.3.1.1. will brick the Tablet due to the Bootloader(s), Correct?

ElijahJ777 said:
Ive heard rollingback from 5.3.1.1. will brick the Tablet due to the Bootloader(s), Correct?
Click to expand...
Click to collapse
Downgrading bootloader on some devices can brick them, it depends on the software though, not the device. Some devices with locked bootloader that can't be downgraded can sometimes extract the bootloader from the newer locked firmware and replace it in the older firmware, this allows the older firmware to be flashed without downgrading the bootloader because it has been modified so that it has the same bootloader. Not all locked devices can do this though, and even the ones that can still can't flash anything custom because of the bootloader, it does allow for downgrading to use things that won't work in the newer firmware. Whether or not that can be done on this or that device is hit or miss though, some can and some can't, it just requires research and trial and error.
Sent from my SCH-I535 using Tapatalk

Droidriven said:
Downgrading bootloader on some devices can brick them, it depends on the software though, not the device. Some devices with locked bootloader that can't be downgraded can sometimes extract the bootloader from the newer locked firmware and replace it in the older firmware, this allows the older firmware to be flashed without downgrading the bootloader because it has been modified so that it has the same bootloader. Not all locked devices can do this though, and even the ones that can still can't flash anything custom because of the bootloader, it does allow for downgrading to use things that won't work in the newer firmware. Whether or not that can be done on this or that device is hit or miss though, some can and some can't, it just requires research and trail and error.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
My Kindle Fire HD 8 (2016) allows me to unlock the Boot loader (OEM Unlock) from the settings menu, Im no sure if this is a good thing? (Easy way to downgrade boot loader alongside OS?) or not but not exactly sure. Would you recommend any tactics with this in mind or to just wait for kingroot or someone to crack 5.3.1.1. and create a Root?
Thank you!

ElijahJ777 said:
My Kindle Fire HD 8 (2016) allows me to unlock the Boot loader (OEM Unlock) from the settings menu, Im no sure if this is a good thing? (Easy way to downgrade boot loader alongside OS?) or not but not exactly sure. Would you recommend any tactics with this in mind or to just wait for kingroot or someone to crack 5.3.1.1. and create a Root?
Thank you!
Click to expand...
Click to collapse
I would wait for root
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
I would wait for root
I DO NOT GIVE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Alright, Appreciate the help!
Have a good day!
-Elijah