[SOLVED] a bit of HELP please... - Kindle Fire General

Hello everyone.
I need a bit of help repairing my partitions on my Kindle.
To try and sum it up quickly, I am rooted, have FFF and TWRP installed. I decided to repartition my Kindle (using FireParted) to allow for more apps space. I did and everything went smooth. After installing some apps, I got a message saying my storage space was getting low. When I looked at the settings, I noticed that I had partioned my Kindle the wrong way. (Had more space for videos, music, pictures).
Sooo I decided to again repartition my Kindle once again using FireParted. Created a backup and let it do its thing. After 10 minutes I noticed the program still wasn't done and then it just stopped. Of course when I restarted it said that the partition couldn't be found. I tried restoring back up but it didn't find any. (wtf)
I then decided to try out the Unbrick utility but when I clicked on OTHER to see what other options were available, it immediately rebooted my Kindle and then I was stuck on the yellow triangle. I lost TWRP because I couldn't even boot into that. So I proceeded to uninstall/reinstall the drivers again. I ran the Kindle Fire Utility, it shows that I'm still rooted. Installed TWRP again and now I'm able to mount/unmount etc. but because my partion is all messed up. I'm unable to install a new ROM.
This is where I need help. I read about going into FASTBOOT mode with the KFU and then typing "fastboot oem format" but when I boot in FASTBOOT, I lose the TWRP and my computer/kfu/adb no longer recognizes the device. I tried entering the command through adb but I get a "'fastboot' is not recognized as a internal or external command".
So at this point I have no clue what to do or where to go. Any help would be appreciated.
Btw, I did look at this thread but it didn't help:
http://forum.xda-developers.com/showthread.php?t=1388996

sounds like you dont have fastboot.exe - issue the commands from the tools folder of kfu - there is fastboot.exe and all other commands you'll ever need

When I click on fastboot.exe from the tools folder of kfu, all it does is open and close right away nothing else. If I use the KFU to boot into fastboot it just gets stuck at activating fastboot but nothing happens.

to click it will not help you !
open an (elevated) command prompt and cd to the tools folder of kfu (ie "cd c:\kfu\tools")
now you can issue the suggested commands - ie "fastboot oem format"
if your drivers are ok the command should succeeed

b63 said:
to click it will not help you !
open an (elevated) command prompt and cd to the tools folder of kfu (ie "cd c:\kfu\tools")
now you can issue the suggested commands - ie "fastboot oem format"
if your drivers are ok the command should succeeed
Click to expand...
Click to collapse
Thanks for the help b63, I appreciate it.
I did what you said, elevated command prompt etc. Fastboot.exe worked correctly now. When I put "fastboot oem format" it just hangs on "waiting for device" but nothing ever happens. How long does this process normally take? It's been like 10 minutes now and no change. I don't know if the kindle is supposed to reboot or what. Right now it's on TWRP recovery...

ANDROID 3G said:
Thanks for the help b63, I appreciate it.
I did what you said, elevated command prompt etc. Fastboot.exe worked correctly now. When I put "fastboot oem format" it just hangs on "waiting for device" but nothing ever happens. How long does this process normally take? It's been like 10 minutes now and no change. I don't know if the kindle is supposed to reboot or what. Right now it's on TWRP recovery...
Click to expand...
Click to collapse
check your device manger - it's a driver issue
update the driver - the right one is "android adb interface"
if your driver is right there is another trick to try:
issue the command and let it sit on <waiting for device>
power down the kf by holding pwr button ~20sec - prw on again
the command should be picked up and finished

I had this problem when using FireParted as well. It causes problems on a stock ROM erasing partition 10 and 11. I was able to recover using the post you sent and have also my own instruction as well. http://forum.xda-developers.com/showthread.php?t=1453816
Hope this helps.

Related

[Q] Super Ultra Brick (WITH VIDEO)

UPDATE 3: I've got it back to as stock as I can get it. I think I'm going to just return it and get a new one. Thank you all for your help.
UPDATE 2: As of right now, I'd like to completely remove FFF from the device, but I can only use fastboot to do it. I have absolutely no adb access. Is there a way?
UPDATE: Here is a video showing what is happening to my KF: http://www.youtube.com/watch?v=MH6oUg1NmC0
I hate to start another thread about boot loops/bricking, but I'm not sure what's going on with my fire.
I had CM7 installed successfully since the day after Christmas. This morning I woke up and my Fire was being really sluggish, so I rebooted it (I did not select reboot into recovery).
After it powered on, I was stuck at the CM7 boot screen (with the skateboarding android). I let it sit, but no luck. I went into TWRP to try and restore the backup I made of the stock rom. It looked successful, but when I rebooted I was stuck at the Kindle Fire boot screen.
Next, I tried wiping the device and re-installing CM7, but I received an error (something along the lines of E:Error unable to find /tmp/sideload/blahblah).
So I again restored my backup of the stock rom. Now when I power on my Fire I see the yellow triangle, then the kindle fire logo, yellow triangle, kindle fire logo, and it just keeps repeating. The problem is I am unable to connect to adb because the PC only seems to recognize the adb device for a few seconds after the yellow triangle, which does not give me enough time to fix the problem.
Any ideas?
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
b63 said:
looks like you'r out of battery ! the kf is rebooting !
would take the wall charger and charge for an hour
it's not possible to charge with the computer - it lasts forever
then it should respond in a stable state
Click to expand...
Click to collapse
Recovery shows my battery level to be at 53%. I've got it on the charger now, but I have a feeling there is something else going on.
Also, I am unable to mount my Fire's SD to my computer in recovery. It looks like it is working, but my computer never acknowledges it.
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
b63 said:
maybe because your last installation failed
nevertheless i would try to charge and then go in twrp and retry the installation
if that's not sucessful i would try to switch the kf to fastboot and copy a new rom. stock or prerooted stock or cm7 - whatever you like
in twrp there is a point "mount" - sdcard - then you should get it from computer
Click to expand...
Click to collapse
Thanks for the reply. Is adb required to get into fastboot? The problem is that I am unable to get into adb because my computer only sees the Fire for about 1 second. When I go into device manager, I don't see it at all.
EDIT: Yeah, I see the mount in TWRP, but it does not do anything when I select it.
Hi Im a beginner but Id like to try to help :
In case you become desperate ignore twrp's battery display and try wall charger.
Anorher idea id have is to shut down throughr twrp and start up then instead of rebooting.
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
skourg3 said:
ADB is needed to get into fastboot, but it's quick. If you use KFU, you can probably hit the option during the couple seconds you have available. I would say your best bet, however, is booting into twrp, doing a full wipe of system, cache, davlik cache, and maybe data, and then trying the rom install again.
Click to expand...
Click to collapse
So this time it looks like the installation worked in TWRP, but after reboot now I'm stuck at the CM7 boot screen. This is at least some progress, so when I get home I'll see what I can do.
Sent via my internet connected mobile cellular telephone.
Well, the battery is definitely not the issue. I've been trying to get fastboot, but the problem is the fact that I can not get adb. Has anyone else had issues with getting adb? I've already tried to install the drivers, and that doesn't work.
EDIT: I've tried issuing "adb devices" from the command prompt repeatedly as soon as I hear the ding until it disconnects a second later, but still I have had no luck.
Also, I found this thread in which someone else appears to have had a similar issue to mine.
[Q] New kind of unfixable Super Brick?
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
b63 said:
at the moment adb is useless - you should try to get the device in fastboot mode - correctly recognised from your computer - then work with fastboot commands - if you don't get that then your next opinion is buying or making a factory cable - but we should try to avoid that ...
Click to expand...
Click to collapse
I can not seem to get fastboot to work either. Does fastboot rely on adb? Or do you just run the .exe file? I tried to run it, and nothing happened.
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
Just wanted to let you know I updated the OP with a video showing what is happening to my KF.
Haven't tried that particular rom yet, but I have wiped data and cache and attempted to re-install CM7.
great idea with the video !!!
b63 said:
fastboot has nothing to do with adb - calling just the exe does nothing -
you have to issue fastboot commands
ok have reread the whole thread and have some ideas:
your currently stuck at the cm7 boot screen ?
have you used the "stock rom version" to wipe data and cache partitions as described here ?
http://forum.xda-developers.com/showthread.php?t=1390773
perhaps it will help to wipe data/cache with twrp ...
Click to expand...
Click to collapse
OK, so I restored my original rooted kindle rom, but I still can't get into fastboot because of the problem I showed in the video. It is doing exactly the same thing, just instead of the CM7 boot screen, it is the Kindle Fire boot screen.
Is is possible to get into fastboot without the computer? Can anyone think of a reason why I would not be able to mount my device in TWRP?
I just want to understand something about fastboot... can you upload and flash roms with it? Or can you only get TWRP / FFF with it? I ask because I already have them, and I still can't do anything (mount from inside TWRP doesn't work). Thanks!
Sent via my internet connected mobile cellular telephone.
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
b63 said:
with fastboot you can install the newest fff and if you need twrp
but with the newest fff you can issue ""fastboot oem format"
see here:
http://forum.xda-developers.com/showthread.php?t=1369405
that should solve every issue ...
Click to expand...
Click to collapse
Cool. I just ordered one of SkOrPn's cables, so once I get it I'll be sure to give an update. Thanks for all the help so far!
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
foxdog66 said:
The cable isn't need when you have the FFF bootloader, in fact, when your computer does see the device for the short amount of time shown in the video, fastboot is active. It's a feature of FFF. Fastboot is a command line tool like adb but is used for different things. It comes in Android sdk which if you have that, you should update the tools packages in the Android manager and it will update adb and fastboot. It looks like something is not working correctly in twrp and the OS is failing to load. I'm not sure you need to oem format tho.....
At some point you had to have used fastboot to install twrp and/or FFF.... Unless you used adb dd? :what:
Anyway, I can help more but it's late where I am, need to sleep. Was going to write more but... Need sleep lol. I'll post some questions and check back tomorrow.
Have you used adb before? Do you know if platform-tools is in your environment variables PATH? In other words, can you open up cmd and type adb or do you need to "cd" to platform-tools then use adb? If you know where adb is located? If so, is a file called fastboot in there? (Maby called fastboot.exe)
Click to expand...
Click to collapse
Yep, I've used adb successfully, and it is set up as an environmental variable. I actually installed FFF and TWRP with the KFU. Problem is I think something else is botched; perhaps it is TWRP itself, since I am unable to mount from TWRP. I'll try again when I get home.
Sent via my internet connected mobile cellular telephone.

[SOLVED] Stuck in boot loop with 6.2.2 and HAVE adb shell access, but still stuck...

Firstly, I'm sorry for creating a new thread, but please know that I searched everywhere (here and around the Internet) first. I barely slept last night. I have read and read. I'm still stuck.
I was able to root following these instructions - http://forum.xda-developers.com/showthread.php?t=1410223 - and all was good for a little while, until I made a bone-headed mistake in the File Expert app while trying to install Google Market. I changed the permissions to /system/app and I'm sure that if I was able to change them back, I'd be fine. I just can't figure out how to do that.
What I can do is connect to the device via ADB, but if I go to adb shell, the prompt is a $. As I understand it, I need that to be a #. I can't get a # prompt, because when I run "su", I get an error that says "Segmentation fault su". (Sometimes I get a different error message, but I'm sorry, I forget what that is right now.)
Anyway, so because I'm not superuser, when I attempt to run "chmod 755 /system/app" (which is what I know I need to do), I get an error "Unable to chmod ... Read-only file system."
In order to get around that error, I know I need to mount as readwrite. However, when I try to run "mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system", I get an error that says, "mount: Operation not permitted."
No doubt, I cannot chmod or mount because I'm not su. In an attempt to regain su, I tried to run BurritoRoot2.bin again (I don't know if that makes sense, but I decided to try it anyway, because BurritoRoot2 is what worked for me last night, and everything really was fine until I messed up those permissions). Anyway, that was last night. Today, BurritoRoot2 won't work anymore. Now I get an error says, "android.util.AndroidException: Can't connect to activity manager; is the system running?"
Well, no. The system is not running. That's sort of my problem.
I have no idea what to do now. I do not have TWRP installed. If I did have that installed, I might be able to flash a completely stock 6.2.1 or 6.2.2 ROM, thus restoring everything to "out-of-the-box" condition, which would be fantastic right about now. I don't know if I can install TWRP at this point, however, since my access to the device is so limited.
PLEASE help me... Where, exactly, should I go from here?
(Thank you for reading this. I'm sorry it's so long; I wanted to be thorough.)
you have to install fff and twrp therefore you have to get to fastboot:
http://forum.xda-developers.com/showthread.php?t=1414832
then install twrp:
download from http://techerrata.com/file/twrp2/twrp-blaze-2.0.0RC0.img
install with:
fastboot -i 0x1949 boot recovery\twrp-blaze-2.0.0RC0.img
and reboot:
fastboot reboot
now you can flash one of the prerroted stock roms or cm7 - whatever you like
would not use the stock rom from amazon cause you'll loose fff, twrp and root
Okay, so far so good! Thank you so much for that information.
It seems as if fastboot has been enabled without complication. I'm moving on now to the download and installation of TWRP and FFF. I'll let you know how it goes!
Well, crap. Now I'm stuck at the yellow triangle and "press power button for recovery", except pressing power does not start recovery.
AND, I can no longer access the device via ADB. The drivers appear to be invalid now. :`-(
I'll be working my way through this thread now - http://forum.xda-developers.com/showthread.php?t=1408056 - and again, will report back later.
CarpeNivem said:
Well, crap. Now I'm stuck at the yellow triangle and "press power button for recovery", except pressing power does not start recovery.
AND, I can no longer access the device via ADB. The drivers appear to be invalid now. :`-(
I'll be working my way through this thread now - http://forum.xda-developers.com/showthread.php?t=1408056 - and again, will report back later.
Click to expand...
Click to collapse
you'll have to update the driver - some did up to 4 times to get the right driver for each boot mode
in short:
normal boot -> android composite adb interface
fastboot -> android adb interface
adb is'nt working in fastboot mode and you'r still in fastboot mode
once you got twrp installed correctly, the drivers updated and correctly recognized you can force to recovery mode:
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
btw. to get to twrp you have to press the button repeatently (not holding,not once) till the button gets orange
After rebooting the Kindle several times, it is now appearing in Device Manager as "Android ADB Interface" (which, if I'm understanding your most recent post, is correct). However, it is not listed when I type "adb devices", so that's troubling. And, when I try to run the "fastboot oem idme bootmode 4000" command, I get an error that "AdbWinApi.dll is missing from your computer".
So far I've only searched the forums briefly, but that error seems to be related to improper drivers, which means I'm even MORE confused, since the drivers appear correct now. Well, they appear correct in terms of what I see in Device Manager. I'm still uncomfortable about "adb devices" not returning anything, though.
just updated my last post
got it - from where do you run the commands kfu tools folder or sdk ?
if you use kfu tools folder (would recommend cause there are all necessary files) then move kfu to something like c:\kfu - it don't like spaces in pathname
ah-HA!!
Thank you. I was running the fastboot from "C:\Kindle Fire Utility v6\", which was clearly wrong. First I renamed that folder to C:\kfu\ and then tried from there (but I was obviously still misunderstanding your post at that point). THEN, I read your post again, and realized I needed to be in the C:\kfu\tools\ folder. From there, I ran...
fastboot -i 0x1949 oem idme bootmode 5001
fastboot -i 0x1949 reboot
...and I am now inside TWRP! It is working.
To be abundantly clear (for any others who many be reading this in the future), after typing those commands, the Kindle rebooted itself. I then waited a little while, and the green light changed to orange (I had tried waiting before, but nothing happened previously). Shortly after the light turned orange, the Kindle rebooted itself again (on its own). It was on that reboot that TWRP started.
And that's where I stand now. I don't have time to actually use TWRP at the moment, though. I'm going to have to come back to this later.
But thank you again SO MUCH for getting me this far. I might just be able to take it from here.
to get to normal boot once your finished maybe you have to issue adb commands since adb is working in recovery
adb shell su -c "idme bootmode 4000"
adb reboot
and:
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
good luck !
HOT DAMN, I have a Kindle again!!
Alright, so once I had TWRP installed, I noticed there was a menu choice labeled "Fix Permissions". Since all I really wanted to do was undo the mistake I made with /system/app, I wondered if clicking that would do it. So I tried it.
When that finished, I connected via adb shell and checked the permissions on /system/app. They were still wrong. But, I also had a # prompt now, not a $. So then I thought, well, I bet I can use chmod now.
And I could! "chmod 755 /system/app" worked! At this point, I thought that might be good enough. I may not need to flash a ROM after all. I mean, changing those permissions is all I really wanted to do last night. Well, that and sleep.
At this point, I tried leaving the shell and running "adb shell su -c "idme bootmode 4000"" from cmd, as instructed, but that didn't work. It said "su" was not found. Hmm. On a whim, I decided to go back into the adb shell, and just type "idme bootmode 4000" right from the # prompt. It seemed to accept that. Then I typed "reboot" from the next # prompt.
The Kindle rebooted. At first, it went to the yellow triangle with the "press power button to enter recovery" screen. I didn't press anything. I just stared at it and waited. Eventually, it rebooted itself. On this reboot, it went to the Kindle Fire logo!! I wondered if it was working again, or just stuck back where I had been this morning. So I waited, tensely. I have mixed emotions about that logo animation now, ya know.
AND THEN IT BOOTED TO THE NORMAL LOCK SCREEN!!!
AND THEN I SWIPED TO UNLOCK, AND EVERYTHING WAS JUST AS I LEFT IT!!!
See? I told you it was just those permissions. I knew it all along.
Anyway, b63 is the best ever! Thank you SOOO much. If you're even in Denver, let me know. I owe you at LEAST a beer! Or if you have PayPal, seriously, I'll hook you up that way too. I really, really appreciate it!
(And... Original title edited. "Solved"!)
I tried following the fix but I am lost at the part that says:
then install twrp:
download from techerrata.com/file/twrp2/twr...e-2.0.0RC0
install with:
fastboot -i 0x1949 boot recovery\twrp-blaze-2.0.0RC0.img
and reboot:
fastboot reboot
I do not understand what that means. Plus, I now have the yellow triangle and ADB does not recognize my kindle.
that is normal - your kf should be in fastboot mode now - adb is'nt working here
regarding the driver you have to reinstall the driver at this point - in fastboot mode it should be "android adb interface" in device manager - here is how to do:
-Go to device manager
-right click on the exclamation mark kindle
-Choose update driver software
-choose browse my computer for driver software
-choose let me pick from a list of devices on my computer
-Then select have disk
-Then select browse
-direct to where you downloaded the usb driver
-Select ok and ok
then resume with the downloads and the commands
I just tried, that, but it said that the driver was the same one installed. Is there a different driver that I am supposed to be using? I selected the one I used to root it in my .android file. Is that the right one?
---------- Post added at 05:50 PM ---------- Previous post was at 05:43 PM ----------
Well, I think I just FUBARed it. I uninstalled the driver, reconnected, and not it is not letting me re install the driver because windows says its broken.
Daniel_Fate said:
I just tried, that, but it said that the driver was the same one installed. Is there a different driver that I am supposed to be using? I selected the one I used to root it in my .android file. Is that the right one?
Click to expand...
Click to collapse
no it is'nt - let's start at the beginning and check the precautions:
1. it would be good to know on what computer you are (os/bit)
2. download last kfu from http://forum.xda-developers.com/showthread.php?t=1399889
3. extract it to c:\ and rename from "kindle fire utility" to "kfu" that it is c:\kfu
4. the driver is now at c:\kfu\drivers\kindle - the file is android_winusb.inf
now you have all what you need
tell me if you'hv got it - i'll guide you further
AHA! I got it back, ill follow what you asked. I am running Win 7 64 bit.
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Alright, I downloaded, unzipped, and renamed the KFU. I went into device manager and selected update driver software, went and browsed and selected the kindle folder for the drivers. It started to install, asked if I trusted this unknown source, then started installing. At the end of the install it said:
"Windows found the driver software for your device but encountered an error while attempting to install it.
Android ADB Interface
This device cannot start. (code 10)"
Now my kindle is tethered and on. The screen is just the static kindle fire logo. thoughts?
Daniel_Fate said:
AHA! I got it back, ill follow what you asked. I am running Win 7 64 bit.
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Alright, I downloaded, unzipped, and renamed the KFU. I went into device manager and selected update driver software, went and browsed and selected the kindle folder for the drivers. It started to install, asked if I trusted this unknown source, then started installing. At the end of the install it said:
"Windows found the driver software for your device but encountered an error while attempting to install it.
Android ADB Interface
This device cannot start. (code 10)"
Now my kindle is tethered and on. The screen is just the static kindle fire logo. thoughts?
Click to expand...
Click to collapse
still trouble with the drivers - try to run install_drivers.bat from c:\kfu\
the status of the kf is ok on the logo - it's fastboot
b63 said:
still trouble with the drivers - try to run install_drivers.bat from c:\kfu\
the status of the kf is ok on the logo - it's fastboot
Click to expand...
Click to collapse
Here's what I did:
Opened cmd
entered "cd c:\kfu\"
entered "install_drivers.bat"
A window popped up saying "Welcome to the Kindle Fire Driver Installer. This will
walk you through updating your Kindle Fire. Click Next."
Clicked next
Says "drivers were successfully installed on your computer: Androidusbdeviceclass"
Clicked finish
Went to device manager
Still have yellow triangle.
Am I missing something here out of stupidity/ignorance?
Daniel_Fate said:
Here's what I did:
Opened cmd
entered "cd c:\kfu\"
entered "install_drivers.bat"
A window popped up saying "Welcome to the Kindle Fire Driver Installer. This will
walk you through updating your Kindle Fire. Click Next."
Clicked next
Says "drivers were successfully installed on your computer: Androidusbdeviceclass"
Clicked finish
Went to device manager
Still have yellow triangle.
Am I missing something here out of stupidity/ignorance?
Click to expand...
Click to collapse
no - you don't miss something - it's allways a hassle with win7 espacialy 64 bit
try to unplug - replug
I unpluged, and replugged about 5 times, each time it came up as an unknown device. I then unplugged it, shut it off, plugged it back in, then turned it back on, and it became a yellow triangle ADB.
Daniel_Fate said:
I unpluged, and replugged about 5 times, each time it came up as an unknown device. I then unplugged it, shut it off, plugged it back in, then turned it back on, and it became a yellow triangle ADB.
Click to expand...
Click to collapse
sounds not bad - let's test it:
you still have the command prompt open in c:\kfu\tools
issue the following command:
"fastboot -i 0x1949 getvar product" - it should return "kindle"

[Q] Bricked my fire using Kindle Fire Utility

I tried to use the kindle fire utility in order to root my fire, but when I tried to use it, the first thing I did was install the drivers..... Then change it into fast boot mode, which I didn't realize would make it automatically reboot.... With out TWRP, or the fire fire fire boot loader. It is stuck at the "Kindle Fire" splash screen, and does not even connect to my computer. Is there a way to change it back to normal boot mode? Because when I tried to use the kindle de-bricking utility, it did not work, because it says waiting for device. If anyone could give me some advice, I would appreciate it.
May not help, but try the following: http://forum.xda-developers.com/showpost.php?p=21477909&postcount=13
have you tried to hold pwr button for ~20sec ?
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
b63 said:
have you tried to hold pwr button for ~20sec ?
Click to expand...
Click to collapse
I actually did, I had tried a hard reboot several times.
then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"
jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I will try as soon as I get home. Thanks for the help so far!
jblack426 said:
I had the same problem and it was because the TWRP file was corrupt or incomplete. It went to reboot, and just stuck on the Kindle Fire logo. tried resetting, and everything. What I did was re-install the drivers, plug the device back in to the computer and even if KFU says your kindle isn't connected, try changing the boot mode back to normal. It worked for me and I restarted and tried the whole TWRP installation process over with a non-corrupt file and it worked just fine.
Click to expand...
Click to collapse
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!
it's not save without fff ! you need it to get to twrp and to have fastboot available for some seconds during startup
would recomend to try with kfu 0.9.3 and 0.9.1
some people have success with only one of the versions
Glad you got back to stock at least. The problem I had was that my internet connection timed out when KFU was downloading the files for the TWRP and FFF installation. There were incomplete files that KFU recognized as being there when i re-tried and it tried to install them again. You need to make sure you delete the files in the TWRP folder before you try again that way KFU won't find them and will download them again, hopefully successfully this time. You could also just delete the entire KFU you already have on your computer and download the whole thing again and re-try.
Hopefully this helps.
elporsche said:
I tried your method and it rebooted my kindle succesfully, although it restored itself to factory conditions (which i dont think it's a bad thing, since i was scared of seeing the device stuck with the logo)
I will try to run kfu all over again and see if it works this time. I'll let know how it goes.
Thanks!
EDIT: Which twrp file did you use the second time? Can you post a link to it?
EDIT2: Nevermind about the first edit; the second time, kfu downloaded twrp instead of using its own recovery.img (which i believe is the corrupt file). I still cannot install firefirefire; a command line says "'adb' is not recognized as an internal or external command, operable program or batch file." Any help with that? Or can my kindle be safe without firefirefire? Thanks again!
Click to expand...
Click to collapse
That means it can't find the ADB.exe in tools for Kindke Fire Utility. The tools folder must be in the same folder as the batch file.
b63 said:
then i would try as suggested above - if it don't work you can do it manually by opening a (elevated) command prompt and cd to the tools folder of kfu (eg c:\kfu\tools) and issue "fastboot -i 0x1949 oem idme bootmode 4000"
if it says <waiting for device> cold reboot the kf - the command should be picked up and finished - another reboot should bring you to normal boot
if this not working then you should check your drivers:
for fastboot it should be "android adb interface"
Click to expand...
Click to collapse
Worked! Thank you so much sir! Now that I followed a guide! (since I am no longer a derp about it) I am now rooted.
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Can you please tell me how you changed the boot mode because i also bricked my kindle by the kfu.
- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...
b63 said:
- run kfu
- key in "1" and enter (bootmode menu)
- key in "1" and enter (bootmode normal)
that's it
can't explain easier ...
Click to expand...
Click to collapse
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)
papugoz said:
Not Exactly. First he needs to check the device status by pressing 0, becouse if device have offline mode in KFU, he can't do much (propably he will need to use fastboot comands rather than adb)
Click to expand...
Click to collapse
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands
So what your saying is i can't do anything.
kingrafa135 said:
So what your saying is i can't do anything.
Click to expand...
Click to collapse
it is nearly impossible to realy brick a kf - just do as i suggested
if it's not working tell us what exactly happens ...
some important hints from the op of kfu:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and from vashypooh - dev of kfu:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
b63 said:
wrong - if the device is in fastboot mode adb will allways be offline !
btw. kfu is using fastboot commands
Click to expand...
Click to collapse
From my exp with KFU, I had to use fastboot command directly, becouse KFU, couldn't hadle it.

[GUIDE] [6.3.3] 1st Gen Kindle Drivers, Rooting, Bootloaders & Recovery, and OtterX

[GUIDE] [6.3.3] 1st Gen Kindle Drivers, Rooting, Bootloaders & Recovery, and OtterX
Hello everyone! I am new to working with the Kindle Fire, however, I am by no means new to rooting and tinkering with my devices. Yesterday, I inherited a Kindle Fire with software version 6.3.3 from my brother and I was completely unsure of how to root the device. I am writing this guide because many of the existing guides were unclear and lead me to screw up multiple times. In addition, some claimed to work with the 6.3.3 software version, however, they were designed for an older version of the firmware and would not actually work.
I WILL NOT BE HELD LIABLE IF YOU BRICK YOUR DEVICE USING THESE INSTRUCTIONS! FOLLOW ALL DIRECTIONS CAREFULLY AND REMEMBER TO BACKUP YOUR DATA! YOUR DATA WILL BE WIPED DURING THIS PROCESS. ONLY CONTINUE IF YOU UNDERSTAND THE RISKS! THESE INSTRUCTIONS ARE IN SEQUENTIAL ORDER, FOLLOW EACH STEP! YOU CANNOT SKIP ANY OF THE STEPS!
0. Checking MD5 Hashes
It is very important to check the MD5 hash of every file that you download for this guide. You may use your favorite MD5 checksum utility. Personally, I prefer using this tool created by Microsoft because it is lightweight and extremely fast. Unfortunately, it does take some knowledge of the Command Prompt to use. To begin, download the file and extract it to any folder that you would like. To use the tool, place the file that you are checking within the same folder as the tool. Then, hold shift on your keyboard and right click. Choose the option to open a new Command Prompt window. Then, issue the following commands:
Code:
fciv.exe <exact name of file you are checking>
This will tell you the MD5 checksum of the file that you are checking and you will want to compare it to the value that is listed with the download. Again, you will want to do this for every file that is downloaded for this guide to ensure that you do not damage your device or need to restart the process.
1. Drivers
One problem that I faced while rooting my Kindle Fire was the installation of drivers. Basically, this guide requires you to use unsigned drivers that Windows will refuse to install under normal circumstances. On Windows 8, Windows 8.1, and in the Windows 10 Technical preview, you need to enable Test Mode. Although you can just disable the driver signature verification for one boot, I found this inefficient because I needed to tinker with the drivers multiple times, with each successive installation requiring a reboot of the computer.
To enable Test Mode on Windows 8, Windows 8.1, and Windows 10 Technical Preview, you need some experience with the Command Prompt. Open an Administrative Command Prompt by typing "cmd" into the Start menu and right clicking on the Command Prompt icon. From there, choose the option to open the program with Administrative privileges. Then, issue the following commands:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot your computer.
Next, you will want to download the KFU utility from this XDA developer thread. We will NOT be using the Kindle Fire Utility for this guide because I was unable to get it working with 6.3.3, instead we will be using the included set of drivers because they worked relatively well with this process. After downloading the latest version of KFU, extract it to a folder on your Desktop. Unplug your Kindle Fire if it is plugged in to your computer or the drivers may not install correctly. You will want to open the "install_drivers.bat" file and follow the prompts. One prompt will ask you if you want to run the unsigned driver, you should choose "Install this driver software anyway!". Please restart your computer before continuing with this guide!
Now, you may plug in your Kindle Fire. Before continuing, please ensure that the installation of applications is allowed on the device by opening the settings drop down, clicking "More", and clicking on "Device". From there, check the box that allows the installation of applications. Next, you will want to navigate to the folder in the "Kindle Fire Utility" called "Tools". From here, hold shift on your keyboard and right click. Then, choose the option to open a Command Prompt window. We are going to test to make sure that the Kindle Fire is recognized by the "adb" program. To do this, we are going to issue the following commands:
Code:
adb kill-server
adb usb
adb devices
If you typed these commands correctly, any old instances of the "adb" server will be destroyed. Then, it will start a new server that will work with USB devices. Finally, it will list the connected devices. If the driver installation has succeeded, you will see the serial number of your Kindle Fire as well as an "Online" status. If you do not see your device or it is not marked as "Online", you may need to repeat the steps for installing the drivers. Do NOT continue until these commands list your device as "Online" because it could theoretically damage the device. If you are unable to get these drivers working, I recommend using the GhostBuster utility to remove old Kindle Fire and Android phone drivers.
2. Rooting the Device
This is where you want to back up anything important on the device!
Since I was unable to find an official root method from the Kindle Fire community for patch 6.3.3, I looked into using other methods. Using SafeRoot was suggested by some people and it worked very well for my Kindle Fire. So, to continue, please download the SafeRoot package from this XDA Developers link. Extract these files to a folder of your choice, preferably somewhere that is easy to access. We are NOT using the Kindle Fire Utility for this step because it simply was not compatible with software version 6.3.3.
Now, run the "install.bat" file and follow ALL of the on-screen instructions. The utility will ask you if you wish to install Busybox on your device. Busybox is a powerful utility that combines many powerful Unix utilities into a single file. You can read more about it here. You will want to choose yes when it asks you if it can install Busybox. After following all of the instructions, you should have a SuperUser application on your device that allows you run root commands!
It is NORMAL for the SafeRoot utility to show a lot of errors towards the end relating to read only files. If there are any other errors, your device may not be rooted!
3. Flashing FFF and the TWRP Recovery (Non-OtterX)
First, you will want to download the FBMode file. This file will allow your device to boot into the Fastboot mode, which allows you to flash new bootloader and recovery images. In addition, you will want to download the FireFireFire bootloader image that we will be flashing to the device. You will also need a custom recovery for this device, which can be found here. If you ignore everything else in this guide, just please remember to MD5 check ALL of these files! This is extremely important because a bad flash could BRICK your device!
Extract each of these files to the "Tools" folder inside of the Kindle Fire Utility folder that we used earlier to install the driver. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Type these commands EXACTLY to copy the "fbmode" file to the device. This file will put the device in Fastboot mode.
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell
You will notice that the Command Prompt window looks slightly different because we are now in a shell for the device. This means we are directly issuing commands to the device! Type the following commands exactly to reboot the device in Fastboot mode. Remember, the "exit" command will need to be typed TWICE!
Code:
su
cd /data/local/tmp
./fbmode
exit
exit
adb reboot
If you did everything correctly, you will now be in Fastboot mode! No, you did not brick your Kindle. The device will not boot into the OS until we tell it to so it WILL remain at the Kindle Fire logo indefinitely, even upon rebooting the device. Depending on your operating system, you may need to toy with the driver installation to 'see' the device again.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img".
This is NOT the FireFireFire file, which is named "fff-u-boot_v1.5.bin". DO NOT flash the FireFireFire file to the recovery partition! If you get any errors during this part of the process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 flash recovery <REPLACE ME WITH THE NAME OF RECOVERY IMAGE FILE>
Next, we will flash the bootloader image! Issue the following command to the device using the same Command Prompt window that we used to flash the recovery image.
Code:
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
Now, we will take the device out of Fastboot mode and make sure that our flashes were successful! If you got any errors during the flashing process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
When you reboot, you should get a new Kindle Fire logo that will be White & Blue. Follow the on-screen instructions to enter the Recovery mode and make sure that the Team Win Recovery image boots. If it does, congratulations! You now have a custom recovery and bootloader on your Kindle device!
4. Installing OtterX Bootloader and Recovery Images
Now that you have a custom bootloader and recovery image flashed, you can now experiment with the OtterX project if you wish. Remember that the OtterX project fundamentally alters the device and it may be extremely difficult to revert these changes to the device! OtterX recoveries, boot loaders, and ROMs are not compatible with stock recoveries, boot loaders, and ROMs. If you still wish to use the device as a Kindle, do not proceed!
Now that the disclaimer is out of the way, let's continue! To continue, you will need the OtterX Bootloader and a copy of the TWRP Recovery for OtterX (Fundamentally different than the TWRP recovery from the last step!). Again, REMEMBER TO CHECK THE MD5 CHECKSUMS OF THESE FILES! A corrupted file could brick your device!
To make sure that the wrong recovery and bootloader are not applied, delete the old copies from your Tools folder inside of the Kindle Fire Utility folder. Then, copy over the OtterX versions of the bootloader and recovery images. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Enter the following commands exactly!
You will need to know the name of your bootloader file. It should be named similarly to "otterx-u-boot_v2.05.bin". Make sure it says OtterX in the name of the file! Power on the device to the Kindle Fire screen and issue the following command on your computer.
Code:
fastboot flash bootloader <Name of OtterX Bootloader File>
Now, reboot the device after the flash has fully completed! You should see a new boot logo, meaning that the flash was successful! Before we continue, we will need to change the partition layout of the device. This will erase all of your files that exist on the device, you should have backed then up a few steps ago! At the bootloader screen, short press the power button to enter the boot menu. Then, use short presses of the power button to navigate to the advanced menu. Then, use a long press to enter that menu. Now, use short presses to navigate down to the "Partition Mode" button and use a long press to enter the submenu. Use short presses to press the navigate down to the Confirm button, and finally use one last long press to start the process.
After this has been completed, reboot the device. Again at the Kindle Fire screen, enter the following command on your computer.
You will need to know the name of your recovery file. It should be named similarly to "otterx-twrp-2.7.1.0-recovery.img". Make sure it says OtterX in the name of the file!
Code:
fastboot flash recovery <Name of Recovery Image>
fastboot oem recovery
After issuing both commands, you should see the TWRP recovery screen again! If you do, congratulations! You have flashed the OtterX recovery and bootloader images to your device,
5. Installing OtterX ROMs
I have found that the easiest way to install ROMs to this device is through a function called "adb sideloading". To begin, you will need an OtterX ROM file. I personally recommend Cyanogenmod because it seems fairly stable on this tablet (with my few hours of experience) and I use it as a daily driver on my Galaxy S3.
To begin, grab a copy of ANY OtterX ROM file. You can download Cyanogenmod ROMs from this website. Next, you will also want to download a Google Apps package for your device. You can get that from this website as well.
From the TWRP recovery menu, select the "Wipe" option and then choose "Factory Reset". Follow the onscreen prompts to reset the files on your device. If you get any errors, mount the partitions shown in the "Mounts" menu on the main screen.
Next, go to the Advanced section and choose "ADB Sideload". You should choose the boxes to wipe both caches. To continue, you will need a more up-to-date version of the adb program. You will want just the SDK tools, not the full Android Studio. You can download those tools from this website. After the tools are installed, open up the SDK manager and choose the "Install x Packages" button at the bottom to update the tools. After this is complete, navigate to "C:\Program Files (x86)\Android\android-sdk\platform-tools" on your hard drive. If you are using a 32 bit computer, navigate to "C:\Program Files\Android\android-sdk\platform-tools". Copy your ROM image to this folder and rename it something easy to work with, such as "CM11-OtterX-M12.zip".
Now, you will want to slide the bar across on your device that says "Swipe to Sideload", as well as open a new Command Prompt window on your computer. You can do this by holding shift and right clicking "Open New Command Prompt Window". Now, you will want to issue the following command to make sure your computer can see your Kindle device.
Code:
adb devices
Your device serial number should be listed here and it should say "Sideload" next to the name.
Now, you will want to issue the following command:
Code:
adb sideload <Name of ROM File ZIP>
Now, you will need to wait about 5 minutes while your device is flashed with a new ROM. In my case, the ROM stopped flashing at around 47% with an "Unknown Command" error, however, my device finished the flash okay and the ROM booted just fine. As long as your TWRP recovery shows "Success!", the ROM flash was probably okay. If the ROM flash had failed, you would still be able to try the flash again without harming anything.
You can now go back to the main menu and choose to reboot your device. If the flash was successful, you should see a boot logo for whichever ROM you chose to install. Remember, the initial boot can take a long time.
After verifying that the ROM installed correctly, copy the Google Apps package to your device's internal storage. Depending on which ROM you used, the device should show up as an MTP compatible device in Windows when powered on. Then, reboot into the recovery menu and choose "Install". Then, choose the Google Apps package that you copied to the device to install them. Upon rebooting, the device will update roughly 30-50 apps depending on how much bloatware is installed with your ROM. After that is complete, you will have access to the Google Play store and many useful apps.
Congratulations, you just installed an OtterX rom onto your device!
We need a new update for 2016
ajwgeek said:
Hello everyone! I am new to working with the Kindle Fire, however, I am by no means new to rooting and tinkering with my devices. Yesterday, I inherited a Kindle Fire with software version 6.3.3 from my brother and I was completely unsure of how to root the device. I am writing this guide because many of the existing guides were unclear and lead me to screw up multiple times. In addition, some claimed to work with the 6.3.3 software version, however, they were designed for an older version of the firmware and would not actually work.
I WILL NOT BE HELD LIABLE IF YOU BRICK YOUR DEVICE USING THESE INSTRUCTIONS! FOLLOW ALL DIRECTIONS CAREFULLY AND REMEMBER TO BACKUP YOUR DATA! YOUR DATA WILL BE WIPED DURING THIS PROCESS. ONLY CONTINUE IF YOU UNDERSTAND THE RISKS! THESE INSTRUCTIONS ARE IN SEQUENTIAL ORDER, FOLLOW EACH STEP! YOU CANNOT SKIP ANY OF THE STEPS!
0. Checking MD5 Hashes
It is very important to check the MD5 hash of every file that you download for this guide. You may use your favorite MD5 checksum utility. Personally, I prefer using this tool created by Microsoft because it is lightweight and extremely fast. Unfortunately, it does take some knowledge of the Command Prompt to use. To begin, download the file and extract it to any folder that you would like. To use the tool, place the file that you are checking within the same folder as the tool. Then, hold shift on your keyboard and right click. Choose the option to open a new Command Prompt window. Then, issue the following commands:
Code:
fciv.exe <exact name of file you are checking>
This will tell you the MD5 checksum of the file that you are checking and you will want to compare it to the value that is listed with the download. Again, you will want to do this for every file that is downloaded for this guide to ensure that you do not damage your device or need to restart the process.
1. Drivers
One problem that I faced while rooting my Kindle Fire was the installation of drivers. Basically, this guide requires you to use unsigned drivers that Windows will refuse to install under normal circumstances. On Windows 8, Windows 8.1, and in the Windows 10 Technical preview, you need to enable Test Mode. Although you can just disable the driver signature verification for one boot, I found this inefficient because I needed to tinker with the drivers multiple times, with each successive installation requiring a reboot of the computer.
To enable Test Mode on Windows 8, Windows 8.1, and Windows 10 Technical Preview, you need some experience with the Command Prompt. Open an Administrative Command Prompt by typing "cmd" into the Start menu and right clicking on the Command Prompt icon. From there, choose the option to open the program with Administrative privileges. Then, issue the following commands:
Code:
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot your computer.
Next, you will want to download the KFU utility from this XDA developer thread. We will NOT be using the Kindle Fire Utility for this guide because I was unable to get it working with 6.3.3, instead we will be using the included set of drivers because they worked relatively well with this process. After downloading the latest version of KFU, extract it to a folder on your Desktop. Unplug your Kindle Fire if it is plugged in to your computer or the drivers may not install correctly. You will want to open the "install_drivers.bat" file and follow the prompts. One prompt will ask you if you want to run the unsigned driver, you should choose "Install this driver software anyway!". Please restart your computer before continuing with this guide!
Now, you may plug in your Kindle Fire. Before continuing, please ensure that the installation of applications is allowed on the device by opening the settings drop down, clicking "More", and clicking on "Device". From there, check the box that allows the installation of applications. Next, you will want to navigate to the folder in the "Kindle Fire Utility" called "Tools". From here, hold shift on your keyboard and right click. Then, choose the option to open a Command Prompt window. We are going to test to make sure that the Kindle Fire is recognized by the "adb" program. To do this, we are going to issue the following commands:
Code:
adb kill-server
adb usb
adb devices
If you typed these commands correctly, any old instances of the "adb" server will be destroyed. Then, it will start a new server that will work with USB devices. Finally, it will list the connected devices. If the driver installation has succeeded, you will see the serial number of your Kindle Fire as well as an "Online" status. If you do not see your device or it is not marked as "Online", you may need to repeat the steps for installing the drivers. Do NOT continue until these commands list your device as "Online" because it could theoretically damage the device. If you are unable to get these drivers working, I recommend using the GhostBuster utility to remove old Kindle Fire and Android phone drivers.
2. Rooting the Device
This is where you want to back up anything important on the device!
Since I was unable to find an official root method from the Kindle Fire community for patch 6.3.3, I looked into using other methods. Using SafeRoot was suggested by some people and it worked very well for my Kindle Fire. So, to continue, please download the SafeRoot package from this XDA Developers link. Extract these files to a folder of your choice, preferably somewhere that is easy to access. We are NOT using the Kindle Fire Utility for this step because it simply was not compatible with software version 6.3.3.
Now, run the "install.bat" file and follow ALL of the on-screen instructions. The utility will ask you if you wish to install Busybox on your device. Busybox is a powerful utility that combines many powerful Unix utilities into a single file. You can read more about it here. You will want to choose yes when it asks you if it can install Busybox. After following all of the instructions, you should have a SuperUser application on your device that allows you run root commands!
It is NORMAL for the SafeRoot utility to show a lot of errors towards the end relating to read only files. If there are any other errors, your device may not be rooted!
3. Flashing FFF and the TWRP Recovery (Non-OtterX)
First, you will want to download the FBMode file. This file will allow your device to boot into the Fastboot mode, which allows you to flash new bootloader and recovery images. In addition, you will want to download the FireFireFire bootloader image that we will be flashing to the device. You will also need a custom recovery for this device, which can be found here. If you ignore everything else in this guide, just please remember to MD5 check ALL of these files! This is extremely important because a bad flash could BRICK your device!
Extract each of these files to the "Tools" folder inside of the Kindle Fire Utility folder that we used earlier to install the driver. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Type these commands EXACTLY to copy the "fbmode" file to the device. This file will put the device in Fastboot mode.
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell
You will notice that the Command Prompt window looks slightly different because we are now in a shell for the device. This means we are directly issuing commands to the device! Type the following commands exactly to reboot the device in Fastboot mode. Remember, the "exit" command will need to be typed TWICE!
Code:
su
cd /data/local/tmp
./fbmode
exit
exit
adb reboot
If you did everything correctly, you will now be in Fastboot mode! No, you did not brick your Kindle. The device will not boot into the OS until we tell it to so it WILL remain at the Kindle Fire logo indefinitely, even upon rebooting the device. Depending on your operating system, you may need to toy with the driver installation to 'see' the device again.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img".
This is NOT the FireFireFire file, which is named "fff-u-boot_v1.5.bin". DO NOT flash the FireFireFire file to the recovery partition! If you get any errors during this part of the process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 flash recovery <REPLACE ME WITH THE NAME OF RECOVERY IMAGE FILE>
Next, we will flash the bootloader image! Issue the following command to the device using the same Command Prompt window that we used to flash the recovery image.
Code:
fastboot -i 0x1949 flash bootloader fff-u-boot_v1.5.bin
Now, we will take the device out of Fastboot mode and make sure that our flashes were successful! If you got any errors during the flashing process, DO NOT continue! You may brick your device!
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
When you reboot, you should get a new Kindle Fire logo that will be White & Blue. Follow the on-screen instructions to enter the Recovery mode and make sure that the Team Win Recovery image boots. If it does, congratulations! You now have a custom recovery and bootloader on your Kindle device!
4. Installing OtterX Bootloader and Recovery Images
Now that you have a custom bootloader and recovery image flashed, you can now experiment with the OtterX project if you wish. Remember that the OtterX project fundamentally alters the device and it may be extremely difficult to revert these changes to the device! OtterX recoveries, boot loaders, and ROMs are not compatible with stock recoveries, boot loaders, and ROMs. If you still wish to use the device as a Kindle, do not proceed!
Now that the disclaimer is out of the way, let's continue! To continue, you will need the OtterX Bootloader and a copy of the TWRP Recovery for OtterX (Fundamentally different than the TWRP recovery from the last step!). Again, REMEMBER TO CHECK THE MD5 CHECKSUMS OF THESE FILES! A corrupted file could brick your device!
To make sure that the wrong recovery and bootloader are not applied, delete the old copies from your Tools folder inside of the Kindle Fire Utility folder. Then, copy over the OtterX versions of the bootloader and recovery images. Again, open a Command Prompt window inside of the Tools folder by holding shift and right clicking, then choosing the option to open a new Command Prompt window. Enter the following commands exactly!
You will need to know the name of your bootloader file. It should be named similarly to "otterx-u-boot_v2.05.bin". Make sure it says OtterX in the name of the file! Power on the device to the Kindle Fire screen and issue the following command on your computer.
Code:
fastboot flash bootloader <Name of OtterX Bootloader File>
Now, reboot the device after the flash has fully completed! You should see a new boot logo, meaning that the flash was successful! Before we continue, we will need to change the partition layout of the device. This will erase all of your files that exist on the device, you should have backed then up a few steps ago! At the bootloader screen, short press the power button to enter the boot menu. Then, use short presses of the power button to navigate to the advanced menu. Then, use a long press to enter that menu. Now, use short presses to navigate down to the "Partition Mode" button and use a long press to enter the submenu. Use short presses to press the navigate down to the Confirm button, and finally use one last long press to start the process.
After this has been completed, reboot the device. Again at the Kindle Fire screen, enter the following command on your computer.
You will need to know the name of your recovery file. It should be named similarly to "otterx-twrp-2.7.1.0-recovery.img". Make sure it says OtterX in the name of the file!
Code:
fastboot flash recovery <Name of Recovery Image>
fastboot oem recovery
After issuing both commands, you should see the TWRP recovery screen again! If you do, congratulations! You have flashed the OtterX recovery and bootloader images to your device,
5. Installing OtterX ROMs
I have found that the easiest way to install ROMs to this device is through a function called "adb sideloading". To begin, you will need an OtterX ROM file. I personally recommend Cyanogenmod because it seems fairly stable on this tablet (with my few hours of experience) and I use it as a daily driver on my Galaxy S3.
To begin, grab a copy of ANY OtterX ROM file. You can download Cyanogenmod ROMs from this website. Next, you will also want to download a Google Apps package for your device. You can get that from this website as well.
From the TWRP recovery menu, select the "Wipe" option and then choose "Factory Reset". Follow the onscreen prompts to reset the files on your device. If you get any errors, mount the partitions shown in the "Mounts" menu on the main screen.
Next, go to the Advanced section and choose "ADB Sideload". You should choose the boxes to wipe both caches. To continue, you will need a more up-to-date version of the adb program. You will want just the SDK tools, not the full Android Studio. You can download those tools from this website. After the tools are installed, open up the SDK manager and choose the "Install x Packages" button at the bottom to update the tools. After this is complete, navigate to "C:\Program Files (x86)\Android\android-sdk\platform-tools" on your hard drive. If you are using a 32 bit computer, navigate to "C:\Program Files\Android\android-sdk\platform-tools". Copy your ROM image to this folder and rename it something easy to work with, such as "CM11-OtterX-M12.zip".
Now, you will want to slide the bar across on your device that says "Swipe to Sideload", as well as open a new Command Prompt window on your computer. You can do this by holding shift and right clicking "Open New Command Prompt Window". Now, you will want to issue the following command to make sure your computer can see your Kindle device.
Code:
adb devices
Your device serial number should be listed here and it should say "Sideload" next to the name.
Now, you will want to issue the following command:
Code:
adb sideload <Name of ROM File ZIP>
Now, you will need to wait about 5 minutes while your device is flashed with a new ROM. In my case, the ROM stopped flashing at around 47% with an "Unknown Command" error, however, my device finished the flash okay and the ROM booted just fine. As long as your TWRP recovery shows "Success!", the ROM flash was probably okay. If the ROM flash had failed, you would still be able to try the flash again without harming anything.
You can now go back to the main menu and choose to reboot your device. If the flash was successful, you should see a boot logo for whichever ROM you chose to install. Remember, the initial boot can take a long time.
After verifying that the ROM installed correctly, copy the Google Apps package to your device's internal storage. Depending on which ROM you used, the device should show up as an MTP compatible device in Windows when powered on. Then, reboot into the recovery menu and choose "Install". Then, choose the Google Apps package that you copied to the device to install them. Upon rebooting, the device will update roughly 30-50 apps depending on how much bloatware is installed with your ROM. After that is complete, you will have access to the Google Play store and many useful apps.
Congratulations, you just installed an OtterX rom onto your device!
Click to expand...
Click to collapse
We need new links for kindle fire first gen 6.3.4 . these methods available don't work. thank you
ataraxioss said:
We need new links for kindle fire first gen 6.3.4 . these methods available don't work. thank you
Click to expand...
Click to collapse
no, this still works with 6.3.4
Sent from my KFFOWI using Tapatalk
---------- Post added at 06:55 PM ---------- Previous post was at 06:54 PM ----------
there is one link to goo.im which is down
With the Fall of Goo.im I will be posting Mirrors OtterX files here:
Otter X Twrp and Bootloader Mirrors
Sent from my KFFOWI using Tapatalk
I've just tried it
Still not working on my kindle fire. sounds to be rooted but can't install twrp.
i was hoping to flash it with Miui 7.
thank you for your precious time, i wish the old links in kindle fire utility could still work.
ataraxioss said:
Still not working on my kindle fire. sounds to be rooted but can't install twrp.
i was hoping to flash it with Miui 7.
thank you for your precious time, i wish the old links in kindle fire utility could still work.
Click to expand...
Click to collapse
did you verify root? try root checker
Sent from my KFFOWI using Tapatalk
reply
sd_shadow said:
did you verify root? try root checker
Sent from my KFFOWI using Tapatalk
Click to expand...
Click to collapse
once it is frozen on "trying to disable knox.." nothing goes right after that. the kindle fire does not reboot and i guess supersu is not updating either.
Ps: i have rooted and installed twrp many times before, then i did a factory reset on the kindle fire.
ataraxioss said:
once it is frozen on "trying to disable knox.." nothing goes right after that. the kindle fire does not reboot and i guess supersu is not updating either.
Ps: i have rooted and installed twrp many times before, then i did a factory reset on the kindle fire.
Click to expand...
Click to collapse
Factory reset doesn't unroot, just reinstall supersu app
Sent from my XT1060 using Tapatalk
So I got up to this point.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img". "
Click to expand...
Click to collapse
The kindle won't restart. When I plug it into my computer I get the error "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." The kindle is stuck on the start up screen where it says "Kindle Fire." Any help would be greatly appreciated. I know nothing about any of this stuff so I am stumped from here on out.
Also nothing is showing up in device manager that is related to the Kindle.
thealy1234 said:
So I got up to this point.
Test to make sure that the Kindle still responds to commands before continuing by issuing the following command within the same command prompt window that we used previously to copy the "fbmode" file.
Code:
fastboot -i 0x1949 reboot
The kindle should reboot into the Fastboot mode again! If not, please use this post to get the drivers working. In my case, the device responded to the reboot command, however, it did NOT show up when I checked the connected devices by issuing the following command:
Code:
fastboot -i 0x1949 devices
If all is well and the Kindle rebooted, it is time to flash the bootloader and recovery images! Remember to check the MD5 hash for these files! You WILL need to know the name of your recovery image, it should be named something very similar to "openrecovery-twrp-2.2.2.1-blaze.img". "
The kindle won't restart. When I plug it into my computer I get the error "The last USB device you connected to this computer malfunctioned, and Windows does not recognize it." The kindle is stuck on the start up screen where it says "Kindle Fire." Any help would be greatly appreciated. I know nothing about any of this stuff so I am stumped from here on out.
Also nothing is showing up in device manager that is related to the Kindle.
Click to expand...
Click to collapse
try a different USB port or cable
Sent from my Motorola XT1060 using XDA Labs
sd_shadow said:
try a different USB port or cable
Sent from my Motorola XT1060 using XDA Labs
Click to expand...
Click to collapse
This was the problem. Turns out this doesn't work when the kindle is plugged into a USB 3.0 port.
That being solved, I now have a different problem. I get the following error when I try and push the recovery image onto my kindle after I added the Otterbox bootloader file: "target reported max download size of 402653184 bytes error: cannot load 'recovery.img': No error."
(I renamed the file to recovery.img on the advice of someone else)
Also note that I had to get the otter recovery image from a different source than what was listed in the guide, for the provided link was broken.
Any ideas would be appreciated.
Thanks
thealy1234 said:
This was the problem. Turns out this doesn't work when the kindle is plugged into a USB 3.0 port.
That being solved, I now have a different problem. I get the following error when I try and push the recovery image onto my kindle after I added the Otterbox bootloader file: "target reported max download size of 402653184 bytes error: cannot load 'recovery.img': No error."
(I renamed the file to recovery.img on the advice of someone else)
Also note that I had to get the otter recovery image from a different source than what was listed in the guide, for the provided link was broken.
Any ideas would be appreciated.
Thanks
Click to expand...
Click to collapse
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
Sent from my XT1060 using Tapatalk
sd_shadow said:
[6.3.4][6.3.3] Flashing FFF and TWRP without Fastboot Cable with Video
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I have followed that guide to the T and I still get that error. It worked just fine when I was installed the TWRP recovery.
For some reason when I am trying to install the otterx twrp version, I am getting that error returned to me.
thealy1234 said:
I have followed that guide to the T and I still get that error. It worked just fine when I was installed the TWRP recovery.
For some reason when I am trying to install the otterx twrp version, I am getting that error returned to me.
Click to expand...
Click to collapse
try OtterX bootloader and OtterX twrp from my post
OtterX files here:
Otter X Twrp and Bootloader Mirrors
Sent from my XT1060 using Tapatalk
The 2.8.5.0 file that you provide worked. One more step closer...
I appreciate the help.
---------- Post added at 10:45 PM ---------- Previous post was at 10:26 PM ----------
I just can't win today.
Now I am stuck because TWRP cannot mount /data for some reason...
thealy1234 said:
The 2.8.5.0 file that you provide worked. One more step closer...
I appreciate the help.
---------- Post added at 10:45 PM ---------- Previous post was at 10:26 PM ----------
I just can't win today.
Now I am stuck because TWRP cannot mount /data for some reason...
Click to expand...
Click to collapse
mount data is ify with OtterX, try adb push with OtterX twrp 2.7.1.0
---------- Post added at 01:11 AM ---------- Previous post was at 01:10 AM ----------
Started a Thread [How To] Fix OtterX Install Errors, Partition sizes, Unable to Mount System... with some possible fixes for those having issues since converting to OtterX, with pushing files, failure to mount system errors when installing Lollipop Roms...
After your help + plenty of head scratching I finally managed to install everything 100%.
Biggest hangup was before I realized this process wouldn't work on a USB 3.0 port....
I'm having an issue with being able to actually install drivers on my computer with Windows 10. I attempted to follow the guide but I am getting denied on an error with "bcdedit -set TESTSINGING ON".
"An error has occurred setting the element data. The value is protected by Secure Boot policy and cannot be modified or deleted."
Any advice for a workaround on installing the drivers?

And now what i do with my Axon 7?

Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Let me link you my ingenious, allmighty Axon 7 Companion Thread.
Try to install twrp with MiFlash if you can enter edl mode
macerf said:
Hello everyone. Meanwhile you excuse me for imperfect English but I use translator, my English language is rusted...
I have a A2017G, I have managed to unlock the bootloader, install TWRP and SuperSu on 6.0.1 version But then I have had the nice idea to update to 7.1.1 then have put update. zip file (renamed), in SD card, turn off the terminal, enter into TWRP but it Disappear!!! Only Originale...io recovery make flash and device updated to B09.
I want to install TWRP and SuperSu and put alternative ROMs but I can't do anything! If I open PowerShell window in adb folder and command "ADB reboot bootloader", the device reboot and appear a screen where to " your devices software can't be checked for corruption, please lock the bootloader", ecc ecc, If I squeeze volume on, it will get into recovery, if I don't do anything it reboot normally.
I can not get into fastboot mode, I fail to install TWRP. What is the best way to go back? or reset everything and start again? I have tried to downgrade from Nougat to MM via SD but after about 1 minute of analysis I aborted the installation....
However the phone will work normally even without all these things but I have purchased ZTE for modding and I don't bear to have half fatto...in work the most difficult thing to be unlocking the bootloader and I do this thing...
Click to expand...
Click to collapse
Your phone works normally
You don't have fastboot
You have stock recovery
If this is the case then most surely you have EDL working...
Install TWRP from EDL mode:
This is taken from Controllerboy's guide
BE SURE THAT WINDOWS SHOWS FILE NAME EXTENSIONS!
A) Flashing TWRP Recovery to your device.
Q: Why do I need TWRP?
A: TWRP is a custom recovery system. It lets your backup your system in case anything goes wrong. It also lets you flash custom ROMs and zip files containing patches like viper4android or A.R.I.S.E. (audio) and root your device via SuperSU.
0) Boot up a windows computer with a 64bits processor. Verify your Axon 7 is charged at least 75%. Temporarily disable your antivirus software to allow axon7tool to work.
1) Backup all the data of your phone's internal memory that you don't want to lose. Copy it to your PC
2) Download the axon7tool from here: http://www.filedropper.com/axon7tool-15-win64
3) Download minimal adb and fastboot from here: https://www.androidfilehost.com/?fid=457095661767103465
4) Unzip the minimal adb and fastboot file, place the folder with the files in it somewhere you can easily find it
5) Place the axon7tool exe in the same folder as adb.exe and rename it to "axon7tool.exe" (it's easier to work with that way)
6) Download the TWRP .img and .bin files from here: https://drive.google.com/open?id=0B4...nlaZU1NRldoRjA
7) Place the TWRP .img file in the same folder as "adb.exe" and "axon7tool.exe", rename it to "recovery.img"
8) Make a copy of the "recovery.img" file and name it "recovery.bin". Leave it in the same folder
9) Go to settings in your phone and go to "About Phone". Tap "Build Number" 7 times to make the Developer Options available
10) Go to "Developers options" and tick "Allow OEM unlock" and "Android Debugging"
11) Connect your Axon 7 to your PC
12) Open a command window by holding shift and right-clicking in a blank space in the folder where the "adb.exe", " axon7tool.exe", "recovery.img" and "recovery.bin" files are located. Click "Open command window here"
13) Type "adb devices" and hit enter. You should see one device with some code listed
14) Type "adb reboot edl" and hit enter. Your device will reboot to EDL mode. It appears to be off, but it is in fact in EDL mode.
15) Go to Device Manager on your pc and verify your Axon 7 is listed as "QUSB_BULK"
16) In command, type "axon7tool -r gpt boot recovery" and hit enter
17) After it is executed, your phone will reboot. Wait until it has fully booted.
18) In command, type "adb reboot edl"
19) Verify you now have 3 backup files in your ADB folder for gpt, recovery and boot. These are backup files in case something goes wrong
20) In command, type "axon7tool -w recovery"
21) Wait until it finishes
22) Your phone should reboot
23) Shut down your phone and boot it to TWRP by holding both the power and volume up button to verify you have TWRP
24) TWRP might ask you for a password. If it does, simply tap cancel. It will ask you if you want to modify system. Swipe to agree
NOTE: if you have problems connecting to your phone as QUSB_BULK, download Zadig and replace your drivers with WinUSB ones. If axon7tool doesn't recignise your device even when connected as QUSB_BULK, try killing adb.exe via task manager before retrying.
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
macerf said:
Hello and thanks for the guide.
I have tried this system... be gone everything OK up to number 16... when I type "Axon7tool -r gpt boot recovery ", the command window should be written "Failed to connect "... and yet the device is in EDL mode.
Be all right, on Device Manager be seen as "QUSB_BULK ", the cable being original, all steps 1 to 16 be ok...io no longer know what to do.
Click to expand...
Click to collapse
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Choose an username... said:
Easy. Hold all 3 keys (power, vol up and down) until Device Manager refreshes (you'll see it as the list of devices contracting), and close CMD. Open it again and do step 16 again
Click to expand...
Click to collapse
Hello and thanks for the advice. Unfortunately it does not change anything.. I have done exactly as you say but the result does not change anything...io have connected the device, Open command window, type "adb devices ", is viewed as "Cd07b2e9 device ", I type "adb reboot EDL ", it restarts in EDL, then go to management Devices and is viewed as "QUSB_BULK ", Run command "Axon7tool-r GPT boot recovery " but it says "Failed to connect ", then I'll return to Device Manager, hold volume up & Down & Power, Icon disappears and returns after a few seconds, close window and launch command "Axon7tool-r GPT boot recovery " but still give "failed to connect "...
So, recapping: I have bootloader unlocked, I can get into EDL but PC does not see device although on Device Manager it exists...
I now launch device into the wall... problem solved.
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
kitcostantino said:
if you really slammed it against the wall, i would love to buy the back housing and speaker grills. hopefully, you were just illustrating frustration (it is a frustrating scenario), and will reach a resolution, but if you actually did smash it, i could use some parts.
Click to expand...
Click to collapse
Of course I'm kidding... have just purchased this device, have a great hardware but the software does not go well for nothing. I have had a dozen phones, I changed about 60 ROMs, so for me it is not difficult to change the software...ma in this case have problems. Is it possible that I fail to solve this problem? Be a way to reset everything and start from scratch? Okay, the bootloader be unlocked but not be any other way to go back? I have seen many guides but not able to solve the problem. I fail to make flash of TWRP, fail to do downgrade to MM....io hope someone help me... thanks.
are you using a USB 2.0 or 3.0 port? it may not apply to this scenario, but with Motorola and RSD Lite, I always had to use usb 2.0 ports or it wouldnt see my device when flashing.
also, the steps @choose an username listed out are the best way to start from scratch, but obviously you have to be able to have your computer see the phone in the desired mode.
@DrakenFX has several guides in the axon 7 forums that should help once the computer sees the phone as well.
I use USB 3.0 with original cable ... but if you now tell me that maybe this is my problem, then I use USB 2.0. Thank you...
Good morning...
Nothing to do... I put the original cable on USB Port 2.0, have redone procedure from window PowerShell, on command "adb devices " Everything OK, on command "adb reboot EDL " It enters EDL mode, but then all the procedures are failed... if command "Axon7tool-R recovery GPT boot "I always get out of the inscription " Failed to connect ", it remains in EDL and I just have to reboot... I replaced the drivers with Zadig 2.3 but did not change anything... are there any other moors to make flash of TWRP? exist lthough an app that do this? I remember that for LG G3 I'll fix everything with an app...

Categories

Resources