So long story short, I followed the initial tutorial to root the Fire HD 8 2018 (https://forum.xda-developers.com/hd8-hd10/general/tut-root-hd82018-via-magisk-t3906554/) after getting the mtk-su temp root. I made sure all the codes were correct before powering off my tablet, and everything seemed to be going smoothly until I ran the code on LInux to go into BootRom mode.
That was when the code was stuck on "Waiting for bootrom...". I connected my device to my PC, but the code didn't change at all. The USB also wasn't being recognized by the computer and was randomly being connected and disconnected. I'm not really sure what to do next as nobody else on the thread seemed to have my problem. I am a newbie, so please bare with me .
If anyone does have the solution, I'd be extremely grateful. Thanks in advance!
Is your tablet bricked as required by the guide? Or does it boot/show Amazon or fire logo?
If it is properly bricked, you could try a different USB port or cable.
If all else fails, your best bet is to follow the instructions in the original unlock/debrick thread:
https://forum.xda-developers.com/hd...fire-hd-8-2018-downgrade-unlock-root-t3894256
Can you use the transferrable micro USB Cable?
I had the same issue with mine. I was getting the device showing in linux as a "mediatek" phone. When I plugged it, it would randomly connect and disconnect. finally it got recognized, and I ran into the BOOT0 broken issue mentioned elsewhere. I commented the != in the main.py first method to ==, and it flashed twrp correctly.
To avoid stuck in Waiting for bootrom...
Make sure your Fire tablet is shut down
Disable or uninstall the ModemManager
Use the transferrable micro USB cable
To short CLK to GND point using conductive objects. Do Not use the diode, capacitor or resistor to short the test point
USB access is enabled in VirtualBox settings
Related
I've attempted to install drivers, but it still isn't recognized by fastboot, kindle fire utility, and everything else. I reconnect it to my computer and it just comes up as "Unknown usb device"... It came to be this way because while I was installing TWRP with Kindle fire utility it froze and it's been like that for at least 30 minutes now. I've tried restarting it, resetting it, and nothing is working. Please help!
Look here http://forum.xda-developers.com/showthread.php?t=1417966
You maybe need to change boot mode to normal
Sent from my Kindle Fire using Tapatalk
But how do I manage to change the bootmode when my computer won't recognize that my kindle is connected?
Sent from my MB525 using XDA App
Follow the instructions posted by me, there and then your device should be recognized....
Sent from my Kindle Fire using Tapatalk
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Had the same issue. This solution worked for me
guillotinedream said:
http://forum.xda-developers.com/showpost.php?p=20421225&postcount=222
Had the same issue. This solution worked for me
Click to expand...
Click to collapse
I love you. No homo, of course. Thanks a ton! This worked great for me. I thought that my kindle was screwed Thanks so much for that!
lol You're welcome. Glad it worked for you
Computer doesn't even recognize that a device is connected...
Okay, I'm not having the same issue, but I'm pretty sure I've completely, irevicalbly, bricked my kindle.
I know that I'm not in Fastboot mode, I've experienced that issue and solved it with the KFU.
Here's what I did:
I used the KFU to root my kindle. That worked fine. I was able to load all the Google apps (which was my initial goal). Then, I got greedy and decided that ICS was my next step - oops.
I followed the instructions on the following site:
androidauthority.com/kindle-fire-miui-4-ics-55853/
Note: I know, I'm an idiot - I should have paid attention to comments! UGH!
After I did this, I now only get the firefirefire logo and that is it. I can't load/reload TWRP and I can't change my bootmode to normal or recovery. The thing is, no matter which computer I plug the device into, the computer won't recognize the device. I get a message saying something "malfunctioned" when I plug it in. I've tried 3 different Windows machines (I've installed/reinstalled drivers I don't know how many times!) and I even tried loading Linux on a spare laptop and that didn't work either.
So, I tried the next thing I could think of. I followed the instructions on the following site:
ramble.karrth.com - Section "Troubleshooting TWRP
which involved removing the back cover, shorting a circuit (to force usbboot) and plugging my Kindle in. This didn't work for me either.
At this point, I'm willing to try anything. I'm not quite sure how to fix this issue. I think my next step is to either order a factory cable or make my own and try that, but if my bootloader is broke (truely broke) will that even work?
Please, if I should post this in another forum/place, just let me know. Any help appreciated!
I should also not that nothing comes up in my device manager. It does come up as a unrecognized USB bit goes away after telling me there was a malfunction (it tries to recognize it twice).
Please don't post the same question in multiple threads... especially ones that have been dead for 4 months. I've replied to the same question as a followup to your other post.
Ok so long story short, i have a nexus 7 2012 which a rooted and installed cyanogen mod.
I was using it as a car install and works perfect, i'm using an otg cable to mount usb sticks, triggering soft shutdown and powering the nexus etc. So usb seems to be working fine.
Basically i removed the tablet it to modify the bootloader to turn on automatically with ac power applied, if the battery runs out i have to manually power on with button, but now i'm running into a problem.
Ever since taking the tablet out and trying to connect over usb, none of my computers detect the tablet.
I've tried different operating systems, drivers, cables etc etc.
Also changed from mtp to ptp in storage and also turned on usb debugging mode. If i connect an otg cable the nexus see's the otg and i can mount usb's etc.
So i thought i might try recover the nexus back to factory, maybe there was an issue with the rom corrupted etc, I've downloaded the original 4.2.2 firmware which is currently installed.
Booted into recovery and tried re-installing the 4.2.2 zip, it keeps aborting. A guy in work tried to use sideloader and connect via adb. no luck.
I'm not very familiar with the android platform so i've no other ideas what to do and other idea's how to recover now.
The guy i work with mentioned using a usb jig, would that be the way to go or can anyone else suggest some else that might help.
Thanks
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Does adb see the device
jadesse said:
Before you updated when was the last time you connected your N7 to your computer?
When you connect your N7 to your computer does it act like it is charging? Have you tried more than one computer? I had a similar problem with mine last year & sent it in 3 times. Asus replaced both the USB port board & the main board on different occassions. I suspect your mainboard might be faulty.
Click to expand...
Click to collapse
I last connected the nexus to the laptop a few monts back to load some music onto it, didn't have a problem. It's only been connected to a computer maybe 3 times. once to root/rom it then another few times to load music etc.
I can't see why the usb board maybe faulty as i can read data from a usb key when the otg cable is connected.
It's a strange one. You could be right, i might try pick up a broken nexus and swap some parts. Usb board etc.
crusrod said:
Does adb see the device
Click to expand...
Click to collapse
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
foster182 said:
Yes adb is shown in device manager, but it's not recognizing the nexus, comes up with an error 10 , cannot start. etc etc
Click to expand...
Click to collapse
I am having this same problem on my (unrooted) HTC One after attempting to "convert" it from an AT&T to a Google Play Edition device with the procedure described here.
As part of the procedure, I attempted to flash the stock Google Play Edition ROM using fastboot commands, but I got an error message. The instructions say to just try the flash again, but the phone no longer connects properly via USB (error 10) while in bootloader mode. While in bootloader mode, the phone indicates there is some sort of problem (a line showing the OS version is highlighted in red), and attempting to enter recovery mode does nothing but display a phone with a big red X in it. The phone seems to operate fine and responds to ADB commands when the phone is fully booted, albeit with the old OS (not Google Play Edition) still in place.
Any Android device could theoretically get in this state. We're sort of "paralyzed", because everything we want to do to regain control of the bootloader and fix the situation seems to require issuing fastboot commands from a computer connected to the phone while it's in bootloader mode. Yet entering recovery mode or getting a computer to connect to it via USB no longer seems possible.
I wonder if there's another way to issue fastboot commands without relying on the USB connection to a computer?
Since there still isn't a Razer Forge TV forum I'm posing this here... I went rogue and edited the build.prop file on my Forge TV after rooting. After powering it off it has been stuck in a bootloop for the past week. Thanks for @patt2k and some other folks on the Razer forums I am able to get into recovery. However, once in recovery I am limited in what I can do. I don't yet have the system images from Razer, but even if I did I'm not sure I could apply them via adb because my PC doesn't recognize the device at all. It's not the situation where the device shows as an unknown device because the drivers are missing, it simply isn't recognized at all. I have it plugged up via male to male USB cord, but the PC just doesn't seem to take any notice of it. If I could get into adb I think I could get it working again. Does anyone have any clues on what to do in a situation like this?
So I was running OmniRom on OP 5 and everything was running really smoothly. Yesterday evening, while browsing the web, it hung up on me so I decided to reboot.
It got stuck on the boot screen and never progressed.
So I decided I'd try to sideload the latest weekly version but here's the big issue.
I cannot get my OP5 to show up on either my Mac or my wife's Windows machine using adb which is really bad.
Does anybody have any possible tips? I really don't know where to go from here because sideloading and using fastboot is my typical failback when something goes awry.
Are you in TWRP?
If so, did you enable adb sideload?
What about 9008 mode?
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
If your PC can recognize your OP5 in this mode, it will be okay.
Thanks for the help!
I figured out the issue. My usb port on my OP5 is failing so in order to get it to connect I have to hold it tightly the entire time or it will disconnect, fun stuff.
On a side note, (and I posted this is the OmniRom thread), but I'm getting "Updater process ended with Error: 7" when trying to sideload from here
https://dl.omnirom.org/oneplus5/
Do you think it's because I don't have the . md5sum file in place?
sippinhenn said:
Thanks for the help!
I figured out the issue. My usb port on my OP5 is failing so in order to get it to connect I have to hold it tightly the entire time or it will disconnect, fun stuff.
Click to expand...
Click to collapse
You should try to clean up your usb port. Take something (i used opened paper clip) and CAREFULLY dig everything unwanted out of the usb port. Try NOT to short out the pins of the usb port and it's recommended to shut down your phone.
I've cleaned once my usb port on op5 and overall there came out alot fuzz. Also it's recommended to take some bright light and look when you see the bottom of port.
Hi.
I tried to unlock my fire hd 10 2017 using virtualbox ubuntu.
I was following the steps and I found that my device's firmware version was 5.6.4.0
I read downgrade was necessary but I didn't know how.
Luckily, I could find a way and downgraded firmware 5.6.4.0 to 5.6.2.0 using sideload.
It bricked as planned so I tried unbrick it using bootrom-step.sh
But it didn't work.
I think repeatedly connected and disconnected usb port is the problem.
I tried installing usb driver for amazon device and mediatek usb vcom driver.
But it didn't work, too.
What could be a problem?
Help me please. Thank you.
pdh4118 said:
Hi.
I tried to unlock my fire hd 10 2017 using virtualbox ubuntu.
I was following the steps and I found that my device's firmware version was 5.6.4.0
I read downgrade was necessary but I didn't know how.
Luckily, I could find a way and downgraded firmware 5.6.4.0 to 5.6.2.0 using sideload.
It bricked as planned so I tried unbrick it using bootrom-step.sh
But it didn't work.
I think repeatedly connected and disconnected usb port is the problem.
I tried installing usb driver for amazon device and mediatek usb vcom driver.
But it didn't work, too.
What could be a problem?
Help me please. Thank you.
Click to expand...
Click to collapse
Oh my god :facepalm:
The script downgrades automatically.... Now there's no solution until you open the device, short the bootrom point and execute the bootrom-step.sh..
Rortiz2 said:
Oh my god :facepalm:
The script downgrades automatically.... Now there's no solution until you open the device, short the bootrom point and execute the bootrom-step.sh..
Click to expand...
Click to collapse
Actually I opened the device and disconnected the battery and display cables.
But I don't have star-shaped screwdriver. And I don't know where the bootrom point is.
Can I short the bootrom point without screwdriver?
Thank you.