Database Users

[SOLVED] Questions about 6.2.2 update

I am going away, and want to run the Kindle to the latest version (6.2.2) before I go. I do not want to get the OTA update in some hotel and have to fix everything. I have a couple questions...
After installing 6.2.2, and re-root with the commands and BurritoRoot2, and install TWRP, how much more will I need to do? Is the market still there, or does that need to be reinstalled too? How about my Go Launcher and all the apps I already have installed from the market or getjar, or whereever?

Well, That was easy. The OTA update came in, so I had to find my way through this. It was actually very simple, and running BurritoRoot2. I am not rooted, and life is pretty good. Trying to get TWRP to install, but the fastboot command just hangs at waiting for device. The device is rooted, and it shows up in my device manager on my PC. Any help?

Try this thread to fastboot: http://forum.xda-developers.com/showthread.php?t=1414832

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:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
switch bootmode to normal manually:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot

If, as you indicate, you already have TWRP installed on 6.2.1 you could always flash one of these pre-rooted versions of 6.2.2 and save yourself the effort of re-rooting and all that.
Pre-rooted stock 6.2.2
Update-Only nfx-update-kindle-6.2.2
EDIT: Oh wait... nevermind. I missed the part where you're already attempting to install TWRP.

I'm good. Thanks for all the help. By following the instructions on the link provided I was able to manually install TWRP 2.0. My upgrade is complete, so I can go back to listening and learning here.

Woke up to an unrooted Kindle. Would someone please just clarify.
I only want root and market. No TWRP or CM7. Do I just refollow the original instructions to root.

upriverpaddler said:
Woke up to an unrooted Kindle. Would someone please just clarify.
I only want root and market. No TWRP or CM7. Do I just refollow the original instructions to root.
Click to expand...
Click to collapse
yes - but the updated ones:
http://forum.xda-developers.com/showthread.php?t=1410223
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
horsegoalie said:
I'm good. Thanks for all the help. By following the instructions on the link provided I was able to manually install TWRP 2.0. My upgrade is complete, so I can go back to listening and learning here.
Click to expand...
Click to collapse
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

I previously used the Kindle Fire Utitlity to root/install market. After my unit was updated to 6.2.2, I used BurritoRoot and verified root using Root Checker.
The 2 things that seem missing still now are contact and calendar sync. Those settings are missing from my google sync settings as well. Do I need to revert to stock and rerun the entire process?

markazali said:
I previously used the Kindle Fire Utitlity to root/install market. After my unit was updated to 6.2.2, I used BurritoRoot and verified root using Root Checker.
The 2 things that seem missing still now are contact and calendar sync. Those settings are missing from my google sync settings as well. Do I need to revert to stock and rerun the entire process?
Click to expand...
Click to collapse
fixed it: reinstalled
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk

markazali said:
fixed it: reinstalled
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
Click to expand...
Click to collapse
I believe I am in this same boat. Was rooted, and had both of these sync adapters configured and working correctly......and now I received 6.2.2 and no longer have root.
At this point, I am not exactly sure what I need to do to regain root access so I can restore the sync adapters.

ontwowheels said:
I believe I am in this same boat. Was rooted, and had both of these sync adapters configured and working correctly......and now I received 6.2.2 and no longer have root.
At this point, I am not exactly sure what I need to do to regain root access so I can restore the sync adapters.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1410223

b63 said:
http://forum.xda-developers.com/showthread.php?t=1410223
Click to expand...
Click to collapse
I am back in business.....

[Q] Need help, please

So I have been reading the forums for a while and want to say thank you to everyone here. I had to register so I could ask a question about my kindle fire, I've been searching for a few days but cant see to find a answer. A friend of mine rooted it for me and we choose to put cm7 on it, loved it but saw that ICS was ready and decided to go fot it. I neglected to back a back up and wiped cm7 off and now am unable to load any rom on to it I have watched dozens of videos and hundreds of pages but I'm now stuck. I run ubuntu 11.10 on my computer I download a rom plug in the fire drom the rom in the SD card folder clear the the approiate things and trey to flash it. when I reboot it brings me right back to TWRP. I'm about ready to use it a a frisbe. Am I missing something?

hillbillyhotrod said:
So I have been reading the forums for a while and want to say thank you to everyone here. I had to register so I could ask a question about my kindle fire, I've been searching for a few days but cant see to find a answer. A friend of mine rooted it for me and we choose to put cm7 on it, loved it but saw that ICS was ready and decided to go fot it. I neglected to back a back up and wiped cm7 off and now am unable to load any rom on to it I have watched dozens of videos and hundreds of pages but I'm now stuck. I run ubuntu 11.10 on my computer I download a rom plug in the fire drom the rom in the SD card folder clear the the approiate things and trey to flash it. when I reboot it brings me right back to TWRP. I'm about ready to use it a a frisbe. Am I missing something?
Click to expand...
Click to collapse
Sounds like you're still in Fastboot mode.
Try these ADB commands:
Code:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot

Thanks
Sorry it took me so long to respond but I had a login problem. From what I have read ADB doest go al that well using ubuntu, that and I'm not really all that good using command line and terminal. Any other ideas?

So my friend tried setting it up remotely last night but it didn't go well, anything I can't do from inside TWRP to make it work?
Sent from my SGH-T959V using XDA App

hey
hey man, in twrp, trying doing mount, then on your computer, put on a stock rom to the drive, then in twrp, run the stock rom

I'm pretty sure that is what I have been doing but I will try again

Ok, tried again and no luck, I have tried cm7 cm9 and a few others with the same result.

semms like the kf is in bootmode 5001 (recovery)
would try to use kfu for mac/linux:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
but use the corrected run.sh from here:
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use option 1 - bootmode normal
an other option is firekit:
http://forum.xda-developers.com/showthread.php?t=1430038

It's alive
Brought it to my friends house yesterday who has windows and that command worked perfectly. Now I have energy ICS installed and cant log in to gapps, lucky me.

Now should I be able to put on a different rom from Ubuntu computer without that happening again?
Sent from my SGH-T959V using XDA

to switch it accidentially to a wrong bootmode can allways happen, but it's no problem:
here all the possible commands to change bootmode:
with adb (secure kernel):
adb shell su -c "idme bootmode 4000"
adb reboot
or (twrp or unsecure kernel):
adb shell idme bootmode 4000
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or:
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or:
fastboot oem idme bootmode 4000
fastboot reboot
the number is the bootmode you want to switch to:
normal boot -> 4000
fastboot -> 4002
boot to recovery -> 5001
and if you know:
normal boot -> adb commands YES -> fastboot commands NO
fastboot -> adb commands NO -> fastboot commands YES
recovery -> adb commands YES -> fastboot commands NO
then you only have to count 1 and 1 together and can master nearly each hanging situation !
Click to expand...
Click to collapse

Way over my head, plus im not able to do the adb from my computer I have to have my friend do it from his windows machine.

just flashed a gapps for a different rom but still not letting me sign in to google. Driving me nuts.

everything is also running on linux (ubuntu) or on a mac
there is a linux/mac version of kfu:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
update the run.sh with this one (original has a bug):
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use the commands in the tools forder also but you have to adapt them
eg: "adb.linux devices" or "./adb.mac devices" (not shure about ./ at linux - just try)
and don't forget to run "install_drivers.sh" from a terminal

b63 said:
everything is also running on linux (ubuntu) or on a mac
there is a linux/mac version of kfu:
http://forum.xda-developers.com/showpost.php?p=21369040&postcount=653
update the run.sh with this one (original has a bug):
http://forum.xda-developers.com/showpost.php?p=23159077&postcount=2
you can use the commands in the tools forder also but you have to adapt them
eg: "adb.linux devices" or "./adb.mac devices" (not shure about ./ at linux - just try)
and don't forget to run "install_drivers.sh" from a terminal
Click to expand...
Click to collapse
I will have to check that out

Gapps
Any clue how to get my gapps working?

the energy rom should have it allready built in:
http://forum.xda-developers.com/showpost.php?p=23255224&postcount=75

It does but I couldn't sign it so I tried a different one, still cant get in.

sorry - don't know the energy rom - would try to ask NRGZ28 in his thread

Thanks for the help

my problem

my problem is that when i used rom toolbox after flashing twrp recovery from hashcode (do all and dont flash the recovery only)for reset my tab into recovery. my tablet entered in a endless recovery, it charged but i could enter the os, then it was with few battery and i recharged it, then it had a few battery and i dont charged it, and now it dont boot, i charged it and nothing, i know that i can use fastboot but my device wasnt recognoized, so i think i will need the drivers. please help me

Kindle Fire HD and 2 First Aide Software - Noob (Simple) Version
persano said:
my problem is that when i used rom toolbox after flashing twrp recovery from hashcode (do all and dont flash the recovery only)for reset my tab into recovery. my tablet entered in a endless recovery, it charged but i could enter the os, then it was with few battery and i recharged it, then it had a few battery and i dont charged it, and now it dont boot, i charged it and nothing, i know that i can use fastboot but my device wasnt recognoized, so i think i will need the drivers. please help me
Click to expand...
Click to collapse
persano,
OK, so if I understand you correctly, you performed Hascodes steps to install TWRP Recovery and now your device loops the Recovery, correct?
If yes, plug in the Fastboot cable to the Kindle first then to your PC but first use our utility to install the drivers then proceed to recover the device.
Here is a link: http://forum.xda-developers.com/showthread.php?t=2096888
We have an option in the software to install the driver - do not use the backup or OTA disable feature, we are working on that function.
If you have trouble with that driver, which you should not but if you do, reply back and we will add instructions. Do Not worry, we will get you back online.

prokennexusa said:
persano,
OK, so if I understand you correctly, you performed Hascodes steps to install TWRP Recovery and now your device loops the Recovery, correct?
If yes, plug in the Fastboot cable to the Kindle first then to your PC but first use our utility to install the drivers then proceed to recover the device.
Here is a link: http://forum.xda-developers.com/showthread.php?t=2096888
We have an option in the software to install the driver - do not use the backup or OTA disable feature, we are working on that function.
If you have trouble with that driver, which you should not but if you do, reply back and we will add instructions. Do Not worry, we will get you back online.
Click to expand...
Click to collapse
the only option of drivers is the adb one

Kindle Bootloops After Installing TWRP On The Kindle
persano said:
the only option of drivers is the adb one
Click to expand...
Click to collapse
persano,
The ADB Driver and Fastboot driver are one of the same drivers, so having said this when you have a working ADB Driver, you will have a working Fastboot driver. Now, we have no idea what Hashcode did when developing TWRP on the Kindle, although he is a genius so I am sure he thought of everything.
Have you posted the issue in his Thread? He may have a way to recover TWRP directly since our Method will place you back to a stock Kindle.

prokennexusa said:
persano,
The ADB Driver and Fastboot driver are one of the same drivers, so having said this when you have a working ADB Driver, you will have a working Fastboot driver. Now, we have no idea what Hashcode did when developing TWRP on the Kindle, although he is a genius so I am sure he thought of everything.
Have you posted the issue in his Thread? He may have a way to recover TWRP directly since our Method will place you back to a stock Kindle.
Click to expand...
Click to collapse
yeah i posted in his thread

How To End A TWRP Bootloop
persano said:
yeah i posted in his thread
Click to expand...
Click to collapse
persano,
Any response yet? Here are some pointers that apply to TWRP on other Androids, so it should apply to your Kindle:
If you get stuck at a screen with a yellow triangle, run:
Code:
fastboot oem idme bootmode 4000 -i 0x1949
If your device is always booting TWRP run:
Code:
adb shell "idme bootmode 4000"
Step 1: If you still can't get out of booting TWRP (A Bootloop), first run:
Code:
adb shell "idme bootmode 4002"
Step 2: Reboot your device, then run:
Code:
adb shell "idme bootmode 4000"
Step 3: Reboot again and you should be out of your bootloop.
Please let us know if one of these solves your issue.

prokennexusa said:
persano,
Any response yet? Here are some pointers that apply to TWRP on other Androids, so it should apply to your Kindle:
If you get stuck at a screen with a yellow triangle, run:
Code:
fastboot oem idme bootmode 4000 -i 0x1949
If your device is always booting TWRP run:
Code:
adb shell "idme bootmode 4000"
Step 1: If you still can't get out of booting TWRP (A Bootloop), first run:
Code:
adb shell "idme bootmode 4002"
Step 2: Reboot your device, then run:
Code:
adb shell "idme bootmode 4000"
Step 3: Reboot again and you should be out of your bootloop.
Please let us know if one of these solves your issue.
Click to expand...
Click to collapse
but my tablet dont boot, it get out of battery after alot of bootloops

How To End A TWRP Bootloop
persano said:
but my tablet dont boot, it get out of battery after alot of bootloops
Click to expand...
Click to collapse
persano,
So at the moment you battery is dead or your Kindle is dead, period?
If the Kindle is dead and will no longer accept a charge, you will need to send it back to Amazon for replacement. If you are out of Warranty or concerned Amazon will not warranty the device, send it to our office and we will get you a new one. We know you are Argentina but if you send it vis UPS or FedEx we will get it quickly.
If you would like a new Kindle send us a PM and we will post our shipping address.

prokennexusa said:
persano,
So at the moment you battery is dead or your Kindle is dead, period?
If the Kindle is dead and will no longer accept a charge, you will need to send it back to Amazon for replacement. If you are out of Warranty or concerned Amazon will not warranty the device, send it to our office and we will get you a new one. We know you are Argentina but if you send it vis UPS or FedEx we will get it quickly.
If you would like a new Kindle send us a PM and we will post our shipping address.
Click to expand...
Click to collapse
thanks then i will see. i think hashcode is a killer developer xD
and how a new kinlde, what you will do with the old?
i bougth it from ebay, amazon will renplace it ?

How To Ship Th Kindle To Xerocomm, Inc.
persano said:
thanks then i will see. i think hashcode is a killer developer xD
and how a new kinlde, what you will do with the old?
i bougth it from ebay, amazon will renplace it ?
Click to expand...
Click to collapse
persano,
If you ship it to us, we will register the device to our business Amazon account, where we own 40 Kindles, then we will ask Amazon to replace it. The old Kindle will go back to Amazon for parts - we will take care of having the device swapped out for you. Be sure you De-register the device from your Amazon Account, if you did not register the device to Amazon better yet.
The only caveat is the Kindle need to be in excellent condition without signs of being dropped, otherwise Amazon will reject the replacement.
If Hashcode can not fix the problem, ship the Kindle (well packaged and insured) to us:
Xerocomm, Inc.
dba The Noob Series
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954-6603
USA
Main Phone: 707-774-5923

prokennexusa said:
persano,
If you ship it to us, we will register the device to our business Amazon account, where we own 40 Kindles, then we will ask Amazon to replace it. The old Kindle will go back to Amazon for parts - we will take care of having the device swapped out for you. Be sure you De-register the device from your Amazon Account, if you did not register the device to Amazon better yet.
The only caveat is the Kindle need to be in excellent condition without signs of being dropped, otherwise Amazon will reject the replacement.
If Hashcode can not fix the problem, ship the Kindle (well packaged and insured) to us:
Xerocomm, Inc.
dba The Noob Series
Attn: Chris Bryant
1684 Northstar Drive
Petaluma, CA 94954-6603
USA
Main Phone: 707-774-5923
Click to expand...
Click to collapse
in the box and with the usb?
its in exellent

II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2

Hashcode said:
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
but my tablet dont boot when i connect it

Hashcode said:
II can add a bit to this discussion from what I gather in the bootloader / TWRP thread:
1. i believe that persano has only flashed the recovery.img and not the boot.img or the stack jump file to system. And then issued a "reboot recovery" in ROM toolbox which has probably set the bootmode to 3 or 5, i forget, but it will direct the stock bootloader to jump to recovery directly.
Unfortunately, without a boot.img (containing a 2nd bootloader) and a stack file to match, this ends with an unloadable recovery.img which will hang the device.
2. The solution (in any case) is to use a fastboot cable which will power the device regardless of battery charge and to enter fastboot mode. Which can be configured via the Android SDK install, and perhaps some reinstallation of USB drivers in the Windows device manager (should show "adb composite device").
Here you can flash back the stock recovery (and/or boot.img if needed) as well as reset the bootmode by entering:
fastboot -i 0x1949 oem idme bootmode 1
And all will be good as new.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
how to configure it in the sdk

persano said:
but my tablet dont boot when i connect it
Click to expand...
Click to collapse
With fastboot cable?

Maromi said:
With fastboot cable?
Click to expand...
Click to collapse
yeah

persano said:
how to configure it in the sdk
Click to expand...
Click to collapse
in the Android SDK manager
click tools
click manage add-on sites
click user defined sites
click new
paste this address
http://kindle-sdk.s3.amazonaws.com/addon.xml

Maromi said:
in the Android SDK manager
click tools
click manage add-on sites
click user defined sites
click new
paste this address
http://kindle-sdk.s3.amazonaws.com/addon.xml
Click to expand...
Click to collapse
and then

amazon will remplace it !!!!! yeah!!!!
i live in argentina but they will remplace it

How To Stop A Kindle Fire HD Bootloop
persano said:
in the box and with the usb?
its in exellent
Click to expand...
Click to collapse
persano,
No, just the tablet. First open a chat with Amazon, see if they will replace the device, if no, send it to us and we will have the device replaced.

Why cant I flash custom recovery on 4.3?

I downloaded the latest twrp recovery and put the file in my platform tools. (also renamed it to twrp.img) and I go into fastboot mode. Run cmd in my platform tools directory and type fastboot flash recovery twrp.img and I get this message twrp.img no error. Im following a youtube video and the guy does the same thing im doing and his works..

Does it do the same with CWM?

EddyOS said:
Does it do the same with CWM?
Click to expand...
Click to collapse
I prefer twrp so no I have not tried CWm

Cjshino said:
I prefer twrp so no I have not tried CWm
Click to expand...
Click to collapse
Fair enough, but try it and see what happens

EddyOS said:
Fair enough, but try it and see what happens
Click to expand...
Click to collapse
still doesnt work

Cjshino said:
still doesnt work
Click to expand...
Click to collapse
1. Is your bootloader unlocked?
Use "fastboot oem unlock" to unlock your phone's bootloader. Be warn that it will wipe everything if you do not use "fastboot format cache" afterwards.
2. Can you see your device after you run command "fastboot devices"?
Install the fastboot drivers, download google usb driver here: http://developer.android.com/sdk/win-usb.html

ksilver89 said:
1. Is your bootloader unlocked?
Use "fastboot oem unlock" to unlock your phone's bootloader. Be warn that it will wipe everything if you do not use "fastboot format cache" afterwards.
2. Can you see your device after you run command "fastboot devices"?
Install the fastboot drivers, download google usb driver here: http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
yes my bootloader is unlocked and when I run command 'fastboot devices' it works. Im really stumped..

is your kernel rooted? if yes use Recovery Tools (on play store).

Cjshino said:
yes my bootloader is unlocked and when I run command 'fastboot devices' it works. Im really stumped..
Click to expand...
Click to collapse
I just flashed it last night without any problems but I renamed the file recovery.img. You sure you have version 2.6 for the Nexus 4? TWRP has different recoveries for each device.
---------- Post added at 01:22 PM ---------- Previous post was at 01:16 PM ----------
Here's another thing to check. Make sure you didn't rename the file twrp.img.img as windows hides extensions by default. In my case when I renamed the file recovery I didn't have to add the extension .img as it was already there.

Cjshino said:
yes my bootloader is unlocked and when I run command 'fastboot devices' it works. Im really stumped..
Click to expand...
Click to collapse
If you're rooted, try this method:
1. Boot to Android system.
2. Enable USB Debugging
3. Connect your phone with USB.
4. Run the command below:
Code:
adb push twrp.img /sdcard/twrp.img
adb shell
5. Next, get root permission and flash the recovery.
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
6. After confirming every steps, boot into recovery.
Code:
adb reboot recovery

Thanks guys i just used a toolkit and I have twrp for 4.3 now

Fastboot help

I have recently unlocked the bootloader on the Note 7 with success and want to install a custom ROM. But the problem I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all. When the phone is booted into MIUI with USB Debug enabled, the phone is listed. I have tried multiple computers, the stock USB cable, multiple USB ports, resetting the phone but the phone just will not show up on the "adb devices" list when it's in fastboot. Any suggestions on what to do next? I really want to install a custom ROM and root, etc....

BlackHawk580 said:
I have recently unlocked the bootloader on the Note 7 with success and want to install a custom ROM. But the problem I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all. When the phone is booted into MIUI with USB Debug enabled, the phone is listed. I have tried multiple computers, the stock USB cable, multiple USB ports, resetting the phone but the phone just will not show up on the "adb devices" list when it's in fastboot. Any suggestions on what to do next? I really want to install a custom ROM and root, etc....
Click to expand...
Click to collapse
try to reinstall the adb drivers on your pc. You can also install a twrp recovery so you can flash roms, root or whatever you want even from your phone

_NikO_ said:
try to reinstall the adb drivers on your pc. You can also install a twrp recovery so you can flash roms, root or whatever you want even from your phone
Click to expand...
Click to collapse
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery

BlackHawk580 said:
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery
Click to expand...
Click to collapse
Has your pc got windows 10?
---------- Post added at 08:19 AM ---------- Previous post was at 08:13 AM ----------
BlackHawk580 said:
I've done that too, I've downgraded ADB Drivers as well and nothing has worked. Also, I can't install TWRP if the phone doesn't even show up on my computer to flash the custom recovery
Click to expand...
Click to collapse
Go in Device Manager in your pc and look for "ADB Interface". If there isnt your android device then you havent installed drivers properly so go check

_NikO_ said:
Has your pc got windows 10?
---------- Post added at 08:19 AM ---------- Previous post was at 08:13 AM ----------
Go in Device Manager in your pc and look for "ADB Interface". If there isnt your android device then you havent installed drivers properly so go check
Click to expand...
Click to collapse
Yes, I've done that too, I've tried installing various different drivers as well, it also has Windows 10 as well

BlackHawk580 said:
Yes, I've done that too, I've tried installing various different drivers as well
Click to expand...
Click to collapse
So your phone is showing up in Adb devuces without any yellow warning or anything?

_NikO_ said:
So your phone is showing up in Adb devuces without any yellow warning or anything?
Click to expand...
Click to collapse
It doesn't show up at all on the list, yeah

BlackHawk580 said:
I'm facing is that whenever the phone is in fastboot mode, running the "adb devices" command, the phone doesn't show up at all.
Click to expand...
Click to collapse
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Code:
fastboot devices
?

BlackHawk580 said:
It doesn't show up at all on the list, yeah
Click to expand...
Click to collapse
If there isnt your computer isnt actually seeing it as an adb device

osd_daedalus said:
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Code:
fastboot devices
?
Click to expand...
Click to collapse
Okay so, I ran that command and it does show up in the list thankfully. But now I have another problem. I can't boot into the recovery. I try the fasboot boot command and it just restarts normally and for some reason, doing volume up and power doesn't enter the recovery either.

BlackHawk580 said:
Isn't that intended? You should use fastboot commands, not ADB commands...
What is the output of
Okay so, I ran that command and it does show up in the list thankfully. But now I have another problem. I can't boot into the recovery. I try the fasboot boot command and it just restarts normally and for some reason, doing volume down and power doesn't enter the recovery either.
Click to expand...
Click to collapse
I'm not sure you can reboot to recovery from fastboot.
Some people tell you can launch "fastboot reboot recovery" but it is not a standard command and does not work for me.
In fastboot you can boot the recovery image file with
Code:
fastboot boot recovery.img
Change recovery.img with your recovery file.
Keeping it simply, can you reboot normally and reboot to recovery via adb? With "adb reboot recovery"

Fastboot is the way to flash anything
Your phone don't have to get recognized by adb, it's more for sideload or apk installation. To flash recovery, you need fastboot.
Try fastboot flash recovery recovery.img (recovery.img should be in the same folder as fastboot.exe)

Is there any news? I have a similar problem:
I boot in fastboot mode and I run `fastboot oem device-info` to check status:
Code:
$ fastboot oem device-info [15:20:59]
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s
And it seems ok.
Now I try
Code:
$ fastboot flash recovery recovery.img
and it stuck there and it don't do anything.
I tried different PCs and different cables, nothing make it works!
Normally it only lasts some seconds...
What should I try?
Thanks in advance