Database Develop

HTC ONE wifi not turning on, can't use as storage, speaker sound cracking

Thanks in advance for helping, i've spent hours searching and did not find anything.
Ill try listing exactly what happened to avoid many questions.
I had my HTC one with an unlocked bootloader and s-off (using revone) with the latest 2.24 firmware. Due to a hardware issue i had to put the phone back to stock and return it.
I used an RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe) for this. I used revone to make it S-on again. But i couldn't manage to get it locked again to i returned it unlocked.
After the hardware issue was repaired, i tried to update the phone to latest firmware via adb, it said successful and my bootloader showed it as updated, but when i switched on the phone a black screen with HTC logo in the center and 4 triangles in the corners of the screen showed up.
It wouldn't switch on. After countless tries it finally switched on and in my bootloader it showed the latest firmware and hboot but in my "about" it showed the old firmware. My wifi wouldn't turn on, and my speakers had a cracking sound when used, the phone was hanging alot and i couldnt use it to transfer anything onto the phone. I even tried saving a file via dropbox and it wouldn't save.(i cant transfer a ROM to SD card)
The phone can still be used via adb though.
Is there anything i can do?
SOLVED
I flashed TWRP using all in one toolkit, and ADB sideloaded android rev HD, flashed it and walla everything was good as new

Install a newer ROM.

BenPope said:
Install a newer ROM.
Click to expand...
Click to collapse
i can't install anything via recovery, as i can't transfer anything to the phone. and the RUU i first used is giving an error too.
any other way?

Try Mike's thread here:
http://forum.xda-developers.com/showthread.php?t=2265618

L0rdNels0n said:
Try Mike's thread here:
http://forum.xda-developers.com/showthread.php?t=2265618
Click to expand...
Click to collapse
i just got an email from technocare (the local HTC dealer). They said the mainboard is damaged and need 900dhs (about $225) to repair it.
i immideately rejected. do you guys think it could be a hardware problem? seeing that it happened after a bad RUU flash im guessing it should be software. thanks for the thread will give it a read once i get the phone tomorrow!

You could get one of those USB OTG devices that lets you plug a flash drive into the phone and access it.
I'm thinking about doing the same just to have it on hand because the lack of removable SD card scares me.
I've been in that spot before where the only way I could get my phone to function was by using my PC to put some files on the SD card to use from recovery. Your recovery might also support sideloading which I've never done but I guess it lets you push a ROM straight from the PC into the recovery. I use philz touch and i believe it does both USB OTG and sideloading although i've verified neither.
Recently I flashed something naughty that messed with my boot.img and it broke my wi-fi (wouldn't turn on). I fixed it by doing a selective restore and restoring only /boot from my nandroid backup.

mojomojo_man said:
You could get one of those USB OTG devices that lets you plug a flash drive into the phone and access it.
I'm thinking about doing the same just to have it on hand because the lack of removable SD card scares me.
I've been in that spot before where the only way I could get my phone to function was by using my PC to put some files on the SD card to use from recovery. Your recovery might also support sideloading which I've never done but I guess it lets you push a ROM straight from the PC into the recovery. I use philz touch and i believe it does both USB OTG and sideloading although i've verified neither.
Recently I flashed something naughty that messed with my boot.img and it broke my wi-fi (wouldn't turn on). I fixed it by doing a selective restore and restoring only /boot from my nandroid backup.
Click to expand...
Click to collapse
thanks for your reply,
I have a nandroid backup .zip but i don't know how to put it on to my phone because i can't transfer anything to it.
My h-boot is 1.54 so i can't run any RUU's. I can't root because i can't transfer superuser to my SD card so i can't gain S-off.
I don't know what else to try, spent loads of hours over this.
Any other way i can root without needing SD card or an RUU for hboot 1.54?
I can't get those USB otg devices cause they aren't available in my country.

HELP - Bricked my HTC One (Sprint)

I'm not even sure where to begin. I've been flashing Rom's on multiple devices for a few years now, and have never had an issue until yesterday. I was running the latest stock 3.04.652.2 (sprint) but was rooted and used a few rooted apps. Everything was fine, but then I decided it was time to try a few new roms as I was getting tired of this one. I flashed CM11, and tried to put 4.4 on there.
I should mention that I was using TWRP for everything, except when I tried to load CM11, it said I needed to use the clockword mod recovery, so I did, and didnt' have any issues. It loaded without a hiccup. I didn't fell in love with this rom, so I tried to flash another. I had thought I successfully made a backup and stored it on my computer, but somehow, it didn't save correctly, and is useless.
I got to the point where I downloaded two Roms on the phone. I was going to try one more, Skydragon 4.0, and then a stock version of the Sprint HTC one zip. While trying to flash the skydragon, it went into the correct mode and began the series of questions prior to the flash, and then, about halfway through, there was an error message about syms issue? I can't remember what the exact wording was. I googled around, and was told that if I wiped the kalvic drive, it would solve the issue. I accidentally wiped everything.
So here I am. Stuck on the bootload screen. I've got a white background...it looks like I'm in recovery, however, there is nothing to recover. I can't even factory reset, because there is nothing on here. It won't load anything. I've tried following every Youtube video, and read through every forum I can find. Nothing works. I've tried downloading every stock rom I can find from Sprint, but I can't get any of the zip drives to open to get to the .image file. So here is what I'm working with...
Tampered
Unlocked
M7_WLS PVT SHIP S-ON RH
HBOOT-1.33.0000
RADIO - 1.00.20.274.0202
OpenDSPv26.120.16:30:08:-1
eMMC-boot
May 8 2013,16:30:08:-01
Fastboot (which I can change to fastboot usb)
Bootloader
Reboot
Reboot bootloader
Power Down
When I try to connect the usb to the phone, nothing happens, it sounds like it recognizes it, but then get an error message stating that the USB is not recognized. None of the other options do me any good. Reboot, power down, etc ,all take me right back to this screen. I've got all of the developer sdk tools and was going to try to manually put them back on, but can't even do any of it because I can't get the ROM to work.
Do I have any options? Or, am I better at this point to just drop it in the toilet, and shell out the money for the insurance claim to get a phone? I thought about taking it to the Sprint store down the street, and just asking for a Christmas miracle, but I"m not sure how much trouble it will get me in...
Please help! I can't go through Christmas without a phone.
John

did you try to make " fastboot erase cahe(s)" ? it may solve the problem.
or you should flash another recovery that support your rom!

Ba7rani said:
did you try to make " fastboot erase cahe(s)" ? it may solve the problem.
or you should flash another recovery that support your rom!
Click to expand...
Click to collapse
I can't even get it to connect to the usb on the computer. It say the usb drive doesn't work. My only options are what's available on the screen. Anything I do reboots me to the recovery screen. There is no way to re-load anything on it. I think I'm screwed. I might try to take it back to sprint and see what they say. Even though it says tampered on the top...the S is set to ON, so maybe that will save me?

redsoxfanatic76 said:
I can't even get it to connect to the usb on the computer. It say the usb drive doesn't work. My only options are what's available on the screen. Anything I do reboots me to the recovery screen. There is no way to re-load anything on it. I think I'm screwed. I might try to take it back to sprint and see what they say. Even though it says tampered on the top...the S is set to ON, so maybe that will save me?
Click to expand...
Click to collapse
Try another computer or just reinstall latest drivers ..if u can get into bootloader ..connect to computer via usb ..u will see FASTBOOT USB ..then go into adb folder ..open cmd ..write fastboot erase cache ..this might help
Sent from my HTC One using xda app-developers app

vaibhav satam said:
Try another computer or just reinstall latest drivers ..if u can get into bootloader ..connect to computer via usb ..u will see FASTBOOT USB ..then go into adb folder ..open cmd ..write fastboot erase cache ..this might help
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
how do I get into the abd folder again? This windows 8 is killing me. I got there last night, but cant remember how. I right clicked on something in the sdk tools, but now can't find it

redsoxfanatic76 said:
how do I get into the abd folder again? This windows 8 is killing me. I got there last night, but cant remember how. I right clicked on something in the sdk tools, but now can't find it
Click to expand...
Click to collapse
Hold "Shift" + right click at empty area then open "open command window here"
Its better to use another windows instead of W8, Its need special drivers I think

Ba7rani said:
Hold "Shift" + right click at empty area then open "open command window here"
Its better to use another windows instead of W8, Its need special drivers I think
Click to expand...
Click to collapse
Absolutely right ..i suggest you to install different os (Windows 7) ..Hold Left Shift + right click on empty area then open cmd
Sent from my HTC One using xda app-developers app

vaibhav satam said:
Absolutely right ..i suggest you to install different os (Windows 7) ..Hold Left Shift + right click on empty area then open cmd
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Ok...got into the cmd prompts...keep getting : fastboot is not recognized as an internal or external command.
the phone won't even connect to the pc. says the usb is not recognized...even when it's on fastboot usb
At this point, I'm so frustrated, I'm going to try to take it to a sprint store...if they tell me I'm screwed, I'll come home, and accidentally drop it in the sink, and then file the insurance. Don't know what else to do...

Its better to use another windows instead of W8, Its need special drivers ..
I face same problem with Win. 8
You are in safe side don't worry
I think u need only to fastboot erase caches

Ba7rani said:
Its better to use another windows instead of W8, Its need special drivers ..
I face same problem with Win. 8
You are in safe side don't worry
I think u need only to fastboot erase caches
Click to expand...
Click to collapse
When you say safe side, do you think I'll get in trouble at the Sprint store? It does say tampered, and unlocked, but the S is on. I'm just going to go with "my brother in law came over last night for the holidays and started messing with my phone. This morning, when I woke up, this is all I can get to." Nothing loads. I'm hoping they will fix it. Otherwise, I'm out $150 for the insurance.
I don't have a win 7 computer, otherwise I would try. This sucks.

redsoxfanatic76 said:
When you say safe side, do you think I'll get in trouble at the Sprint store? It does say tampered, and unlocked, but the S is on. I'm just going to go with "my brother in law came over last night for the holidays and started messing with my phone. This morning, when I woke up, this is all I can get to." Nothing loads. I'm hoping they will fix it. Otherwise, I'm out $150 for the insurance.
I don't have a win 7 computer, otherwise I would try. This sucks.
Click to expand...
Click to collapse
Why are you posting in the GSM One forums ?
Sprint HTC one is totally different than these.
If you have flashed a GSM Rom to your Sprint phone your going to have to RUU back to stock to get your partitions repaired.
if fastboot is not working on your windows 8.1 PC it means you hboot is older than 1.55.000 .... try this RUU with your phone in the bootloader screen
http://dl3.htc.com/application/RUU_..._NV_SPCS_4.38_003_release_335355_signed_2.exe
Edit: your going to need to use fastboot, type this cmd: fastboot oem lock this will relock the bootloader
to accomplish this I suggest an Ubuntu boot CD

I got a similar problem a few days ago, and this is how i solved it. First make sure you have TWRP installed, while in recovery, push the rom into your phone memory. Then go to your phone and click install. Good luck!

Toraxii said:
I got a similar problem a few days ago, and this is how i solved it. First make sure you have TWRP installed, while in recovery, push the rom into your phone memory. Then go to your phone and click install. Good luck!
Click to expand...
Click to collapse
How do you push it? I tried sideloading and it says device not recognized

A Hot Mess, Need Help - M7, S-On, Trouble with ADB

The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.

Youngtusk said:
The Whole Story:
So yesterday I successfully upgraded my HTC One M7 to Lollipop for the first time. I was very excited because the UI is awesome. However, my cellular service didn't work. I read that this is because the firmware was out of date.
In trying to update said firmware, somehow I wiped the internal storage of my device (I know...) including my backup. But that doesn't really matter that much... because while using the HTC One Toolkit I also managed to idiotically turn S-ON! So I can't get into recovery anyway...
So I've been trying to get S-Off with firewater because if I can just get into recovery I can install an older backup I have from last year and then get a new ROM and try this circus all over again in a few weeks when my brain is hopefully not dumb. And that is where I've run into trouble with adb.
In the adb console I can see my phone's serial but it always is listed as offline. In fastboot, however, it is listed fine. I have tried so so many things, but at this point I'll try and re-try anything all over again just to get this to work.
Honestly, I'm surprised this thing isn't brIcked by now with all the f--k ups I've had in the past two days.
TL; DR: I royally messed up and accidentally turned S-On. Not sure if it is related, but now adb lists my HTC as offline while fastboot seems to recognize it fine. I can also access all my files on the phone from Windows.
One thing that (I think) is an important detail is that I cannot seem to get the RSA prompt to appear when I plug my phone into Windows with debugging mode on. I have never used this computer with this phone before, so I know it isn't saved or anything (maybe it's worth clearing the RSA keys anyway?).
What I've tried so far:
-Downloaded latest drivers from HTC (2.0.7.29 from 3/3/15)
-Installed Android Studio and updated Google USB Drivers and Platform Tools
-Rebooted Computer and Phone Multiple times
-Unplugged and re plugged USB cord
-Unchecked and rechecked USB debugging
Please...Please, I desperately need people who are better at this than I am.
Click to expand...
Click to collapse
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!

eyeyousee said:
maybe flashing the boot.img and stock recovery of the firmware you are into will help you!
Click to expand...
Click to collapse
Thanks for the tip. Does flashing a boot.img and stock recovery require adb? Currently, that is where my main setback is.
If it doesn't require adb, can you point me into the direction of the right keywords to Google to find out how to do that?

USB not working as expected under custom ROMs

Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you

Marco2G said:
Hello everybody
I'm having a problem. After ditching the first custom ROM (Pure Nexus) because Sygic App kept crashing, I wanted to go back to stock but noticed that I couldn't connect to my windows box via USB anymore. It would display the Nexus 6 device with an warning sign in device Manager. Since it had worked on stock it can't be a hardware issue.
So going stock through fastboot was out because no device was found. ADB also didn't find anything. So after going to LightROM, Sygic worked but I still can't connect via USB. The Nexus 6 is displayed in Windows Explorer but no storage underneath it. ADB still doesn't work and Wug's toolkit, as a consequence, can't work with the device either. I can't fiddle with USB options either, since LightROM doesn't pop up a USB notification and I just can't find the options in system settings.
So I'd like to flash via TWRP, which is installed, but for the life of me I can't find any of the TWRP flashable stock ROMs I see mentioned on the net. Also, there ought to be ZIP update packages since OTA doesn't work on rooted devices. Where can I find those?
Thank you
Click to expand...
Click to collapse
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.

danarama said:
If Fastboot cannot connect in the bootloader, it is nothing to do with the ROM. The ROM and bootloader are completely separate, so it is likely a USB hardware issue, or driver issue. Hardware could be PC Port, Nexus port or cable.
I recommend addressing your fastboot issue first rather than trying to work around it.
Click to expand...
Click to collapse
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.

Marco2G said:
I'm almost tempted to walk away from this whistling like I was never even here...
Even though I unlocked the device in fastboot, I completely forgot you'd have to boot into fastboot in order for that to work. As such I should have put this in the noob question thread. I do appologize for wasting your time so spectacularly.
Obviously, as soon as I did boot into fastboot, flashing stock worked like a charm.
Sorry 'bout that.
Click to expand...
Click to collapse
Haha, no worries. Sometimes it is hard to see the wood for the trees.

Recovery Mode - what to do?

Found my fire tablet with a black screen and in Amazon system recovery <3e> this morning - not sure how it got into that state & how to get out of it. To my knowledge I didn't press any combination of keys that would get me into that state. It had been only very low battery when I plugged it into the electrical socket last night but I didn't touch it until the morning when I found it in this black screen state.
From searching I think this is the Amazon version of Android System Recovery screen. The exact options are:
-------
Amazon system recovery <3>
Volume up/down to move highlight;
enter button to select.
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
----------
I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)"
(http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122)
I've had it for about a month without problems although a couple of days ago it kept trying to update several times in succession.
It has attempted to update a couple of times in the past, which put me into a panic at the time but when I'd check afterwards it would still show 5.0.1. firmware. Also the difference this time was that in the past it would only attempt to update the once, not several times in succession.
I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed. So when it happened in the past I didn't worry.
I'm not sure what to do (logically I'd assume I should just select the 1st option and reboot) but I'm not sure how I even got into this screen and if there's a reason for it so hoped someone might be able to advise me.
With thanks & crossed fingers
Frankie

Sorry - one other question!
Which key is the "enter button"?

FrankieChen said:
Sorry - one other question!
Which key is the "enter button"?
Click to expand...
Click to collapse
I've not used it but as we only have three buttons I'm going with the power button.

Pond-life said:
I've not used it but as we only have three buttons I'm going with the power button.
Click to expand...
Click to collapse
That's what I suspected!

Update
Well I ran out of power so the tablet switched off.
When I plugged it into an electricity socket, I decided to try the "reboot system now" option but it just rebooted and cam back to the same screen. I tried it about 4 times with the same result so I tried the "power down" option but it still returned to the same screen when switched back on.
Would really appreciate anyone's help.

Hmm, is there anything in the recovery logs?
Maybe reboot to bootloader, and see if it'll let you twrp to it from a pc, head to the twrp thread and grab the files.
fastboot boot TWRP_Fire_2.8.7.0.img
If it'll do that it's not on 5.1.1 at least, if not it might have tried to get there.

I haven't followed your instructions yet as after I posted last, it started to flash an error message along the lines of battery was too low to "factory reset" and something else - I don't recall what though. I didn't actually select any options apart from reboot and power down.
It was plugged in at the time but I unplugged it & replugged it in, in case for some reason it wasn't charging.
Since then the error message has stopped flashing and I just have a blank screen although you can see it is backlit. Pressing the power button has no effect

And that's on the charger it came with?
It's not looking good.

FrankieChen said:
...I haven't rooted the tablet although I did apply the "Installing Google Framework/Playstore...
...I'd assumed that installing "Installing Google Framework/Playstore without Root (5th Gen Amazon Fire 2015)" doesn't stop the fire downloading updates but prevents them being installed....
Click to expand...
Click to collapse
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.

julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
True but the thread he's referring to does offer that function as an option in the batch file.
http://forum.xda-developers.com/amazon-fire/general/installing-google-framework-playstore-t3216122
Tomsgt has put together a little install bat (Amazon-Fire-5th-Gen-Install-Play-Store.zip)
Now includes Removing Advertising and Blocks Over the Air System Updates (02 Nov 2015)
Click to expand...
Click to collapse

julianpaul said:
I know this doesn't help your current situation, but just FYI, neither root nor google framework have anything to do with OTA updates. Only hiding/disabling/deleting the OTA related apks will prevent updates.
Click to expand...
Click to collapse
It's still useful information - thanks

It's on the charger it came with and it has finally returned to the same Amazon system recovery screen.
In regards to preventing the updates - I think I did that when I installed the google apps but it was the 1st time i ever did this (it's my 1st tablet), and as it was over a month ago I can't be sure - this is all very new to me.
There are 4 recovery logs, completely meaningless to me.
/cache/recovery/last_kmsg
/cache/recovery/last_log
/cache/recovery/last_log1
/cache/recovery/last_log2
the kmsg log zooms past too fast to read with endless pages dealing with "swapper/0"
the last_log seems to have stuff reffering to tzdata, build, product.cpu, ro.product, dalvik and so on . Log1 and log2 seem to be similar stuff but shorter.
Any idea what I should be looking for?

I hoped it would be readable, build number might yield clues.
Given it will show something seems worth trying to see if twrp can see it in bootloader.

It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
In desperation this morning I took the wipe data/factory reset option but it didn't work. It returned with the same screen and the error message
E:Error in /cache/recovery/dropbox_last_kmsg (Read-only file system)
I had installed the dropbox app but I had never actually signed in so there wouldn't be any data there.
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.

FrankieChen said:
After rebooting and being returned to the same screen, I attempted again to wipe data/factory reset.
This time it gave the message "data wipe complete" but still returned to the Recovery screen.
I've read the term "bricked" in several of the forums - is this what has happened to my device?
I wondered if I should contact Amazon about it as it's still under warranty but wondered if by installing gapps (and most likely having prevented updates as I followed all the instructions), whether I'd have invalidated my warranty.
Click to expand...
Click to collapse
At this point, if you have adb drivers (or are comfortable installing them) you may as well try sideloading an update bin file. Links are here. I'd get the 3820 file.
If you want to do this, post back and I or someone will give you the steps. Otherwise, Amazon has been good about replacing tablets if you just describe what you say in the 1st paragraph of your post.

FrankieChen said:
It may not have any thing to do with the updates as it was working after the updates had tried to install though I have to admit I only used it for a few minutes and I didn't check it before I plugged it in to charge the night before I found the black screen.
I don't actually have a clue what you mean when you say "twrp can see it in bootloader." so I will have to spend some time reading the forums to figure out what to do.
Click to expand...
Click to collapse
use the reboot to bootloader option
set pc up with fastboot and see if it can be booted into twrp by fastboot
http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548

Thank you for the replies. Sorry not to have responded earlier, I had a busy few days and although I have spent a lot of hours trying to read through the forums and find out about twrp, this is the 1st opportunity I have had to get back to trying to resolve the problem.
If I understand correctly, DoLooper has suggested sideloading an update bin file. (3820). I just started trying to do this but as the file to be downloaded is over 600MB and I am on a very slow connection it's showing it's going to take between 7-8 hours to download. If I take this option I will need to wait until tomorrow when I can get to a faster internet.
Pond-life, you have suggested that I
1. "use the reboot to bootloader option"
I'm presuming that this means that I have to select this option from the recovery screen on the tablet - does the tablet have to be attached to the pc via the USB cable when I select the option?
What should I expect once I have selected this option?
Would the tablet not need to be rooted to access the bootloader (as it isn't)?
2. "set pc up with fastboot and see if it can be booted into twrp by fastboot"
When I 1st got the tablet I had difficulties getting the adb drivers to install on my pc and after several days of trying I ended up doing it on another pc which I no longer have access to.
I have tried again to reinstall the drivers using rootjunkies file but again without success. I tried doing it using that method as I remember trying to do it that way (what felt like a billion times) though I don't remember if I finally ended up succeeding with that method or another.
I followed your link "http://forum.xda-developers.com/showpost.php?p=63635664&postcount=9" and tried the 1st method
"[TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 by Snoop05"
running the "adb-setup-1.4.3.exe" I get "0 files copied" after selecting "Yes to install ADB system-wide" which I recall was the problem (zero files copied) that I had previously.
Openning Device Manager after this does show any Fire or Android devices even when the tablet is connected so I'm assuming that the adb driver installation is failing.
I tried again with "adb-setup-1.3.exe". This time I had 4 files copied and got fire listed in the device manager but when I tried to update the driver I am not given the Android option in the list when I select the option to install driver.
I googled to see if anyone else had this error and I found that some peoplehad difficulties installing on XP but seems that MTP not being supported is the reason and it is resolved by installing WMP v10 and above. I have v11 so presume that's not the problem.
I don't have access to another computer at the moment to try and install the adb drivers but should be able to use another one tomorrow. Last time when I got the drivers to install it was on a vista machine so I wondered if that might have something to do with it.
The other thing that occurred to me was maybe there is something wrong with the cable as I only get the fire shown in the device manager for a few moments before it refreshes and then the fire is no longer shown.
I wondered if I should try to use USBDeview (as per http://www.inlovewithandroid.com/android-usb-connection-problems.html) to see if that is the problem. Certainly if I can the drivers installed on another pc it might suggest that there's a problem with mine.
Anyway, if I get the adb drivers to install successfully on another pc, could you explain what I am trying to do by "booted into twrp by fastboot"? Sorry to be so useless!
Huge thanks

Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.

Pond-life said:
Yeah the files needed will all be pretty hefty. So if thinking about going to a custom rom this would be a good time. Though wouldn't download one or the stock until you've seen if you can use it.
1. Yeah I did mean choose that option on that menu you have onscreen. Doesn't need to be attached to go to the screen technically, but won't be able to do anything there until it is connected so no benefit in not waiting until you are. No doesn't need to be rooted. You'd expect it to go to an almost blank screen with =>FASTBOOT mode.... on it in landscape.
2. On plus side you wouldn't need the adb drivers... But the fastboot ones are probably similarly tricky. These ones worked for me https://developer.amazon.com/appsan...etting-up-your-kindle-fire-tablet-for-testing
Though I've not used XP.
If it will fastboot into twrp then you can put the original stock rom on or either of the custom ones from there, so it's not dead and can get to downloading. (or 5.1.1 stock using the safe twrp method)
Did you use a different cable on the machine you got it to work on then? If not probably not the cable.
Click to expand...
Click to collapse
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.

FrankieChen said:
Thanks for all your help Pond Life.
I had such difficulties get the files to download that in the end I gave up and rang Amazon and they offered to send me a replacement.
Sorry to bail out, this is all new to me and most of what everyone has said has me completely baffled so I've decided to take the easy way out.
Thank you again - I really appreciated all your advice.
Click to expand...
Click to collapse
Better luck with the new one