A while back I tried flashing a rom using TWRP and after it restarted it had a bootloop. I have tried everything I can think of to get this back into recovery mode to flash a good rom. I have tried two computers, both running Windows 10 x64, and neither recognize the Kindle. When I do either an adb or fastboot command it just says "waiting for device". The kindle does not even show up under 'device manager'. It hasn't been recognized for a long time even before I screwed up the Kindle. I have tried several utilities, but none will work due to my device not being recognized. Any help to get this thing back online would be greatly appreciated!!
EDIT: Also, I am able to get into fastboot mode with a fastboot cable I just received in the mail. Doesn't help the pc recognize it thought.
Anyone?
Bump
Connect your kindle to the pc, and let it start bootlooping.
Then, hold the power button for at least 40 seconds. the kindle will turn off early on; disregard this.
now, leaving it attached to PC, turn on the kindle again.
It should now be recognised by PC
After this you can use normal methods to restore it back such as SRT
Sorry for replying 5 years too late, but better later than never I guess :/
Related
Noob here,
My viewsonic Gtablet has been softbricked and I've been attempting to get it into a functional status for the last couple of weeks.
I have tried -
1) installing the factory reset roms onto the microsd card and booting gtablet in recover mode. This lead to an indefinite "booting recovery kernal image".
2) installing clockword mod in hopes of fixing the bootloader. This led to the same result
I'm now attempting to nvflash the device. I have all folders installed and the entire setup is ready to commence HOWEVER; when I boot the gtablet in APX mode and connect it to my windows pc, there is no prompt indicating a new device. After checking device manager I cannot find the device there either. I have the drivers in a folder and ready to install, but I don't know how when I'm given no indication that the computer even recognizes the gtablets existence.
Any ideas?
Which windows os? 98?
my apologies, I forgot to mention.
I have tried to nvflash on both windows 7 and ubuntu linux but neither OS picked up or detected the presence of the gtablet at all
Have you checked if your usb chord is working? I know, sounds silly. But this happened to me a number of years ago. Really thought it was the computer or my camera. Until I tried another usb chord and voila!
Oh God, wouldn't you know that fixed it instantly. Here I tried everything in the world and it was the USB cable all along. Thanks a bundle man!
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
JNiels1980 said:
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
Click to expand...
Click to collapse
When you press up on the USB icon and it freezes that it normal.. This is fastboot mode.
You now must access it over a PC after installing the naked drivers.. If it is not showing on your PC then either try a different PC or your cable is faulty.
Thanks for the quick reply.
I tried once more to enter fastboot. Same result.
But when I disconnected my usb cable to connect it to an other computer, suddenly I got this message on my tablet:
"Starting Fastboot USB download protocol"
This message didn't show up before.
I plugged the tablet back to my pc, but still no device detection in device manager, even when refreshing (So I can't install naked drivers, as it is not recognized).
My computer is a Windows 8.1 system.
I restarted my tablet again, (after disconnecting it from my pc) and followed the procedure to enter Fastboot again.
I waited for the message "Starting Fastboot ..." and then I connected the cable to my other pc (Windows 7 system)
Same result as on the Windows 8.1 machine, not recognized
You say it could be that my cable is broken. Maybe, but it's a strange coincidence that this happened when switching from ICS to JB.
I know JB for the tf201 is been out a long time, and I updated since I could. So over time, maybe my cable could be broken now. But I'm sure I had this problem (not recognizing) since then, because right after updating I wanted to do some things with ADB and so I found out I had this problem.
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
aaronthew said:
Hi
New on here so sorry if I don't know to much
I have a Nexus 7 2012. Install Timurs kernel and Rom on my tablet and installed it in my car, and it worked great for months, then the other day it shut down. When I rebooted it, it gets stuck on the Google logo.
If I try boot into recovery it once again gets stuck at the Google Boot logo
I can get it into Fastboot mode but it wont connect to the PC. I am sure the Drivers are ok as I have another nexus 7 and i have today flashed a new rom using the WUGs Nexus Toolkit
Any Ideas anyone as at the moment I would class this as bricked as it wont boot, wont go into recovery and wont connect to the PC
Any advice would be hugely appreciated
Cheers
Aaron
Click to expand...
Click to collapse
You can't go into your recovery?
Install ADB and try to connect your Nexus to your PC and enter "adb devices". See if your tablet is recognized like that.
How to setup ADB
Do not use toolkits with Nexus devices.
cheers for the advice but nope no luck still wont connect
aaronthew said:
cheers for the advice but nope no luck still wont connect
Click to expand...
Click to collapse
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
es0tericcha0s said:
When you plug your tab in, does it even attempt to load drivers and just fails or does it not even recognize that you plugged anything in? Make sure by checking the Device Manager as you plug / unplug. If it just doesn't load correctly, then attempt to load the Naked Universal Drivers manually and then you should be able to get things back on track at least with fastboot flashing the stock img files back to it. If the Device Manager doesn't change or show any differences when you plug in the tab, then that's a bad thing... If you can boot to the bootloader still, most likely it can be fixed. If it only boots to a black screen and when plugged in shows the APX driver, you're boned. That problem IS fixable, but only if you would have saved your blob.bin and wheelie blobs before it went down, which I am certain you didn't do as it is not a common procedure.
Click to expand...
Click to collapse
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
aaronthew said:
Hi
I can get to the bootloader screen and it says Fastboot mode on the tablet.
When i plug the tablet into the Pc, device manger does not refresh and the computer makes no acknowledgement at all when I plug the device in
Click to expand...
Click to collapse
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
es0tericcha0s said:
Hmm. Very odd. Typically if the bootloader is still there, the rest is easily solvable. What happens when you choose the recovery option from bootloader? Unfortunately you have to test some more things to eliminate the easy stuff. These include trying different cords, ports, and computers. If possible, see if you can try a Linux PC as well or at least a Live CD. If TWRP still loads at all and supports USB OTG, you might be able to load something from it as a long shot.
Click to expand...
Click to collapse
if i choose recover, to gets stuck on the google screen
Tried different cables, Pc and PC ports no luck
I could try get linux on vm when i get home? never used it thou
Sucks man. Such a random thing and not typical of most Nexus issues. This is the only other option I can think of then: http://mobiletechvideos.mybigcommerce.com/asus-nexus-7-2012/ - Brick service. These guys are legit. They have a great reputation and I've personally used their services twice (different devices) and one was fixed while the other was a lost cause, but Josh was nice enough to refund some of the money since it didn't work. I'm guessing they would need to do what's called a JTAG service where they hook up (usually solder) a special cable to a specific port on the board and it kind of circumvents the other issues and reloads the OS back on.
Thanks for all you hep mate will prob give them a try
No problem. Good luck!
Hi everyone. I've tried searching everywhere, but I can't find anyone with this same particular issue. I recorded what's going on so you can better understand what I'm trying to explain. youtube(dot)com/v/0Rp9XWEfVwE (sorry, I don't have the required number of posts for a link)
My Nexus 5 connects to then immediately disconnects. This happens with any computer I try it with. It will then not recognize or be recognized by any other computer, or charger until you restart the phone.
I can't connect the phone to the computer to unroot it for me to apply the OTA update.
My laptop is able to recognize my Nexus 7. It is also still able to recognizes as a Nexus 5 for the second that it connects.
Any ideas as to what's going on, and how I can solve this? I have no idea where else to pose the question.
I've done several factory resets, both in the menu and in fastboot. I've also erased the cache from fastboot.
I was able to connect to any computer just fine before I updated to 5.0. That's when this issue started.
I've tried several different computers and OS's, they all have the same result. It's not the drivers. Regardless of if there are any drivers on the PC, it will still show up for a second, then immediately disconnect and the phone doesn't respond to any further connections/charging until restart.
As the title says, I have an Ariel Fire HD 7 stuck at the Amazon logo. At this point, I suspect I have no bootable OS because after using powerpoint45's Linux Unbricking ISO successfully, I downgraded to 4.5.3 to root, then tried to upgrade to Lollipop, probably flashing an incompatible bootloader. It is not detected by ADB, ./handshake.py in the Unbrick ISO fails after about half an hour of waiting, and Windows 7 Device Manager detects it as an "MTP USB Device" with error 10 "The device cannot start". If this is recoverable, please post a thread URL in this thread, and I will try the method detailed in it, then post the result here. Thanks in advance!
Not sure if this would help, but you can get the MTP USB Device to change to Fire ADB by watching device manager. In Win10, I have Device manager open, wait for the MTP to opo into it and quickly right click on it and clicking update driver.
When mine did that it would pop up and dissappear pretty quickly. Does yours do that? If so after clicking on update driver, click on browse for driver. Should bring up a list of devices it could be. Click on all devices and go down to Amazon and use those adb driver. A pop up asked if I really wanted to do that, and I clicked yes when I heard the device pop into device manager again. It was always there since you were working on it, but really it wasn't. I had to wait for the sound it makes when popping up.
As for ./handshake.py what I did was take the cover off the kindle and unplug the battery. Plugged the cable into the usb port, used the handshake command and after it said waiting, I plugged the battery back in. may have to hold the power button for a while if it's in a bootloop to turn it off totally.