Related
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 rooted my phone about a month ago using PurpleDrake and now I'm on SkyDragon G3 V0.0.5 w/ TWRP. I had never been able to boot into download but thought nothing of it since it wasn't crucial at the time. Then, yesterday I accidentally took the new OTA update, but was able to fix it with the ADB commands that others have posted. Being able to get into download mode would have made life easier so I tried to fix it today. Flashed stock boot.img and tried to re-run PurpleDrake to see if I missed a step but it won't detect my phone for a reason I don't know. At my wit's end.
Not being able to get into download mode is a concern in case I ever to fully return to stock. Wondering if any one has some insight on how I can do that or if there's some image file I need to flash, etc.?
Thanks!
mypenismighty said:
I rooted my phone about a month ago using PurpleDrake and now I'm on SkyDragon G3 V0.0.5 w/ TWRP. I had never been able to boot into download but thought nothing of it since it wasn't crucial at the time. Then, yesterday I accidentally took the new OTA update, but was able to fix it with the ADB commands that others have posted. Being able to get into download mode would have made life easier so I tried to fix it today. Flashed stock boot.img and tried to re-run PurpleDrake to see if I missed a step but it won't detect my phone for a reason I don't know. At my wit's end.
Not being able to get into download mode is a concern in case I ever to fully return to stock. Wondering if any one has some insight on how I can do that or if there's some image file I need to flash, etc.?
Thanks!
Click to expand...
Click to collapse
volume up button + plug the phone into the computer here is everything you need for stock in one thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
mypenismighty said:
I rooted my phone about a month ago using PurpleDrake and now I'm on SkyDragon G3 V0.0.5 w/ TWRP. I had never been able to boot into download but thought nothing of it since it wasn't crucial at the time. Then, yesterday I accidentally took the new OTA update, but was able to fix it with the ADB commands that others have posted. Being able to get into download mode would have made life easier so I tried to fix it today. Flashed stock boot.img and tried to re-run PurpleDrake to see if I missed a step but it won't detect my phone for a reason I don't know. At my wit's end.
Not being able to get into download mode is a concern in case I ever to fully return to stock. Wondering if any one has some insight on how I can do that or if there's some image file I need to flash, etc.?
Thanks!
Click to expand...
Click to collapse
which adb commands did you use to fix it because I have the same problem and how are you able to access adb command prompts?
jameslee2 said:
which adb commands did you use to fix it because I have the same problem and how are you able to access adb command prompts?
Click to expand...
Click to collapse
I linked you in the other thread
ThePagel said:
volume up button + plug the phone into the computer here is everything you need for stock in one thread http://forum.xda-developers.com/tmobile-lg-g3/general/firmware-t-mobile-lg-g3-t2818667
Click to expand...
Click to collapse
Thanks for the reply. Sorry, I could have been more clear in my post. I have visited that thread and held volume up while plugging my phone in, but all that happens is the LG logo screen pops up for a few seconds, then the phone shows the charging percentage. When I try to do it from the advanced reboot menu when the phone is powered on, it simply reboots into the system. Same deal if I try to do it from TWRP. Really not sure what I'm doing wrong here. Is it possible that I somehow corrupted the bootloader or something else that's hopefully fixable?
mypenismighty said:
Thanks for the reply. Sorry, I could have been more clear in my post. I have visited that thread and held volume up while plugging my phone in, but all that happens is the LG logo screen pops up for a few seconds, then the phone shows the charging percentage. When I try to do it from the advanced reboot menu when the phone is powered on, it simply reboots into the system. Same deal if I try to do it from TWRP. Really not sure what I'm doing wrong here. Is it possible that I somehow corrupted the bootloader or something else that's hopefully fixable?
Click to expand...
Click to collapse
Are you using the stock data cable. Also try pulling the battery for 10 sec then pluging in the USB.
Sent from my LG-D851 using XDA Free mobile app
jameslee2 said:
which adb commands did you use to fix it because I have the same problem and how are you able to access adb command prompts?
Click to expand...
Click to collapse
adb reboot download
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
mypenismighty said:
Thanks for the reply. Sorry, I could have been more clear in my post. I have visited that thread and held volume up while plugging my phone in, but all that happens is the LG logo screen pops up for a few seconds, then the phone shows the charging percentage. When I try to do it from the advanced reboot menu when the phone is powered on, it simply reboots into the system. Same deal if I try to do it from TWRP. Really not sure what I'm doing wrong here. Is it possible that I somehow corrupted the bootloader or something else that's hopefully fixable?
Click to expand...
Click to collapse
I think you made a wrong procedure.
Take the battery out and put back in.
Press and hold volume up button.
Plug in the cable.
Release the button when you see download mode screen.
In addition, make sure you have LG PC Suite with phone driver installed.
Cal-El said:
Are you using the stock data cable. Also try pulling the battery for 10 sec then pluging in the USB.
Sent from my LG-D851 using XDA Free mobile app
Click to expand...
Click to collapse
mingkee said:
adb reboot download
---------- Post added at 07:50 AM ---------- Previous post was at 07:46 AM ----------
I think you made a wrong procedure.
Take the battery out and put back in.
Press and hold volume up button.
Plug in the cable.
Release the button when you see download mode screen.
In addition, make sure you have LG PC Suite with phone driver installed.
Click to expand...
Click to collapse
Thanks but I have already done this with the same result as I've described. I know how it is supposed to be done with the hardware keys and I am using the stock data cable. Even watched a YouTube video demonstrating how it is to be done. Are there any other possibilities?
Just tried it with my nexus 7 cable on a different usb port (which I had done couple times before) and it worked this time! Not sure why or how but appreciate the help, everyone!
Hi to all,
yesterday I attempted to install LineageOS on my LG G4 h815.
I followed this tutorial -> https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Everything went fine. I was able to boot under LineageOS reinstall my apps etc, etc.
This morning when I woke up everything seemed normal too. But, few minutes ago, I sent an SMS via Google Messages the phone froze and then black screen.
When it froze I had 97% battery.
Ï tried to reboot it with power button -> Nothing.
I tried to remove the battery put it back on and pressed the power button -> One tiny vibration but nothing
I tried several times the same last process and finally I managed to get the screen with "Bootloader state : Unlocked !", but I cannot go further.
If I connect the phone with a USB cable, wether he's "turned on" or turned off no led is blinking.
Does someone have a clue to fix this or has ever encountered this issue ?
Tanks in advance and do not hesitate to refer to an old post. I wil check (but found no same case).
Jérémie.
Monkeypox95 said:
Hi to all,
yesterday I attempted to install LineageOS on my LG G4 h815.
I followed this tutorial -> https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Everything went fine. I was able to boot under LineageOS reinstall my apps etc, etc.
This morning when I woke up everything seemed normal too. But, few minutes ago, I sent an SMS via Google Messages the phone froze and then black screen.
When it froze I had 97% battery.
Ï tried to reboot it with power button -> Nothing.
I tried to remove the battery put it back on and pressed the power button -> One tiny vibration but nothing
I tried several times the same last process and finally I managed to get the screen with "Bootloader state : Unlocked !", but I cannot go further.
If I connect the phone with a USB cable, wether he's "turned on" or turned off no led is blinking.
Does someone have a clue to fix this or has ever encountered this issue ?
Tanks in advance and do not hesitate to refer to an old post. I wil check (but found no same case).
Jérémie.
Click to expand...
Click to collapse
Take note of what version of recovery you have you at need to try a few different versions or your device has the dreded boot loop issue........
---------- Post added at 10:38 AM ---------- Previous post was at 10:22 AM ----------
stinka318 said:
Take note of what version of recovery you have you at need to try a few different versions or your device has the dreded boot loop issue........
Click to expand...
Click to collapse
This at help to........
https://forum.xda-developers.com/g4/help/installing-twrp-issue-t3606772
stinka318 said:
Take note of what version of recovery you have you at need to try a few different versions or your device has the dreded boot loop issue........
---------- Post added at 10:38 AM ---------- Previous post was at 10:22 AM ----------
This at help to........
https://forum.xda-developers.com/g4/help/installing-twrp-issue-t3606772
Click to expand...
Click to collapse
Not sure to understand but how can I try different versions of TWRP if I can't get to Recovery mode ?
Monkeypox95 said:
Not sure to understand but how can I try different versions of TWRP if I can't get to Recovery mode ?
Click to expand...
Click to collapse
What version did you flash.......
stinka318 said:
What version did you flash.......
Click to expand...
Click to collapse
I flashed this img twrp-3.0.2-1-h815.img
Monkeypox95 said:
I flashed this img twrp-3.0.2-1-h815.img
Click to expand...
Click to collapse
Is there another version that you can try found on Samsung device sometimes flashing a older version may work.....
stinka318 said:
Is there another version that you can try found on Samsung device sometimes flashing a older version may work.....
Click to expand...
Click to collapse
I really would like to try another version but how ? I can't even get to recovery mode... I'm stuck on the first LG logo.
Monkeypox95 said:
I really would like to try another version but how ? I can't even get to recovery mode... I'm stuck on the first LG logo.
Click to expand...
Click to collapse
If you can get it in to download mode use you laptop to flash recovery this is probably why it has failed.......remember Google s your friend.
stinka318 said:
If you can get it in to download mode use you laptop to flash recovery this is probably why it has failed.......remember Google s your friend.
Click to expand...
Click to collapse
Just to perfectly understand.
Are you advising me to flash my recovery with an older version via my laptop (I imagine via adb/fastboot) despite I can't even get my LG be recognized by my laptop ?
Will the adb/fastboot command be functional as the LG seems not to be recognized on the PC?
Monkeypox95 said:
Just to perfectly understand.
Are you advising me to flash my recovery with an older version via my laptop (I imagine via adb/fastboot) despite I can't even get my LG be recognized by my laptop ?
Will the adb/fastboot command be functional as the LG seems not to be recognized on the PC?
Click to expand...
Click to collapse
The best way to get your laptop I recognize your phone is to get LG up running then with the usb plugged n drop the battery out then put battery back in then close off LG up.
Then start it again and when it go's into download mode the pull usb and close off LG up Then plug it back in with dos prompt open............
stinka318 said:
The best way to get your laptop I recognize your phone is to get LG up running then with the usb plugged n drop the battery out then put battery back in then close off LG up.
Then start it again and when it go's into download mode the pull usb and close off LG up Then plug it back in with dos prompt open............
Click to expand...
Click to collapse
Thanks for your reply and your time. I didn't know this software "LG Up", I will give it a try this evening (in France ^^') and give you feedback then.
Monkeypox95 said:
Thanks for your reply and your time. I didn't know this software "LG Up", I will give it a try this evening (in France ^^') and give you feedback then.
Click to expand...
Click to collapse
LG UP had no effect on the phone.
However, now the phone seems to have 0% battery and when I try to boot it I get the graphics to plug the phone on a source of energy. Once I do that the front led is blinking in orange (I guess because I had less than 1 or 2% o battery) and now the front led is still lit on in orange. Is this a good news or I'm hoping for nothing.
Anyway tomorrow I will try to get it back to my retailer.
Does anyone succedeed to get it replaced by LG even if the bootloader is unlocked ?
Thanks.
After a little journey to the repair shop of my retailer everything seems to work correctly, for the moment, with LineageOS !
Thanks everyone for your help !
I just see black screen with fire tv now. It doesn't show up when I type adb devices anymore. I was running commands on it left and right. I was able to unlock bootloader after hardware mode then was trying to install a custom rom ??? The command I know was something like abcde .......wipe/ system ._. Yea I know. Tried to do the hardware mod again but not picking it up. Is it gone ?
tune345 said:
I just see black screen with fire tv now. It doesn't show up when I type adb devices anymore. I was running commands on it left and right. I was able to unlock bootloader after hardware mode then was trying to install a custom rom ??? The command I know was something like abcde .......wipe/ system ._. Yea I know. Tried to do the hardware mod again but not picking it up. Is it gone ?
Click to expand...
Click to collapse
TWRP is still there when you restart/boot the stick? (you have to use OTG y cable + mouse in order to check that).
If TWRP is still there, then you can use it to restore a full stock rom or flash the system image.
tune345 said:
I just see black screen with fire tv now. It doesn't show up when I type adb devices anymore. I was running commands on it left and right. I was able to unlock bootloader after hardware mode then was trying to install a custom rom ??? The command I know was something like abcde .......wipe/ system ._. Yea I know. Tried to do the hardware mod again but not picking it up. Is it gone ?
Click to expand...
Click to collapse
What custom rom (there isn't one available for the 4k)? From a linux install try a lsusb and see if anything is there (preloader or phone). When you were running commands, were you in the hacked fastboot? As @Pretoriano80 said, get in into twrp and flash, here is a link to the latest to flash to restore, but hopefully you made a backup for you started.
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
Pretoriano80 said:
TWRP is still there when you restart/boot the stick? (you have to use OTG y cable + mouse in order to check that).
If TWRP is still there, then you can use it to restore a full stock rom or flash the system image.
Click to expand...
Click to collapse
TWRP was there but after performing /systemwipe i just see that black screen with firetv logo on the screen it skips the TWRP :/ nothing shows up when i type in adb devices (Minimal ADB and Fastboot) like before it would give a serial number and connected status. nothing in adblink either.
i did ordered that cable like 1 month ago it's not here yet. I might ordered another one today from amazon. I was wondering isn't there any software which can turn laptop keyboard to firestick keyboard from some commands? Adb link has remote which i can use ONCE it's inside the fireOS. A physical keyboard with OTG cable is must for this ? Any alternative ?
and i did search all the first 3 pages of the forum to find the stock rom for 4k firestick but couldn't may be because its was 3 am lol
Thanks for the reply!
Michajin said:
What custom rom (there isn't one available for the 4k)? From a linux install try a lsusb and see if anything is there (preloader or phone). When you were running commands, were you in the hacked fastboot? As @Pretoriano80 said, get in into twrp and flash, here is a link to the latest to flash to restore, but hopefully you made a backup for you started.
https://forum.xda-developers.com/fire-tv/general/official-stock-image-fire-tv-stick-4k-6-t4059777
Click to expand...
Click to collapse
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
tune345 said:
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
Click to expand...
Click to collapse
Why you installed tank rom in mantis...
Redo kamakiri and flash prerooted.
tune345 said:
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
Click to expand...
Click to collapse
Sounds like you unlocked. Did you make it to twrp?
Lsusb is a Linux command in terminal that will show what is connected. This will tell what mode it is in. I broke a chip off one of mine too (tweezers were a bad thought), but that was 7 months ago missing it and it still runs like the rest of mine sticks. The 4k is called mantis, tank is the fire stick2. Totally different.
---------- Post added at 02:30 PM ---------- Previous post was at 02:26 PM ----------
tune345 said:
was trying to find the stock rom to install but was installing tank one which i think is for another version for fireos stick? i don't know what i was doing x_x Can you please put more light on that lsusb? how does it work? i don't know if i was in hacked fastboot it had fully unlocked bootloader...hmm?
Thanks for the stock rom link, i wished i would have found that last night earlier but i guess it's too late now ._. i will try the hardware mod again but it's not detecting it. i also broke one of the chip before, the hardware mode still went last night earlier so it should work again ?
Click to expand...
Click to collapse
Rortiz2 said:
Why you installed tank rom in mantis...
Redo kamakiri and flash prerooted.
Click to expand...
Click to collapse
You never know how deep the water is until you jump head first. I admire people who try!
Rortiz2 said:
Why you installed tank rom in mantis...
Click to expand...
Click to collapse
¯\_(ツ)_/¯
Rortiz2 said:
Redo kamakiri and flash prerooted.
Click to expand...
Click to collapse
I just literally just did that process again after like 7th try but it's still the same not showing up anywhere and black screen with firetv logo. Attaching the picture of the final process, does that mean it's good? it doesn't look like the first process ending.
Thanks !
tune345 said:
¯\_(ツ)_/¯
I just literally just did that process again after like 7th try but it's still the same not showing up anywhere and black screen with firetv logo. Attaching the picture of the final process, does that mean it's good? it doesn't look like the first process ending.
Thanks !
Click to expand...
Click to collapse
That shows you an obvious error in the fastboot step.
Try using a different cable and be sure to do the process from an 2.0 Port.
Since the bootROM part is already done, just type:
Code:
sudo ./boot-fastboot.sh
Connect the stick WITHOUT SHORT ANYTHING and the script will ask to the Preloader to boot to Hacked Fastboot Mode.
When you see "Hacked Fastboot Mode" in the screen of the device, try running fastboot-step.sh again.
Rortiz2 said:
That shows you an obvious error in the fastboot step.
Try using a different cable and be sure to do the process from an 2.0 Port.
Since the bootROM part is already done, just type:
Code:
sudo ./boot-fastboot.sh
Connect the stick WITHOUT SHORT ANYTHING and the script will ask to the Preloader to boot to Hacked Fastboot Mode.
When you see "Hacked Fastboot Mode" in the screen of the device, try running fastboot-step.sh again.
Click to expand...
Click to collapse
sorry where am i entering that code exactly ? because that window was still open with the final error in the instructed directory and i entered that it said command not found so i connected it back to my other laptop and ran Minimal ADB and Fastboot and ran that command there...nothing..
then i went back to linux laptop and close the terminal and re opened a new one and ran that command again said command not found.
tune345 said:
sorry where am i entering that code exactly ? because that window was still open with the final error in the instructed directory and i entered that it said command not found so i connected it back to my other laptop and ran Minimal ADB and Fastboot and ran that command there...nothing..
then i went back to linux laptop and close the terminal and re opened a new one and ran that command again said command not found.
Click to expand...
Click to collapse
You have unlocked and flashed recovery. Do you have a OTG (google if if you don't)? looks like you have TWRP now...
Michajin said:
You have unlocked and flashed recovery. Do you have a OTG (google if if you don't)? looks like you have TWRP now...
Click to expand...
Click to collapse
i have ordered last month, still not here yet. Might order another one from amazon today. isn't there any software which can convert laptop keyboard temporarily for firestick?
and this might be thinking too oddly but lets say i have a micro usb to usb adapter after i plug that in firestick can i take a usb to usb cable and plug it into usb hub? and then plug keyboard mouse usb drive in it ....all going to firestick via usb to usb cable finally converting the signal from usb to usb micro adapter. i believe i have a usb hub which can be powered...
X_X
tune345 said:
i have ordered last month, still not here yet. Might order another one from amazon today. isn't there any software which can convert laptop keyboard temporarily for firestick?
and this might be thinking too oddly but lets say i have a micro usb to usb adapter after i plug that in firestick can i take a usb to usb cable and plug it into usb hub? and then plug keyboard mouse usb drive in it ....all going to firestick via usb to usb cable finally converting the signal from usb to usb micro adapter. i believe i have a usb hub which can be powered... _X
Click to expand...
Click to collapse
No, it has to be a otg. On boot, it will detect it and automatically give you the option for recovery. If you can get into fastboot (you were there before when you ran fastboot.sh you might be able to boot into recovery with fastboot reboot recovery or something simalar. But being in recovery you wont be able to do much unless you have adb connections, or a mouse/keyboard with OTG. Amazon is basically shipping a week for everything right now. I think you really need a OTG to pull it out. ADB and fastboot commands can really screw things up from my novice experience. Get that OTG and try it. I will warn, get one that says it will work for the firestick4k, they dont all work....Make you you give a thanks to the people trying to help, no one is getting paid here...
Michajin said:
No, it has to be a otg. On boot, it will detect it and automatically give you the option for recovery. If you can get into fastboot (you were there before when you ran fastboot.sh you might be able to boot into recovery with fastboot reboot recovery or something simalar. But being in recovery you wont be able to do much unless you have adb connections, or a mouse/keyboard with OTG. Amazon is basically shipping a week for everything right now. I think you really need a OTG to pull it out. ADB and fastboot commands can really screw things up from my novice experience. Get that OTG and try it. I will warn, get one that says it will work for the firestick4k, they dont all work....Make you you give a thanks to the people trying to help, no one is getting paid here...
Click to expand...
Click to collapse
Thank you for that information. Appreciate it. Yea everything is late on amazon now even prime :/ but hopefully i find one which works on the first try otherwise it would be a super bumber...
..but then again how would i know if it's the otg NOT working OR the firestick software/hardware? i did broke one capacitor and was running commands on it like a mad man lol , i believe the CLK one on the picture. what it is for ? why was the firestick still working almost normally after i broke it ? attaching the picture
Thanks again !
tune345 said:
Thank you for that information. Appreciate it. Yea everything is late on amazon now even prime :/ but hopefully i find one which works on the first try otherwise it would be a super bumber...
..but then again how would i know if it's the otg NOT working OR the firestick software/hardware? i did broke one capacitor and was running commands on it like a mad man lol , i believe the CLK one on the picture. what it is for ? why was the firestick still working almost normally after i broke it ? attaching the picture
Thanks again !
Click to expand...
Click to collapse
There are some that say they work. The ones i have had issues with are the OTG hubs. Depending on which chip was damaged, but i broke one off of mine too about 7 months ago (tweezers are bad) but it has been working the same as the rest of mine. could be a heat thing?
Aaahhhhh hit that virus with a brick because i was able to finally fix my firestick last night, pheww!!
thank you everyone for helping
now i need to research the fastest way to clone my ENTIRE setup. I rooted it.
tune345 said:
Aaahhhhh hit that virus with a brick because i was able to finally fix my firestick last night, pheww!!
thank you everyone for helping
now i need to research the fastest way to clone my ENTIRE setup. I rooted it.
Click to expand...
Click to collapse
I have a similar problem with my firestick, How did you manage to fix yours?
Had to do the hardware mode multiple times until i landed at TWRP screen then used adb to flash the stock rom
tinybilbo said:
I have a similar problem with my firestick, How did you manage to fix yours?
Click to expand...
Click to collapse
Were you unlocked? Unless you were playing with recovery, If you have a OTG plugged in from a power off state you should get a recovery option.
Michajin said:
Were you unlocked? Unless you were playing with recovery, If you have a OTG plugged in from a power off state you should get a recovery option.
Click to expand...
Click to collapse
Hi Michajin (Thanks for the reply)
Yes I have an unlocked bootloader, TWRP, and was rooted.
I can get into TWRP via OTG, but it doesn't matter what I flash (Stock or Pre-Rooted), all I get is a black screen (I've left it overnight just to be sure).
I was thinking maybe I should try to flash directly from bootloader rather than TWRP, or making a backup from my other firestick and trying that (the data partition at least).
Either way I'll have to do a little more research first, so any thoughts would be greatly appreciated....