Related
Hi all. I apologize in advance for my English. I use google translator. I have a problem with my hox, I had him in the service but did not find what it is. Telephone writes that the application has stoped and it gradually all aplication and services. I wanted to hard reset or reinstall rom but to no avail. The phone will not run. I wanted to use nvflash but I could not find the files for flashing. Warranty does not. Thank you for your help.
HTC OneX
cid: tmob101
hboot:1.36
3.14.111.27
mafian59 said:
Hi all. I apologize in advance for my English. I use google translator. I have a problem with my hox, I had him in the service but did not find what it is. Telephone writes that the application has stoped and it gradually all aplication and services. I wanted to hard reset or reinstall rom but to no avail. The phone will not run. I wanted to use nvflash but I could not find the files for flashing. Warranty does not. Thank you for your help.
HTC OneX
cid: tmob101
hboot:1.36
3.14.111.27
Click to expand...
Click to collapse
it happend the same to me few days ago, i installed the cyanogen 10.1 from Trip and that has solved this issue for now...
As the only way I can see nvflash. I can not even get into fastboot. :crying:
mafian59 said:
As the only way I can see nvflash. I can not even get into fastboot. :crying:
Click to expand...
Click to collapse
that's weird, if you cannot get into fastboot you probably bricked your device... what is does actually?
Does the pc recognize it as APX maybe ?
Mr Hofs said:
Does the pc recognize it as APX maybe ?
Click to expand...
Click to collapse
i was wondering how could he get errors (so the phone is on) and he is not able to get into fastboot... that's strange
phone is switched off and I get to apx. only lack the necessary files that I should-flashing. I got here just for tablets
When I try to turn on the phone and I have it connected to the PC so it is connected as the NVIDIA USB Boot-recovery driver for Mobile Devices
mafian59 said:
phone is switched off and I get to apx. only lack the necessary files that I should-flashing. I got here just for tablets
When I try to turn on the phone and I have it connected to the PC so it is connected as the NVIDIA USB Boot-recovery driver for Mobile Devices
Click to expand...
Click to collapse
ok so if you are on apx mode the only thing you can do is return the phone to the manufacturer
matt95 said:
ok so if you are on apx mode the only thing you can do is return the phone to the manufacturer
Click to expand...
Click to collapse
And why not in apx mode via nvflash?
APX is at the moment still a hardware brick where no real solution exist for. There is a thread somewhere about that. But when you get out of apx it probably kicks back in after several hours/a day or 2 max
It is strange to me that the phone occasionally moves into fastboot. Now charging the batteries.
Well it ain't that good anyway.....that's for sure !
Mr Hofs said:
Well it ain't that good anyway.....that's for sure !
Click to expand...
Click to collapse
I know that too, so I'm trying to solve.
mafian59 said:
I know that too, so I'm trying to solve.
Click to expand...
Click to collapse
I think the only way to fully solve this is with S-Off (and the proper knowledge ) at least that's what i read about.
Mr Hofs said:
I think the only way to fully solve this is with S-Off (and the proper knowledge ) at least that's what i read about.
Click to expand...
Click to collapse
Probably. I finally got into fastboot and clockworkrecovery but I am in error E: Unable to write to ums lunfile (No Such file or directory)
Then you need to upgrade the recovery. You have an older one. Try cwm 5.8.4.0 it solves that problem
Mr Hofs said:
Then you need to upgrade the recovery. You have an older one. Try cwm 5.8.4.0 it solves that problem
Click to expand...
Click to collapse
i have this problem on recovery-clockwork-touch-5.8.4.0-endeavoru.img. I do not have a problem only with sdcard but when i want to mount system or data or cache ...
mafian59 said:
And why not in apx mode via nvflash?
Click to expand...
Click to collapse
In order to use nvflash you need the sbk which is something that hasn't been leaked.
Also the apx mode that you are stuck in is the low level recovery mode.
Nobody has found a way yet to safely enter and exit this mode.
Certain Hardware faults trigger this mode which means you should see these questions.
Why are you in apx mode?
What has caused you to enter this mode?
And the most likely answer is that something in your device has stopped working.
So even if you can use nvflash to reflash your devices partitions. It's still unlikely to work again as the thing that caused it to enter apx in the first place has not been addressed
Edit: stupid phone. Only loaded half of the comments.
I hope your in luck and back alive but note that it is highly likely that you will end up stuck back in apx soon
Sent from my HTC One X using xda app-developers app
Alex240188 said:
In order to use nvflash you need the sbk which is something that hasn't been leaked.
Also the apx mode that you are stuck in is the low level recovery mode.
Nobody has found a way yet to safely enter and exit this mode.
Certain Hardware faults trigger this mode which means you should see these questions.
Why are you in apx mode?
What has caused you to enter this mode?
And the most likely answer is that something in your device has stopped working.
So even if you can use nvflash to reflash your devices partitions. It's still unlikely to work again as the thing that caused it to enter apx in the first place has not been addressed
Edit: stupid phone. Only loaded half of the comments.
I hope your in luck and back alive but note that it is highly likely that you will end up stuck back in apx soon
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
something that is probably true. I lost my phone, the police found him. phone returned to me with a broken display. I changed the display and since then I have found increasingly in apx mode.
I would swap the motherboard but I do not know where to buy it.
Okay, so recently installed the 4.4.2 OTA on my completely stock nexus 7 (unrooted, bootloader still locked).
Tried connecting to my PC via bluetooth (for headset) and noticed that it wasnt working (was working on 4.4), so decided that maybe a reboot would fix the problem.
And now the tablet doesn't boot. Completely unresponsive, no charging icon etc. either. Tried holding down the power button, power and +/- vol for 20+ secs to no avail. Connecting the tablet to my laptop makes windows update search for the QHSUSB_DLOAD driver. From what I've read this is supposed to be some sort of hardbrick?
I left the tablet completely stock and haven't done any tinkering except use the Wugfresh toolkit to do a backup (which only needed USB debugging on). Also the battery was definitely 60%+ before I attempted rebooting.
Help please? This is completely out of the blue seeing as I never even unlocked the bootloader or anything?
Please help!
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
mdamaged said:
See if something in this thread helps: http://forum.xda-developers.com/showthread.php?t=2393604
...and http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
crash91 said:
Gone through both of them, tried the steps in the first one but I cant get to fastboot, still a blank screen and QHSUSB_DLOAD in device manager. The second one mentions in it's FAQ that the bootloader must be unlocked before using it? Mine was locked so I guess I cant use that method?
Click to expand...
Click to collapse
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
mdamaged said:
Hmm, well, last ditch would be to charge it overnight, and hold the power button down for several minutes, if that doesn't do it, you may have to just use the warranty.
Click to expand...
Click to collapse
I'll update this tomorrow morning, thanks for your help!
crash91 said:
I'll update this tomorrow morning, thanks for your help!
Click to expand...
Click to collapse
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
mdamaged said:
No problem, keep us updated, too bad there isn't a 100% sure-fix answer though.
Click to expand...
Click to collapse
Alright so still no dice. Warranty is out of the question because I bought an imported version off eBay before it was officially available on Google play here in India.
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
crash91 said:
(...)
From what I've understood this may be recoverable. People have made fixes for some HTC devices etc. Basically if someone could makes a "QCN" backup from a working device I may be able to restore the bootloader using the Qualcomm drivers. Or would this tool be of any use?
http://forum.xda-developers.com/showthread.php?t=1308546
Not too familiar with all this low level flashing stuff - so need a second opinion. Will try again today evening, leaving it unplugged this time.
Click to expand...
Click to collapse
Yeah, I don't know much about that either, sorry, I'm not going to be much help there.
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
crash91 said:
Ok, am I the first person with this problem? When the device is plugged in to the PC and I try holding down the buttons (tried almost every combo I could think of) the disconnect/connect sound plays and the tablet is re-detected by device manager as QHSUSB_DLOAD. Im extremely disappointed that this can happen even without screwing around with the system.
The warranty card with the tablet seems to imply international warranty although not specifically stated, it's from the US, so would taking it to an Asus center in India be of any use?
Click to expand...
Click to collapse
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
malikmoreni said:
check this: http://forum.xda-developers.com/showthread.php?t=2415471
and try holding your power button for 30-35secs
Click to expand...
Click to collapse
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
crash91 said:
Only works for a couple of HTC devices, tried asking in the IRC channel and was told that it wont help at all. Held the power button for over a minute nothing happens, still the same in device manager although I can tell it restarts back into the same mode from the connect/disconnect sound.
Click to expand...
Click to collapse
Try using the Qualcomm product support Tool google "QPST" for download links
malikmoreni said:
Try using the Qualcomm product support Tool google "QPST" for download links
Click to expand...
Click to collapse
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
crash91 said:
Downloaded them, I think a USB driver is needed for the tablet to show up as a COM port, I've tried a few drivers but QPST Configuration was unable to connect. Even if it were able to connect I dont know what to do after that, it seems that some device-specific hex/qcn/xml files are needed and this is the mode the manufacturer uses when flashing the bootloader. Does this mean that my bootloader somehow magically corrupted itself?!
Click to expand...
Click to collapse
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
Click to expand...
Click to collapse
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
malikmoreni said:
obviously your bootloader Got Corrupted, i'm outta options here....Please lemme know if you fix this; incase if i run into this too:good:
---------- Post added at 08:44 PM ---------- Previous post was at 08:36 PM ----------
okay, i think i found a solution. search the factory image for the bootloader and flash with fastboot
try following the instructions here
http://forums.androidcentral.com/go...1477-guide-nexus-7-factory-image-restore.html
use "fastboot flash bootloader ****************#####***###*#.img" when you find the bootloader
GOODLUCK:good:
Or you can't get it to fastboot mode also?
Click to expand...
Click to collapse
That's exactly the thing, it doesnt get into fastboot mode or anything, I assume you need a working bootloader to be able to boot fastboot? If it was in fastboot I would have attempted this already.
Anyway the seller says that the item is covered under a 1 year international warranty, thats my only chance now I guess....
The thing that concerns me is that I was completely stock, locked bootloader and unrooted. Only installed the official OTA updates (no sideloading either).
For those who are interested - I finally had time to drop by the service centre. They replaced the battery and motherboard (it was under warranty). I was expecting them to do some magic with QPST or something though.
The same has just happened to me, but I'm out of luck, the warranty has expired.
Did anyone have managed to fix it with the QPST drivers?
thanks.
Fyi, http://www.androidpolice.com/2015/0...rate-not-likely-a-result-of-firmware-updates/
Not sure if its really bricked or not but Its all messed and wont fully boot so it doesnt have lan access anymore for ssh and adb over wifi. I have a male to male usb cable and my pc is recognizing when its plugged in but there are no device drivers installed and adb/fastboot wont recognize (no usb debugging enabled?) so it just hangs on <waiting on device> any idea how I can install devices drivers and move forward with restoring backup of the file I fuxored? Thx guys!
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Havnt got that far yet myself but the way i tinker i will be there shortly .. but as a warning to others, if you are not 100% sure what you are doing, dont muck around especially if you remount /system as rw.
Playing around will be much safer once we get recovery..
Building a recovery shouldnt be too difficult.. its booting a custom recovery that will be the trick.. Jcase had allready said he has figured it out perhaps he will share now that root is out.
roustabout said:
Have you tried disconnecting that A to A cable? When I tried using an A A cable from my laptop to the Fire, it hung when it booted.
It powered on, went to the first white on black Amazon logo, and halted. Disconnecting the cable and power cycling let it complete the boot cycle.
Click to expand...
Click to collapse
Ive got fastboot connected now so it appears it was some funky unknown issue. Fastboot isnt like adb tho and the only time ive ever used it was to re-write whole img files so is that my only option or is there some way I can push stuff through fastboot? The OTA firmware links posted a few weeks back are now dead too..
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Luxferro said:
You can download the OTA updates (they are complete roms). http://forum.xda-developers.com/showthread.php?t=2709811 - links still work, i just redownloaded them (not sure where I put my old ones).
Only problem is the recovery looks for them at /cache/, which isn't writable w/o root. I'm not sure of the functions available via fastboot w/ Fire TV (don't have a cable), but if you can't get into the recovery from fastboot, you can always try to boot a dumped recovery.img from fastboot... but still not sure how you can work around the stock recovery looking for the update file at /cache/
edit: actually don't think fastboot will be of much use with a locked bootloader.
Click to expand...
Click to collapse
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Im not have any luck with those links either ive even tried assigning a static public dns to make sure my opendns stuff was no longer blocking. Does anyone have an alternate link?
alwaysbless said:
Im rooted already, but basically what youre saying is to wait until bootloader is unlocked then flash that via fastboot and then flash recovery via fastboot. I feel like there has to be an easier way lol but im a noob so who knows.
Click to expand...
Click to collapse
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
I had a similar instance. Gained root messed around too much and got it to not boot. Amazon is sending a replacement... But if there is a way around that in the future I would love to just fix it my self.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Luxferro said:
Nah, not saying that at all - would love for an unlocked bootloader, but you might be waiting forever.
this is also one of the reasons that jcase hasn't released what he had (according to his G+ page). since if you bork the stock rooted rom, you'll have a hard time getting it fixed (since the rooted rom is the only current way in). If you can't boot the rom, then you can't fix anything. I'm no expert, so maybe one will chime in. But I think the next step after rooting, is to have a custom recovery, and a way to boot into it if the rom breaks - which we don't have yet.
Click to expand...
Click to collapse
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
alwaysbless said:
So I couldnt even take the system.img and rewrite it using fastboot without having an unlocked bootloader? Sounds like the only way this thing will recover is install cwm/twrp recovery.img whenever that becomes available and then reflash w/ custom recovery.
Click to expand...
Click to collapse
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Luxferro said:
Except you won't be able to install a custom recovery since only your ROM has root access and it doesn't boot.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Got you now. So this is def the first bricked fire tv lol. Guess ill just sit it to the side and see if someone smarter than I can figure something like this out in the future.
Have you tried fastboot boot commands? Like fastboot boot blahblahblah.img? If it is softbricked i guess it can't hurt to try rite?
I don't know if this will work or not, but if you've already tried pulling the power, pulling USB and powering on the next thing I'd try is to obtain a 1 gig or so USB drive, format it fat32 and copy the OTA update to it.
- Leave it zipped.
- Name it update.zip
- pull the plug on the FTV
- put the USB stick in
- power it on and leave it for a bit. Watch it - is the power LED going out? If so, it may doing a recovery install of the signed OTA and rebooting - many Android devices will install anything on the sdcard called Update.zip if it's there at boot time.
What you're hoping is that the USB mass storage is mounted as a possible recovery source at power on and that the OTA is isntalled via the stock recovery. If it works, great, if it doesn't, too bad.
another brick on the wall ?
Dear OP ' i think you are not the only one .
im not sure if im bricked or plain noob
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su
pm disable com.amazon.dcp" . all was good and i had an issue with audio in xbmc and in my great wisdom i did a reset to factory settings.
since then i can not register to amazon i believe because it can not accsses amazon site for verification. so im stuck in there.
i tried to SSH and through command line no device was recognized .
any assistance to this stupidity will be much appericiated
thanks yigo
Yigo said:
after i rooted successfully and did the blocking through host editor guide in fire tv news and for a good measure i run this command "su pm disable com.amazon.dcp" .
Click to expand...
Click to collapse
Afraid I can't help you, but in light of preventing other people (and me) to have the same issues:
I assume the /etc/hosts file will survive factory-resets, it's a file that probably is not restored (so immediatly removed the host-lines from mine), but wonder if the pm disable dcp will also survice a reset ? I assume not (core funcationality for amazon, likely in factory-reset group), but you never know, esp. not in the v1 versions we are running.
Anybody knows if this is the case ? I like the pm disable solution, but if this means that borking up my installation will prevent me from ever restoring it (as unable to connect to amazon), I'll have to fall back to the router-blockage solution, and would suggest other ppl to do that as well
Deregistering AFTV may help with registration issue.
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
To de-register your Fire TV-
1 - log on to your amazon account
2 - Hold the mouse over where it says 'Your Account" but do not click. You will get a list of options.
3 - Click "Manage Your Content and Devices"
4 - Click the center tab "Your Devices"
5 - Click on your Fire TV.
6 - Click "Deregister" right below your Fire TV.
You will ge a message saying it there may be a delay for it to take effect.
[email protected] said:
I had problems registering after factory reset.
I only disabled my amazon.dcp nad had dns and router blocks to prevent updates.
I did not edit my host file.
Click to expand...
Click to collapse
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Still Learning - Passing it on.
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I read your other posting about update blocking.
Seems I did not have my amazon.dcp disabled.
I was not in SU mode when executing command and amazon.dcp was just killed not disabled.
Sorry for any confusion. Thanks
JPDeckers said:
So (while you need to de register the FTV itself within amazon), it looks like you can factory reset after disabling the amazon.dcp service.
Which is good news, as this allows easier disabling of update checks on machine level instead of router level (which not everybody will be able to do) and disabling the update service is better then overlooking a (hidden) fallback URL.
N=1 though, so'll have to wait if more confirmations come in, or somebody will be brave enough to try it
Click to expand...
Click to collapse
I hope one of the folks with a softbricked device gets a chance to see what happens with the over the air update file copied to a fat32 formatted USB stick and renamed update.zip.
With luck, at power on if there is media present, the stock recovery is looking to removable media to see if there's a file named update.zip it can process.
I don't want to softbrick mine to test, though.
So if I am understanding correctly, you should enable updates before you factory reset?
I own a HTC One V. And I did something at the TWRP menu like installing this CARBON-JB-UNOFFICIAL-20131022-1552-primoc thing.. and ever since then the phone doesn't boot.. it won't even go to that menu where it says FASTBOOT{ I think it's called the recovery menu :3 }
But, I charge it.. And then I plug it into the comp, it just connects and disconnects, like it's giving a faint indicator of life :3
Please help. I was on Ignorance V5..
Installing a rom can't hard brick your device.
Try to shut it down by holding the power button and immediately press vol down + power to enter your bootloader. Then you can select recovery and install a backup of your ignorance rom or do whatever you want.
BTW: It looks like you forgot to install the kernel for the custom rom.
ManishByatroy said:
I own a HTC One V. And I did something at the TWRP menu like installing this CARBON-JB-UNOFFICIAL-20131022-1552-primoc thing.. and ever since then the phone doesn't boot.. it won't even go to that menu where it says FASTBOOT{ I think it's called the recovery menu :3 }
But, I charge it.. And then I plug it into the comp, it just connects and disconnects, like it's giving a faint indicator of life :3
Please help. I was on Ignorance V5..
Click to expand...
Click to collapse
Most likely you flashed the wrong ROM.
PrimoU <> PrimoC
Boot loader should still work as expected I guess:
<vol.down>+<power> should get you to the hboot menu.
kvestas said:
Most likely you flashed the wrong ROM.
PrimoU <> PrimoC
Boot loader should still work as expected I guess:
<vol.down>+<power> should get you to the hboot menu.
Click to expand...
Click to collapse
It's not going into Boot Loader. If it did, I would flash back Ignorance.
Please help
ManishByatroy said:
It's not going into Boot Loader. If it did, I would flash back Ignorance.
Please help
Click to expand...
Click to collapse
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
jonas2790 said:
Installing a rom can't hard brick your device.
Try to shut it down by holding the power button and immediately press vol down + power to enter your bootloader. Then you can select recovery and install a backup of your ignorance rom or do whatever you want.
BTW: It looks like you forgot to install the kernel for the custom rom.
Click to expand...
Click to collapse
It isn't going to bootloader when i press power+volume down button.. :\
If I could enter the bootloader menu, I wouldn't have been this worried. :3
kvestas said:
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
Click to expand...
Click to collapse
Can you please tell me where to run this Command? I'm a noob sorry. :/
ManishByatroy said:
Can you please tell me where to run this Command? I'm a noob sorry. :/
Click to expand...
Click to collapse
This command has to be run on a computer.
Similar as you are running fastboot commands to root phone or install custom recovery.
Please google if you are not familiar with fastboot commands at all.
Make sure you have installed proper phone usb drivers to make your phone "visible" from computer.
Btw how did you get running Ignorance?
kvestas said:
Did you try fastboot command to reboot into bootloader?
The command might be accepted by phone during it's initial loading stage:
* connect phone to a computer
* run command (e.g. fastboot reboot-bootloader), must be waiting for response from device
* reboot your phone
* if you are lucky enough the command will be accepted on load.
Click to expand...
Click to collapse
kvestas said:
This command has to be run on a computer.
Similar as you are running fastboot commands to root phone or install custom recovery.
Please google if you are not familiar with fastboot commands at all.
Make sure you have installed proper phone usb drivers to make your phone "visible" from computer.
Btw how did you get running Ignorance?
Click to expand...
Click to collapse
My friend got ignorance running for me.. Like I don't know what and where to enter these fast boot commands.. Any link to learn or you explaining will be appreciated.
phone is blank. hasnt lighted a pixel in a week
phone is charged. how do i know this? because i charged it for 3 days :3
tried all combinations of buttons to get to bootloader. i just cant!!!
i connect it to a comp, it connects and disconnects simultaneously.. :/
pls tell me what to do
ManishByatroy said:
phone is blank. hasnt lighted a pixel in a week
phone is charged. how do i know this? because i charged it for 3 days :3
tried all combinations of buttons to get to bootloader. i just cant!!!
i connect it to a comp, it connects and disconnects simultaneously.. :/
pls tell me what to do
Click to expand...
Click to collapse
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
kvestas said:
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
Click to expand...
Click to collapse
Just tried it. I selected device but stuck on downloading drivers
Thanks for the help tho mate
ManishByatroy said:
Just tried it. I selected device but stuck on downloading drivers
Thanks for the help tho mate
Click to expand...
Click to collapse
You can download HTC drivers from almost any other hOV thread.
Like this one in example:
http://forum.xda-developers.com/showthread.php?t=1996665
Basic Requirements. 4th item.
Remember, all you need to try with this tool is to reboot into bootloader. Try to click the tool button while your phone is starting to load.
By the way, you may find fastboot files in that thread as well (Basic Requirements. 5th item).
kvestas said:
You can download HTC drivers from almost any other hOV thread.
Like this one in example:
http://forum.xda-developers.com/showthread.php?t=1996665
Basic Requirements. 4th item.
Remember, all you need to try with this tool is to reboot into bootloader. Try to click the tool button while your phone is starting to load.
By the way, you may find fastboot files in that thread as well (Basic Requirements. 5th item).
Click to expand...
Click to collapse
Yes, I have the HTC Sync installed which gives the necessary drivers for the recognition of HTC phones.. ( My ONE V)
But, the computer just sounds that music when a USB device is connected, the phone is dead. Not even lighting up..
The WinDroid isn't recognizing my device as well..
ManishByatroy said:
Yes, I have the HTC Sync installed which gives the necessary drivers for the recognition of HTC phones.. ( My ONE V)
But, the computer just sounds that music when a USB device is connected, the phone is dead. Not even lighting up..
The WinDroid isn't recognizing my device as well..
Click to expand...
Click to collapse
The computer should not recognize your phone because it is not loaded completely (neither os, neither recovery).
But it might be recognized for a few seconds only while trying to load os. And you might be able to supply reboot command at that particular moment.
Just try what I said.
kvestas said:
You may download and try this tool:
http://forum.xda-developers.com/showthread.php?p=46202420
This might be easier to start from.
Click to expand...
Click to collapse
kvestas said:
The computer should not recognize your phone because it is not loaded completely (neither os, neither recovery).
But it might be recognized for a few seconds only while trying to load os. And you might be able to supply reboot command at that particular moment.
Just try what I said.
Click to expand...
Click to collapse
Yeah.. I tried that.. But nothing is working.. The OS too isn't booting up. So I don't really know when my phone is on or off
ManishByatroy said:
Yeah.. I tried that.. But nothing is working.. The OS too isn't booting up. So I don't really know when my phone is on or off
Click to expand...
Click to collapse
Do you mean led is always off?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Try holding power button down for 30s.
kvestas said:
Do you mean led is always off?
---------- Post added at 04:17 PM ---------- Previous post was at 04:14 PM ----------
Try holding power button down for 30s.
Click to expand...
Click to collapse
Tried. Ain't working. LED ain't even turning on while charging too.. So there's really no way to find out whether it's charging..
Update : Still haven't fixed my phone. Any help would be appreciated. Can't enter Bootloader menu. Phone when connected to computer, gives "sound" that every normal USB when connected gives.. So the phone isn't completely dead. After connecting, the computer doesnt react in any way :crying:
I followed the AFTV guide to a T. Flashed 51.1.4.0, had the boot menu, CWM and everything was golden. Pushed 51.1.5.3 to the SD, rebooted to CWM, flashed, now stuck in a loop. I cant even connect to it with the adb connect command. Am I screwed? Is this thing done? I dont understand. It doesnt even show the boot menu anymore. Just straight to the looping firetv logo. Was i supposed to reflash the boot menu after installing prerooted 51.1.4.0? This sucks if it's done for.....
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Calibaan said:
Have a look here:
http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/
Click to expand...
Click to collapse
Thanks man. Hopefully one of those methods works. I've been at this for 4 hours carefully working my way through every single step. The highest high of the one last flash to go, turning into the gut wrenching sickness of a boot loop is too much for tonight and I'll try tomorrow.
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
supremekizzle said:
On a side note: who runs that site? Guy is a God and needs a golden fire TV sent to him.
Click to expand...
Click to collapse
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
AFTVnews.com said:
LOL! Glad you're finding the site useful. Sorry you ran into issues, but if you unlocked your bootloader already, then you should be able to recover. Follow the guide Calibaan linked.
Maybe I should write a "Hello, I'm Elias" post to put a face to my work.
Click to expand...
Click to collapse
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
supremekizzle said:
Yea bootloader is unlocked. I was literally at the step of flashing the newest prerooted version when it happened. So, if I get past the bootloop, which step should I continue with?
Click to expand...
Click to collapse
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
AFTVnews.com said:
Once you get into recovery, you should follow the "Resetting with Recovery Mode" section found here: http://www.aftvnews.com/how-to-unbrick-and-prevent-bricking-an-amazon-fire-tv/#toc3.2
Some of the steps will likely be redundant and unnecessary, but it ensures everything is in a good state to proceed. Most likely something went wrong when you installed the boot menu, so be sure to verify the boot menu is working by using it to enter recovery mode BEFORE flashing the 51.1.5.3 ROM.
Click to expand...
Click to collapse
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
supremekizzle said:
Thank you. I'm perfectly fine redoing all the steps no matter how redundant. I just want to make sure it's OK to reflash some of the stuff without first deleting the old. Will it just overwrite?
Click to expand...
Click to collapse
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
AFTVnews.com said:
Yes, it's alright to re-flash anything. You should manually delete any files you "pushed" to the Fire TV and re-push them to ensure a corrupted file wasn't the cause of the boot loop. (You don't want to use the same corrupted file when you re-do things.)
Click to expand...
Click to collapse
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
supremekizzle said:
doesnt matter. just tried to fastboot and it isnt detecting any. I know the bootloader was unlocked. I did the adb shell command and it showed unlocked bootloader. WTF happened? EVERYTHING was followed.
OK tried just fastboot device minus the "s" and it's just waiting on device.
It's dead. Isn't it?
Click to expand...
Click to collapse
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
supremekizzle said:
OMG OMG OMG OMG OMG!!!!!!!!!! Keyboard trick worked! It didnt work last night, but hitting the keys in quick succession finally made it boot into recovery!!!! What is the BEST way to proceed now that I'm here. I cannot eff this up!
Click to expand...
Click to collapse
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
AFTVnews.com said:
The Fire TV will still connect via fastboot even if the bootloader is locked. You just can't flash anything if the bootloader is locked.
While it's powered off, connect it to your PC using the A-to-A USB cable. Then plug in the Fire TV power. When it powers on, see if it's stuck on the white Amazon logo. If it is, then you're in fastboot mode, which means it's just an issue with PC drivers. If it's still doing a boot loop, then it's either too far damaged, or there's something wrong with your USB cable/USB port. As for PC drivers, I don't have an exact driver to tell you to use because, at the time I tried many and am not sure which one ultimately worked. It's something I;ve been meaning to figure out.
When the Fire TV detects power coming in through the USB port while it's booting, it enters fastboot mode (indicated by the stuck white Amazon logo).
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
If you're in recovery, install 51.1.4.0 and then proceed with the guide I linked.
Click to expand...
Click to collapse
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
supremekizzle said:
THANK YOU! While doing the keyboard trick there were a couple of times it stuck on the static amazon logo so it must have detected that, but 4 or 5 times connecting to my computer trying to fastboot it did not. I have to go to the Zoo right now, but will continue this later. Just one more question: As long as I'm now in recovery, I should be able to recover. Right? I already went out and bought another rootable FTV, but if this one is saved I can just go return that one.
Click to expand...
Click to collapse
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
AFTVnews.com said:
I cant' say for sure, but if you're in recovery, there is a very good chance you'll get it back to full working condition.
Click to expand...
Click to collapse
Any suggestions?:
http://forum.xda-developers.com/fire-tv/help/fire-tv-boots-white-amazon-logo-screen-t3139511
supremekizzle,
Glad it worked out for you.:good:
supremekizzle said:
So, should I be using the ip shown as "current ip address in CWM" for ADB or the one I had written down from when it was working?
Nevermind. Cannot connect to either IP from adb
lol. I'm dumb. Gotta connect the ethernet.
.....flashed 51.1.4.0 annnnnnnddddd boot loop again gaaaahhhhhhhhhh. Help me fix AFTVNews and I will make a nice donation to you
BOOTED!!!!
AND.... On latest rooted version. Thanks for bearing with me through that emotional roller coaster of despair and hope. None of this would be possible without AFTVNews collecting all of the information into one place and all of the others who put so much work into this like rbox. Round of beers going out to those two via donation. Thank you!
Click to expand...
Click to collapse
Glad it all worked out and glad I could help!
For future reference, when you edit a post, it doesn;t trigger XDA to send out a notification to the user you're quoting (me). That's why I didn't respond to your last message until now (when I manually checked it). Post a reply and use the '@' symbol (like this: @supremekizzle ) to ensure the user gets notified.