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/
I recently got around to trying to get CM11 on my Xperia M. After following Sony's official instructions on their World developer siteon unlocking the bootloader, my phone induced a bootloop. I also suspect that fastboot isn't working, as volume down + usb plug in doesn't activate the characteristic blue LED on the phone's base... I'm really stumped. Any help would be much appreciated. Another question, since I have no idea whether the whole process worked or not, will I be able to send it in to service, in case the situation's rough?
NickTheBrick said:
I recently got around to trying to get CM11 on my Xperia M. After following Sony's official instructions on their World developer siteon unlocking the bootloader, my phone induced a bootloop. I also suspect that fastboot isn't working, as volume down + usb plug in doesn't activate the characteristic blue LED on the phone's base... I'm really stumped. Any help would be much appreciated. Another question, since I have no idea whether the whole process worked or not, will I be able to send it in to service, in case the situation's rough?
Click to expand...
Click to collapse
So you were trying to use flashtool to revert your phone back to Stock... I guess the phone is now hardbricked :C Cause most of the time when people unlock their bootloader and did something wrong, the chance of reverting it back is incredibly low... I guess you should bring it back to where you bought it :C and not to mention entering fastboot is not working :C
I see, thanks anyway for your input mate!
NickTheBrick said:
I see, thanks anyway for your input mate!
Click to expand...
Click to collapse
:good:
NickTheBrick said:
I recently got around to trying to get CM11 on my Xperia M. After following Sony's official instructions on their World developer siteon unlocking the bootloader, my phone induced a bootloop. I also suspect that fastboot isn't working, as volume down + usb plug in doesn't activate the characteristic blue LED on the phone's base... I'm really stumped. Any help would be much appreciated. Another question, since I have no idea whether the whole process worked or not, will I be able to send it in to service, in case the situation's rough?
Click to expand...
Click to collapse
I knw is that having bootloop after following the instruction sony introduced is just normal. You can fix it by flasing the 4.3 ftf.
Volume down + power is not fastboot mode it is download mode. You can only see green led flash once.
NickTheBrick said:
I recently got around to trying to get CM11 on my Xperia M. After following Sony's official instructions on their World developer siteon unlocking the bootloader, my phone induced a bootloop. I also suspect that fastboot isn't working, as volume down + usb plug in doesn't activate the characteristic blue LED on the phone's base... I'm really stumped. Any help would be much appreciated. Another question, since I have no idea whether the whole process worked or not, will I be able to send it in to service, in case the situation's rough?
Click to expand...
Click to collapse
Fastboot mode is volume up (+) and power.. Then plug usb make sure adb driver installed in your computer...
Sent from my C1905 using xda premium
fahrulridwan03 said:
Fastboot mode is volume up (+) and power.. Then plug usb make sure adb driver installed in your computer...
Sent from my C1905 using xda premium
Click to expand...
Click to collapse
He mentioned that fastboot isn't working.. Read the post again.
AndyPhoenix9879 said:
He mentioned that fastboot isn't working.. Read the post again.
Click to expand...
Click to collapse
actually he said that fastboot doesnt start when connecting usb + volume down. That combination does not start fastboot, it starts flashmode. Fastboot is activated while connecting usb + volume up.
[SCRIPT][BATCH][TOOL]Motorola Moto 360 Super Tool bootloader unlock, root, & Restore
Motorola Moto 360 Super Tool
View attachment 2962247
View attachment 2962248
WARNING USE THIS TOOL AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR ANY DAMAGE OR BRICKED DEVICES.
That Being said I have tested this on my device many times without any problems
Download the Super Tool HERE
Motorola Moto 360 Super Tool Options
1. Install adb and fastboot drivers from motorola and test them
2. unlock the bootloader of the watch
3. relock the bootloader of the watch
4. flash stock wear recovery image
5. flash stock wear boot image
6. restore your Moto 360 to stock KGW42N official
7. Root the Moto 360
8. flash TWRP recovery
9. boot to TWRP recovery from bootloader mode
VIDEO ON USING THIS TOOL
http://youtu.be/FMrywAnwqZ0
Latest Super Tool Version 5
CHANGE LOG
Version 1
based on KGW42N Firmware
Version 2
based on KGW42R Firmware
CLeaned up batch file script
Version 2.1
Added TWRP recovery
Added Lollipop Root with TWRP recovery and supersu.zip
Added boot to TWRP from Bootloader and removed boot to stock recovery from bootloader
Version 3
Based on LWX48T Firmware Lollipop android 5.0.1
Version 4
Based on LWX49L Firmware Lollipop android 5.0.2
Version 5
Based on LDZ22O Firmware Lollipop android 5.1.1
Requirements to use this Motorola Moto 360 Super tool
USB interface cable. if you need one watch this video on how to make it
Download the Super Tool HERE at RootJunkysdl.com
Know how to remove the watch band. check this VIDEO
May have a Video coming on how to use this tool soon
i downloaded version 2 and again it cannot send the boot.img
i tried to flash stock firmware and on the sending 'motoboot' it says FAILED data transfer failure (too many links)
The only thing i can do is lock and unlock the bootloader.
vincenzo697 said:
i downloaded version 2 and again it cannot send the boot.img
i tried to flash stock firmware and on the sending 'motoboot' it says FAILED data transfer failure (too many links)
Click to expand...
Click to collapse
It sounds like you didn't unlock your bootloader yet. That or your fastboot drivers are not installed. Run the driver test in the tool
The only thing i can do is lock and unlock my bootloader. Its weird because i follow all your steps
vincenzo697 said:
The only thing i can do is lock and unlock my bootloader. Its weird because i follow all your steps
Click to expand...
Click to collapse
I have a idea to clean up any problems you might be having. In my tool folder there is a program called rsdlite install it and then connect the device in bootloader / fastboot mode. Then it will show up in rsd lite. next select the XML file in the folder and flash the watch to factory. See if this fixes the problems
Tomsgt said:
I have a idea to clean up any problems you might be having. In my tool folder there is a program called rsdlite install it and then connect the device in bootloader / fastboot mode. Then it will show up in rsd lite. next select the XML file in the folder and flash the watch to factory. See if this fixes the problems
Click to expand...
Click to collapse
Thanks my friend. When I will go home I will try it and report back.
vincenzo697 said:
Thanks my friend. When I will go home I will try it and report back.
Click to expand...
Click to collapse
Good luck hopefully you have used rsd lite before.
Tomsgt said:
Good luck hopefully you have used rsd lite before.
Click to expand...
Click to collapse
I tried it but again it doesnt pass the first step. If you come with another idea please tell me.
Unfortunately, My comp doesnt reconize the watch. It just comes up with unreconized device. I have tried 2 diff cables, 3 diff comps, uninstalled, reinstalled drivers multiple times. ANY ideas what could be the issue??
suzook said:
Unfortunately, My comp doesnt reconize the watch. It just comes up with unreconized device. I have tried 2 diff cables, 3 diff comps, uninstalled, reinstalled drivers multiple times. ANY ideas what could be the issue??
Click to expand...
Click to collapse
manually install the motorola adb and fastboot drivers in device manager on the computer. the computer will say that they arent compatible but they will work.
Tomsgt said:
manually install the motorola adb and fastboot drivers in device manager on the computer. the computer will say that they arent compatible but they will work.
Click to expand...
Click to collapse
Well, where are the drivers????? I have the packages in the download, but there are no seperate drives. Thanks for the reply
suzook said:
Well, where are the drivers????? I have the packages in the download, but there are no seperate drives. Thanks for the reply
Click to expand...
Click to collapse
in device manager you will see update devices click it then click manually install. next look at both compatible and uncompatible drivers until you find the motorola drivers. then pick one if it works good and if not then try a different one.
Some times i have to install them manually like this. also make sure usb debugging is turned on on the moto 360 watch. the computer will not see it without this step.
Tomsgt said:
in device manager you will see update devices click it then click manually install. next look at both compatible and uncompatible drivers until you find the motorola drivers. then pick one if it works good and if not then try a different one.
Some times i have to install them manually like this. also make sure usb debugging is turned on on the moto 360 watch. the computer will not see it without this step.
Click to expand...
Click to collapse
Thanks, i have tried all that...im just about out of options.
suzook said:
Thanks, i have tried all that...im just about out of options.
Click to expand...
Click to collapse
Are you sure you are connecting the cable to the correct 4 pins on the watch? This can be confusing because if you flip it over to connect the cable the connections flip also.
Tomsgt said:
Are you sure you are connecting the cable to the correct 4 pins on the watch? This can be confusing because if you flip it over to connect the cable the connections flip also.
Click to expand...
Click to collapse
Yup, double checked wiring, pin, 3 diff comps, everything. Guess I wont have root if I can never get the proper drivers installed. Bummer, thanks for your time.
Hello
Download link is dead
upload new link pls
scumpicule said:
Hello
Download link is dead
upload new link pls
Click to expand...
Click to collapse
download link works fine try again
No more USB after Root??
I was able to unlock the BL and Root my Moto 360 with your tool, thank you very much for the "easy way"!! My concern is that now I cannot reconnect via USB. I have even made 2 more connectors and nothing, not even the USB connection sound. Is this a normal side effect? or did I screw it up? I'm leaning on user error because I was pulling the connector off the watch before unplugging it from the computer and it zapped, shut down the PC and rebooted the watch. Watch seems to be fine, no noticeable issues after it rebooted. So I dunno...
burkebacar said:
I was able to unlock the BL and Root my Moto 360 with your tool, thank you very much for the "easy way"!! My concern is that now I cannot reconnect via USB. I have even made 2 more connectors and nothing, not even the USB connection sound. Is this a normal side effect? or did I screw it up? I'm leaning on user error because I was pulling the connector off the watch before unplugging it from the computer and it zapped, shut down the PC and rebooted the watch. Watch seems to be fine, no noticeable issues after it rebooted. So I dunno...
Click to expand...
Click to collapse
you probably need to uninstall the device in device manager then let the drivers install again
Tomsgt said:
you probably need to uninstall the device in device manager then let the drivers install again
Click to expand...
Click to collapse
I'll give that a shot! Thanks
I'll report back with how it goes.
Hi All,
Request all to provide any suggestions related to the below issue:
I rolled back from android n preview 2 to android m after which my display is scrambled.I am not able to view any thing on it.
But I am getting calls and able to pick them when I roughly expect the place where I can swipe the dialer right to pick the call.
Few things that I want to highlight is :
1)I had unstable wifi connection while downloading the android m OTA.
2)I removed the unlock bootloader check before rolling back in the developer options.
3)I can also sense that i am able to take screen shots when I am holding the power button and the volume down button based on the sound it normally makes (while capturing screenshots)
I am not able to come to conclusion whether this a hardware issue?(may be i need the replacement of the screen) or can it be due to corrupt ota file update?
Any suggestions would be much appreciated.
thanks
I would first see if flashing the m factory image solves the issue. Then look at hardware.
k.s.deviate said:
I would first see if flashing the m factory image solves the issue. Then look at hardware.
Click to expand...
Click to collapse
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
NeverBackDown said:
thank you but the problem is I am not able to see the screen at all and hence I am not able to go to the fastboot mode or recovery mode.
Click to expand...
Click to collapse
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
k.s.deviate said:
use "adb reboot bootloader" from command prompt to enter bootloader or if you know the device is off, press power + vol up + vol down for roughly 5sec, thatll get into bootloader. than flash factory image.
or last case scenario use wug fresh toolkit to force flash the image, make sure you select the device fails to boot box (I think that's what its called, the only other one states "device on/normal" <-- so NOT that one)
Click to expand...
Click to collapse
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
NeverBackDown said:
Thanks I am first looking for type c to usb to connect it to my computer,I will try for it tomorrow and also the first option you provided will work only if usb debugging is already enabled on my phone ,right?
Click to expand...
Click to collapse
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
k.s.deviate said:
yes, the adb command will only work if debugging is on. Once in bootlader, use fastboot commands, debugging doesn't matter at that point.
Click to expand...
Click to collapse
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
k.s.deviate said:
Not that I'm aware of. Sorry, there is a thread on here that may prove useful that deals with bricked phones with OEM unlocked off. The info there might help you at least get back to stock.
Click to expand...
Click to collapse
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
Possibly, I have no experience dealing with a service center unfortunately.
NeverBackDown said:
In that case ,do you think the service center guys have some other means to deal with if it is a software issue?
Click to expand...
Click to collapse
I also want to highlight that,I am getting a black screen on the fastboot mode too,i cant see nothing there..Only way i am able to identify that my device is in fastboot mode is by giving fastboot devices command.
So can this be a software issue?
NeverBackDown said:
Hi All,
I got the cable ,I had everything to flash the official factory images.But the problem is as mentioned earlier I haven't checked the oem unlock in the developer option and this is not allowing to flash the factory images and fastboot flashing unlock is failing.
Is there any work around for this please?
Click to expand...
Click to collapse
You might want to look into android screencast.
I don't know if it still works with the latest android releases, but back in kitkat days if I had a screen that wouldn't display I could use screencast and I'd get the framebuffer displaying on the PC. While viewing on PC I could then do touchscreen "guesses" more accurately and presumably you'd be able to enable OEM unlocked bootloader so you can flash factory images.
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....