Develop Bugs

[Q] Bricked Kindle Fire (first gen.) computer won't recognize

I have had my Kindle Fire for over a year and I have used various ROMs. Most recently, I was using the HellFire ROM and it crashed out on me. I decided to go back to stock for a while but noticed a new version of FFF (v1.4a) so decided to install that. Now, it boots to the FFF screen but nothing else. I cannot enter the boot menu. My computer does not recognize the device (no sound from the computer recognizing that it was plugged in) with either a regular or factory USB cable (I've used the factory cable before to unbrick the device).
I have read through the other posts regarding similar problems but all of those posts were resolved with either a driver problem or with a factory cable. None of the utilities or terminal commands are useful since the device is not recognized.
I have let the battery completely drain (letting it sit in a drawer while I take a break from the problem). It does recharge with the factory charger, but one thing of note is that the LED stays green during the charge. It never turns amber either on the charger or when it is connected to the computer.
Anyone have any ideas? I've been scratching my head lots over this. Many thanks for anyone willing to scratch along with me.

So have you tried Soupkit? How did you flash your bootloader?

Thepooch said:
So have you tried Soupkit? How did you flash your bootloader?
Click to expand...
Click to collapse
First of all, thanks for replying and trying to help. I have tried SoupKit and the Macintosh utilities but I keep getting the same response "Your device appears to be offline."
I originally rooted the kindle by manually entering adb commands. I installed the bootloader with KFU.

Is the bootloader splash static or does it blink on and off? Are you able to accces the boot menu to reset bootmode or enter recovery or select normal boot?

Thepooch said:
Is the bootloader splash static or does it blink on and off? Are you able to accces the boot menu to reset bootmode or enter recovery or select normal boot?
Click to expand...
Click to collapse
The bootloader splash is static. I am unable to access the boot menu at all.
I have been playing with the "short the point" install TWRP over USB but to no avail. I get "waiting for OMAP44xx device" and that's all.

Gnex: bricked or dead? Please help.

Hey guys, I just inherited a non-functioning gnex. The previous owner said the phone was working fine until it fell of a ledge whilst in a bag. There is no obvious physical damage to the phone chassis or screen.
When I try to power on the phone, it vibrates once but nothing further seems to happen and the screen stays black. Several minutes later though, it starts making some of the android system noises seemingly at a random. If I press either of the volume buttons, it makes the standard volume up or volume down ringer noise. But nothing else really happens other than a continuation of some of the system noises. Sometimes it seems to load a media file or a game once the phone has been powered on with the battery in. When connected to a windows machine, the device mounts and the contents of the phone are uncorrupted.
I've tried different combinations of the power buttons+volume rockers to get into recovery or fastboot, but so far no luck.
I've also tried the OMAP flash but can't get the computer to recognize the phone as a omap4460 for more than a couple of seconds. I've tried the Samsung drivers and the universal naked driver.
The only thing I haven't tried is ODIN (which I'm assuming won't work without being able to enter fastboot or recovery?), which might be last act of desperation before giving up. I'll update accordingly.
Any other suggestions would be greatly appreciated.

I think you have a damaged screen.
try to put phone in odin mode, pull battery out, reinsert it, press volume down with power button for 3 seconds, connect to pc, open odin, see if odin recognize your phone.

Yep it sound like everything is working except for screen. You can try to open it to disconnect and reconnect the screen: http://www.ifixit.com/Teardown/Samsung+Galaxy+Nexus+Teardown/7182/1 (not sure exactly how) if it doesn't work you can order a replacement screen (eBay or such) and do it yourself (expensive and not easy) or give it to a repair shop (expensive but easy).

Sounds like it's a damaged LCD, not cheap...
I'd buy it off you if its the vz nexus (For parts.)

Thanks guys, I suspect it's the screen also. I haven't gotten around to Odin yet but that will likely be my final attempt at trying to revive the phone.
If it is just screen damage though, would that prevent me from entering recovery mode?
I should've probably already mentioned that this the international version of the gnex (i9250m from Bell Canada), so no LTE.

horseycraze said:
Thanks guys, I suspect it's the screen also. I haven't gotten around to Odin yet but that will likely be my final attempt at trying to revive the phone.
If it is just screen damage though, would that prevent me from entering recovery mode?
I should've probably already mentioned that this the international version of the gnex (i9250m from Bell Canada), so no LTE.
Click to expand...
Click to collapse
I'd recommend fastboot. Same thing, less steps, though you will need adb...
(If its available for your model, if not odin would be your only choice. )
Odin has a few more steps...
Long story short you wouldn't know if the screen is dead sadly, with out a replacement, best of luck!

Any insight on how to get into ADB or fastboot? As stated in the OP, the power button combos don't work. Furthermore, I don't have a way of enabling debugging mode.
I still haven't tried Odin, I won't have access to a windows pc for a few more days. I'll update accordingly.

Getting into fastboot is very easy:
Turn off. Since you can't see anything pull battery and reinsert to make sure.
Press volume up, volume down and power at the same time for few seconds.
You feel a vibration like it does on every boot.
That's it, you are in fastboot mode.
To verify, plug into computer and type fastboot devices
If it writes something like this:
0149BD34ABCDABCD fastboot
then you are in fastboot mode.
If it doesn't work, check the drivers. Remember that you need to install the drivers once for every mode (in Windows). fastboot? drivers. MTP? drivers. ADB? drivers. ADB in custom recovery? drivers. Download mode? drivers. OMAPFlash? drivers again. And different modes have different drivers too.

[Q] Using Nexus Root Toolkit without USB Debugging enabled

I have a 2013 Nexus 7 wifi tablet, bootloader locked, with USB debugging disabled. It decided mid-activity that all it would like to do in life is display the "Google" image on the boot up screen.
I can access the bootloader so I tried doing the standard wipe in recovery mode but that did not work.
Investigated Wugfresh's Nexus Root Toolkit. Drivers (Windows 7) are installed but under Step 4 of the Full Driver Configuration guide it is unable to find the device as an ADB device, even though the device does show up on my Device Manager (but only as bootloader interface, not ADB). Tried to use the unlock feature anyway but on the tablet it just gets stuck on the "unlock bootloader" screen after trying to run the unlock tool (choosing "yes" by pressing the up volume button to scroll to the yes option, followed by the power button to select it).
My questions based on this are simple:
1) Can I unlock this device without having USB debugging enabled? If so, how?
2) Can I restore to factory stock settings without having USB debugging enabled (and not using recovery mode on the device itself, as that does not work)? If so, how?
All of the tools I have seen thus far require that USB debugging be enabled on the device. Since I can't actually boot up the device, there is no way to make this happen. I don't really care about any of the data on the device, I just want it to function again to avoid buying a new one.

Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.

nhizzat said:
Stop using a toolkit. Your device will never be recognized by adb when booted into the bootloader.
Unlocking the bootloader is simple if you have the Windows drivers set up correctly. Open command prompt with admin privileges, type 'fastboot oem unlock' and done. This is why I hate toolkits.
Click to expand...
Click to collapse
I believe this also requires that USB Debugging be enabled. I would paste links but the forum prevents me from doing so since I just signed up.
If I am incorrect in thinking that USB Debugging must be enabled for this to work, then please let me know. All I really need is clear instructions on how to hard reset the device without USB debugging enabled. Unlocking just seems to be a prerequisite for that in most of the tutorials I have found so far.

You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.

skrypj said:
You can flash the device back to stock with wugs without adb. There should be an option you pick under the factory restore button that says "soft bricked" which tells wugs that it needs to go straight fastboot mode instead of trying to restart the tablet with adb.
Click to expand...
Click to collapse
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).

Bugnerd said:
Thanks for your reply. I have tried this option without the ADB (but with my computer recognizing the device). Since it did not work I expect the device is well and truly screwed (the recovery mode factory reset also does not work on the tablet itself).
Click to expand...
Click to collapse
Couple of things:
1. You may also have a driver issue, I was playing with this the other day on both my Nexus 5 and Nexus 7. My nexus 5 worked fine, but later that day when i tried my nexus 7 I had troubles with my PC recognizing the N7 in fastboot mode. It would be fine in ADB and would reboot, but then the computer would freak out when it saw the fastboot device. Sometimes it would kinda work, sometimes the N7 would freeze on the bootloader screen or fail to flash during the process. It even locked my PC at one point. I completely uninstalled(per the Step 1 instructions in Wug's) all Android associated drivers(Samsung, LG, Asus, whatever. Kill them all) on the PC and reinstalled and it solved the issues. It sounds like maybe your PC is failing to flash properly like mine was.
2. Not sure if you tried this yet but; go to Options Menu>Flash Stock Tab>Check "Enable 'Force Flash Mode' . . . " Then try to flash stock + unroot again with the soft-bricked option selected. This basically makes Wug's ignore the check process at the beginning of the flash. I had to do this for both my N5 and N7.
Keep in mind, you will lose EVERYTHING on your N7 if you unroot and flash, including your internal storage.

Yeah, it does not seem to want to do the unroot + flash even with the override of checks. It seems unlocking is really a prerequisite for that tool (according to the text that appears as it proceeds), and unlocking appears to require the USB debugging. If it really can be unlocked without that, then it is not cooperating and just getting stuck on the unlocking screen. I expect it is now a very expensive paperweight.
All of this nonsense just over a year since I bought it, of course.

Try it with another computer, another USB cable...

I'm in the same boat, can't get it to unlock so it's essentially dead now
I've tried original and a G3 usb cord and nothing, front and rear USB ports, just will not unlock, almost to the point of sending it on and paying to get it fixed if possible , will try another computer first

Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:

Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?

Az-one786 said:
Can you boot manually into fasboot mode and do flashing full stock firmware for ur device..
Bcoz I thinks you don't need usb debugging when on fastboot mode..
if you want to use toolkit, you must setup all driver for ur device first using the toolkit.. but you must do it when ur device is full "working", not when It's just stuck on google image... that's ur main problem now ...
you should try install the driver again on new "fresh" pc ....
Good luck bro... :fingers-crossed:
Click to expand...
Click to collapse
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.

skrypj said:
Did you try to manually unlock it? Boot to the boot loader screen(down volume+power) and the fastboot unlock it using the cmd in windows?
Click to expand...
Click to collapse
I looked into this a week or so ago and I think I determined that it would also require the USB debugging to be on (at least from the tutorials). Do you have any recommendations of tutorials on this process? Screwing around with this stuff is not really my bag.

Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
I can try the drivers again on another PC, but I have a feeling that won't fix anything.
Click to expand...
Click to collapse
Ok.., Your have no choice by now, you'll need to find a working driver for your PC to get recognize your tablet when on fastboot mode..
I've got this issues before when I want to update my tab using toolkit...
My PC can recognized my tab as adb devices, but when it's reboot to check fastboot status it fail to detect my device is on fastboot mode..
But maybe I'm so lucky that day, Moboginie notification has pop-up and it's has searching and found the driver and fix it itself ...
Then i try again and this time it's has no problem at all till now... I still can access my storage using Moboginie but until now window explorer still fail to recognized my N7...
It's so weird isn't it ...

Try Moborobo

Bugnerd said:
I can boot into fastboot mode but when I then switch to recovery mode manually to reset it does not go to the recovery mode screen (it did at first, but now just gets stuck on the sick robot screen, then on the "Google" loading screen).
Click to expand...
Click to collapse
After the recovery screen with "sick" Andy, did it automatically begin to reboot? If not, you know that it's very tricky with the power+vol up button (sometimes I think it's power+both volume buttons that works) to access that screen in recovery (the one past sick Andy). Sometimes I've tried five or six times. I have twrp so I can't check it out right now.
As far as adb/fastboot drivers set up to run any commands, I thought they were required. I'm not certain about USB debugging. It seems you've tried with your device in fastboot and running Cmd (fastboot oem unlock) from your fast boot directory. Do you get a device code when you enter [fastboot devices] while in that directory? If not, your N7 will not accept fastboot commands.
Sent from my Nexus 7 using Tapatalk

[Q] Phone stuck in bootloop, can't flashboot anything. Suggestions?

Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"

SyrStorm said:
Ahh my phone has had quite the past week on this CM12 Android 5.0 ROM...
I was just listening to music and checking social media on my phone when bam, it turns off.
I held the power button and it didn't turn on the first few times.
Then finally, it boots, but it won't get past the splash screen.
It's stuck in a bootloop and I can't get into the recovery. I can't factory reset it either.
I tried to go to fastboot and flash the recovery again, but my computer doesn't recognize my phone.
I have adb, fastboot, and all of the correct drivers installed and it won't do anything.
I tried flashing with "fastboot flash recovery twrp.img" but it just said "<waiting for device>" even though my phone was connected and in fastboot mode.
I don't know what to do. I can't boot it, I can't get into recovery, I can't factory reset it, and I can't fastboot anything.
What should I do? Please I am open to ANY suggestions at this point. I can't deal with this constantly not having a phone crap.
Thanks, it'll be much appreciated.
Extra Info:
Device manager lists my phone as this: "Unknown USB Device (Device Failed Enumeration)"
Every time I go into fastboot, my computer displays this message: "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it"
Click to expand...
Click to collapse
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.

dottat said:
Make sure you aren't connected via usb to your computer when you attempt to force a reboot. It should be vol up and power until it reboots and then switch to vol down to enter hboot.
Click to expand...
Click to collapse
I can get into hboot and all that just fine. The phone won't boot, and I can't get into recovery is my problem. Oh and the fact that the computer doesn't recognize my phone in fastboot

Update: I just whipped out a really old computer running Windows XP and I installed the platform-tools and HTC One drivers on it. I hooked the phone up to the computer, and the drivers worked. I flashed TWRP and it flashed successfully according to fastboot, but it won't go into recovery still. What should I do now? I know I can RUU somehow (I'm not really sure how though), but I want to try and avoid that, if possible. Any suggestions? Thanks people!
EDIT: NVM it actually booted! What a success! This stuff is crazy!

Soft Bricked LG G Pad II 8.0 (LGV498) Wifi only

So I soft bricked my LG G Pad II 8.0 Tablet... Not the worst thing in the world, except that 1.) There seems to be not much at all on the internet as far as stock ROMs or how to guides on fixing my particular tablet. 2.) My computer does not seem to be recognizing my tablet when trying to use ADB, despite having installed all the drivers etc.
My device is stuck in a BootLoop, it will allow me to try a Hard Reset, which is unsuccessful. But it will not go into recovery mode OR Download mode no matter what sequence of the buttons I push and i've scoured the internet trying different button sequences.
My Tablet will charge when plugged into USB, my comp will also go *ding* when i press the power button with the tablet plugged in as if it is reconginzing it and everything. Also Device Manager seems to have it listed with no Exclamation Point or any sign of trouble... Just when I go to use ADB and i search for the device it says *error no device found*
The Tablet just sits there with the LG Logo screen pissing me off more and more as my attempts fail.
I will say USB debugging was not enabled beforehand *cough cough* my mistake
Will reflashing it work by using the MicroSD card method? If that is the only way i will have to just buy one i guess. It did not come with it and it is a Wifi only tablet, no carrier attached.
And if I try the MicroSD method, will it still work without being able to put the tablet into recovery mode?
I believe I have the correct .IMG file for my stock ROM... I just can't seem to get anywhere with flashing it to the device at this point.......
Please Help!

bbrumley said:
So I soft bricked my LG G Pad II 8.0 Tablet... Not the worst thing in the world, except that 1.) There seems to be not much at all on the internet as far as stock ROMs or how to guides on fixing my particular tablet. 2.) My computer does not seem to be recognizing my tablet when trying to use ADB, despite having installed all the drivers etc.
My device is stuck in a BootLoop, it will allow me to try a Hard Reset, which is unsuccessful. But it will not go into recovery mode OR Download mode no matter what sequence of the buttons I push and i've scoured the internet trying different button sequences.
My Tablet will charge when plugged into USB, my comp will also go *ding* when i press the power button with the tablet plugged in as if it is reconginzing it and everything. Also Device Manager seems to have it listed with no Exclamation Point or any sign of trouble... Just when I go to use ADB and i search for the device it says *error no device found*
The Tablet just sits there with the LG Logo screen pissing me off more and more as my attempts fail.
I will say USB debugging was not enabled beforehand *cough cough* my mistake
Will reflashing it work by using the MicroSD card method? If that is the only way i will have to just buy one i guess. It did not come with it and it is a Wifi only tablet, no carrier attached.
And if I try the MicroSD method, will it still work without being able to put the tablet into recovery mode?
I believe I have the correct .IMG file for my stock ROM... I just can't seem to get anywhere with flashing it to the device at this point.......
Please Help!
Click to expand...
Click to collapse
*UPDATE* So I happened to stumble upon a random piece of information that proved REALLY useful in this situation. Someone put in a forum that Lollipop ONLY is detected when plugged into USB 2.0 ports NOT USB 3.0 ports like I was using. So I did this and was able to make my tablet enter into Download Mode FINALLY.... Anyone have any good methods on how to Flash Stock ROM using ADB and a connected soft bricked tablet?
I have already tried a couple methods that I have found and they were unsuccessful. One was using ODIN software and the other was using LG Flash Tool, unfortunately neither worked....