Develop Bugs

[Root][Bootloader] BurritoRoot3 - The whole enchilada. Easy root edition

For 6.3 see http://forum.xda-developers.com/showthread.php?p=24129239
Please do not reupload/redistribute BurritoRoot2/BurritoRoot3, instead link directly to my hosting. I own the server, it will no go away any time soon. This allows me to update it if a bug is found.
BurritoRoot3 is not opensource, it is free, but it is not free to distribute. Please do not redistribute it.
Tested on 6.2, 6.2.1 and 6.2.2
Disclaimer:
BurritoRoot3 may void your warranty. While it was tested, over and over, a chance of data loss or hardware damage always exists. If something bad happens due to your use of BurritoRoot3, well it is your fault not our's, don't blame any of us.
Wine/Coffee/Device Funding:
To donate to jcase of TeamAndIRC for BurritoRoot go here:
http://forum.xda-developers.com/donatetome.php?u=2376614
To donate to pokey900 for the FireFireFire Bootloader go here:
http://forum.xda-developers.com/donatetome.php?u=466725
Download:
http://download.cunninglogic.com/BurritoRoot3.apk
BurritoRoot3 is an all in one package, to root and install the custom bootlaoder, FireFireFire, onto the KindleFire.
Instructions are pretty plain and simple, however you will have to get adb working on your own (if you have written, or know of adb guides for the Kindle Fire please PM me to list them here).
ADB GUIDES
MAC GUIDE: http://forum.xda-developers.com/showthread.php?t=1443071
WINDOWS GUIDE: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
LINUX GUIDE: http://forum.xda-developers.com/showthread.php?p=22067293
What it does:
Gains root, installs superuser, installs su and installs the FireFireFire bootloader.
At this time, we do not have permission to distribute any recovery, once one is available for our use, we will add auto flashing of recovery.
How to use:
adb shell chmod 777 /data/local/tmp
Run app, follow directions given by the app.
Usage example :
[email protected]:~$ adb shell chmod 777 /data/local/tmp <---- This one is important, it may not create BurritoRoot3.bin if this is not done
[email protected]:~$ adb install BurritoRoot3.apk
4897 KB/s (1151520 bytes in 0.229s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
<go open the app now>
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
Installing Superuser APP, if it erros as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Success
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --install
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
BurritoRoot3 kroot 0.1 - TeamAndIRC
Remounting /system...
Cleaning up, ignore any errors
rm failed for /system/xbin/su, No such file or directory
rm failed for /system/bin/su, No such file or directory
Installing su...
Remounting /system..
Root installed
Starting: Intent { act=android.intent.action.MAIN cmp=net.andirc.burritoroot3/.FireFireFire }
Please check your Kindle's screen
[email protected]:~$
If you already have root, and want to safely install the FireFireFire bootloader, you can use the app, just install, open/close the app then
adb shell am start -a android.intent.action.MAIN -n net.andirc.burritoroot3/net.andirc.burritoroot3.FireFireFire
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery

Would you support the archos G9 devices

jutley said:
Would you support the archos G9 devices
Click to expand...
Click to collapse
Doesn't archos sign or lock system?

I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
CharlieBoy808 said:
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
Click to expand...
Click to collapse
LoL Nevermind I think I know why mine isn't there... I've already installed ADB from before. I shall continue on and see what happens :-D

I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.

AproSamurai said:
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
should see it now

Quit following me around jcase

Unheard said:
Quit following me around jcase
Click to expand...
Click to collapse
Hah Where you been?

I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.

notsointeresting said:
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
Click to expand...
Click to collapse
I'm sure its related to windows' drivers but I have no clue. Sorry

jcase said:
adb kill-server
sudo -s
adb devices
should see it now
Click to expand...
Click to collapse
Thanks man, I knew I must have failed to do something. It's much appreciated.

Dis this last night and it worked fine. Thanks!
I did have a few minor stumbles though. It seems the newest version of the software changed the name of the superuser app but the guide still uses the old name in the install command. Once I realized this I just changed the name in the command and it went right in.
Also for some reason I couldn't select the text in the adb box on the web page so I had to enter the commands by hand. No big deal but I would have felt more secure if the commands were in simple text so I could have copy/paste them in.
Like I said though everything worked and I have the market installed now. Thanks for the hard work!

I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated

My sd card is showing up as unmounted and not sure how to remount it. I sent adb remount and it didn't work. Any help would be appreciated.

Fee454 said:
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
Click to expand...
Click to collapse
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889

[/COLOR]
b63 said:
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Press any key to continue . . .
I tried to install the drivers for the kindle but i receive the above message
---------- Post added at 09:56 PM ---------- Previous post was at 09:07 PM ----------
My issue is it cannot find my device...where can I find the kindleADB.zip I keep hearing about?

did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue

You should get the same files from the android Sdi. Good luck.
Jcase, I know that you said the unroot button did not work, but is there a method of unrooting?

b63 said:
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
Click to expand...
Click to collapse
Yes thank you. Moving it to the same as the run.bat seemed to have worked as it shows online now when running the Kindle Fire Utility. I switched it to fast boot but now seems to have been frozen at the kindle fire logo for quite some time now. I heard you have to switch to fastbook to install TWRP first before rooting?
I am not sure if I should attempt to somehow reboot this as it seems to be stuck at the boot up screen

wrong - switch back to normal boot and use the utility

Need help getting Fire Fire Fire and TWRP and Cyanogenmod on Kindle Fire 6.3.3

I've been trying on Windows, and followed the instructions, but when the Kindle rebooted, I didn't see any recovery menu. On Ubuntu now, and I installed Soupkit, adb, and fastboot. But I don't know what to do with these in Linux. I tried one guide, and it tried to load u-boot.bin, which wasn't included in the Soupkit install, and it turns out that Soupkit installed files in the wrong directory, so I tried making the directory path, and copying the files over there, and downloaded the u-boot.bin file I just ended up noticing and putting it in both directories, and it still wouldn't work.
Also, am I supposed to install Fire Fire Fire before TWRP?

Can't use twrp without fff bootloader
Sent from my DROIDX using Tapatalk
---------- Post added at 02:11 PM ---------- Previous post was at 02:06 PM ----------
SoupKit will not work until Kindle is rooted and in fastboot mode
see http://forum.xda-developers.com/kin...w-to-firefirefire-twrp-6-3-3-factory-t2817362

sd_shadow said:
Can't use twrp without fff bootloader
Sent from my DROIDX using Tapatalk
---------- Post added at 02:11 PM ---------- Previous post was at 02:06 PM ----------
SoupKit will not work until Kindle is rooted and in fastboot mode
see http://forum.xda-developers.com/kin...w-to-firefirefire-twrp-6-3-3-factory-t2817362
Click to expand...
Click to collapse
Know how I go about getting fff installed? I tried looking up "Install Fire Fire Fire Kindle 6.3.3" and other similar searches, all I got was how to unbrick with twrp and stuff like that.
Edit: nvm, didn't notice the link. I tried Soupkitchen without the Kindle plugged in. Am I supposed to run it with it plugged in? I tried to run Soupkitchen again, but it's not letting me now.

Overlord Valvatorez said:
Know how I go about getting fff installed? I tried looking up "Install Fire Fire Fire Kindle 6.3.3" and other similar searches, all I got was how to unbrick with twrp and stuff like that.
Edit: nvm, didn't notice the link. I tried Soupkitchen without the Kindle plugged in. Am I supposed to run it with it plugged in? I tried to run Soupkitchen again, but it's not letting me now.
Click to expand...
Click to collapse
Is kindle rooted?

sd_shadow said:
Is kindle rooted?
Click to expand...
Click to collapse
I rooted it with Saferoot. Ran a root check app to make sure, and it said it's rooted. I tried following the instructions on the page you linked but it ends up pointing to Soupkit and it says no such file or directory when I try the push command.
I have adb.exe, fastboot.exe, and u-boot.bin in the Soupkit directory. I used the official Soupkit download, through terminal.

Overlord Valvatorez said:
I rooted it with Saferoot. Ran a root check app to make sure, and it said it's rooted. I tried following the instructions on the page you linked but it ends up pointing to Soupkit and it says no such file or directory when I try the push command.
I have adb.exe, fastboot.exe, and u-boot.bin in the Soupkit directory. I used the official Soupkit download, through terminal.
Click to expand...
Click to collapse
Kindle must be in fastboot mode to use SoupKit.
If windows command prompt says " it says no such file or directory when I try the push command."
adb/fastboot files are not in same older as command prompt is pointing to.

sd_shadow said:
Kindle must be in fastboot mode to use SoupKit.
If windows command prompt says " it says no such file or directory when I try the push command."
adb/fastboot files are not in same older as command prompt is pointing to.
Click to expand...
Click to collapse
I have the exe files in the Soupkit folder. Is there anything I'm missing that I need to get fbmode to work? I'll go look around for a pack.

Overlord Valvatorez said:
I have the exe files in the Soupkit folder. Is there anything I'm missing that I need to get fbmode to work? I'll go look around for a pack.
Click to expand...
Click to collapse
yes, SoupKit can not put the Kindle Fire with system version 6.3.3 in fastboot mode, you need to manually push the files with adb
---------- Post added at 03:22 PM ---------- Previous post was at 03:21 PM ----------
like in the the link i posted http://forum.xda-developers.com/kin...w-to-firefirefire-twrp-6-3-3-factory-t2817362

sd_shadow said:
yes, SoupKit can not put the Kindle Fire with system version 6.3.3 in fastboot mode, you need to manually push the files with adb
---------- Post added at 03:22 PM ---------- Previous post was at 03:21 PM ----------
like in the the link i posted http://forum.xda-developers.com/kin...w-to-firefirefire-twrp-6-3-3-factory-t2817362
Click to expand...
Click to collapse
I have the fbmode file. I always get stuck at the push command. I know I have the files that are needed, and I have two Soupkit folders just in case. One in jason/bin and the other in bin. I even tried copying the files in the files folder directly into the Soupkit folder, still no joy. I have adb.exe, fastboot.exe, fbmode.exe, and u-boot.bin and haven't messed around with any other folders I think. This is a sample of my terminal text.
[email protected]:~$ adb push fbmode /data/local/tmp
bash: /home/jason/bin/SoupKit/files/adb: No such file or directory

According to http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
enter and run this command:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
And you're all set up! You can send commands to your device from any terminal window.

sd_shadow said:
According to http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
enter and run this command:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
And you're all set up! You can send commands to your device from any terminal window.
Click to expand...
Click to collapse
It says nothing was upgraded, and I already have the newest version. And when I try the push command, I still get the same error. Tried skipping ahead to adb shell and still getting a no such file or directory error. I downloaded the files that were linked in the guide, and I'm pretty sure I'm missing certain files, but I forgot what those were. I borked my bootloader when trying to use EasyBCD to replace Android x86 with Ubuntu. Ended up plugging in my spare drive and grabbing Ubuntu off of that, and loading it from my USB, so I have an OS again, but the files I had were lost, so I've been having to hunt down missing files.
Edit: I have Superuser on my Kindle. I wonder if there's anything I can do from there to make things easier.

[Q] HELP: ADB server didn't ACK... Cannot connect to daemon

I have a 1st gen kindle fire.. That I rooted. But when i tried to install GAPPS and TWRP, the CMD window wouldn't let me. The error: "ADB server didn't ACK... Cannot connect to daemon" would pop up. So nothing else would load.
I then tried and tried various methods of fixes ( three days now), but none would work. Same constant error message in CMD window.
To make matters worse now, In one of my attempts to fix the problem, I've managed to brick the kindle. It's stuck on load page. Just says kindle fire on the screen.
ANY ANY ANY help .. would be greatly appreciated

pistol865 said:
I have a 1st gen kindle fire.. That I rooted. But when i tried to install GAPPS and TWRP, the CMD window wouldn't let me. The error: "ADB server didn't ACK... Cannot connect to daemon" would pop up. So nothing else would load.
I then tried and tried various methods of fixes ( three days now), but none would work. Same constant error message in CMD window.
To make matters worse now, In one of my attempts to fix the problem, I've managed to brick the kindle. It's stuck on load page. Just says kindle fire on the screen.
ANY ANY ANY help .. would be greatly appreciated
Click to expand...
Click to collapse
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
http://forum.xda-developers.com/showpost.php?p=54124313&postcount=3
Sent from my XT1028 using Tapatalk

That was exactly one of the post I was working off of. So when I got to step 4: Push Fastboot Mode File to Kindle.. in the command window, I would get the error message, " ADB server didn't ACK... Cannot connect to daemon". I tried for three days now, various fixes.. nothing seemed to work. And NOW, during one of my fixes, it bricked the Fire.

pistol865 said:
That was exactly one of the post I was working off of. So when I got to step 4: Push Fastboot Mode File to Kindle.. in the command window, I would get the error message, " ADB server didn't ACK... Cannot connect to daemon". I tried for three days now, various fixes.. nothing seemed to work. And NOW, during one of my fixes, it bricked the Fire.
Click to expand...
Click to collapse
Stuck at Boot logo?
With animation or no change?
Sent from my XT1028 using Tapatalk
---------- Post added at 03:31 PM ---------- Previous post was at 03:24 PM ----------
Does boot logo, fade in and out slightly?
Sent from my XT1028 using Tapatalk

No fading in and out.

pistol865 said:
No fading in and out.
Click to expand...
Click to collapse
It's in fastboot mode then, send the fastboot commands
Sent from my XT1028 using Tapatalk

"It's in fastboot mode then, send the fastboot commands "
Don't really know what that means?
Fastboot mode?
Send fastboot commands?
Send where?
As I said.. kind of a newbie.. I'm not familiar with all the jargon/terms.
If you have a solution.. could you spell it out like I'm a five year old.. step by step? Otherwise.. I am just going to keep being Lost.
Thank you again

pistol865 said:
"It's in fastboot mode then, send the fastboot commands "
Don't really know what that means?
Fastboot mode?
Send fastboot commands?
Send where?
As I said.. kind of a newbie.. I'm not familiar with all the jargon/terms.
If you have a solution.. could you spell it out like I'm a five year old.. step by step? Otherwise.. I am just going to keep being Lost.
Thank you again
Click to expand...
Click to collapse
There are 2 different types of commands sent from pc to an android device, adb and fastboot.
Adb is used when device is in recovery or system/Rom is running.
Fastboot is used when device is in fastboot mode or bootloader mode.
Sent from my XT1028 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
See step 6
Sent from my XT1028 using Tapatalk

sd_shadow said:
There are 2 different types of commands sent from pc to an android device, adb and fastboot.
Adb is used when device is in recovery or system/Rom is running.
Fastboot is used when device is in fastboot mode or bootloader mode.
Sent from my XT1028 using Tapatalk
---------- Post added at 04:41 PM ---------- Previous post was at 04:39 PM ----------
See step 6
Sent from my XT1028 using Tapatalk
Click to expand...
Click to collapse
I tried that.. Got the response: Fastboot is not recognized as an internal or external command,
operable program or batch file.

Also whenever I try and run a command from CMD.. I also get "ADB server didn't ACK.. cannot connect to daemon".

pistol865 said:
I tried that.. Got the response: Fastboot is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
adb.exe and other adb files are not in the same folder that the command prompt is running from.
You need to change directory with cd\

sd_shadow said:
adb.exe and other adb files are not in the same folder that the command prompt is running from.
You need to change directory with cd\
Click to expand...
Click to collapse
Step 3 says to put them all in the same folder on my C drive.
"Step 3: Place Files
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder."
I am sooooooo confused right now!!!
I was following step by step. I got the kindle to Root... but then it all went down hill from there. And now it's bricked. ANd I can't figure out how to get out of it.
As I said.. i've been trying for three days now.. All different methods.
I keep running into problems with the CMD prompts..
That is until I somehow bricked it. Now I can't seem to do ANYTHING on it.

pistol865 said:
Step 3 says to put them all in the same folder on my C drive.
"Step 3: Place Files
Create a folder in c drive named adb,
unzip/extract files,
copy AdbWinUsbApi.dll, AdbWinApi.dll, adb.exe, fastboot.exe, fbmode, fff-u-boot_v1.5.bin, and openrecovery-twrp-2.2.2.1-blaze.img to adb folder."
I am sooooooo confused right now!!!
I was following step by step. I got the kindle to Root... but then it all went down hill from there. And now it's bricked. ANd I can't figure out how to get out of it.
As I said.. i've been trying for three days now.. All different methods.
I keep running into problems with the CMD prompts..
That is until I somehow bricked it. Now I can't seem to do ANYTHING on it.
Click to expand...
Click to collapse
Create a folder in c drive named adb

One of the methods I was trying was this : http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
However, once again, whenever it goes into the CMD phase, I get the phrase: "ADB server didn't ACK... Cannot connect to daemon"
So before I can unbrick it, I'm thinking I need to fix this other problem FIRST. The "ADB server didn't ACK... Cannot connect to daemon" problem.

pistol865 said:
One of the methods I was trying was this : http://www.androidauthority.com/how-to-unbrick-your-amazon-kindle-fire-46412/
Click to expand...
Click to collapse
I have not got that to work with System version 6.3.3 or 6.3.4.
So before I can unbrick it, I'm thinking I need to fix this other problem FIRST. The "ADB server didn't ACK... Cannot connect to daemon" problem.
Click to expand...
Click to collapse
It's not bricked it's in fastboot mode, where it needs to be to flash FFF and Twrp, the problem is your pc and the commands you are using.
Create a folder in c drive named adb

sd_shadow said:
I have not got that to work with System version 6.3.3 or 6.3.4.
It's not bricked it's in fastboot mode, where it needs to be to flash FFF and Twrp, the problem is your pc and the commands you are using.
Create a folder in c drive named adb
Click to expand...
Click to collapse
OK.. done..
I've attached an image showing what files are in the folder.
Now I opened a cmd window in C and Started step 4. But I got an error message: * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon.

pistol865 said:
OK.. done..
I've attached an image showing what files are in the folder.
Now I opened a cmd window in C and Started step 4. But I got an error message: * daemon not running. starting it now on port 5037 * ADB server didn't ACK * failed to start daemon * error: cannot connect to daemon.
Click to expand...
Click to collapse
Kindle is in Fastboot mode
adb commands will not work
Use Fastboot commands
see Step 6

sd_shadow said:
Kindle is in Fastboot mode
adb commands will not work
Use Fastboot commands
see Step 6
Click to expand...
Click to collapse
Thank you so much for your help so far..
OK.. so I went ahead and tried step 6. Although the response didn't come back as it should have. I then went to the troubleshooting page and input:
If you got to step
Code:
fastboot devices
and do not get a proper code return, and you have checked drivers in Device Manager, or drivers don't seem to install correctly
you can try
Code:
fastboot -i 0x1949 oem idme bootmode 4000
then
Code:
fastboot -i 0x1949 reboot"
But now when i try to move ahead, the cmd window says it's waiting for device.
The Kindle at first looked as if it were going to reboot, but after a couple of times where the Kindle Fire logo went on and off ( at first disjointed then normal) . then it just stayed on that . Now underneath it says : Battery is too low ( 29%) . Please wait while your Kindle charges.
So I guess I just wait for it to charge? I'm not sure.
What do you suggest my next steps to be?
Again.. Thank you so much for taking the time to help me!

pistol865 said:
Thank you so much for your help so far..
OK.. so I went ahead and tried step 6. Although the response didn't come back as it should have. I then went to the troubleshooting page and input:
If you got to step
Code:
fastboot devices
and do not get a proper code return, and you have checked drivers in Device Manager, or drivers don't seem to install correctly
you can try
Code:
fastboot -i 0x1949 oem idme bootmode 4000
then
Code:
fastboot -i 0x1949 reboot"
But now when i try to move ahead, the cmd window says it's waiting for device.
The Kindle at first looked as if it were going to reboot, but after a couple of times where the Kindle Fire logo went on and off ( at first disjointed then normal) . then it just stayed on that . Now underneath it says : Battery is too low ( 29%) . Please wait while your Kindle charges.
So I guess I just wait for it to charge? I'm not sure.
What do you suggest my next steps to be?
Again.. Thank you so much for taking the time to help me!
Click to expand...
Click to collapse
UPDATE:
Well after a while , the Kindle Fire restored itself to factory.. Had me input all my info again on the Kindle.
So I guess one problem is fixed... It's not Bricked.
Is it still rooted as it was before the problem. And if it is, can I then install FFF and TWRP?
And Finally.. THANK YOU so much for helping me UNBRICK it in the first place!!

pistol865 said:
UPDATE:
Well after a while , the Kindle Fire restored itself to factory.. Had me input all my info again on the Kindle.
So I guess one problem is fixed... It's not Bricked.
Is it still rooted as it was before the problem. And if it is, can I then install FFF and TWRP?
And Finally.. THANK YOU so much for helping me UNBRICK it in the first place!!
Click to expand...
Click to collapse
Did you use install.drivers.bat from Kindle Fire Utility? If not do so now.
Then watch my video, follow my written steps.

OnePlus 3 Won't Boot Please help

Hey all,
Today I noticed that my oneplus 3 was using a ridiculous amount of battery ( I charged it to 100% and it said I had 3 hours left) I did some research and found out it was android and system or something like that using all my battery. The guide I found said to try turning off Google backup and erase the cache for android system, so I did that and then decided to rebood my phone just in case some odd bug was causing my CPU to run at full speed or something.
Now the problem is it won't boot back up. My phone is bone stock, the only non stock thing about it is that I'm in the program to get updates more often. Anyway... I'm able to boot into the stock recovery so I did that and tried deleting cache and system settings and my phone still won't boot. When I try to boot it up it shows the powered by android logo, and then it starts to boot the OS normally, problem is the dots never stop spinning. So basically I need to know if it's possible to get my pictures off of the phone before they're gone forever or if there's a way to get the thing to boot, even if it's just long enough to get my picture off. I haven't made a backup of my pictures since December (because I'm an idiot) so I really don't want to delete them unless I've tried everything.
I don't know if I had USB debugging enabled so I don't know what kind of options that leaves me with. Is it possible to re flash the OS while keeping the files and password intact?
Lastly... If I did a full factory reset from the recovery would I be able to recover any of the pictures after the fact with software or would it just be gone?
Any help would be greatly appreciated!

frasercow said:
Hey all,
Today I noticed that my oneplus 3 was using a ridiculous amount of battery ( I charged it to 100% and it said I had 3 hours left) I did some research and found out it was android and system or something like that using all my battery. The guide I found said to try turning off Google backup and erase the cache for android system, so I did that and then decided to rebood my phone just in case some odd bug was causing my CPU to run at full speed or something.
Now the problem is it won't boot back up. My phone is bone stock, the only non stock thing about it is that I'm in the program to get updates more often. Anyway... I'm able to boot into the stock recovery so I did that and tried deleting cache and system settings and my phone still won't boot. When I try to boot it up it shows the powered by android logo, and then it starts to boot the OS normally, problem is the dots never stop spinning. So basically I need to know if it's possible to get my pictures off of the phone before they're gone forever or if there's a way to get the thing to boot, even if it's just long enough to get my picture off. I haven't made a backup of my pictures since December (because I'm an idiot) so I really don't want to delete them unless I've tried everything.
I don't know if I had USB debugging enabled so I don't know what kind of options that leaves me with. Is it possible to re flash the OS while keeping the files and password intact?
Lastly... If I did a full factory reset from the recovery would I be able to recover any of the pictures after the fact with software or would it just be gone?
Any help would be greatly appreciated!
Click to expand...
Click to collapse
you should try a factory reset , but it'll erase everything and you want be able to recover it sadly...
if the factory reset didn't work, you must download the latest zip of full rom (beta i presume) and adb from PC.

Factory reset don't erase internal memory of the phone. Pictures, music, video, camera photos should be ok.
If you format the phone, then it will erase ALL. you will have a clean, empty storage. After Format, reboot to RECOVERY !

theduke7 said:
you should try a factory reset , but it'll erase everything and you want be able to recover it sadly...
if the factory reset didn't work, you must download the latest zip of full rom (beta i presume) and adb from PC.
Click to expand...
Click to collapse
null0seven said:
Factory reset don't erase internal memory of the phone. Pictures, music, video, camera photos should be ok.
If you format the phone, then it will erase ALL. you will have a clean, empty storage. After Format, reboot to RECOVERY !
Click to expand...
Click to collapse
I downloaded the rom from oneplus and tried to adb sideload and it gave me an error saying "cannot read file" So then I tried the full factory reset and it still won't boot. I'm totally out of ideas, all I did was reboot the phone!

frasercow said:
I downloaded the rom from oneplus and tried to adb sideload and it gave me an error saying "cannot read file" So then I tried the full factory reset and it still won't boot. I'm totally out of ideas, all I did was reboot the phone!
Click to expand...
Click to collapse
the error you describe means that adb drivers are not installed correctly
use driver on the following thread on post number 3
https://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
and the driver verification on windows must be off...follow the following guide
http://www.drivethelife.com/windows...e-enforcement-on-windows-10-8-7-xp-vista.html
after disabling driver verification , install the driver and accept all the message (in red ) that will appear) when it's done side load the rom you downloaded through adb... (when you install driver say yes to install for all users)
in case all fails, the following thread will always save your phone
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700

"cannot read file"
frasercow said:
I downloaded the rom from oneplus and tried to adb sideload and it gave me an error saying "cannot read file" So then I tried the full factory reset and it still won't boot. I'm totally out of ideas, all I did was reboot the phone!
Click to expand...
Click to collapse
The error the error "cannot read file" is beacause you are using a old version of ADB, try this one: https://androiddatahost.com/bnjkh

theduke7 said:
in case all fails, the following thread will always save your phone
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Click to expand...
Click to collapse
I'm trying to do the first option in that thread, but when I click start in MsmDownloadTool V3.0 it just says "waiting for device connection."
jeffrey268 said:
The error the error "cannot read file" is beacause you are using a old version of ADB, try this one: https://androiddatahost.com/bnjkh
Click to expand...
Click to collapse
Your version isn't working either.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
8835ae16 sideload
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload OnePlus3Oxygen_16_OTA_055_all_1708211845_1a87aaf0fba54c3d.zip
loading: 'OnePlus3Oxygen_16_OTA_055_all_1708211845_1a87aaf0fba54c3d.zip'
* cannot read 'OnePlus3Oxygen_16_OTA_055_all_1708211845_1a87aaf0fba54c3d.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot>

frasercow said:
I'm trying to do the first option in that thread, but when I click start in MsmDownloadTool V3.0 it just says "waiting for device connection."
Your version isn't working either.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
8835ae16 sideload
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload OnePlus3Oxygen_16_OTA_055_all_1708211845_1a87aaf0fba54c3d.zip
loading: 'OnePlus3Oxygen_16_OTA_055_all_1708211845_1a87aaf0fba54c3d.zip'
* cannot read 'OnePlus3Oxygen_16_OTA_055_all_1708211845_1a87aaf0fba54c3d.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Rename the file to OTA.zip
Start CMD as an administrator
And then type the following: C:\Program Files (x86)\Minimal ADB and Fastboot\adb.exe sideload ota.zip
---------- Post added at 08:21 PM ---------- Previous post was at 08:01 PM ----------
frasercow said:
I'm trying to do the first option in that thread, but when I click start in MsmDownloadTool V3.0 it just says "waiting for device connection."
Your version isn't working either.
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
8835ae16 sideload
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload OnePlus3Oxygen_16_OTA_055_all_1708211845_1a87aaf0fba54c3d.zip
loading: 'OnePlus3Oxygen_16_OTA_055_all_1708211845_1a87aaf0fba54c3d.zip'
* cannot read 'OnePlus3Oxygen_16_OTA_055_all_1708211845_1a87aaf0fba54c3d.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Sorry pointed you to the wrong ADB, download SDK Platform-Tools for Windows here:
https://developer.android.com/studio/releases/platform-tools.html
Unpack the folder to your'e C drive, move the OTA file to the same directory.
Put your phone into adb sideload mode.
Open CMD as an administrator an type the folowing:
C:\platform-tools\adb.exe sideload OTA.zip
It should work now.
More info can be found here: https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/

EDIT It's working now thank you so much to everyone who helped!
That's not working either. Take a look at the following pictures to see if I'm missing something.
https://photos.app.goo.gl/gEeqqWgiI4SSmP393

wery wery big problem

Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully *
fastboot devices havent
quamqom other method driver pls help

byjon09 said:
Minimal ADB and Fastboot>adb devices
List of devices attached
adb server version (31) doesn't match this client (39); killing...
* daemon started successfully *
fastboot devices havent
quamqom other method driver pls help
Click to expand...
Click to collapse
TRY update adb flatform tool

ı m 100 files download maybe just bootloader opened download mode no normal mode no recovery no
bootloader files find

Hard_k.i.k said:
TRY update adb flatform tool
Click to expand...
Click to collapse
the problem is that I stupidly turned off the bootlarder lock while downloading the android version, now fastboot devices don't see it, adb devices see it in fastboot,n I need to turn on the phone when I can't

https://queeshop.blogspot.com/2017/11/tutorial-how-to-fix-qhsusbbulk-or.html this method ?????​

https://www.droidwin.com/fix-adb-server-version-doesnt-match-this-client-killing/ whichi*******???