So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?
philip1192 said:
So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?
Click to expand...
Click to collapse
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again
Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
persano said:
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again
Click to expand...
Click to collapse
I'll try that and see if it'll help.
mindmajick said:
Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is that a problem?
Other than voiding the warranty since you opened the device... And removed a battery not meant to be removed? Naaaah
You should NEVER have to pull the battery on ANY android device.
Edit: couple more things
1. As long as you are USING the device it won't charge on USB to PC. Always better to charge off a wall outlet. MUCH faster charging too.
2. NEVER flash a ROM if your battery is low.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.
philip1192 said:
When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.
Click to expand...
Click to collapse
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1
mindmajick said:
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
How was it not actually unlocked?
Hopefully someone can...
philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163
philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
soupmagnet said:
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163
Click to expand...
Click to collapse
Well, they're lame. I like HTC better.
mindmajick said:
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I guess I'll see if I can make that work. If not, I guess I have an expensive paperweight on my hands...
Related
So the other night, my power button literally stopped working. I called Verizon and requested another device to be sent to me, but now I have to return this thing to stock before I send it back. I've tried to Galaxy Nexus Root Toolkit by Wug, but my device won't show up. I can't get into bootloader mode because my power button won't work!!
Is there anything else I can do?
matt6906 said:
So the other night, my power button literally stopped working. I called Verizon and requested another device to be sent to me, but now I have to return this thing to stock before I send it back. I've tried to Galaxy Nexus Root Toolkit by Wug, but my device won't show up. I can't get into bootloader mode because my power button won't work!!
Is there anything else I can do?
Click to expand...
Click to collapse
Is your phone on? Just use adb's command "adb reboot bootloader". If your phone is off, I don't know how you can turn it on without a power button.
Sent from my Galaxy Nexus using xda premium
connect to your computer and use
Code:
adb reboot bootloader
when you finally need to power it off to send it in, just pull the battery.
adb won't recognize my device. =/ It's stuck off.
You shouldn't have to worry then because they won't be able to turn it on either. lol
[email protected] said:
You shouldn't have to worry then because they won't be able to turn it on either. lol
Click to expand...
Click to collapse
Lmao, now thats funny......and it makes sense
Sent from my Galaxy Nexus using xda premium
Do you get some sort of animation when it's plugged into the charger?
if its on
open terminal and type:
su
reboot bootloader
if its off use a usb jig to get into odin mode
[email protected] said:
You shouldn't have to worry then because they won't be able to turn it on either. lol
Click to expand...
Click to collapse
Uh.. Yeah they will. The physical power button isn't working but as they unscrew the Galaxy nexus they can trigger the mechanic to power the phone on. And then just replace the button and reflash it to stock and then resell the phone.
If they see that the device was already bootloader unlocked, don't be surprised to see additional charges on your next bill.
Sent from my Galaxy Nexus using xda premium
Have you tried the GN Toolkit: http://forum.xda-developers.com/showthread.php?t=1392310
If i remember correct, when the phone is ON, you can connect the phone, then reboot it with the GN toolkit to bootloader and install stock.
I think that could solve your problem
Take the battery out, plug the phone in, and then replace the battery. See if it will power up by itself.
Sent from my Xoom using Tapatalk
Things I have tried:
GN Rootkit (adb/fastboot won't recognize device)
Plugging phone into computer and restarting computer
Draining battery and allowing to charge in phone until enough juice to turn on automatically
Plugging phone in with no battery
Nothing will work. Never tried a USB jig. Guess I will order one and see if that helps. Never used one before but I guess a google search will help. Guess I'll call Verizon and ask them to extend my return period before they bill me for the device.
Tried the naked drivers?
http://forum.xda-developers.com/showthread.php?t=1379875
Usb jig will bring you to download mod ,then you have option to reboot(automatic phone turns on) ...befor you can flash stock rom and no more problems!
Sent from my GT-I9100 using XDA Premium App
i highly doubt they will send the verizon police to repossess the replacement for when the find the unlocked bootloader.
you can send it in rooted
I had Verizon replace my last phone with Asurion insurance because of a blown speaker. The phone was running Cyanogen. There was no problem.
To be clear:
1. The phone was CLEARLY running Cyanogen because it powered on, showed the CM7 boot animation, and worked perfectly
2. They never called me, hassled me, or anything. Just credited my account.
good luck
Got into Odin mode, but no options to reboot. Just says "Downloading... Do not turn off target !!" The only option displayed is "Start" but I'd have to use the power button to select it (can't do that lol). What can I do from Odin?
Well, pretty sure I just hard-bricked it, so whatever.
Downloaded this: i9250xx_itl41f_fl.zip
and ran it while the phone was connected to the computer in odin mode.
Was kind of distracted by gf and didn't verify that it was for CDMA. I guess its GSM only. Anyways, now the jig won't bring up Odin mode, and I have an imagine of a phone connected to a monitor with a yellow exclaimation triangle between the two.
Guess that's it.
Found a CMDA odin image. gonna try to flash this. didnt realize you needed Odin3 too, lol. Will let you guys know how it worked..
Image worked. Back to stock 4.0.2. I suppose that means it's unrooted. Used the GN Rootkit to relock bootloader. I don't know if stock recovery is installed or not, though. I tried to reboot into recovery using the rootkit, but i just got a red triangle. Any ideas?
I rooted my fire a couple weeks ago. Used the KFU and everything worked perfectly. I have the android marketplace. I even downloaded the OTA something that allows you to temporally disable so I can still watch prime videos.
But tonight it powered off on its own and got stuck on the yellow triangle screen. I tried using the KFU and change it to normal boot mode. which seemed to work. It got to the Kindle fire screen and booted up. As soon as the carousel popped up it shutdown immediately and got stuck on the yellow triangle screen. It keeps doing this. Any ideas.
I tried reading many of the other threads, but I got majorly confused. So any help is appreciated. Thanks
edit: I noticed i had a few seconds before it would shutdown on me. I was able to open OTA rootkeeper and turn the root back on before it shutdown. As soon as I click restore root, it shutdown again, but it booted up fine. Im thinking the issue was caused by the root temporally being disabled. Is this a known problem. Seems to be working fine, will update tomorrow.
Edit: seems I have to changed it no normal boot everytime. Is there a way to unroot my fire. Hopefully its not too complicated.
Thanks for anything guys.
And I think the root is disabled at the moment, but not a %100 sure. NOt sure if that matters.
Mine's doing the same thing. I think it has something to do with the new OTA update? Mine will start up then reboot into recovery...any thoughts guys?
I'd start here, since it appears many others had similar problems with the OTA push:
http://forum.xda-developers.com/showthread.php?t=1634075&page=2
Supposedly KFU rooting still works. You may need to try this method again. Check this thread and see what others had to say as far as what worked for them. Good luck!
How do I unroot it completely. Its still getting stuck on yellow triangle. I used it for 30 minutes last night. Now unless I make it boot up normally, it gets stuck. getting frustrated.
Now when I use KFU to start it in normal mode, it gets to the Kindle fire screen, and occasionally the screen where I typed in my code to unlock it and it turns off, black screen, It will only turn on when plugged in.
edit: I guess my battery somehow died overnight. Swear it was full when I went to bed
Would updating my fire with the usb get rid of the root? I just want it back to normal. What is easiest way to do that?
Now its stuck on this cycle where it says theres an error and the kindle fire must reset to its original factory settings its does this. Reboots I think and does it again. Its stuck like this.
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
soupmagnet said:
To break root and restore everything back to original:
http://forum.xda-developers.com/showthread.php?p=25681034
Click to expand...
Click to collapse
Thanks but I cant get out of the cycle of what I said in my last post. I think my Fire is broken for good.
Can you boot into recovery? Do you know how?
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I was able to before. My computer doesn't recognize the Kindle anymore
Guess I will be buying a new one.
TURBO1112 said:
I was able to before. My computer doesn't recognize the Kindle anymore
Click to expand...
Click to collapse
Your computer doesn't need to be recognized by the computer to boot into recovery.
soupmagnet said:
Can you boot into recovery? Do you know how?
Click to expand...
Click to collapse
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then <waiting for device>. Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
fzdolfan said:
I *think* I'm having the same issue. When the fire is not plugged in, it's a black screen. No method of pressing the power button does anything (length of time, number of times, etc.). When it IS plugged in, the standard kindle fire/android logo just blinks. Again, power button has no effect whatsoever.
KFU shows ADB offline and Boot unknown.
Just some background info, I had a rooted working Fire. Out of the blue (likely the OTA update) it got stuck at the triangle logo screen and was able to get it into recovery mode. The first time I just reset it to factory.
Rooted again using KFU, said successful root, but installing Google apps kept saying failed or error until finally saying "All done!"
Then tried to install TWRP, and KFU got stuck at trying to put the fire into fast boot mode then . Recovery screen came up again, and (here's where I made a bonehead decision) figuring I would help things along, I selected fast boot mode. It was stuck on the kindle fire screen for hours. I even tried reinstalling the drivers but that failed. I left it plugged in to my PC and when I woke up this morning I found it in the state it is in now that I first described above.
I will continue to search more threads for an answer, but if I don't update this one that I've found one, it means I haven't.
Click to expand...
Click to collapse
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
soupmagnet said:
The "blinking" boot logo is indicative of a dead battery, probably caused by leaving it in fastboot mode for so long.
http://forum.xda-developers.com/showthread.php?p=25400963
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
http://forum.xda-developers.com/showthread.php?p=20317299
Your best bet is to follow the first link and do what you can to install FFF1.4 and that will allow you to charge your battery from such a low power state.
You'll have to use the fastboot flash command for this so be sure that the file you use to flash your bootloader is in a .bin format. Simply renaming a .zip to .bin will not work. You have to extract the u-boot.bin from the FFF1.4.zip, otherwise you will hard-brick your device. If you're unsure of what you're doing, ask for help.
On the chance you can't get FFF1.4 installed, you'll need to acquire a factory cable to keep the device powered on long enough to install your bootloader.
Another user recently had a problem that required a factory cable to fix. Take a look at that thread so you have an idea of what needs to be done and how to fix your problem. His problem was different from yours but the solution is the same. http://forum.xda-developers.com/showthread.php?p=25693109
Click to expand...
Click to collapse
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
fzdolfan said:
Even after reading the posts regarding the factory cable, I'm still not sure what the difference is. I have been (successfully) using a Motorola Android phone cable that when plugged into the Fire (when it was working) would say that USB is connected and I can now transfer files. I also successfully rooted it once before and installed all the apps and such with the KFU. What would be different that would make this cable only now insufficient?
Btw, I was able to charge it using the stock wall charger. At least I assume it is charged because it is no longer blinking the kindle fire logo, and I am able to shut it down by holding the power button even when plugged into the USB cable.
However, it still won't do anything but show the android/kindle fire logo (static, not flashing/oscillating) whether it's turned on with or without a cable plugged in. Opening the KFU and trying boot modes does nothing. There is no acknowledgment whatsoever that it is connected to the PC either from the fire or the PC. I don't even get the sound effect from the PC that something has been connected via USB.
Click to expand...
Click to collapse
A "factory cable" is specially made to interact with the device in a way that is different from the OEM Motorola USB cable you are currently using. With a little research and a little more reading you'll be able to find out what the difference is and why it works for fixing dead battery issues.
Using the stock charger was one of the very first things covered in the first link that I gave you. I'm trying to help you fix your problem so please try to pay attention to the information I'm giving you.
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
soupmagnet said:
Using the stock charger was one of the very first things covered in the first link that I gave you.
Click to expand...
Click to collapse
I realize that, and I acknowledged it in my post by stating that it solved the drained battery issue. I also gave thanks on your post.
Accusing me of not paying attention is not necessary.
I only said that I don't see the difference in the factory cable because a) my drained battery was resolved by other means and b) I did read in the factory cable thread that "Seems like you have power and this cable is maininly for when your ... battery is dead and you need to ... fastboot with no battery life left.... So the cable does not matter in your case since your battery has power you can use any usb cable."
soupmagnet said:
So now that your battery issue is resolved, you have to fix the next part of the problem which is resetting your bootmode. By far the easiest way to do this is by flashing the latest 1.4 version of FireFireFire in recovery. Be sure to use recovery to install it or you may find yourself in more trouble than you started.
The thread for the new version along with important information on how to install and use it can be found here: http://forum.xda-developers.com/showthread.php?t=1632375
Click to expand...
Click to collapse
I also looked at this thread, but the initial post seems to imply that I already know how to "Apply this flash.zip from recovery just like any other ROM or kernel .zip file.", which I do not.
As I said, my fire is currently stuck at the kindle fire logo and does not respond to being plugged in to the PC (other than turning on to the kindle fire screen).
Admittedly, I only went about 4 pages deep into the thread, but it seemed to be all posts of thanks (for the most part) to the original post. I will continue reading the thread if you're saying that it indeed contains more helpful information.
I apologize if my post came across as ignorant or lazy, but the fact is that I've been researching this for the better part of the day, and I see plenty of info on what to do if I can get my PC to communicate with my Fire, but the first problem is that I cannot find out how to hurdle that first very important obstacle.
Just to save us both some time (and I do appreciate your patience and willingness to help), are you saying that I need a factory cable regardless of the state of the battery? Because if that's the case, then my first priority is to figure out how to get one, because my knowledge, means, and experience in soldering and inner workings of electronics is zero, so making one myself is not an option.
Forgive my impatience but playing twenty questions with other, less motivated to learn users, gets kind of old after a while (not to say that you fall into that category). Not to mention, I'm a prick and have very little patience to begin with.
With a good charge on your battery there is no longer a need for a factory cable.
Most of the users here are fairly proficient with the use of recovery so its easy to overlook those who aren't. That's why it's important to know up front what your level of experience is, to avoid such assumptions.
Your recovery (TWRP or CWM) has a mount function for mounting certain partitions as external drives onto your computer. Your computer will recognize it in the same way it does a thumb drive. Use it to mount your sdcard and transfer the FFF1.4 so it can be installed while in recovery.
Once installed, reboot and hold the power button as if you were trying to enter recovery again and you will be able to select which mode to boot with. Choose "Normal Boot".
Today I rooted my T-999, which had been running 4.3. Used saferoot to do so, then installed SuperSU, then flashed CWMR. All reported success, and there were no immediate indications of a problem.
After a couple hours, I manually commanded the phone to reboot. It shut down, but never rebooted. I let it go a few minutes, and then tried to boot it with the power button. No luck.
I've since played around with removing the battery, plugging it in without the battery, and a couple other combinations. In all cases, the phone won't boot. No light, no recovery/bootloader, nothing at all.
Any new ideas about how to restart, what order to remove the battery, plug in, etc. that might help? THANK YOU.
After some searching, I have not been able to find a situation quite like mine. I'm sure I've just missed it -- if the new post annoys you, sorry. I need help.
Can you get into Downloading mode ? Put the battery in and then hold Vol Down+Home+Power.
Perseus71 said:
Can you get into Downloading mode ? Put the battery in and then hold Vol Down+Home+Power.
Click to expand...
Click to collapse
Thanks for the reply - Haven't been able to get it to boot in DL or recovery mode unfortunately.
Does your computer recognize or say any kind of message when you plug it in? Sounds like it's hard bricked
Sent from my SGH-M919 using Tapatalk
serio22 said:
Does your computer recognize or say any kind of message when you plug it in? Sounds like it's hard bricked
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
No, nothing when I plug it in on USB. Can't get adb to recognize it either.
buzban said:
No, nothing when I plug it in on USB. Can't get adb to recognize it either.
Click to expand...
Click to collapse
Try the unbrick thread
Sent from my SGH-M919 using Tapatalk
hey guys i have a major problem, i was going back to otter fro otter x, i flash everything, but then i have a problem on the recovery, it shows the storge as 0mb, and with a problem to mount the storage so i couldnt copy the rom to the device, i was stuck there, the kindle was with %100 battery, but then it reboot itself and now i cant turn it on, im going crazy as i dont know what to do, i hope anybody can help.
more info neede. which bootloader version, twrp version did you have installed. have you held the power button for 20 seconds. if you plug it in does the led light come on. dont worry it is fixable 99% of the time. @sd_shadow if he's around will help you. im just going to bed but if your still stuck in about 8 hours time p post in my slimpop thread in the development section and i will help you. cheers and good luck steve
Sent from my Nexus 5 using Tapatalk
Isn't like 4:30am there? might as well stay up now, lol
lovejoy777 said:
more info neede. which bootloader version, twrp version did you have installed. have you held the power button for 20 seconds. if you plug it in does the led light come on. dont worry it is fixable 99% of the time. @sd_shadow if he's around will help you. im just going to bed but if your still stuck in about 8 hours time p post in my slimpop thread in the development section and i will help you. cheers and good luck steve
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
twrp 2.8.1.1, when i plug it in the led doesnt light up, i held the button for 20 sec and nothing.
legendkiller647 said:
twrp 2.8.1.1, when i plug it in the led doesnt light up, i held the button for 20 sec and nothing.
Click to expand...
Click to collapse
tried wall charger and pc?
sd_shadow said:
tried wall charger and pc?
Click to expand...
Click to collapse
yes both of them and nothing, not even the led light up.
zip-twrp-2.8.1.1.otter.blaze.zip, FFF 1.4a?
nothing showing up in device manager?
could take back cover off and disconnect battery for 10 secs
sd_shadow said:
zip-twrp-2.8.1.1.otter.blaze.zip, FFF 1.4a?
nothing showing up in device manager?
could take back cover off and disconnect battery for 10 secs
Click to expand...
Click to collapse
nothing showing on device manager, im gonna do the battery thing and tell you what happen.
legendkiller647 said:
nothing showing on device manager, im gonna do the battery thing and tell you what happen.
Click to expand...
Click to collapse
still nothing
legendkiller647 said:
nothing showing on device manager, im gonna do the battery thing and tell you what happen.
Click to expand...
Click to collapse
did you install a FFF bootloader? or keep the OtterX bootloader?
couple of other options
order or make a Fastboot cable http://forum.xda-developers.com/showpost.php?p=53652317&postcount=2
try the boot to usb, short trick to reflash bootloader http://forum.xda-developers.com/showthread.php?t=1430038
Even though twrp reported battery at 100% it could have been wrong, or battery is failing.
Could leave connected to pc for a few hours
sd_shadow said:
Even though twrp reported battery at 100% it could have been wrong, or battery is failing.
Could leave connected to pc for a few hours
Click to expand...
Click to collapse
Hey i tried doing the thing with ubuntu, but when i type the commands it said error, the command does not exist, i dont know what else to do, im stuck with the kindle dead and i need it for work, any ideas?
my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz
LumberjackZac said:
my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz
Click to expand...
Click to collapse
Can you still boot into TWRP?
dhplap said:
Can you still boot into TWRP?
Click to expand...
Click to collapse
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available
LumberjackZac said:
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available
Click to expand...
Click to collapse
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
That is awesome. Been looking at Note 4's on ebay because.... not looking good
ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
Hey buddy. I've been reading that qhsusb_bulk is a hard brick, possible fried bootloader. But I guess if you can make this unbrick.img on to a sdcard it may work. I'm scratching my head on what files go into this unbrick.img and if I can make it myself. Any ideas