Develop Bugs

[Q] Seemingly stuck in bootloop

I used the Kindle FIre Utility that was stickied to install ClockworkMod. Unfortunately, the utility gives an error message when I attempted to root or install FFF or really do anything else. However, I was able to boot into CWM using the utility. I remember from my experience with ROMs on the Samsung Captivate (AT&T) that installing new ROMs would overwrite things like being unrooted or even recovery mode itself. So I downloaded the zip of Alien Droid and flashed it using ClockworkMod. I wiped data and cache and dalvik cache. I then rebooted the device to find it bootlooping on the Alien Droid logo. So I plug it back into the computer, the computer recognizes the ADB interface as "Android." However, Kindle Fire Utility does not recognize the device anymore since it is not known as "kindle" or at least that's what I seemed to gather. So It's stuck bootlooping for now and I'm not sure how to get it out of the boot loop or how to get back to stock. Anybody have any pointers?
Links:
[Root][TWRP][FFF][CWM]Kindle Fire Utility v0.9.6 (5/09/12)
[ROM] [CM10] [JB]►Alien Droid◄(Complete GUI customization)

What version of CWM did you use? (very important)

soupmagnet said:
What version of CWM did you use? (very important)
Click to expand...
Click to collapse
The version that came with the Kindle Fire Utility I linked above. I'm not sure what number it is, but it allowed for touch functions and was black with red text.

The only version that comes to kfu anymore is sbloods but I only know it to be gb and ics safe don't know about jelly bean
---------- Post added at 09:47 PM ---------- Previous post was at 09:41 PM ----------
Also you should have included a factory reset and system wipe to you scheme of wipes all you have is a broken system very likely...

I would say install twrp manually in fastboot (temporary or otherwise)

Thepooch said:
The only version that comes to kfu anymore is sbloods but I only know it to be gb and ics safe don't know about jelly bean
---------- Post added at 09:47 PM ---------- Previous post was at 09:41 PM ----------
Also you should have included a factory reset and system wipe to you scheme of wipes all you have is a broken system very likely...
Click to expand...
Click to collapse
I did do a factory reset. I accidentally mentioned in the post that I wiped data, but what I meant was factory reset. The kindle still shows up in the computer when I plug it in, so I feel like there is some hope.

Did you create a backup?

soupmagnet said:
I would say install twrp manually in fastboot (temporary or otherwise)
Click to expand...
Click to collapse
How would I go about this while bootlooping?
Thepooch said:
Did you create a backup?
Click to expand...
Click to collapse
No, but how would I use a backup anyway while bootlooping?
EDIT: could I use a backup from another kindle fire using this method?

My thought was to get back into recovery and restore your backup but that's not possible without fff
A backup from another kindle if it was created in cwmr yes I believe this is possible...

thethinkman said:
How would I go about this while bootlooping?
Click to expand...
Click to collapse
Even while bootlooping, you should still be able to issue adb commands, check your drivers. Also, the Alien Droid animation takes a really long time the first time around. How long did you let it sit before shutting it off?

soupmagnet said:
Even while bootlooping, you should still be able to issue adb commands, check your drivers. Also, the Alien Droid animation takes a really long time the first time around. How long did you let it sit before shutting it off?
Click to expand...
Click to collapse
If your bootlooping but still get adb acces before it reboots, you should try the steps in this post...
http://forum.xda-developers.com/showpost.php?p=30098800&postcount=7
Then flash whatever rom or erase cache/dalvik-cache/userdata.

Even while bootlooping, you should still be able to issue adb commands, check your drivers. Also, the Alien Droid animation takes a really long time the first time around. How long did you let it sit before shutting it off?
Click to expand...
Click to collapse
This is true. Although I don't know much about how to operate adb, I do have it installed. I waited an hour or two, the animation stops at some point and freezes but the usb connection still works.
lmntone said:
If your bootlooping but still get adb acces before it reboots, you should try the steps in this post...
http://forum.xda-developers.com/showpost.php?p=30098800&postcount=7
Then flash whatever rom or erase cache/dalvik-cache/userdata.
Click to expand...
Click to collapse
I don't currently have TWRP installed on the kindle, just clockworkmod. I will try to install TWRP from adb and see what I can do.
EDIT: While my computer detects the kindle as an "Android ADB Interface" when I type "adb devices" into cmd nothing shows when the kindle is plugged in (but my phone shows when it's plugged in with USB debugging enabled, so I know I have it installed properly at least). I think the proper drivers are not installed.
EDIT 2: I uninstalled the driver for it to install the google usb driver but it failed to install the new one. Now when I plug the Kindle in it shows up as an empty Removable device in Computer butt does not show up anywhere else.

thethinkman said:
This is true. Although I don't know much about how to operate adb, I do have it installed. I waited an hour or two, the animation stops at some point and freezes but the usb connection still works.
I don't currently have TWRP installed on the kindle, just clockworkmod. I will try to install TWRP from adb and see what I can do.
EDIT: While my computer detects the kindle as an "Android ADB Interface" when I type "adb devices" into cmd nothing shows when the kindle is plugged in (but my phone shows when it's plugged in with USB debugging enabled, so I know I have it installed properly at least). I think the proper drivers are not installed.
EDIT 2: I uninstalled the driver for it to install the google usb driver but it failed to install the new one. Now when I plug the Kindle in it shows up as an empty Removable device in Computer butt does not show up anywhere else.
Click to expand...
Click to collapse
"Android ADB Interface" usually appears in the device manager when the KF is in fastboot mode, but if you are seeing the boot animation from the ROM, it cannot be in fastboot mode. I'm not sure where your KF is in the boot process, so it's important to figure that out first. Take a look at this fastboot guide...
http://forum.xda-developers.com/showthread.php?t=1668159
and it sounds like your device drivers are going to need some help as well...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2

kinfauns said:
"Android ADB Interface" usually appears in the device manager when the KF is in fastboot mode, but if you are seeing the boot animation from the ROM, it cannot be in fastboot mode. I'm not sure where your KF is in the boot process, so it's important to figure that out first. Take a look at this fastboot guide...
http://forum.xda-developers.com/showthread.php?t=1668159
and it sounds like your device drivers are going to need some help as well...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
Click to expand...
Click to collapse
I installed the drivers and now the Kindle is detected by adb when I type adb devices. ADB tells me it is in normal boot mode (4000). However, I cannot switch to ffastboot. It tells me it cannot find the drive specified and that permission is denied.

FFF, assuming you installed it, goes into temporary fastboot for the first few seconds the the bootloader is running. Use that time to do what you need to do in fastboot. When the device detects you are trying to do something in fastboot during this time, it will stop the countdown and stay in fastboot.

[Q] Problems after unrooting Kindle Fire 1st Gen

I used this method that I got from this thread to unroot the device to 6.3.3: http://forum.xda-developers.com/showthread.php?t=1399072. The setup wifi came up, but I decided to skip that. Whenever I unlock the screen, it keeps giving me two errors like android.process.acore and something about calendar storage unfortunately stopped. Then it reboots the device. Does anyone tell me how I can stop all this? Does this mean I can't use it anymore?

Try a factory reset
Sent from my XT862 using Tapatalk

Cannot do a factory reset
sd_shadow said:
Try a factory reset
Sent from my XT862 using Tapatalk
Click to expand...
Click to collapse
I don't think I can do it. I think I have to go into the settings and then go to there. I don't have much time to click on things before it reboots again. The two messages come up, then I i have a few seconds to get to settings. Another message telling me that the "android.process.acore has stopped unfortunately" error comes back again. I hit force close. Then by the time I get to the place I want to be in the settings, the device is rebooting.

aReZ12 said:
I don't think I can do it. I think I have to go into the settings and then go to there. I don't have much time to click on things before it reboots again. The two messages come up, then I i have a few seconds to get to settings. Another message telling me that the "android.process.acore has stopped unfortunately" error comes back again. I hit force close. Then by the time I get to the place I want to be in the settings, the device is rebooting.
Click to expand...
Click to collapse
may need to try to root, then install twrp/bootloader or get a fastboot/factory cable and install twrp/bootloader

sd_shadow said:
may need to try to root, then install twrp/bootloader or get a fastboot/factory cable and install twrp/bootloader
Click to expand...
Click to collapse
I don't think I will be able to root it normally. So if I do get the cable, where would I buy it from? Would you able to get it from Amazon?

aReZ12 said:
I don't think I will be able to root it normally. So if I do get the cable, where would I buy it from? Would you to able to get it from Amazon?
Click to expand...
Click to collapse
Several options to get a Fastboot or Factory cable
I use a TBH Factory adaptor
SkOrPn fastboot cable
Fastboot Motorola Factory Cable-ebay
Fastboot Motorola Factory Cable-Amazon
---------- Post added at 06:55 PM ---------- Previous post was at 06:39 PM ----------
then see my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery

sd_shadow said:
Several options to get a Fastboot or Factory cable
I use a TBH Factory adaptor
SkOrPn fastboot cable
Fastboot Motorola Factory Cable-ebay
Fastboot Motorola Factory Cable-Amazon
---------- Post added at 06:55 PM ---------- Previous post was at 06:39 PM ----------
then see my Using Factory/Fastboot Cable to Flash FFF Bootloader and TWRP Recovery
Click to expand...
Click to collapse
I am looking at the thread you gave me. It says that after you install TWRP, install "update-kindle-prerooted.6.3.3.v1.zip". That would be a rooted version of the stock right? How would I install the nonrooted version? I had the Kindle Fire rooted with a custom rom before the problems occurred and wanted to unroot the device.

aReZ12 said:
I am looking at the thread you gave me. It says that after you install TWRP, install "update-kindle-prerooted.6.3.3.v1.zip". That would be a rooted version of the stock right? How would I install the nonrooted version? I had the Kindle Fire rooted before the problems occurred and wanted to unroot the device.
Click to expand...
Click to collapse
download update-kindle-6.3.3_D01E_4112920.bin
verify 204 MB (214,586,505 bytes) MD5: 89A4DEF015289F2291BF502E09A70554
rename update.zip, place on sd card
install in TWRP 2.2.2.1

Kindle Fire not Shown on List of ADB devices
I got the fastboot cablee a few days ago. The device is not listed when I type in "adb devices". I was able to get it the computer to recognize the device as "Android Composite ADB device", but the device is not listed. When I looked at the Hardware IDs, I saw they were different. The original IDs are supposed to be than what is listed on here: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/.
My Hardware Ids show:
USB \VID_1949&PID_0006&REV_0100
USB \VID_1949&PID_0006
I changed in the "android_winusb.ini" file to
;Kindle Fire%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB \VID_1949&PID_0006
When I tried updating the driver, it had "The device could not be started. (error 10)" I unplugged the device from the computer for like half an hour and then plugged it back in. When I did that and went to the device manager, the Android Composite ADB Interface had no exclamation point with a yellow triangle. It also says the driver is working correctly. I still cannot get the device to show up in the ADB device list though. There is no way I can enable USB debugging. How can I get the device to show up in the list?

adb commands do not work when using a Fastboot cable
use fastboot commands
like
Code:
fastboot devices
should get something like
Code:
123456789 fastboot

Thanks!
sd_shadow said:
adb commands do not work when using a Fastboot cable
use fastboot commands
like
Code:
fastboot devices
should get something like
Code:
123456789 fastboot
Click to expand...
Click to collapse
Thanks for your help! I was able to fix the Kindle. I think I figured out why I got the errors and reboots. I didn't factory reset the device before installing the stock rom and decided to either factory reset the device or clear the dalvik cache/cache after I installed the stock rom, which I don't think you are supposed to do.

[Q] TWRP flash failed but firefirefire installed, now I can't get to fastboot mode

I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.

kas782000 said:
I've been trying to root my Kindle Fire running 6.3.3. I bought a fastboot cable and got it to boot into fastboot mode to flash TWRP and firefirefire. I ran the commands and TWRP failed but firefirefire installed. Now when the kindle boots I get the firefirefire bootloader but it cant boot into the recovery because the TWRP never installed. Also, I can't get it to fastboot anymore, not even with the cable. Can anyone please help me get TWRP installed? I've read many forums and tried about everything I found.
Click to expand...
Click to collapse
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle

sd_shadow said:
FFF bootloader supports fastboot commands, but the flash command is now
fastboot flash recovery file name
ie drop the -i 0x1949
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.1-otter.img
because the fastboot mode window is short
with kindle connected to pc, power off kindle, enter commands, then power on kindle
Click to expand...
Click to collapse
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.

kas782000 said:
I've been trying this for about 30 minutes or so with no luck...I even downloaded a different version of the twrp image. Do I have to wait for the fastboot screen to start the command or do I start the process before powering on the device? I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Should be able to do it either way but I press enter, before the power button
This will not work if drivers are not correct
could try
Code:
fastboot devices
as a test should get something like
Code:
123456789 bootloader
back in command prompt

I finally got it to work and I can't thank you enough. You were right. I knew my computer recognized the device with adb in normal boot but my computer wouldn't recognize the device in fastboot mode until i reinstalled the android driver while it was in fastboot mode. Now I have a custom ROM running Google Play apps! Again, thank you!

Hey, I don't know if this will help others, but I had a hell of a time trying to get my kindle to recognize while in the bootloader/fastboot mode... It frustrated me so much that I had to write about it.
I recently switched to Windows 10, so it seems like my computer is relearning drivers and stuff...
My kindle was fine when on, and I could issue adb commands from the main screen, but when in fastboot mode, I couldn't get it detected. I knew the drivers were an issue, but I couldn't figure out how to do it. I looked at Amazon's support pages, went through the SDK route, tinkered with the adb.ini and so forth... to no avail.
Post after post said that the easiest way to install the drivers was through the Kindle Fire Utility, but for some reason, the drivers in the .bat file kept failing and would not load. It took a good few hours to figure out the solution.
When I asked the Web why the drivers kept failing, I came across a post that said Windows was actually blocking unknown drivers from loading onto my system. I really wish Windows had told me that instead of just saying "Fail"...
I had to hold down the shift button and click restart on the start menu, and when the computer restarted, I when through: troubleshoot -> advanced options -> startup settings and clicked on Restart. It eventually gave me the option to disable that signature verification [F7]
My explanation is crude, because I want you to look it up properly. Just search for "disable driver signature enforcement" and you should be fine.
Hope this helps others out. I may have to revisit my own post just to see how to do this again.

[RESOLVED] Stuck in "fastboot mode", Help needed

Okay some background information that might help.
Haven't touched my daughter's kindle in over 2 years after rooting with Kindle Fire Utility 0.9.6 and putting CM 10.1 on it, as well as TWRP Blaze 2.4.1.0. Fast forward to today and she says it's acting weird. I chalk it up to it being very out dated and look into updating to the latest and greatest. So I head on over to OtterX ROM/TWRP/Bootloader [TWRP 2.7.1 2014-06-08]. I make sure adb is up and running and that I can push files while in recovery. I flash the latest bootloader and reboot. Everything seems normal until I head to the next step of flashing the new recovery. Try to boot into recovery and the device just boots normally... tried to use the fastboot method and it just hangs on "waiting for device". The device reboots, but instead of doing what it's supposed to do, it just boots normally. Now I'm getting a little impatient with everything and no longer having the ability to boot back into recovery. So now here's where I really shot myself in the foot, I proceed to think its a great idea to use the fix EMMC corrupted device option that proceeds to wipe everything (which I knew was going to happen) and now can't get past the fastboot mode screen....
I now don't seem to have a recovery... but I can still turn on the device, see the initial "Kindle Fire" screen with the power options to get into Normal boot, Recovery boot, advanced. Normal boot does nothing but boot into fastboot mode, as well as recovery. The advanced menu pops up normally but I'm not sure if that really matters in this case. While connected to the computer it shows up as an unspecified device named "kindle" with an exclamation point on it. I'm not sure what to even do at this point in time... Any help would be great.

DrkGhst87 said:
Okay some background information that might help.
Haven't touched my daughter's kindle in over 2 years after rooting with Kindle Fire Utility 0.9.6 and putting CM 10.1 on it, as well as TWRP Blaze 2.4.1.0. Fast forward to today and she says it's acting weird. I chalk it up to it being very out dated and look into updating to the latest and greatest. So I head on over to OtterX ROM/TWRP/Bootloader [TWRP 2.7.1 2014-06-08]. I make sure adb is up and running and that I can push files while in recovery. I flash the latest bootloader and reboot. Everything seems normal until I head to the next step of flashing the new recovery. Try to boot into recovery and the device just boots normally... tried to use the fastboot method and it just hangs on "waiting for device". The device reboots, but instead of doing what it's supposed to do, it just boots normally. Now I'm getting a little impatient with everything and no longer having the ability to boot back into recovery. So now here's where I really shot myself in the foot, I proceed to think its a great idea to use the fix EMMC corrupted device option that proceeds to wipe everything (which I knew was going to happen) and now can't get past the fastboot mode screen....
I now don't seem to have a recovery... but I can still turn on the device, see the initial "Kindle Fire" screen with the power options to get into Normal boot, Recovery boot, advanced. Normal boot does nothing but boot into fastboot mode, as well as recovery. The advanced menu pops up normally but I'm not sure if that really matters in this case. While connected to the computer it shows up as an unspecified device named "kindle" with an exclamation point on it. I'm not sure what to even do at this point in time... Any help would be great.
Click to expand...
Click to collapse
When in fastboot mode
Code:
fastboot devices
Should get a return of something like 123456789 kindle
Sent from my DROIDX using Tapatalk
---------- Post added at 11:00 PM ---------- Previous post was at 10:54 PM ----------
If fastboot devices stops at waiting for device, kindle is not connecting to PC correctly, like cause is incorrect drivers
Sent from my DROIDX using Tapatalk

sd_shadow said:
When in fastboot mode
Code:
fastboot devices
Should get a return of something like 123456789 kindle
Sent from my DROIDX using Tapatalk
---------- Post added at 11:00 PM ---------- Previous post was at 10:54 PM ----------
If fastboot devices stops at waiting for device, kindle is not connecting to PC correctly, like cause is incorrect drivers
On windows 8.1 and under devices, under unspecified there is "kindle". When I click properties it doesn't even give me a driver to install or update.
I'm not sure if I have what ever needs to be set up on my PC end for fastboot, in order to get at least a recovery to it
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
hmm, fastboot devices returns nothing... adb shell comes up with an error: device not found

How is kindle listed in device manager?
Sent from my DROIDX using Tapatalk

sd_shadow said:
How is kindle listed in device manager?
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
under Unspecified, listed as just kindle

It should be android phone double click should show adb interface
Sent from my DROIDX using Tapatalk

sd_shadow said:
It should be android phone double click should show adb interface
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Unfortunately no. Double click brought up properties and under device information everything is unavailable except model:kindle

Uninstall kindle in device manager, check delete drivers box, reinstall drivers from kindle fire utility's install.drivers.bat, reboot PC and kindle.
Sent from my DROIDX using Tapatalk
---------- Post added at 11:10 PM ---------- Previous post was at 11:08 PM ----------
http://forum.xda-developers.com/showthread.php?t=2192818
[Root][TWRP][COTR][BOOTLOADERS]Kindle Fire Utility v0.9.9 (4/5/13) [1st Gen Only!]
Sent from my DROIDX using Tapatalk

going to give that a try, brb with results

it won't let me install the drivers that came with the KFU... keeps giving me Install Failed

If you get fastboot devices command to work
You need a recovery.IMG file for otterx
Can be found in recovery.zip by extracting files it will be in /cache folder.
You should be using twrp 2.7.1.0 or newer and 2.05 bootloader
Flash twrp.IMG in fastboot mode with
Code:
fastboot flash recovery twrp.file.name
fastboot reboot
Sent from my DROIDX using Tapatalk
---------- Post added at 11:27 PM ---------- Previous post was at 11:25 PM ----------
DrkGhst87 said:
it won't let me install the drivers that came with the KFU... keeps giving me Install Failed
Click to expand...
Click to collapse
Window 7, 8?
You extracted zip, not running bat in zip?
Checked file size or md5 checksum?
Sent from my DROIDX using Tapatalk

Yea, no idea why it's not showing up as a device.
I did technically use the EMMC Corruption Fix that wiped everything on my device, just short of the bootloader. Not sure why the computer isn't recognizing it. Must be that my computer isn't really set up for fastboot? Weird thing to is, it no longer shows a serial number like it used to before under the "Advanced" options... Don't know if that's significant. Other things that have changed that I've noticed from the advanced menu is that Charger Mode: OFF (was on before) Serial Console: OFF (was on before) Serial #: BLANK (used to have something there) and that's about it. Don't know if I just need to set up something on my PC end to not only recognize the kindle but to actually be able to use the fastboot stuff. I think that's where my problem my also be.

sd_shadow said:
Window 7, 8?
You extracted zip, not running bat in zip?
Checked file size or md5 checksum?
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Windows 8.1, Extracted and ran as administrator

Your problem is drivers, that is all
Sent from my DROIDX using Tapatalk
---------- Post added at 11:35 PM ---------- Previous post was at 11:33 PM ----------
DrkGhst87 said:
Windows 8.1, Extracted and ran as administrator
Click to expand...
Click to collapse
Drivers will not install on windows 8 without disabling signature enforcement first
Sent from my DROIDX using Tapatalk
---------- Post added at 11:37 PM ---------- Previous post was at 11:35 PM ----------
https://learn.sparkfun.com/tutorials/disabling-driver-signature-on-windows-8/all
Sent from my DROIDX using Tapatalk

Disabled and installed drivers. Going to reset pc real quick and see if it now is recognized.

Okay, now when I try fastboot devices i get <NULL> fastboot
Also, it's still listed under Unspecified as kindle. This time when you double click and go into Hardware, it shows Android ADB Interface and Type as Phone

DrkGhst87 said:
Okay, now when I try fastboot devices i get <NULL> fastboot
Also, it's still listed under Unspecified as kindle. This time when you double click and go into Hardware, it shows Android ADB Interface and Type as Phone
Click to expand...
Click to collapse
Try disconnecting USB cable and rebooting kindle
Sent from my DROIDX using Tapatalk
---------- Post added at 11:49 PM ---------- Previous post was at 11:48 PM ----------
Then reconnect USB cable
Sent from my DROIDX using Tapatalk

I think I have everything running. Thanks so much for your help. Even though it said NULL, I gave that command line a try and it recognized the device and I was able to push the TWRP img to the device and from there follow the rest of the instructions on the linked page from earlier. Again thanks so much!!!

Got my bootloader unlocked, trying to boot into TWRP but hit a speedbump?

So I got my bootloader unlocked so obviously fastboot drivers are working, I have the SU zip copied to my internal storage and the IMG file in my Minimal Fastboot folder location....
When I run :
fastboot boot "path to IMG".img
My command prompt just says "waiting for devices" and does nothing?
Do I run this command from while in bootloader mode? Power + Vol down ? When I have it plugged into my PC in this mode and I run "adb devices" it does't find my device? Does that mean I don't have the right drivers installed?
What am I missing here? Damn this phone is complicated.

msmall82 said:
So I got my bootloader unlocked so obviously fastboot drivers are working, I have the SU zip copied to my internal storage and the IMG file in my Minimal Fastboot folder location....
When I run :
fastboot boot "path to IMG".img
My command prompt just says "waiting for devices" and does nothing?
Do I run this command from while in bootloader mode? Power + Vol down ? When I have it plugged into my PC in this mode and I run "adb devices" it does't find my device? Does that mean I don't have the right drivers installed?
What am I missing here? Damn this phone is complicated.
Click to expand...
Click to collapse
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
If you already have TWRP rc1 installed then you just want to boot to recovery and install su2.79sr3
In fastboot type in fastboot devices and if it comes back with your device number your good to go

mac796 said:
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
Click to expand...
Click to collapse
I know the command I want, I'm asking where I run it from? Do i run it while my phone is in Android connected to my PC or do I run the command from fastboot while my phone is in the bootloader mode??? When I have my phone connected normally and run an "adb devices" it doesn't find my phone but obviously it recognizes my phone otherwise it wouldn't have been able to copy dePixel8 and unlock my bootloader.
My question is *where* do I run that command. As I said before, if I run it while my phone is powered up normally and connected to my PC it just says "waiting for devices". If I power my phone up into bootloader mode (power + vol up) my fastboot doesn't see my phone????

mac796 said:
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
If you already have TWRP rc1 installed then you just want to boot to recovery and install su2.79sr3
Click to expand...
Click to collapse
I guess what I am saying is how the heck do I boot into the TWRP IMG ? My bootloader is definitely unlocked, I have SU on my internal storage, I have the IMG in my minimal fastboot folder. I just need to know how the heck to boot into "recovery mode" using the :
fastboot boot "path to".img
If I run that command while my phone is connected normally with USB debugging enabled it just says "waiting for devices"
Am I missing something here...?

[QUOTE.
My question is *where* do I run that command. As I said before, if I run it while my phone is powered up normally and connected to my PC it just says "waiting for devices". If I power my phone up into bootloader mode (power + vol up) my fastboot doesn't see my phone????[/QUOTE]
Run the command with your phone in bootloader mode and your computer in fastboot

msmall82 said:
So I got my bootloader unlocked so obviously fastboot drivers are working, I have the SU zip copied to my internal storage and the IMG file in my Minimal Fastboot folder location....
When I run :
fastboot boot "path to IMG".img
My command prompt just says "waiting for devices" and does nothing?
Do I run this command from while in bootloader mode? Power + Vol down ? When I have it plugged into my PC in this mode and I run "adb devices" it does't find my device? Does that mean I don't have the right drivers installed?
What am I missing here? Damn this phone is complicated.
Click to expand...
Click to collapse
First off get rid of minimal. That is not your current problem, but you will have problems later. It is old, it doesn't know about our partitions or handle their larger size. Get googles
https://developer.android.com/studio/releases/platform-tools.html
Put the TWRP img in the same folder, skip the path
Fastboot BOOT {twrpfilename.img}

mac796 said:
[QUOTE.
My question is *where* do I run that command. As I said before, if I run it while my phone is powered up normally and connected to my PC it just says "waiting for devices". If I power my phone up into bootloader mode (power + vol up) my fastboot doesn't see my phone????
Click to expand...
Click to collapse
Run the command with your phone in bootloader mode and your computer in fastboot[/QUOTE]
You need to follow the steps I gave you. You need su2.79 , and rc1 on your internal storage. Then you need TWRP rc1 boot image on your computer. Put it in your platform tools folder or wherever you got your other firmware. Put phone in bootloader mode, then open a command window where you have TWRP boot image saved , type in fastboot devices, to make sure computer is seeing the phone, then the command should be fastboot boot TWRP.img, then install rc1 off your phone storage, then boot to system once, then boot back to recovery and install su 2.79 sr3

mac796 said:
You want fastboot boot twrp.img
Then you want to install TWRP rc1 from your internal storage from TWRP. Then you want to boot to system once then boot to recovery and install su2.79 sr3 from your internal storage
You want to be in bootloader mode/fastboot for the first step
---------- Post added at 06:29 PM ---------- Previous post was at 06:27 PM ----------
If you already have TWRP rc1 installed then you just want to boot to recovery and install su2.79sr3
In fastboot type in fastboot devices and if it comes back with your device number your good to go
Click to expand...
Click to collapse
OK I figured it out, while the phone is booted into Android you have to actually issue the command to reboot it into the bootloader mode otherwise it won't detect the phone (at least it wouldn't on my PC)
I ran this command from my minimal fastboot folder (shift + right click -> open command prompt)
I then typed this:
adb reboot bootloader
Then once it is rebooted into bootloader mode issue the
fastboot boot .img command
It then rebooted into TWRP, and I was able to flash the SU zip
Sorry for bugging everyone, this phone is a Pain in my....but it's damn fast and damn nice!

Delete
---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------
Sorry for bugging everyone, this phone is a Pain in my....but it's damn fast and damn nice![/QUOTE]
Good deal. Yea I usually use ADB to put phone in bootloader mode it's faster

TonikJDK said:
First off get rid of minimal. That is not your current problem, but you will have problems later. It is old, it doesn't know about our partitions or handle their larger size. Get googles
https://developer.android.com/studio/releases/platform-tools.html
Put the TWRP img in the same folder, skip the path
Fastboot BOOT {twrpfilename.img}
Click to expand...
Click to collapse
Thanks Tonik, got SU on there and all is right with the world, already installing Ti Backup and root explorer and such.....ahhh so relieved.
Love all of you lol

mac796 said:
Delete
---------- Post added at 06:49 PM ---------- Previous post was at 06:45 PM ----------
Sorry for bugging everyone, this phone is a Pain in my....but it's damn fast and damn nice!
Click to expand...
Click to collapse
Good deal. Yea I usually use ADB to put phone in bootloader mode it's faster[/QUOTE]
Thanks man, I figure other people might run into these problems so I might as well post about them. If I booted directly into the bootloader my PC wouldn't recognize the phone, if I issued the command to reboot it would. Weird...but whatever, I'm unlocked and rooted....
THANK YOU!