Hello
Posted this over in Pauls MoDaCo forum as well but not had any replies yet so thought it best to try here as well.
I've bricked my Desire, phone loads up but the sim and sd card aren't recognised (though I can still use wi fi).
When connecting the phone to my PC (tried windows 7 and XP) the drivers fail to install and I get various faults like the device being recognised as android 1.0 usb to a Qualcomm device.
The phone is still rooted (I can install rooted apps from the market) however after following various unbricking guides I always get stuck at stage 2 (i.e. enable sd card), if the PC won't recognise the device how can i run the 'fastboot oem enableqxdm 0' command?
I've also tried running fastboot using a terminal app on the phone but it doesn't recognise fastboot, should i be in a specific directory on the phone when running this command?
Any help greatly appreciated.
Cheers
Have you tried using a different jab port? I had to use one at the back of my pc front ports wouldn't install drivers properly.
Sent from my HTC Desire using XDA App
You need to follow the guide on modaco for unbricking your device. You have the usb brick, and it can easilly be fixed.
Follow the steps religiously and you will be up n running in no time again.
I've followed the guide lots of time, it's not that long winded so it shouldn't be to hard to follow.
I get stuck on step two, using the fastboot command.
My PC and also tried laptop (Win XP and 7), different USB ports (front and back) but each time it attempts to load drivers and I end up with it either being recognised as an Android 1.0, Android Bootloader Interface or a Qualcomm device. I then run fastboot, and get the device not recognised error.
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
celticone said:
I've now tried to connect my phone to a windows Xp and 7 PC and a laptop, a Linux laptop and tried using the Tiny Linux root guide to see if that would work, but each time the PC/laptop fails to recognise the phone so can't get into recovery or run the fastboot command.
Click to expand...
Click to collapse
You don't need to get into recovery for this.
You have sdk installed, so boot your phone by pressing power while holding down the volume down button.
Use a command prompt on your pc and cd to the tools directory in the sdk. If the sdk is saved to the root of your C: drive on the pc you would type
Code:
cd C:\android-sdk-windows\tools
When in there type
Code:
fastboot oem enableqxdm 0
This will re-enable your sd card and allow you to continue.
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
celticone said:
That doesnt work, just stops on the waiting for device line and doesnt continue.
Also using the cmd 'adb devices' shows nothing so I'm guessing my phone isn't recognised on my PC. At the moment it's in fastboot usb (on phone) and in devices on the PC I've got Android Bootloader Interface with the yellow problem sign against it.
thanks for your help, it's appreciated, tried a few forums but no one is that interested in helping.
Cheers
Click to expand...
Click to collapse
It definitely sounds like the old usb brick problem, so that's a good thing! When you tried the commands were you booted into fastboot? When you connect the phone to the computer does the phone display change from saying fastboot to fastboot usb? I think thats what it should say, can't remember to be honest!
Have you tried another usb port, and a different cable too?
Edit: I'd also try rebooting the computer to ensure any running process etc are closed.
Got it fixed, final throw of the dice this morning I connected the phone to a Vista laptop and it was recognised straight away, so downloaded HTCSync then ADB tools on to the laptop and finally got the re enable command to work.
Jeez that took for ever, strange that Xp, Win7 and Linux PCs couldn't recognise the phone but Vista did.
Still got it sorted, thanks for the help.
No worries. Glad you got it sorted.
I have almost the same problem.
but with the legend.
SD is not recognized.
Can´t Call,
Can´t connect via USB.
Is there something I can do in the built in terminal in the ROM?
So short story, my galaxy nexus's power button doesnt work anymore. It stopped working for no reason yesterday, yet when I plug it into the charger the charging screen comese on. I want to be able to power my phone on so that I can get all the information onto my computer so that I can easily transfer stuff to my new phone (replacement gnex coming tomorrow) Is there a way I can turn on my phone without using the power button? Any help would be much appreciated.
If you've got the SDK or just ADB available, you should be able to use the command of "adb reboot" to get the device to boot up. Could be wrong.
Can someone guide me in the direction I need so I can do this adb reboot?
chantheman525 said:
Can someone guide me in the direction I need so I can do this adb reboot?
Click to expand...
Click to collapse
Download the ADB file (usually bundled with Fastboot) from any one of these guides that requires it. Or just Google for it.
Unzip all of that, use command line to get into it's directory, hook your phone up over USB, and type:
Code:
adb reboot
Again, not sure if this will work when the phone is off. If it will work, I think you had to have USB debugging turned on. Its not working for me currently on OSX. So I don't think it will. Maybe there's a different ADB command that can help you.
Its a long shot. There are probably better options.
I'd agree with adb reboot if your computer will recognize it from this mode...
Use the guide linked in my sig to set up ADB if you need.
I'm a newbie to all this, but I don't think anyone here mentioned the necessary step of downloading and installing your phone's specific ADB drivers to your computer.
So, to recap:
Download your phone's ADB drivers on to your computer and install them.
Plug your phone in.
Go to your command prompt and type 'adb reboot'.
I think. I'm new, as you can see by my post count and thanks meter.
I tried to adb reboot. Unfortunately the galaxy nexus cant be recognized when the phone is off. Disappointing but not the end of the world. Thanks for everyones help.
If adb works in download mode you could make a jig to get you there.
Sent from my Galaxy Nexus using Tapatalk
So instead of spamming the forums, I thought I would just make on consolidated post asking for help
Background: I have suffered from a visual disability for over 20 years. There are many facets to it but the one that is relevant here is that some displays trigger instant eye strain and migraines when I view them. I have been to over 27 specialists in 7 states over 2 decades and no one has been able to find out exactly what us causing it. All we know is the issue isn't really caused by the display, but what is driving the display, and seem to be related to colors somehow.
Anyway, I ordered a 4k Fire Stick on July 15, 2019. SO looking at https://forum.xda-developers.com/t/...is-prerooted-stock-images-6-2-8-0_r1.3983091/, it looks like my Fire Stick came with OS 6.2.6.5_r1. I do not recall it ever asking for updates before this, so I do not know if it ever updated to 6.2.7.7_r1 (which is the last update prior to the UI update). I would like to flash OS 6.2.6.5_r1 which is the closest ROM I can find to what was on the stick when I first bought it and it worked.
I also have an unopened 4k Fire Stick I purchased on Nov 29, 2019. This is still sitting new in the box and have never been opened or plugged into anything.
So here is where my questions start
General Questions
1. Are the sticks I ordered the "mantis" one? So I would look for "mantis" instructions for working with it? Can someone provide a stock Mantis 6.2.6.5 ROM, I really don't care too much about being rooted honestly.
Questions for upgraded stick (that I cannot use right now due to disability)
1. Is there any hope for this device? As I understand it there is an eFuse blown during the 6.8 upgrade preventing downgrades.
2. Is there any work going on that will allow that blown eFuse to be bypassed (like a modified 6.2.6.x ROM that doesn't check the eFuse status)?
Questions for unopened stick
1. Is there any way to block the updates while setting up the device (prevent auto update)?
- 1a: I know there is a "BlockUpdate.apk" that can be sideloaded and run, but to do that I would need to have the device up and running to enable ADB Debugging and connect to the device, so I would have had to go though the initial setup, which will update the device, making it to late to install the APK and block the update
- 1b: I know you can also install Remote ADB Shell on the stick and use the PM disable user commands to block OTA updates, but again, you can't get to the point where you can turn on ADB Debugging and install those apps before going though the initial setup, which will update the device, making it to late to block the updates
2. I saw there were some methods where people were using their routers to block access to certain Amazon and/or akamai servers so you could activate the stick but the update check would fail, but all those guides seem to be for Fire TV's, not Fire Sticks, and are all from 2016-ish. Do these still work?
Questions for Rooting device
1. I saw the aluminum foil trick, but all the guides I see seem to start after a point where the device has been activated, which would have forced the update and would be to late for me. Can you root BEFORE the device is activated?
2. How do you connect a Fire Stick to a PC to allow the Linux scripts to see it and root it? I can't connect to the TV and then to my wifi, cause once it connects to wifi, it auto updates, and we're stuck again.
So can anyone help me out? My end goal is to have my upgraded Fire Stick downgraded to the 6.2.6.5 version and will NEVER install a system update, and/or have my unopened FireStick activated and working and NEVER install an update. I don't really care about any enhanced "debloating" or anything after that.
Many thanks up front.
Yes, you can try the unlock infront of the setup, that is the way to go.
But I would test your ruined stick first, it doesn't harm anything... maybe big A. messed the efuse burning up, who knows. Short the stick and in case you can't see 'phone' mode in lsusb, the efuse is burned as expected.
Sus_i said:
Yes, you can try the unlock infront of the setup, that is the way to go.
But I would test your ruined stick first, it doesn't harm anything... maybe big A. messed the efuse burning up, who knows. Short the stick and in case you can't see 'phone' mode in lsusb, the efuse is burned as expected.
Click to expand...
Click to collapse
Thanks, how would I unlock the device and block the updates without having to go through through Fire Stick setup (which would force the update)
As I understand it, I could
1 - Boot up the modified Linux iso in a VM
2 - Open the Fire Stick and use the aluminum foil to short it
At that point, how do I connect the Fire Stick to my PC? If I plug it into my TV and connect it to my network, it's going to auto update.
Once the above quesiton is answered, I could then run the scripts and get root and get twrp via the scripts in the Linux iso. But at that point, what would I flash in TWRP to block the OTA updates? I would not be anle to get to any point that allows me to enable ADB debugging without going through the Fire Stick setup, which would force the OTA updates
The thing is really easy.
Older 4k sticks are vulnerable to the current kamakiri exploit, and newer sticks are not.
Amaz. fixed with 6.2.8.0 the bootrom feature used in kamakiri, so any kamakiri vulnerable stick gets fixed with that update... Only way to prevent this fix, is to unlock it first, then the OTA updates can't harm anything.
The unlock protects them. In this case the update is fine...
If you want to try the unlock, you need to follow the kamakiri OP.
You don't need a TV or a network connection for your stick.
You need the usb cable and some tinfoil.
No one knows if your stick is vulnerable or not.
You may check this in a terminal with the lsusb command, while shorted (see the unlock OP for details).
If you can keep the stick with the short in 'phone' mode (look in lsusb a few times instead of running the bootrom-step), you're lucky and the unlock may work.
Sus_i said:
The thing is really easy.
Older 4k sticks are vulnerable to the current kamakiri exploit, and newer sticks are not.
Amaz. fixed with 6.2.8.0 the bootrom feature used in kamakiri, so any kamakiri vulnerable stick gets fixed with that update... Only way to prevent this fix, is to unlock it first, then the OTA updates can't harm anything.
The unlock protects them. In this case the update is fine...
If you want to try the unlock, you need to follow the kamakiri OP.
You don't need a TV or a network connection for your stick.
You need the usb cable and some tinfoil.
No one knows if your stick is vulnerable or not.
You may check this in a terminal with the lsusb command, while shorted (see the unlock OP for details).
If you can keep the stick with the short in 'phone' mode (look in lsusb a few times instead of running the bootrom-step), you're lucky and the unlock may work.
Click to expand...
Click to collapse
I thought even if you were unlocked, once you were auto updated, the eFuse is blown and you can't downgrade?
FOr the old Fire Stick (that has never been upgraded so it should be fine) once I unlock the device and flash TWRP, what would I flash to prevent the OTA update from taking place during the setup of the device?
emkorial said:
I thought even if you were unlocked, once you were auto updated, the eFuse is blown and you can't downgrade?
FOr the old Fire Stick (that has never been upgraded so it should be fine) once I unlock the device and flash TWRP, what would I flash to prevent the OTA update from taking place during the setup of the device?
Click to expand...
Click to collapse
No, unlocked = safe.
There isn't a reason to mess with the initial update, as long as you've done the unlock successfully and TWRP is in place. Then you can downgrade anytime later to whatever OS version, if you like.
After you did the unlock, flash magisk, do the initial setup, enable adb, you can use adb shell commands to disable the OTA updates.
You don't need a TV or a network connection for your stick.
Click to expand...
Click to collapse
How do I interact with TWRP if it isn't plugged into the TV?? What do you see the TWRP screen on to navigate it??
See post two and three in the unlock thread...
Most people use always TWRP commandline via ADB.
Sus_i said:
See post two and three in the unlock thread...
Most people use always TWRP commandline via ADB.
Click to expand...
Click to collapse
So I am still very confused. If I have the Fire Stick only connected to my computer via USB cabl, there will be no Fire Stick display anywhere. So I will be unable to interact with TWRP. But step 1 of post 2 says I can use an OTG mouse to interact with TWRP. How can you use a mouse when the Stick isn't plugged in to a TV?? How do you even boot into TWRP when the stick isn't plugged in?
The second point says use a command line and use ADB, but I thought you need to have ADB permissions set on the device to allow that to work, and you can't get to those ADB permissions without activating the device, which will update it, which defeats the whole purpose
I really appreciate the help but I am totally confused. This is so very frustrating.
You can plug the hdmi into your TV, but that wont help you to interact, because you use TWRP commands via adb. Ofc you see the commands and the TWRP txt output in the terminal window...
If the unlock is done, you can unplug the usb and use OTG + mouse, if you like. Should work too, but you need an usb hub and a storage stick too, if you like to install a ROM or Magisk or whatever. TWRP commandline is easier, you can push files via adb and then just run a adb shell twrp install command...
If TWRP is up, adb is always enabled...
Only the fireOS wants a permission, if you want to use adb.
Sus_i said:
You can plug the hdmi into your TV, but that wont help you to interact, because you use TWRP commands via adb. Ofc you see the commands and the TWRP txt output in the terminal window...
If TWRP is up, adb is always enabled...
Only the fireOS wants a permission, if you want to use adb.
Click to expand...
Click to collapse
OK, that is helpful, so you are saying if I unlock the device, flash TWRP, and reboot into recovery, ADB will be enabled, there is no need to allow ADB Debugging and I can run those pm uninstall commands?
SO are you saying this is the process?
1 - Download linux iso and script to unlock
2 - boot linux iso
3 - plug Fire Stick into PC with supplied USB cable only. Do not plug the HDMI into anything
4 - run the script and do the tinfoil thing
5 - After the script is done type "./fastboot-step.sh" which will reboot the device into TWRP. I will have no idea if this is working because there is no display for me to look at, correct?
6 - I would I guess wait a few minutes for the device to reboot since I would have no display available I would have no idea when it is done rebooting, but at some point I would type "adb devices" and my device would appear in the list?
If that is all correct, then I know I can type "adb shell" at that point to get to a shell window where I can send adb commands. Could I then execute the pm disable commands? Or do I NEED to flash a new rooted ROM before I do that? I honestly don't care at all about being rooted, I just want to disable OTA
7 - And then after that, OTA would be disabled, I can unplug the Stick from my PC, plug it into my TV for the first time, and it would let me register and not auto update during the registration process and never bug me for updates again?
Also I have seen many different variants of the actual pm disable commands required to disable OTA, can you provide the actual correct ones?
Thanks again
emkorial said:
OK, that is helpful, so you are saying if I unlock the device, flash TWRP, and reboot into recovery, ADB will be enabled, there is no need to allow ADB Debugging and I can run those pm uninstall commands?
Click to expand...
Click to collapse
No, never said something like that
You cannot run pm uninstall commands in TWRP adb...
but you can run adb push/pull, adb shell, twrp install and all the other TWRP commands, in order to 'interact' with TWRP.
Maybe do some research, read a bit more about it. There are also some youtube guides out there.
emkorial said:
3 - plug Fire Stick into PC with supplied USB cable only. Do not plug the HDMI into anything
4 - run the script and do the tinfoil thing
Click to expand...
Click to collapse
It doesn't matter if hdmi is in or out.
But you need to follow the unlocks OP.
You need to short the stick infront any usb connection...
i.e. run the script, keep the short, then connect usb and so on.
Take your time, follow the OP
Maybe @Bertonumber1 answers some of your other questions, I've got no time to continue for now... sry.
Sus_i said:
No, never said something like that
Click to expand...
Click to collapse
Thats exactly what you said. You said "If TWRP is up, adb is always enabled..." So which is it, will I be able to run adb shell and then run the pm commands once it boots into twrp or not?
Sus_i said:
You cannot run pm uninstall commands in TWRP adb...
but you can run adb push/pull, adb shell, twrp install and all the other TWRP commands, in order to 'interact' with TWRP.
Click to expand...
Click to collapse
So you are saying I cannot run adb commands from TWRP, but you say I can run adb shell from twrp, which I can then run adb commands from. Which is it?
Sus_i said:
Maybe do some research, read a bit more about it. There are also some youtube guides out there.
Click to expand...
Click to collapse
I've read everything there is on the topic and it's very poorly documented from a step by step perspective. Can you answer the questions where you gave two opposite answers?
And the other questions no one has answers:
1 - Do I need to flash a rooted ROM before running the pm uninstall commands?
2 - Do I need Magisk installed? If so how do I install it?
I've been a remember of xda dev for years and years over many devices and I will never, ever understand how no one on this site ever seems capable of just giving simple step by step instructions and answering simple direct questions with simple direct answers.
At this point I am more confused than when I started so I feel it is still to risky to try this
Sus_i said:
It doesn't matter if hdmi is in or out.
But you need to follow the unlocks OP.
You need to short the stick infront any usb connection...
i.e. run the script, keep the short, then connect usb and so on.
Click to expand...
Click to collapse
I get that the HDMI does not need to be hooked up. Can you answer my quesiotn about how to know when the device is rebooted if I have no display? So I just keep checking adb devices until it shows up?
Sus_i said:
Take your time, follow the OP
Maybe @Bertonumber1 answers some of your other questions, I've got no time to continue for now... sry.
Click to expand...
Click to collapse
Can you just answer this, once I unlock, and reboot, if I wait and then my device shows up in adb devices, can I then run adb shell and run the pm uninstall commands?
emkorial said:
Thats exactly what you said. You said "If TWRP is up, adb is always enabled..." So which is it, will I be able to run adb shell and then run the pm commands once it boots into twrp or not?
So you are saying I cannot run adb commands from TWRP, but you say I can run adb shell from twrp, which I can then run adb commands from. Which is it?
Click to expand...
Click to collapse
lol. Its just like I said yesterday:
You can run adb push/pull, adb shell, twrp install and all the other commands, in order to 'interact' with TWRP.
Click to expand...
Click to collapse
You see, it isn't TWRP that searchs for updates
It is the fireOS that wants to keep the stick up-to-date.
If you want to disable this OTA update process inside the fireOS, you need to run the pm disable commands while fireOS is up and running.
Then I said yesterday:
It doesn't matter if hdmi is in or out.
But you need to short the stick infront any usb connection...
i.e. run the script, keep the short, then connect usb and so on.
Take your time, follow the OP
Click to expand...
Click to collapse
About four hours later, you ask the same question, in the same wrong order!??:
emkorial said:
I do not want to flash another firmware. I don't care about being rooted at all. I'm never going to install any silly add-on's or pointless extras. I have one goal and one goal only: Keep the OS version on the stick now and prevent it from ever updating.
Here is the process I have put together from scouring about 20 different threads and a half dozen conversations.
1 - Download the linux iso and the script to unlock the Fire Stick
2 - boot a PC with the linux iso
3 - plug Fire Stick into PC with supplied USB cable only. Do not plug the HDMI into anything
4 - Run the script and do the tinfoil thing
Click to expand...
Click to collapse
At this point It doesn't make sense, just to write it again and again, if you can't get the point.
emkorial said:
I've been a remember of xda dev for years and years over many devices and I will never, ever understand how no one on this site ever seems capable of just giving simple step by step instructions and answering simple direct questions with simple direct answers.
At this point I am more confused than when I started so I feel it is still to risky to try this
Click to expand...
Click to collapse
I'm sorry to hear that.
I've just realized that I can't help you at all, so I'm going to stop answering.
Wish you good luck. Have fun.
Sus_i said:
If you want to disable this OTA update process inside the fireOS, you need to run the pm disable commands while fireOS is up and running.
Click to expand...
Click to collapse
OK, that makes sense. But since Fire OS is up and running and sitting at the setup screen, USB Debugging has never been turned on. So how do you connect to the Fire Stick via ADB since you cant get to developer options?
UNLESS, does the pre rooted image you flash after unlocking have USB Debugging enabled by DEFAULT, so you DON'T have to turn it on via Settings? THAT would make this ALL make sense. Is that the case?
If so, then it would be
1 - Download iso and script
2 - boot iso and do foil trick and run script
3 - flash a rooted ROM (that will have USB Debugging enabled by default)
4 - boot Fire Stick and just sit at initial screen, don't go though setup
5 - Connect via ADB (which will work since USB Debugging is turned on by default)
6 - Run pm commands
7 - Continue with setup and OTA will be blocked
Is that correct?
Edit: I suppose I can just keep trying at each step until it works. Like this
Step 1 - Take the stick out of the box, plug it into the TV, get to the welcome screen, do not connect to wifi or set up the device (so no OTA updates will occur), connect the USB cable to my PC, and see if I can run the ADB Commands. If that doesn't work...
Step 2 - Unlock the device via the foil trick, plug the stick into the TV, get to the welcome screen, do not connect to wifi or set up the device (so no OTA updates will occur), connect the USB cable to my PC, and see if I can run the ADB Commands. If that doesn't work...
Step 3 - Flash a custom ROM, plug the stick into the TV, get to the welcome screen, do not connect to wifi or set up the device (so no OTA updates will occur), connect the USB cable to my PC, and see if I can run the ADB Commands. That should work as that mirrors the process in the guide.