[Q] KF2 - HELP w TWRP! - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hello! Can someone please help me.. Ive been reading and reading different threads and cant come up with a clear solution to my problem...
So I have a rooted KF2 and I am able to get it into fastboot using :
adb shell
su
reboot bootloader
But now what? IDK what to do next. How do I get TWRP onto the device? Once in fastboot it just seems to sit there and do nothing. Ive tried in fastboot mode typing :
fastboot -i 0x1949 boot Downloads/openrecovery-twrp-2.3.3.1-blaze.img
but it just comes back 'waiting for device' and nothing happens. Do I not have the correct fastboot drivers on my comp? Please help. Im using windows 8 too. Not sure if that is making a difference or not?

grantpatrickfarrell said:
Hello! Can someone please help me.. Ive been reading and reading different threads and cant come up with a clear solution to my problem...
So I have a rooted KF2 and I am able to get it into fastboot using :
adb shell
su
reboot bootloader
But now what? IDK what to do next. How do I get TWRP onto the device? Once in fastboot it just seems to sit there and do nothing. Ive tried in fastboot mode typing :
fastboot -i 0x1949 boot Downloads/openrecovery-twrp-2.3.3.1-blaze.img
but it just comes back 'waiting for device' and nothing happens. Do I not have the correct fastboot drivers on my comp? Please help. Im using windows 8 too. Not sure if that is making a difference or not?
Click to expand...
Click to collapse
Type "fastboot -i 0x1949 devices" and tell me what it says?
Also... Everything but the ROM and gapps needs to be in the same folder as your fast boot and adb. So it needs to be in the platform tools folder of the android sdk
---------- Post added at 12:20 PM ---------- Previous post was at 11:57 AM ----------
In fact I believe that your issue is that your files aren't where they need to be. Cm10.1 and gapps go on the kindle, everything else needs to be in the platform tools folder of the android sdk:good:

also make sure you are not on a USB 3.0 port.

Don"t you need a factory cable?
Sent from my KFTT using xda premium

KindleFireGuy said:
Don"t you need a factory cable?
Sent from my KFTT using xda premium
Click to expand...
Click to collapse
It is highly recommended but it can be done without one

Related

I'm Bricked Help

I can put myself into fastboot. I can see my KFTT. The bootloader is broken, the recovery is broken, the boot image is broken. I am in need of drastic measures. There has to be someone that has figured this out. There must be a hardware way to access the storage as it is flash memory. Has someone figured this out? please help. Already tried firstaide I have tried everything on xda please help.
Opideousneo said:
I can put myself into fastboot. I can see my KFTT. The bootloader is broken, the recovery is broken, the boot image is broken. I am in need of drastic measures. There has to be someone that has figured this out. There must be a hardware way to access the storage as it is flash memory. Has someone figured this out? please help. Already tried firstaide I have tried everything on xda please help.
Click to expand...
Click to collapse
Flash Amazon OS 7.2.3. http://forum.xda-developers.com/showthread.php?t=1951254
thank you
seokhun said:
Flash Amazon OS 7.2.3. http://forum.xda-developers.com/showthread.php?t=1951254
Click to expand...
Click to collapse
I can get to fastboot but it wont detected fastboot. It just sits there on the fast boot screen. I'm hoping for something a little more drastic.
Opideousneo said:
I can get to fastboot but it wont detected fastboot. It just sits there on the fast boot screen. I'm hoping for something a little more drastic.
Click to expand...
Click to collapse
Type "fastboot devices" when your device is in fastboot mode and is connected to the computer. If you see no line of crazy numbers and characters, you can't use fastboot mode, in which case, you have a fancy paperweight. Unless you're in warranty, in which case, contact Amazon for an exchange.
I dont think
seokhun said:
Type "fastboot devices" when your device is in fastboot mode and is connected to the computer. If you see no line of crazy numbers and characters, you can't use fastboot mode, in which case, you have a fancy paperweight. Unless you're in warranty, in which case, contact Amazon for an exchange.
Click to expand...
Click to collapse
Just attempted "fastboot devices" nothing said no internal or external command. Should i do this from adb shell? Where should i do this from? How should i run it? Maybe I'm doing it all wrong. Also they will be able to see that it was my fault since i have a blue Kindlefire logo....
Opideousneo said:
Just attempted "fastboot devices" nothing said no internal or external command. Should i do this from adb shell? Where should i do this from? How should i run it? Maybe I'm doing it all wrong. Also they will be able to see that it was my fault since i have a blue Kindlefire logo....
Click to expand...
Click to collapse
Type "fastboot devices" and hit Enter.
You have the 2nd-bootloader installed? That won't do. You're stuck with the paperweight.
Opideousneo said:
Just attempted "fastboot devices" nothing said no internal or external command. Should i do this from adb shell? Where should i do this from? How should i run it? Maybe I'm doing it all wrong. Also they will be able to see that it was my fault since i have a blue Kindlefire logo....
Click to expand...
Click to collapse
If you can still get the device into fastboot then you still have ways to fix your device. [Fastboot devices] will always show nothing. Use this cmd:
Code:
fastboot -i 0x1949 getvar product
If nothing happens then you just have a driver issue. If you get a response saying "tate-something-something" Then you can proceed to using fastboot to reflash your backups or a backup.
You are amazing
onemeila said:
If you can still get the device into fastboot then you still have ways to fix your device. [Fastboot devices] will always show nothing. Use this cmd:
Code:
fastboot -i 0x1949 getvar product
If nothing happens then you just have a driver issue. If you get a response saying "tate-something-something" Then you can proceed to using fastboot to reflash your backups or a backup.
Click to expand...
Click to collapse
I'm not gay but I would marry you after a week of trying to get help you solved it thank you.
My kindle is brick,too
My kindle fire hd 7" is bricked 3 hours ago. I was trying to install 2nd boot loader and twrp recovery for the first time. i made one mistake. I didn't check one box of fireflash1.1. So, after reboot, my kindle is showing red screen. i want to know whether i can get to fastboot with fastboot cable(i don't have one right now but i'll order or make one my own). Also, i want to know how you brick your kindle.
myatkaung said:
My kindle fire hd 7" is bricked 3 hours ago. I was trying to install 2nd boot loader and twrp recovery for the first time. i made one mistake. I didn't check one box of fireflash1.1. So, after reboot, my kindle is showing red screen. i want to know whether i can get to fastboot with fastboot cable(i don't have one right now but i'll order or make one my own). Also, i want to know how you brick your kindle.
Click to expand...
Click to collapse
Yep, you can get to fastboot with a factory cable. I haven't used fire flash so I'm not sure what this red screen is, but the factory cable should work.
onemeila said:
If you can still get the device into fastboot then you still have ways to fix your device. [Fastboot devices] will always show nothing. Use this cmd:
Code:
fastboot -i 0x1949 getvar product
If nothing happens then you just have a driver issue. If you get a response saying "tate-something-something" Then you can proceed to using fastboot to reflash your backups or a backup.
Click to expand...
Click to collapse
How would i reflash a backup?
I got it..
myatkaung said:
My kindle fire hd 7" is bricked 3 hours ago. I was trying to install 2nd boot loader and twrp recovery for the first time. i made one mistake. I didn't check one box of fireflash1.1. So, after reboot, my kindle is showing red screen. i want to know whether i can get to fastboot with fastboot cable(i don't have one right now but i'll order or make one my own). Also, i want to know how you brick your kindle.
Click to expand...
Click to collapse
Droidit! I got it remember I used fire flash. Anyway tell me what you checked and what the partions have in them boot and recovery.
---------- Post added at 08:20 AM ---------- Previous post was at 08:18 AM ----------
myatkaung said:
My kindle fire hd 7" is bricked 3 hours ago. I was trying to install 2nd boot loader and twrp recovery for the first time. i made one mistake. I didn't check one box of fireflash1.1. So, after reboot, my kindle is showing red screen. i want to know whether i can get to fastboot with fastboot cable(i don't have one right now but i'll order or make one my own). Also, i want to know how you brick your kindle.
Click to expand...
Click to collapse
Get a factory cable even if you problem is solved with out the cable they are still nice to have just in-case.
CVanB said:
Droidit! I got it remember I used fire flash.
Click to expand...
Click to collapse
Ahh, ok. Got ya now :good:
onemeila said:
If you can still get the device into fastboot then you still have ways to fix your device. [Fastboot devices] will always show nothing. Use this cmd:
Code:
fastboot -i 0x1949 getvar product
If nothing happens then you just have a driver issue. If you get a response saying "tate-something-something" Then you can proceed to using fastboot to reflash your backups or a backup.
Click to expand...
Click to collapse
im havveing the same problem mine just says waiting for devices . i am in fastboot im useing a mac and fastboot was working when i tried to flash second bootloader
xiro49 said:
im havveing the same problem mine just says waiting for devices . i am in fastboot im useing a mac and fastboot was working when i tried to flash second bootloader
Click to expand...
Click to collapse
Uninstall and then reinstall drivers
CVanB said:
Uninstall and then reinstall drivers
Click to expand...
Click to collapse
im on a mac i dont have drivers
xiro49 said:
im on a mac i dont have drivers
Click to expand...
Click to collapse
Oh can you get access to a windows pc
CVanB said:
Oh can you get access to a windows pc
Click to expand...
Click to collapse
yeah
xiro49 said:
yeah
Click to expand...
Click to collapse
Use a pc and install the drivers. then go through your process
Cool But would like to know whats up with my mac.
the macs usb ports work fine
The kindle charges
so wheres the problem?
note adb was off when this happen but that shouldnt mess with fastboot?

[Q] stuck at kindle fire logo! never been rooted! help!

just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.
joeyx2 said:
just as the title says! its my moms. any help or links to get help would be nice. most of the stuff i find is able to turn on or must be rooted.
Click to expand...
Click to collapse
ok well in either situation your going to need a fastboot cable/adapter, i recommend getting the blackhat adapter mentioned in hashcodes 2nd bootloader + twrp tutorial. Now for the other thing i need to know, is this a 2012 or 2013 model? (2013 has no front facing camera)
It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.
joeyx2 said:
It does have a front facing camera. Can you give me a link? First time looking in the Kindle fire section.
Click to expand...
Click to collapse
Ok lemme grab 2 links you will need.
The thread i was talking about it this: http://forum.xda-developers.com/showthread.php?t=2128848
I personally recommend a custom rom over amazon os so that tutorial could be useful to you in the future should you decide to flash a custom rom on it. There's a link towards the top that goes to the site where you get the fastboot adapter.
Alright and secondly you will need this: http://forum.xda-developers.com/showthread.php?t=2096888
Read its instructions or you might have issues. Also when you plug in your kindle with the fastboot adapter it will show up as a tate device in the device manager, download the drivers in my signature and extract them somewhere on your computer, then in the device manager right click the tate device and hit update drivers and choose a place to search for them and choose where you extracted my drivers and it should install the drivers. If you are on windows 8 you will have to disable driver signature enforcement first though. Once drivers are working you should be able to restore with kffa.
well i ordered the fastboot adapter and it does go into fastboot mode but i have tried a few utilities and they all seem to blow right threw the process. its like it seeing the phone but not doing anything. the only thing i can think of is USB debugging was not turned on and that may be why i cant get it to act right. of course i cant turn it on cause i'm stuck at the logo so is there a way around that or is there a program like Samsung has called Odin that i can use to flash stock everything on?
Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
Nonono. Adb has nothing to do with fastboot. Adb commands can't even be used with fastboot, only fastboot commands can. Try opening a command prompt that's cd'd into a directory with fastboot in it (kffa or SRT) and run "fastboot -i 0x1949 getvar product", if it reports back something then we can establish that fastboot is atleast working.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.
joeyx2 said:
ok sorry but i havent played with the kindle much as far as rooting, or with command prompt on any device so im kinda lost on what to do and not sure what kffa or srt is.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1951254
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Kffa was one of the links I sent you.... download and extract it. Shift + right click it's folder and hit New command window here. Then run that command I mentioned.
Sent from my LG-P769 using Tapatalk
i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.
joeyx2 said:
i did what you said and at first i didn't but eventually got the command you told me to put in to recognize and read something tate in the command window but i did not see tate in device manager and the utilities still blows though really fast and dont work. im on vista so do you think that is the problem? this is really pissing me off that i cant get this figured out. im about to uninstall everything and delete everthing and start over.
Click to expand...
Click to collapse
well the good news is that means fastboot is working, it only is called a tate device in the device manager initially, once you isntall th edrivers it will show up a s a adb interface which is confusing becuase you don't use adb with fastboot. Anyways you should be able to attempt manualyl flashing the device from that command prompt now using certain commands like
Code:
fastboot -i 0x1949 flash <partition name> imagename
so something like
Code:
fastboot -i 0x1949 flash system system.img
it could be that kffa failed to retreive the files or something so it dint flash, sometimes its download links don't work, try srt i think linear posted the link to it, it might actually work out of the box.

ADB works, but fastboot won't recognize device. Can't update TWRP to 2.7 for kitkat

edit : crap ..... worng section ... how do I delete ?
Hello.
I have a KFHD 7" happily running under Hashcode's CM10.0. I'd like to update to kitkat.
For that, it seems I need to upgrade my recovery from TWRP 2.4 to 2.7. ( If the rom should install under TWRP 2.4, let me know, cause I got an error when I tried. )
So, after messing a bit with my drivers, I got ADB to work fine.
However, I need fastboot to update recovery. My Kindle can go into fastboot, no problem.
But windows just won't recognise it. "Fastboot devices" always show no devices connected.
I tried with various drivers ( including those from QEMU thread ) on 2 differents computers.
So I'm starting to wonder if there is something I missed in the virious threads. Is there something I should know that would prevent me from seing the device under fastboot but not ADB ?
kaceps said:
Hello.
So I'm starting to wonder if there is something I missed in the virious threads. Is there something I should know that would prevent me from seing the device under fastboot but not ADB ?
Click to expand...
Click to collapse
Are you running Windows 8.1?
Sent from my Nexus 4 using Tapatalk
Thanks for the answer.
No, I'm runing 7.
Also, I will delete this thread and re-post in Q&A. As soon as I find the option ...
Try flashable zip.! To update
kaceps said:
edit : crap ..... worng section ... how do I delete ?
Hello.
I have a KFHD 7" happily running under Hashcode's CM10.0. I'd like to update to kitkat.
For that, it seems I need to upgrade my recovery from TWRP 2.4 to 2.7. ( If the rom should install under TWRP 2.4, let me know, cause I got an error when I tried. )
So, after messing a bit with my drivers, I got ADB to work fine.
However, I need fastboot to update recovery. My Kindle can go into fastboot, no problem.
But windows just won't recognise it. "Fastboot devices" always show no devices connected.
I tried with various drivers ( including those from QEMU thread ) on 2 differents computers.
So I'm starting to wonder if there is something I missed in the virious threads. Is there something I should know that would prevent me from seing the device under fastboot but not ADB ?
Click to expand...
Click to collapse
If you have the image,try using FireFlash by stanga72. Just place the image on the sdcard,open fireflash,select "Flash Recovery" and choose the image. Hit Flash,and reboot into recovery.
SafinWasi said:
If you have the image,try using FireFlash by stanga72. Just place the image on the sdcard,open fireflash,select "Flash Recovery" and choose the image. Hit Flash,and reboot into recovery.
Click to expand...
Click to collapse
This.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
For some reason, Kindle devices won't be recognized in fastboot without the specific flag "-i 0x1949". For example, "fastboot devices" becomes "fastboot -i 0x1949 devices" and "fastboot flash recovery recovery.img" becomes "fastboot -i 0x1949 flash recovery recovery.img".
I'm positive this is the issue.
Have a nice day!
Sent from my Nexus 7 using Tapatalk
Download .zip file and install from recovery
Sent from my Amazon Tate using XDA Free mobile app
xuxu09 said:
Download .zip file and install from recovery
Sent from my Amazon Tate using XDA Free mobile app
Click to expand...
Click to collapse
He's not asking for a workaround, he's asking how to use his fastboot, which my answer covers thoroughly.
Sent from my Amazon Tate using Tapatalk

[Q] Bootloop after exploiting files from CM

Hi there,
I have a new KFHD 7" with bootloader version 7.4.9, which I tried to put a custom ROM with the How-To from the Cyanogen website (Install_CM_for_tate).
I have a fastboot cable and everything went fine, after flashing the files, the device started TWRP. I pushed the CyanogenMod and Gapps over, which completed successfully and then back-upped as recommended.
After that, I was asked if I wanted it to install SU which I accepted. In the next reboot, I got into a bootloop with the kindle logo not turning blue anymore.
I tried to reflash, but that resulted also in a bootloop without getting into TWRP.
Any ideas what I should try next? Thanks!
3rd gen.
2012
Tate-PVT-08
thatissounfair said:
Hi there,
I have a new KFHD 7" with bootloader version 7.4.9, which I tried to put a custom ROM with the How-To from the Cyanogen website (Install_CM_for_tate).
I have a fastboot cable and everything went fine, after flashing the files, the device started TWRP. I pushed the CyanogenMod and Gapps over, which completed successfully and then back-upped as recommended.
After that, I was asked if I wanted it to install SU which I accepted. In the next reboot, I got into a bootloop with the kindle logo not turning blue anymore.
I tried to reflash, but that resulted also in a bootloop without getting into TWRP.
Any ideas what I should try next? Thanks!
3rd gen.
2012
Tate-PVT-08
Click to expand...
Click to collapse
Use the KFHD system restore tool. Make sure it's for the 7" tablet. You'll need a fastboot cord to restore.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Use the KFHD system restore tool. Make sure it's for the 7" tablet. You'll need a fastboot cord to restore.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your reply!
I tried following the instructions from Thread 1951254.
Problem is, I plugged in the fastboot cable, the Kindle shows the fastboot logo, I enter
Code:
adb shell su -c "reboot bootloader"
and get
Code:
error: device not found
When entering
Code:
fastboot -i 0x1949 getvar product
the product type is printed.
I thought adb commands don't work in fastboot mode?
Is it maybe the Kindle boot version that I have? I think it was 7.4.9...
Adb takes adb commands.
Fastboot takes fastboot commands.
There is no need to issue a reboot command because you are already in bootloader mode (fastboot).
thatissounfair said:
Thanks for your reply!
I tried following the instructions from Thread 1951254.
Problem is, I plugged in the fastboot cable, the Kindle shows the fastboot logo, I enter
Code:
adb shell su -c "reboot bootloader"
and get
Code:
error: device not found
When entering
Code:
fastboot -i 0x1949 getvar product
the product type is printed.
I thought adb commands don't work in fastboot mode?
Is it maybe the Kindle boot version that I have? I think it was 7.4.9...
Click to expand...
Click to collapse
The ADB commands are there in case you still have access to your OS and root. That's when this can be done with a regular USB cord. You don't have that so use your fastboot cord to enter fastboot automatically (should.) Run the bat and choose option 3.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
The ADB commands are there in case you still have access to your OS and root. That's when this can be done with a regular USB cord. You don't have that so use your fastboot cord to enter fastboot automatically (should.) Run the bat and choose option 3.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Awesome, it worked!! Thanks for the explanation too, very helpful!
I would like to retry the flashing. Any recommendations or tips I need to follow?
Got it, thanks everyone!!
thatissounfair said:
Awesome, it worked!! Thanks for the explanation too, very helpful!
I would like to retry the flashing. Any recommendations or tips I need to follow?
Click to expand...
Click to collapse
If you want the 2nd bootloader and TWRP,use FireFlash or Flasher or flash them manually
Sent from my device running CyanogenMod 11

HTC One ATT (US) Soft Brick needs help to un brick the phone

Good day everyone.
I rebooted my phone one day and came into the looping Logo splash screen issue. I followed all the step which ATT (that is the carrier I have and of course they tried both Factory resets and wipe the cache) which didn't work (still looping into the logo screen). They told me I have to buy a new phone BUT why buy a new phone when I know the answer is out there. This is why I love this forum, even though I have been reading it for a day, but already learned a lot.
I can get in the HBOOT menu and also can get into the bootloader menu but when I try to recover my phone, using a program like:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1
Or
HTC One Toolkit - Squabbi - 3.1.2
It doesn't work because when it reboots the phone, the bootloader will not go into the "FASTBOOTUSB" mode which I think is the issue. The USB for the FASTBOOT never comes on with the black HTC screen (when trying to do a recovery)
If the FASTBOOTUSB would come on automatically it could help but wanted advice from you all.
Here is my phone info:
**** LOCKED ****
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4T.20.3218.13
OpenDSP-v31.120.274.0617
OS-3.17.502.3
eMMC-boot 2048MB
Sep 10 2013.01:21:12.0
Can someone please lead me the right way to unbrick this soft bricked phone?
If you have any questions, please ask, I will be more then happy to answer.
Thank you all in advance
Firstly, are you sure you have the correct/updated drivers on your computer?
also I think you're using the wrong RUU btw unless you have a superCID phone and it sounds like you're completely stock, the one you posted is for the eu version and you need this http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/ for an att device.
Next Download this http://forum.xda-developers.com/showthread.php?t=2317790 if you don't already have adb and fastboot and then see if your computer is recognizing adb at least when you're at the main hboot menu by typing "adb devices" once you open a command prompt and navigate to the adb and fastboot folder by typing "cd /(whatever your adb folder is called)"
If adb works you should gain s-off for your device using this http://firewater-soff.com/instructions
Now you should be able to flash the RUU following directions and in this guide http://forum.xda-developers.com/showthread.php?t=2358738
jukiewalsh said:
Firstly, are you sure you have the correct/updated drivers on your computer?
Download this http://forum.xda-developers.com/showthread.php?t=2317790 if you don't already have adb and fastboot and then see if your computer is recognizing adb at least when you're at the main hboot menu by typing "adb devices" once you open a command prompt and navigate to the adb and fastboot folder.
Click to expand...
Click to collapse
I am not sure if I have the updated drivers but I did install the HTC sync so maybe I do. I am still a noob so sorry if this sounds very noobish.
Question question before I install the the adb program...
Should I go through this before I do anything??
http://www.youtube.com/watch?v=LENBpQW7mM4#t=872
I just watched the video and just want to know will it work with my issue? I know it is a general question but doesn't hurt to ask correct?
Thanks again!
jukiewalsh said:
Firstly, are you sure you have the correct/updated drivers on your computer?
Download this http://forum.xda-developers.com/showthread.php?t=2317790 if you don't already have adb and fastboot and then see if your computer is recognizing adb at least when you're at the main hboot menu by typing "adb devices" once you open a command prompt and navigate to the adb and fastboot folder.
Click to expand...
Click to collapse
Also when I typed in adb devices into the cmd prompt after installing the program it just says:
List of devices
Nothing is under that.
Any recommendation from there? Thank you again!
djjonaaron said:
Also when I typed in adb devices into the cmd prompt after installing the program it just says:
List of devices
Nothing is under that.
Any recommendation from there? Thank you again!
Click to expand...
Click to collapse
I just updated my first response with another helpful guide, and you need to uninstall/remove htc sync from your computer COMPLETELY. That's probably your culprit for not getting recognized by the computer.
jukiewalsh said:
I just updated my first response with another helpful guide, and you need to uninstall/remove htc sync from your computer COMPLETELY. That's probably your culprit for not getting recognized by the computer.
Click to expand...
Click to collapse
Thank you very much Jukiewalsh.
I am downloading the CORRECT program and following your directions. I will keep you updated my friend!
Much much respect!!!
Jon
djjonaaron said:
Thank you very much Jukiewalsh.
I am downloading the CORRECT program and following your directions. I will keep you updated my friend!
Much much respect!!!
Jon
Click to expand...
Click to collapse
But before you do anything else is your device still under warranty? If you send it to HTC chances are you could get a completely new phone...
Sent from my HTC One using XDA Premium 4 mobile app
jukiewalsh said:
But before you do anything else is your device still under warranty? If you send it to HTC chances are you could get a completely new phone...
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I already check with ATT and HTC.. Out of warranty as of June 19th 2014. Yeah.. That SUCKSSSSSSSS
Two weeks over and they will not work with me at all. grrrrr
jukiewalsh said:
Firstly, are you sure you have the correct/updated drivers on your computer?
also I think you're using the wrong RUU btw unless you have a superCID phone and it sounds like you're completely stock, the one you posted is for the eu version and you need this http://www.htc1guru.com/dld/ruu_m7_...13_10-33-1150-01_release_318450_signed_2-exe/ for an att device.
Next Download this http://forum.xda-developers.com/showthread.php?t=2317790 if you don't already have adb and fastboot and then see if your computer is recognizing adb at least when you're at the main hboot menu by typing "adb devices" once you open a command prompt and navigate to the adb and fastboot folder by typing "cd /(whatever your adb folder is called)"
If adb works you should gain s-off for your device using this http://firewater-soff.com/instructions
Now you should be able to flash the RUU following directions and in this guide http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
Quick question.
If I run "adb devices" and it says it is trying to connect to the port number and doesn't find anything. That isn't good is it? I am in the HBOOT menu, uninstalled everything HTC related on my computer. When I run adb devices now it says
List of devices:
Nothing of course is listed.
Thanks,
djjonaaron said:
Quick question.
If I run "adb devices" and it says it is trying to connect to the port number and doesn't find anything. That isn't good is it? I am in the HBOOT menu, uninstalled everything HTC related on my computer. When I run adb devices now it says
List of devices:
Nothing of course is listed.
Thanks,
Click to expand...
Click to collapse
Okay that's weird, sound like a connection problem somewhere. Double check you drivers, reinstall them, and then if it still won't see it then try a different USB port (the one in the back is your best bet)
Does your computer recognize that SOMETHING being connected at all? Like does it make that "ding" sound when you plug it in? haha
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
Also once you have removed all the HTC programs reboot your computer for good measure and then just google search for HTC USB drivers and see if you need yours updated
Sent from my HTC One using XDA Premium 4 mobile app
jukiewalsh said:
Okay that's weird, sound like a connection problem somewhere. Double check you drivers, reinstall them, and then if it still won't see it then try a different USB port (the one in the back is your best bet)
Does your computer recognize that SOMETHING being connected at all? Like does it make that "ding" sound when you plug it in? haha
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 06:29 PM ---------- Previous post was at 06:24 PM ----------
Also once you have removed all the HTC programs reboot your computer for good measure and then just google search for HTC USB drivers and see if you need yours updated
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok.. uninstalled everything, rebooted, Plugged in the USB into the back. Installed the new drivers from here:
http://forum.xda-developers.com/showthread.php?t=2217396
The computer says there is something connected because the plug in device sound kicks up just fine.
Then did this:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
I don't know if that looks good or not. What do you think?
Again thank you!!!
And you not in fastboot mode are you? It would say on your phone screen
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
Wait... When the phone worked was USB debugging enabled?
Sent from my HTC One using XDA Premium 4 mobile app
jukiewalsh said:
And you not in fastboot mode are you? It would say on your phone screen
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 07:06 PM ---------- Previous post was at 07:05 PM ----------
Wait... When the phone worked was USB debugging enabled?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I tried with Fastboot and then not fastboot
The problem is.. the ONLY way for this phone to connect via USB to my computer is through FASTBOOT. When I select FASTBOOT it goes right to FASTBOOT USB. Otherwise it will not connect via USB
One more thing to add.
When i do a factory reset, it gets to Backup CW Package and freezes there if that tells you anything.
Last thing.. I did do this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT35VW911121 fastboot
Is that a good? It recognizes it on the fastboot but not ADB.... hummmm
djjonaaron said:
Last thing.. I did do this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT35VW911121 fastboot
Is that a good? It recognizes it on the fastboot but not ADB.... hummmm
Click to expand...
Click to collapse
Yeaaaaah! You can only be in one separate mode at a time so you were probably just in fastboot before. Okay now I'm going to take you a different route than the RUU because you can't s off without an operating system right now which means you can't flash an RUU.
Now you need to first go here http://htc-one.wonderhowto.com/how-...htc-one-running-android-4-4-2-kitkat-0151186/ and follow the steps to unlock your bootloader (second section), your phone might hang at the end where it reboots but thats fine we just need it to get unlocked for now.
Next download this twrp recovery img http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.7.1.1-m7.img and save it to where your adb/fastboot files are and rename the file to "recovery". After this manually reboot your phone into the hboot again and get it into fastboot mode and then after navigating to your adb/fastboot folder in a cmd prompt type "fastboot flash recovery recovery.img"
next on your phone use the volume keys to highlight "bootloader" and press the power button. It should take you back to the main bootloader screen. Now highlight recovery and press the power button.
once twrp is booted you can set your phone aside for now... download this http://www.androidfilehost.com/?fid=23329332407581059 and save the zip to your adb/fastboot folder. Now type in the command prompt "adb push m7_Stock_Rooted_4.18.502.7_Odex.zip /sdcard/
m7_Stock_Rooted_4.18.502.7_Odex.zip" wait for it to finish and type "adb reboot recovery"
now go to install and select the m7_Stock_Rooted_4.18.502.7_Odex.zip file on your sd card and wait for it to install and then reboot. After you get to this point I'll help you return completely back to your stock tomorrow.:good:
jukiewalsh said:
Yeaaaaah! You can only be in one separate mode at a time so you were probably just in fastboot before. Okay now I'm going to take you a different route than the RUU because you can't s off without an operating system right now which means you can't flash an RUU.
Now you need to first go here http://htc-one.wonderhowto.com/how-...htc-one-running-android-4-4-2-kitkat-0151186/ and follow the steps to unlock your bootloader (second section), your phone might hang at the end where it reboots but thats fine we just need it to get unlocked for now.
Next download this twrp recovery img http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.7.1.1-m7.img and save it to where your adb/fastboot files are and rename the file to "recovery". After this manually reboot your phone into the hboot again and get it into fastboot mode and then after navigating to your adb/fastboot folder in a cmd prompt type "fastboot flash recovery recovery.img"
next on your phone use the volume keys to highlight "bootloader" and press the power button. It should take you back to the main bootloader screen. Now highlight recovery and press the power button.
once twrp is booted you can set your phone aside for now... download this http://www.androidfilehost.com/?fid=23329332407581059 and save the zip to your adb/fastboot folder. Now type in the command prompt "adb push m7_Stock_Rooted_4.18.502.7_Odex.zip /sdcard/
m7_Stock_Rooted_4.18.502.7_Odex.zip" wait for it to finish and type "adb reboot recovery"
now go to install and select the m7_Stock_Rooted_4.18.502.7_Odex.zip file on your sd card and wait for it to install and then reboot. After you get to this point I'll help you return completely back to your stock tomorrow.:good:
Click to expand...
Click to collapse
Sounds great. I will do this once I get home from work tonight and should be ready with everything done above by tomorrow. *crossing fingers*
I really do appreciate your guidance and help through this. You are helping me out so much!!!
Much respect again,
Jon
No problem, and while you're doing it read all the steps on the websites before you begin and then make sure you have a general understanding before you do anything.
Sent from my HTC One using XDA Premium 4 mobile app
jukiewalsh said:
No problem, and while you're doing it read all the steps on the websites before you begin and then make sure you have a general understanding before you do anything.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well i think I just bricked my phone. I took home the phone.. and now it is not booting... there is a USB connection but the screen stays black and when i hold the power button down and/or power button + the volume down it is not booting.
However when i do press the power button down and/or power button + the volume down it does connect and reconnect to the computer. any ideas?
jukiewalsh said:
No problem, and while you're doing it read all the steps on the websites before you begin and then make sure you have a general understanding before you do anything.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Should I try this? do you think it might work? http://forum.xda-developers.com/showthread.php?t=2770684
Thank you kind sir!

Categories

Resources