Develop Bugs

HELP! bricked? cant enter fastboot

hey!
a little panicky here, i just unlocked and rooted my one x today, installed the latest cwm and tried several different roms with their respective boot.img files.
after a while i thought i'd go back to my nandroid of the stock but it wouldnt start. in cwm i copied the boot.img from my nandroid to my pc and rebooted, trying to get into fastboot mode but my phone wouldnt let me. whenever i reboot by pressing power for 10 seconds i just get back to the white thc quietly brilliant screen, no matter which buttons i press. so i CANNOT enter fastboot mode. HELP please!

Plug your USB cord in & type adb reboot bootloader.
Sent from my HTC One X using xda premium

thanks for the quick reply, im trying both windows and ubuntu at the mo, in windows it says
error: device not found
i do hear the sound of a device being attached to the computer when i plug it in tho.

ok. 'progress'.
unfortunately in the wrong direction. i rebooted again to try to get into fastboot mode and now its dead. doesnt respond to anything, no charging light, no screen. i think im pretty much f**cked

nestnest said:
ok. 'progress'.
unfortunately in the wrong direction. i rebooted again to try to get into fastboot mode and now its dead. doesnt respond to anything, no charging light, no screen. i think im pretty much f**cked
Click to expand...
Click to collapse
ok first things first...
1) Plug your phone into a charger.... NOT a PC USB cable, but a genuine wall charger and leave for 30 minutes to make sure there's plenty of charge.The wall chargers deliver more current to the battery than a PC USB port. Don't be tempted to keep turning the phone on and off, as this could kill any little power left in your battery (just in case that's an issue).
2) Make a cup of coffee and try and calm down <---- important
3) When you power of the device make 100% sure you're holding the volume down button BEFORE (and during) the power on process... and keep holding it down. From your description, it sounds like you're not doing this properly. If this is successful, you'll get to the HBOOT menu. From there, you 'should' be able to get into the Fastboot menu - where you can then start issuing ADB / Fastboot commands.
PLEASE do all three, and don't skip any steps.

thank you! wish i had known that before my quasi heart attack. i actually did exactly that after the phone went completely dead, it worked and im back on my stock rom now.
apparently you cant enter fastboot below a certain margin on your battery?
if i hadnt found this out just half an hour or so ago i would be eternally grateful, now you will have to settle for pretty grateful.
no seriously thank you!!

TheBrilliantMistake said:
ok first things first...
1) Plug your phone into a charger.... NOT a PC USB cable, but a genuine wall charger and leave for 30 minutes to make sure there's plenty of charge.The wall chargers deliver more current to the battery than a PC USB port. Don't be tempted to keep turning the phone on and off, as this could kill any little power left in your battery (just in case that's an issue).
2) Make a cup of coffee and try and calm down <---- important
3) When you power of the device make 100% sure you're holding the volume down button BEFORE (and during) the power on process... and keep holding it down. From your description, it sounds like you're not doing this properly. If this is successful, you'll get to the HBOOT menu. From there, you 'should' be able to get into the Fastboot menu - where you can then start issuing ADB / Fastboot commands.
PLEASE do all three, and don't skip any steps.
Click to expand...
Click to collapse
Can't stress enough the importance of second step.
Sent from my HTC One X using xda premium

yeah i guess i shouldnt be let alone in the room with devices beyond 500 euros lol

nestnest said:
yeah i guess i shouldnt be let alone in the room with devices beyond 500 euros lol
Click to expand...
Click to collapse
Lol
In case of panic, slap yourself silly.
Sent from my HTC One X using xda premium

[Q] Nexus Power Woes - Troubleshooting assistance request

I've never been in this situation before, and I'm hoping that throwing this out there will either help me think this through, or at least get someone who has seen this before.
Situation is as follows:
Battery Only, device will not power on.
Wall Charger Only (battery removed), device will not power on.
The only way I can get the device to boot is the following procedure: Plug into Wall, Insert Battery, Power On
Battery > Wall does NOT work.
I can boot into CyanogenMod no problem.
I can boot into ODIN no problem.
I can boot into bootloader no problem.
I cannot boot into recovery via any method. (I reinstalled recovery via ROM Manager after it wouldn't work. No Change)
I cannot use a PC-USB cable to power on the device. As soon as I unplug the device from the wall it powers off, so I can not get it connected to a PC.
If I plug the device into a PC - the PC notices there is an OMAP device attached for about 1s, then it vanishes. About 1s later, it reappears.
When the device is booted into CM, it shows the battery at 99%/100%.
My current theory is it's a bad battery, but I don't have a spare to test with. Based on this information, is bad battery what everyone else is thinking?
Thanks for the help!

mindlessbb said:
If I plug the device into a PC - the PC notices there is an OMAP device attached for about 1s, then it vanishes. About 1s later, it reappears.
My current theory is it's a bad battery, but I don't have a spare to test with. Based on this information, is bad battery what everyone else is thinking?
Thanks for the help!
Click to expand...
Click to collapse
During that 1s that the device appears, you have to manually feed it the drivers for omapflash - I'm not sure, but I think the naked drivers available on the dev section support this.
Since it boots to Android fully, under a certain condition, I'm inclined to think you don't need omapflash, but a new battery.
Sent from my Nexus

I spent hours today wading through the OMAP Flash threads, found the appropriate tool, and it runs perfectly.
At this point, I think it's either a battery issue, or the motherboard has some serious issues and is requiring more power than normal to run.
I'll have to hit up Verizon tomorrow and see if they have any in store I can test with.
Thanks for the feedback.

Huzzah!
Somehow I have been paying $2 a month for extended warranty..... I would be pissed, but now I can abuse it.
Now I just need to clear my trail, or break it so good they can't tell.
Suggestions?

mindlessbb said:
Huzzah!
Somehow I have been paying $2 a month for extended warranty..... I would be pissed, but now I can abuse it.
Now I just need to clear my trail, or break it so good they can't tell.
Suggestions?
Click to expand...
Click to collapse
While in cyanogen replace your boot animation with stock and delete your framework-res. Unless cyanogen keeps and makes use of a backup that should make your phone hang at the boot animation.

[Q] Fastboot USB Required?

So short backstory, I've been loading and troubleshooting custom ROM issues on my phone for 4+ years. I'm by no means a developer but I can read word-for-word, research and follow instructions. I was given this 'bricked' Kindle Fire by a friend who knew enough to try and reset but didn't want to bother crawling through XDA to sort it out (he came across it through an acquaintance and the past history of the device is unknowable). So I figured I'd charge her up and poke around -
1. I don't have the cable the device came (or any wall unit charger) but have been using a generic micro-USB and from what I've gathered, this shouldn't be an issue. I've used it with all my other Android devices without issue...
2. While the power button's LED does light up amber while attached to my PC (back panel USB, of course) it never seems to actually charge. I've let it run all the way down to where it wouldn't boot at all, then connected to my computer overnight and the next morning it still flashes low battery. Oddly, while the amber light stays lit while plugged in, when I press the power button it somewhat randomly will actually give me the low-battery notification. Maybe 1/3 times I press it. With the device unplugged, if I press the power button, it will turn on just long enough to give me the low-battery message...but it will do this every time I press the button. Not randomly like when it is plugged in. Sorry if some of this info is extraneous but I'm also trying to sort out whether there is some type of circuitry damage....
3. The device NEVER is recognized by my PC in any way, shape or form. I've installed the KFU drivers, rebooted, disconnected, reset Kindle, uninstalled and reinstalled KFU drivers....every combination under the sun. No beeps, blips or changes in my device manager. This is obviously the biggest bummer and at first I figured I could order a fastboot cable and eventually sort it...but with all the other weird charging issues....maybe this thing is just FUBAR.
EDIT: I completely forgot to add some pertinent information - after sitting on the charger for a half an hour or so...the device will automatically boot to the 'kindlefire' logo screen and then reboot 5 or 6 times in a row flashing between the low-battery message and boot logo...where it eventually stays and still isn't recognized by my computer. I typically will try and reset it after a while...in which it then turns goes back to the normal power button lit up with amber. It then takes another 30 or so minutes and then it will randomly reboot to the logo screen again boot loop all over again. Makes zero sense.
I'd be more than happy to give more information and troubleshoot any other ideas to get this thing going, but I just wanted to illicit opinion before spending money on the cable.

I can tell you right off the bat you need a kindle (or comparable) charger. USB does not cut it. Kindle Fire has big charging requirements. Start with that and you might have better luck!
Sent from my GT-p511x

sharonbw said:
I can tell you right off the bat you need a kindle (or comparable) charger. USB does not cut it. Kindle Fire has big charging requirements. Start with that and you might have better luck!
Sent from my GT-p511x
Click to expand...
Click to collapse
Thanks...I had read that before and then read varying other information to the contrary. Instead of spending money just buying a Kindle Fire stock cable...I'm assuming I might as well spend the extra couple of bucks for a fastboot cable?
EDIT: It's late, I now realize you mean I need to buy the wall charging unit first, correct? I have a wall charger for my Samsung Galaxy S III, would that potentially work?

Ordered appropriate charger...I knew the PC and phone wall charger were underpowered but I never bothered to look up the respective specs until now...they are quite a bit underpowered.
Will check back in once received. Thanks again...

jaxwithanx said:
Ordered appropriate charger...I knew the PC and phone wall charger were underpowered but I never bothered to look up the respective specs until now...they are quite a bit underpowered.
Will check back in once received. Thanks again...
Click to expand...
Click to collapse
Unsintall any drivers you have for the kindle in Device Manger. Than run the driver in the KFU folder. If it takes 2 seconds to install you didn't uninstall it. It takes more than a minute to install the driver. Once it is installed than use the unbrick utility

mattmejia said:
Unsintall any drivers you have for the kindle in Device Manger. Than run the driver in the KFU folder. If it takes 2 seconds to install you didn't uninstall it. It takes more than a minute to install the driver. Once it is installed than use the unbrick utility
Click to expand...
Click to collapse
I mentioned above that my PC does not recognize the Kindle when it is plugged in, so I can't uninstall any drivers from the Device Manager. This is also not my only issue....did you read the entire post?

jaxwithanx said:
I mentioned above that my PC does not recognize the Kindle when it is plugged in, so I can't uninstall any drivers from the Device Manager. This is also not my only issue....did you read the entire post?
Click to expand...
Click to collapse
He meant your windows device manager. The kindle drivers are temperamental. Once you have fully charged device and properly installed drivers, you might find that your situation has changed.
Sent from my GT-p511x

sharonbw said:
He meant your windows device manager. The kindle drivers are temperamental. Once you have fully charged device and properly installed drivers, you might find that your situation has changed.
Sent from my GT-p511x
Click to expand...
Click to collapse
Yeah I knew he was talking about Windows Device Manager, that's why I mentioned that as of right now, there is nothing to uninstall from the Device Manager because the PC isn't recognizing anything. But yes, after the device fully charges, with any luck, I'll at least pull something up in the DM and then I will make sure to uninstall and reinstall before poking around.

Well, same problem remained. Charged on wall for 6+ hours with appropriate charger but the light remained lit amber and frozen at 'kindlefire' bootscreen.
Hard reset it and it now just flashes the low battery message to me briefly before powering the screen off again (remains 'charging' if on charger or just turns back off if not on charger). I figured that this wasn't my issue due to the fact my computer wasn't recognizing the Kindle in any state, even when stuck on boot logo. It's not just that it doesn't assign the right drivers....it never notices anything plugged in at all. Restarted, hard booted again, restarted with the Kindle connect stuck on boot screen and every combination in between.
No clue...any help appreciated...

Any thoughts at all here??
Been plugged in for over 12 hours...still amber light. Sometimes frozen on 'kindlefire' boot logo screen...other times just off entirely....alternates.

I'm wondering if you have a bad usb port - a common kindle defect. Sounds like you might build up enough charge for the device to attempt to boot then it goes dead again until a little more juice trickles in. This is total conjecture because I think typically it just comes off the board and quits working completely. You might want to search about replacement.
Sent from my GT-p511x

sharonbw said:
I'm wondering if you have a bad usb port - a common kindle defect. Sounds like you might build up enough charge for the device to attempt to boot then it goes dead again until a little more juice trickles in. This is total conjecture because I think typically it just comes off the board and quits working completely. You might want to search about replacement.
Sent from my GT-p511x
Click to expand...
Click to collapse
Yeah, I got this for free so I'm not going to bother paying for a replacement. Just an auxiliary device.
I cracked it open yesterday to take a look at that very issue but didn't have a small enough screwdriver with me at the time to take the board off to look. I've soldered things here and there.
I don't necessarily hold out much hope that is the issue because the charging light stays lit and never seems to falter no matter if I wiggle or move around. But who knows, I've seen weirder things...I just find it interesting that I get no response at all from my computer even when it's stuck on the boot logo. Typically with most devices, that seems to be far enough for it to be sending something out at that point. Maybe it is stopping just short of that moment though....who knows...

[Q] Completely Bricked Kindle, could use some help.

Long time reader, first time poster. I've been coming here for years for all my Kindle needs, but unfortunately I'm a bit stuck, and I'm asking for some help.
So I have an original Kindle Fire. Back probably in 2011 or 2012, I rooted the device and installed a custom ROM. I didn't exactly know what I was doing, but I read some tutorials and followed them carefully, and everything seemed to work fine. I avidly used it until I bought newer devices. I ultimately lost interest in it. It traveled with me from house to dorm to apartment.
Now just recently I get it out, and the thing won't start. Completely dead. The screen won't light up; the button doesn't glow; it is completely unresponsive. From what I've read, this seems to indicate that my "bootloader and recovery ... are broken".
Following some other help threads on xda, I was ultimately directed to pokey9000's Firekit LiveUSB repair kit, where I installed Ubuntu, opened the Kindle, performed the "USB Boot Shorting Trick", and through FireKit, managed to successfully send USB-Boot commands to the Kindle:
the Kindle powers on and displays a yellow triangle with fire logo inside of it. The kindle says something along the lines of "press power button for recovery", but that doesn't do anything.
On my computer, FireKit hangs at <Waiting For Device>, and nothing happens.
I feel like I'm so close to fixing it, I can't just give up. But I honestly don't know how to proceed; I'm stuck and asking for help.
I take it, the yellow triangle is an old version of FireFireFire. Does this mean I'm in FastBoot? Ostensibly, shouldn't I be able to reboot into Windows and use a tool such as Kindle Fire Utility or Kindle Fire Unbrick Utility to send fastboot commands, and fix any problems from there? Because that doesn't seem to work.
Willing to throw some Walmart or Dunkin' Donut e-gift cards your way if you can point me in the right direction.
Thanks in advanced. :good:

I'm guessing that the battery is dead, and that is all.
Can take hours even days to on Wall charger to see progress.
Sent from my XT907 using Tapatalk

sd_shadow said:
I'm guessing that the battery is dead, and that is all.
Can take hours even days to on Wall charger to see progress.
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
That's an interesting thought. I know I've left it plugged in 'overnight', but not for a few days. I'll give it a try.
Finger's crossed, thanks.

sonicfanrs said:
That's an interesting thought. I know I've left it plugged in 'overnight', but not for a few days. I'll give it a try.
Finger's crossed, thanks.
Click to expand...
Click to collapse
Hmm okay, so it's been charging with the OEM charger since April 20th, and it still won't power on.
If anyone has any suggestions, please let me know; I would love to get it working again.
I'll be playing around with Linix/FireKit/USB-Boot, and hopefully make some progress. Thanks so much.

sonicfanrs said:
Hmm okay, so it's been charging with the OEM charger since April 20th, and it still won't power on.
If anyone has any suggestions, please let me know; I would love to get it working again.
I'll be playing around with Linix/FireKit/USB-Boot, and hopefully make some progress. Thanks so much.
Click to expand...
Click to collapse
Have you tried a different charger (or are you certain that the OEM charger works)? Is the USB port in good shape (no wiggling, your kids didn't dry to tight-rope walk the USB cable when it was plugged in)?

pfederighi said:
Have you tried a different charger (or are you certain that the OEM charger works)? Is the USB port in good shape (no wiggling, your kids didn't dry to tight-rope walk the USB cable when it was plugged in)?
Click to expand...
Click to collapse
Nah, I left it in the corner of my bedroom plugged in all by itself, just pressed the power button a few times a week to see if it would power on. Only tried the one charger, which charges other devices just fine. Seems to be a 'high-power" charger because on a working Kindle, I do not get the message "Connected to Low-Power Charger".
I'm pretty sure the battery is charging. A few weeks ago I usb-booted and left it sit at the (fff?) yellow-fire-triangle, device unplugged and screen constantly on. It stayed that way for at least an hour, before I manually turned it off. So that would lead me to believe the battery is in good shape, and the USB port is fine.
Could give it another week or so with a different charger. Got nothing to lose, I suppose.
Thanks for your reply.

sonicfanrs said:
Nah, I left it in the corner of my bedroom plugged in all by itself, just pressed the power button a few times a week to see if it would power on. Only tried the one charger, which charges other devices just fine. Seems to be a 'high-power" charger because on a working Kindle, I do not get the message "Connected to Low-Power Charger".
I'm pretty sure the battery is charging. A few weeks ago I usb-booted and left it sit at the (fff?) yellow-fire-triangle, device unplugged and screen constantly on. It stayed that way for at least an hour, before I manually turned it off. So that would lead me to believe the battery is in good shape, and the USB port is fine.
Could give it another week or so with a different charger. Got nothing to lose, I suppose.
Thanks for your reply.
Click to expand...
Click to collapse
@ (fff?) yellow-fire-triangle, do you see press power for options?

sd_shadow said:
@ (fff?) yellow-fire-triangle, do you see press power for options?
Click to expand...
Click to collapse
Yeah I do. But pressing power doesn't do anything. Whether it's a long press, or a short press, or a quick press right as the triangle appears, nothing.

sonicfanrs said:
Yeah I do. But pressing power doesn't do anything. Whether it's a long press, or a short press, or a quick press right as the triangle appears, nothing.
Click to expand...
Click to collapse
Have you tried flashing by sending fastboot commands, then powering on kindle like in my
[url="http://forum.xda-developers.com/showpost.php?p=54156780&postcount=5]"Flashing Twrp in FFF bootloader with fastboot.exe[/url]
Sent from my XT907 using Tapatalk

Have you tried using a Linux OS? I've seen lots of threads/posts all over XDA about how people can't get their device to work with Windows. Maybe you could grab a live version of some OS and put it and the binaries for adb and fastboot on a flash drive and boot from it. The only time I've ever had issues with my devices and Linux is just recently when I discovered a faulty USB cable (is your cable good?).
Perhaps it may be easier to just replace the motherboard. I did that when my USB port got wrecked. The best deal I've found is here: http://www.powerbookmedic.com/Kindl...-REGISTER----Good-Micro-USB-Port-p-27164.html If you don't intend to run Amazon's OS, then it doesn't matter that it can't be registered. If you do replace the board, be very careful of the data cable for the LCD; it is fragile.

Stuck in recovery with no volume keys

So hi. Had an issue with my GNex where I had to replace the charging port (easy) and I managed to tear the volume button cables in the process. Wasn't a huge issue until I had the clever idea of booting into recovery.
Currently using ClockworkMod Recovery 6.0.2.3, and because I'm not smart it's not the touch version. All I can do is select "reboot system now" and choose "no" to fixing root, because I can't navigate without the volume keys. Choosing to restart just brings me back to recovery, so I can't get back into the OS to flash the touch version (would I even be able to without the volume keys?).
Is there any way I can flash a touch recovery on the device without being able to use the volume keys? I can't boot it into Odin mode here.
(I suppose I could bite the bullet and get a soldering iron... I've got the replacement volume key, I'm just **** at small parts, obviously)

Got it into Fastboot mode with ADB, but for whatever reason the device driver that works while it's in Recovery mode does not work in Fastboot mode, so Fastboot isn't detecting it and I can't load the new recovery.
Baby steps.

For whatever reason Windows wasn't installing the ADB drivers properly so I had to do it manually? It even told me the driver I'd selected wasn't recommended, but it went ahead with it anyways and now both ADB and Fastboot work.
It's been so long since this has worked it looks like it's got a Jellybean AOKP ROM on it. Currently initiating swagger, though it's taking a while.
Aaand looks like it's a version of AOKP that just sits there loading eternally. Think I ran into this before, which is how I ended up in this situation to begin with. Must have found a way to get into recovery from here.
So... again, still not working, but for a different reason this time at least.
I really should just get a soldering iron.

If the connection to the motherboard isn't broke and its just the buttons that are broke, you can try using a paper clip to make contact with it and short out the connection which tells the phone the button is pressed its what i did when my power button went out, its a pain to do and get right but it might be worth is i wish i had pictures to show you what i'm talking about so i hope you understand! but if all else fails ebay is your best friend for new parts!

Dudeyourdead said:
If the connection to the motherboard isn't broke and its just the buttons that are broke, you can try using a paper clip to make contact with it and short out the connection which tells the phone the button is pressed its what i did when my power button went out, its a pain to do and get right but it might be worth is i wish i had pictures to show you what i'm talking about so i hope you understand! but if all else fails ebay is your best friend for new parts!
Click to expand...
Click to collapse
So, it's the ribbon cable connecting the buttons to the motherboard that's been damaged. I have a replacement, but I am not great with soldering and haven't tried it yet.
In the meantime, I bought a jig on ebay, and with that I've got it back into Odin mode. I'm absolute **** at retaining information/skills though and can't for the life of me remember how to get ADB to detect the damn thing once it's in Odin mode.
One thing I did just remember is that the USB connection on this phone is deep, so a few of the cables I have don't go in far enough, which causes complications.

Odin detects the phone, Heimdall detects the phone, Kies detects the phone (and tells me it's not supported). I just can't get ADB or Fastboot to detect the phone.
I've tried uninstalling and reinstalling drivers, I've tried swapping USB ports, I've tried different cables, I know this works because I've had it working before.
This phone is going to drive me to drink.

Sweet buttery gonads, I've got it booting into stock Android (no ADB, but Odin still working? Alright, there's a workaround).
I wish I still had that Moto G, it never had these problems...

So much luck using the Nexus Root Toolkit, and GAPPS/CWM Recovery Touch by Koush, I appear to have a functioning Galaxy Nexus running CM12.1? It's still verifying/optimizing apps, and that's where my Note 8.0 ran into trouble, so I suppose only time will tell.
22 of 91 apps optimized.

TL;DR for what I did:
I bought a jig on ebay. $1.50, free shipping, can't go wrong. It plugs into the bottom of the phone (with the power off) and puts the phone in Odin/download mode.
After getting fed up with trying to get ADB/Fastboot working on my desktop (it worked once, can't get it to now, no idea why) I tried it on my laptop. Tracked down a Nexus Root Toolkit (from Wugfresh) which automated a lot of the process, and had a good walkthrough for driver installation. Took three driver wipe/reinstalls on the laptop before it took.
Also the usb port (this being the one I replaced) is broken again, so I have to hold the USB cable at an upward angle for ADB/Fastboot to detect the phone at all. I just rested the cable on a screwdriver next to the phone and that did the trick. No jiggling at all.
The nice thing about the Toolkit is that it automates installation and does all the recovery stuff itself, which bypasses the lack of volume keys entirely. It flashed an up to date TWRP recovery, not sure if it flashed a touch one since I can't boot into recovery mode without the toolkit/ADB/Fastboot anyways.
The phone is still on it's last legs, but I've got CM12.1 installed now, as well as the Blackberry keyboard from the Priv, which was the whole point of digging the GNex out in the first place.
Links:
Nexus Root Toolkit:
http://www.wugfresh.com/nrt/

Glad to Hear! in all fairness i completely restored my Gnex but buying an broke one with functioning part someone sold it bricked for $14.67 on eBay, But if you bought the whole power button flex cable then its just a matter of opening up and snapping it down no soldering required i promise just push till you hear a click!

Dudeyourdead said:
Glad to Hear! in all fairness i completely restored my Gnex but buying an broke one with functioning part someone sold it bricked for $14.67 on eBay, But if you bought the whole power button flex cable then its just a matter of opening up and snapping it down no soldering required i promise just push till you hear a click!
Click to expand...
Click to collapse
Power button's fine, it's the volume keys that are damaged. I've got a bad history with translucent orange ribbon cables.