I f*cked up by rooting it and then played around with the file permissions and now it says when I try to boot;
Kindle Fire System Recovery
Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue.
Volume up/down to move highlight;
power button to select.
Reboot your Kindle
Reset to Factory Defaults
I tried both and it still comes up. please help me
Sounds like you may need to reflash your device. I think, although not entirely sure, you can use onemeila's KFHD System.img Recovery Tool in the Android Development section of this forum. That means you'd have to buy a factory cable though.
Imenak said:
Sounds like you may need to reflash your device. I think, although not entirely sure, you can use onemeila's KFHD System.img Recovery Tool in the Android Development section of this forum. That means you'd have to buy a factory cable though.
Click to expand...
Click to collapse
what is reflashing? does it have something to do with a computer? because my computer doesn't recognize the device as it used to now that it's bricked.
also, i rooted it, does rooting affect my warranty and will amazon know about it? after all it is bricked so they cant check that right?
Thanks a lot!
Toxification said:
what is reflashing? does it have something to do with a computer? because my computer doesn't recognize the device as it used to now that it's bricked.
also, i rooted it, does rooting affect my warranty and will amazon know about it? after all it is bricked so they cant check that right?
Thanks a lot!
Click to expand...
Click to collapse
Amazon would probably be able to tell that you messed with the device. Reflashing is basically just reinstalling system software to the device. Yes it has to be connected to your computer and you have to be in fastboot which requires a factory cable. Once in fastboot your computer will recognize the device as long as the drivers you installed to root are still in place. The details to buy or make a factory cable are in the link below. Personally I made mine, it's pretty easy if you are handy with things. That said if not done right it has the potential to seriously screw up your device as well as your computer. So buying one for $12 might be a better choice for some.
After you get the factory cable power the device off, connect it to the device and computer, and the device should automatically boot up in fastboot. If successful you will see a screen that has a logo saying "fastboot kindle fire". Then you are ready to use the system recovery tool in the android development section mentioned in the last post. I am in the process of updating it with the 7.2.1 system software. Also only use that tool if you have a KFHD. If you have a KF2 you will need a backup .img from a KF2.
Factory cable info-
http://forum.xda-developers.com/showthread.php?t=1392693
I just noticed in another thread that you have the 32gb version with 7.2.0. I don't know how different the system is from 7.2.1 or whether they can swapped. The only difference between the two is storage capacity. Theoretically I would think it could work. Actually I just read on amazon that the 32gb now runs the same 7.2.1 v. If yours isnt you just didn't get the update yet. So the process above will work. I'll be uploading the recovery tool with .img from 7.2.1 sometime today.
onemeila said:
Amazon would probably be able to tell that you messed with the device. Reflashing is basically just reinstalling system software to the device. Yes it has to be connected to your computer and you have to be in fastboot which requires a factory cable. Once in fastboot your computer will recognize the device as long as the drivers you installed to root are still in place. The details to buy or make a factory cable are in the link below. Personally I made mine, it's pretty easy if you are handy with things. That said if not done right it has the potential to seriously screw up your device as well as your computer. So buying one for $12 might be a better choice for some.
After you get the factory cable power the device off, connect it to the device and computer, and the device should automatically boot up in fastboot. If successful you will see a screen that has a logo saying "fastboot kindle fire". Then you are ready to use the system recovery tool in the android development section mentioned in the last post. I am in the process of updating it with the 7.2.1 system software. Also only use that tool if you have a KFHD. If you have a KF2 you will need a backup .img from a KF2.
Factory cable info-
http://forum.xda-developers.com/showthread.php?t=1392693
I just noticed in another thread that you have the 32gb version with 7.2.0. I don't know how different the system is from 7.2.1 or whether they can swapped. The only difference between the two is storage capacity. Theoretically I would think it could work. Actually I just read on amazon that the 32gb now runs the same 7.2.1 v. If yours isnt you just didn't get the update yet. So the process above will work. I'll be uploading the recovery tool with .img from 7.2.1 sometime today.
Click to expand...
Click to collapse
Thanks a lot!
"Once in fastboot your computer will recognize the device as long as the drivers you installed to root are still in place."
sorry what does this mean? what drivers did I install?
Toxification said:
sorry what does this mean? what drivers did I install?
Click to expand...
Click to collapse
When you initially tried to root it, you hopefully installed some drivers in order for your device to be recognized on your computer. Those are the drivers he's talking about, which are linked in this post: http://forum.xda-developers.com/showthread.php?t=1893838.
oh them, right thanks
Usually I fix all my friends and families androids, and am know as the head of technology amongst my people, but here I am asking bigger people for help. I have a Kindle Fire HD 7", 7.4.1, rooted with no second bootloaders or custom roms whatsoever, just a stock to root. It recently ran out of battery and I've been stuck for the last hour trying to get it to turn on PROPERLY. I've googled it, checked here at XDA, and all I read is "charge it, hold for 20-30 seconds, play with the volume buttons while pressing power, etc" but it does not help. At first sight, the battery is indeed dead. I had the settings to sleep the screen in 5 minutes and that's how it got like that. Now IT DOES turn on, I see the nice Kindle Fire logo, it flashes once as it always does when its ready to start up, but that's where it stays. It will not go beyond that. I've tried all types of tricks here at XDA, I have NO factory cable, (wouldn't mind making one if I had the proper thread/tools) and the ridiculous USB and charging base I'm using is not the original (they are good brand though...), so I'm assuming, from what I've heard, its not getting the proper charge. Okay I'd admit that, but why does it stay stuck in the logo? I did nothing but play Falling Fred before it died, and I have no type of custom mods to it for it to be bricked or in a boot loop? Can anybody help/guide me into what to do?
Crossvxm said:
Usually I fix all my friends and families androids, and am know as the head of technology amongst my people, but here I am asking bigger people for help. I have a Kindle Fire HD 7", 7.4.1, rooted with no second bootloaders or custom roms whatsoever, just a stock to root. It recently ran out of battery and I've been stuck for the last hour trying to get it to turn on PROPERLY. I've googled it, checked here at XDA, and all I read is "charge it, hold for 20-30 seconds, play with the volume buttons while pressing power, etc" but it does not help. At first sight, the battery is indeed dead. I had the settings to sleep the screen in 5 minutes and that's how it got like that. Now IT DOES turn on, I see the nice Kindle Fire logo, it flashes once as it always does when its ready to start up, but that's where it stays. It will not go beyond that. I've tried all types of tricks here at XDA, I have NO factory cable, (wouldn't mind making one if I had the proper thread/tools) and the ridiculous USB and charging base I'm using is not the original (they are good brand though...), so I'm assuming, from what I've heard, its not getting the proper charge. Okay I'd admit that, but why does it stay stuck in the logo? I did nothing but play Falling Fred before it died, and I have no type of custom mods to it for it to be bricked or in a boot loop? Can anybody help/guide me into what to do?
Click to expand...
Click to collapse
Many Android devices, once depleted of battery, will not boot properly until the battery is anywhere from 20% or above. Try letting it charge longer. To speed up the process, use a wall adapter from your other devices. it will pump more voltages. As you said, there aren't any mods I can see that would cause bootloops or bricks.
Try charging it for a good hour, not booted up. To make sure it has charge. Then try to turn it on. This is very weird though, first time I heard a Android device acting up like that.
Sent from my air conditioner unit running CyanogenMod
I left it charging from 5am to now and it hasn't charged a thing because when I disconnected it and tried to turn it on it turned off after 7 minutes of the Kindle Fire logo. I also noticed that the reflection animation on the logo moves faster than it usually does. It just stays there. I'm guessing my only option would be a factory cable of some sort. No matter how many 20 second power button thing I use, it just stays stuck on the logo, as if something had damaged the firmware somewhere, but how? I will try to charge it once more for a while and see.
EDIT : I made my own "factory cable" and got it to fastboot. Now what can I do to restore it???
Hopeless???
Okay so here's how far I've gotten:
1. Tried to charge it for hours, used 20 second reset (no good)
2. Looked up instructions on how to restore from a brick (bologna because I can't get the ADB working at all, no clue how to use)
3. Made my own factory cable off of a Samsung USB, got into fastboot with no problem
4. Stuck at what to try next. I tried using the thread http://forum.xda-developers.com/showthread.php?t=2166637 (which I know I'm not hard bricked but either way tried) and used the KFHD_SRTv1.3.5 for 7.3.0 from another thread and my device does not get detected. When I go to Device Manager, the Kindle appears as Tate-PVT-08, don't know if that's normal, but I have run out of solutions.
Where do I possibly go from here? Its only been 19 hours without this thing and I already miss it...unlike other "noobs" who ask for help here, I actually tried on my own to get a solution but got nowhere.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Crossvxm said:
Okay so here's how far I've gotten:
1. Tried to charge it for hours, used 20 second reset (no good)
2. Looked up instructions on how to restore from a brick (bologna because I can't get the ADB working at all, no clue how to use)
3. Made my own factory cable off of a Samsung USB, got into fastboot with no problem
4. Stuck at what to try next. I tried using the thread http://forum.xda-developers.com/showthread.php?t=2166637 (which I know I'm not hard bricked but either way tried) and used the KFHD_SRTv1.3.5 for 7.3.0 from another thread and my device does not get detected. When I go to Device Manager, the Kindle appears as Tate-PVT-08, don't know if that's normal, but I have run out of solutions.
Where do I possibly go from here? Its only been 19 hours without this thing and I already miss it...unlike other "noobs" who ask for help here, I actually tried on my own to get a solution but got nowhere.
View attachment 2012991
View attachment 2012994
Click to expand...
Click to collapse
Once you get into fastboot, unplug the cable and plug in a regular USB cable that came with the device, and try to restore with the System Restore Tool.
seokhun said:
Once you get into fastboot, unplug the cable and plug in a regular USB cable that came with the device, and try to restore with the System Restore Tool.
Click to expand...
Click to collapse
I tried and the System Recovery Tool does not detect the device. It stays at "waiting for device"
One step forward and two steps back
Okay each time I advance, I am stuck with a new obstacle. I got ADB working (can use its commands) but my device isn't detected when I use the command "adb devices." As mentioned before, in Device Manager > Other Devices, Kindle appears as Tate-PVT-08, updating that "driver" is no use, and here I am Kindle-less once again. This is like a nightmare. Had I caused this issue by flashing a rom, or second bootloader, I'd probably give up and say "oh well I read the warnings, went along and I messed it up." But the case is that I did nothing to cause this, it only ran out of battery which happened once before and that time there were no issues starting up. I've searched left and right, high and low but cant find a way to now get this thing detected so I can see what I can do next. Can anyone please give me a list of what to do to get out of this Kindle Fire logo?
Since you can go to fastboot.
I suggest you check if you have the fastboot drivers installed since you said that you see the <waiting for device>. After that use the KFHD SRT
Sent from my air conditioner unit running CyanogenMod
dugoy13 said:
Since you can go to fastboot.
I suggest you check if you have the fastboot drivers installed since you said that you see the <waiting for device>. After that use the KFHD SRT
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Yeah I tried searching for drivers for it and I can't find them. I found one Chinese/Japanese website mentioning updating the driver by using the "android_winusb.inf" found inside sdk > extras > google > usb_driver, but when I try updating it with that file edited as they described, all I get is an error mentioning that the driver WAS found, but is likely corrupt or the victim of tampering. (which technically I did tamper with it by adding the lines I was told to add to the file from the following website)
http://translate.google.com/translate?hl=en&sl=ja&u=http://ameblo.jp/conpe/entry-11437514328.html&prev=/search%3Fq%3DTate-PVT-08%26biw%3D1366%26bih%3D673
Is there any specific place/thread with the drivers to the fastboot?
If you installed the Kindle Fire adb drivers,
Boot the kindle to fastboot mode and plug it in your PC
Then go to device manager, you will see a name called kindle with a yellow triangle beside it. After that right click on it and press "Update Device Drivers", then click "Let me pick", then click "browse installed drivers" then find the name Kindle Fire in the list and press next. You should see two things, Android ADB Interface and Android Composite ADB Interface. Click the Android Composite ADB Interface and press install/next. After that the drivers should be installed
Sent from my air conditioner unit running CyanogenMod
Possibly Solved
Crossvxm said:
Yeah I tried searching for drivers for it and I can't find them. I found one Chinese/Japanese website mentioning updating the driver by using the "android_winusb.inf" found inside sdk > extras > google > usb_driver, but when I try updating it with that file edited as they described, all I get is an error mentioning that the driver WAS found, but is likely corrupt or the victim of tampering. (which technically I did tamper with it by adding the lines I was told to add to the file from the following website)
Is there any specific place/thread with the drivers to the fastboot?
Click to expand...
Click to collapse
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
CVanB said:
Solutions
1. What root tool did you use? A: if it was bin4ry type in notepad 0x1949 and save it to .android under users/Your User/.android
Like for me it would be users/chris/.android and you would save it to .android dir. if you dont have an .android dir. make one. Then see if your device is reconized as android composite adb device or at least kindle. Also try installing drivers for the kindle and uninstall the drivers and reinstalling them
2. I had a similar problem i rooted my kfhd and it became so slow it wouldnt turn on eventully after 30min. it turned on but was so slow when i sided to unlock it took five minutes. I also i tried rerooting without unroot. it worked so i used binary's root like i was unrooted and my kindle was back again. it turned out when i rooted i only had 50% battery and you NEED to have at least 90%. this also fixed any audio issues.
3. your original kf cord that came when shipped maybe shot and you may need a new one if it wont charge like someone else said "android devices need at least 20% battery to turn on". i dont find this to be true i need at least 5% but find a new cord and charge it seee if it works then.
4. if it turns on the the kindle fire logo flashes quicker then you can boot into recovery. the recovery screen should be a red warning sign saying reboot or restore click restore.
5. with a home made factory cord try booting into recovery mode and follow solution (4).
6. what root apps did you have on the device fire flash? A: fire flash will not work with the new 7.4.1 ota update
Let me know from there if you get your kindle working if no i can supply more solutions based on your answers and the reactions from my solutions.
I can also supply drivers and root tools
Click to expand...
Click to collapse
Yeah I used "Root_with_Restore_by_Bin4ry_v26." The .android folder has adb_usb.ini and inside it is named "0x1949" although I'm no sure sometimes I check it and it comes with extra words like "do not edit this" and extra numbers. I'm guessing maybe SDK did it? But it was fine, its battery just died, then the thing won't come on no matter how much I put it to charge. I don't have that original cable, as this was given to my by a friend who no longer needed it.
When I put the device into fastboot, that's where I'm stuck. I see it stays on the fastboot logo, but no matter how many times I connect it to any USB, my computer does detect it as a device being connected, but ADB or any other related software always says (waiting for device) and I cant make any moves.In the device manager, its neither Kindle, or Android ADB Interface, just Tate-PVT-08.
I will try to uninstall and reinstall things just to make sure
An other option
Crossvxm said:
Yeah I used "Root_with_Restore_by_Bin4ry_v26." The .android folder has adb_usb.ini and inside it is named "0x1949" although I'm no sure sometimes I check it and it comes with extra words like "do not edit this" and extra numbers. I'm guessing maybe SDK did it? But it was fine, its battery just died, then the thing won't come on no matter how much I put it to charge. I don't have that original cable, as this was given to my by a friend who no longer needed it.
When I put the device into fastboot, that's where I'm stuck. I see it stays on the fastboot logo, but no matter how many times I connect it to any USB, my computer does detect it as a device being connected, but ADB or any other related software always says (waiting for device) and I cant make any moves.In the device manager, its neither Kindle, or Android ADB Interface, just Tate-PVT-08.
I will try to uninstall and reinstall things just to make sure
Click to expand...
Click to collapse
1. Also, ive heard this but it could be the case
The usb your using for fastboot could be using the name of an other device that was used for charging or connecting to the computer. Try connecting the other device to the usb and eject it properly then connect the kindle.
2. also using a fastboot cable that is specifed for the kindle could help.
3. the one thing i dont understand is the kindle isnt bricked so the firmware must be corrupted possibly because of the ota update to 7.4.1 in other words you rooted durring the ota update or tried to use superuser during an update.
4. also the last time you turned it on fully did it say updating kindle or anything like that. lastly you could have lost power when the update was installling or was about to install this could corrupt the data.
CVanB said:
1. Also, ive heard this but it could be the case
The usb your using for fastboot could be using the name of an other device that was used for charging or connecting to the computer. Try connecting the other device to the usb and eject it properly then connect the kindle.
2. also using a fastboot cable that is specifed for the kindle could help.
3. the one thing i dont understand is the kindle isnt bricked so the firmware must be corrupted possibly because of the ota update to 7.4.1 in other words you rooted durring the ota update or tried to use superuser during an update.
4. also the last time you turned it on fully did it say updating kindle or anything like that. lastly you could have lost power when the update was installling or was about to install this could corrupt the data.
Click to expand...
Click to collapse
It updated randomly from 7.3.1 to 7.4.1 on May 30th (aprox 5 days ago) that same day I rooted it after it erased my root with the same guide I used for 7.3.1 that was based on 7.4.1. It worked perfectly, but around that time I never let the battery die during those few days. In record, I've only let the battery die once before, this time makes it 2 times total. The cable I made is from a Samsung, I made it using instructions on making it for the Kindle Fire HD 7 specifically, although as I've heard, you may be right. But when I research that "device" (Tate-PVT-08) on google, the Kindle Fire pops up in search results, but none are really helpful. Example, the bottom of this thread I'm posting below, people have similar issues and the "Tate" thing:
http://forum.xda-developers.com/showthread.php?t=1930656
Same problem
I´m noob, certainly, but I spend many hours searching and reading (dealing with the problem that english is not my native language as you could see) but I think I have a similar problem as the described here with the difference that my battery was ever up 50 - 55%. I have post a threat a few days ago where I think it would be pertinent and I´m waiting for a response.
My big problem (I think) is that I have ADB disabled on my KFHD as I post here: http://forum.xda-developers.com/showthread.php?t=2308788 I´m now trying Seokhun guide but I´can´t make it for this reason.
Thanks for any idea.
dugoy13 said:
If you installed the Kindle Fire adb drivers,
Boot the kindle to fastboot mode and plug it in your PC
Then go to device manager, you will see a name called kindle with a yellow triangle beside it. After that right click on it and press "Update Device Drivers", then click "Let me pick", then click "browse installed drivers" then find the name Kindle Fire in the list and press next. You should see two things, Android ADB Interface and Android Composite ADB Interface. Click the Android Composite ADB Interface and press install/next. After that the drivers should be installed
Sent from my air conditioner unit running CyanogenMod
Click to expand...
Click to collapse
Crossvxm, did you ever try what dugoy said, that should work for getting your device recognized?
---------- Post added at 10:03 PM ---------- Previous post was at 09:45 PM ----------
Elgari said:
I´m noob, certainly, but I spend many hours searching and reading (dealing with the problem that english is not my native language as you could see) but I think I have a similar problem as the described here with the difference that my battery was ever up 50 - 55%. I have post a threat a few days ago where I think it would be pertinent and I´m waiting for a response.
My big problem (I think) is that I have ADB disabled on my KFHD as I post here: http://forum.xda-developers.com/showthread.php?t=2308788 I´m now trying Seokhun guide but I´can´t make it for this reason.
Thanks for any idea.
Click to expand...
Click to collapse
Elgari, if I get your situation correctly, you won't be able to use adb. Adb can only be used when you're in recovery or when you're booted. You'll have to go with fast boot. If you can get into fast boot, then you can use the kindle SRT tool from the development thread. Do you have a factory cable?
DroidIt! said:
Crossvxm, did you ever try what dugoy said, that should work for getting your device recognized?
---------- Post added at 10:03 PM ---------- Previous post was at 09:45 PM ----------
Elgari, if I get your situation correctly, you won't be able to use adb. Adb can only be used when you're in recovery or when you're booted. You'll have to go with fast boot. If you can get into fast boot, then you can use the kindle SRT tool from the development thread. Do you have a factory cable?
Click to expand...
Click to collapse
Yeah I tried that and even my own little invention. But I give up. I'm just scrapping the whole project. Its useless, I'll just have to get me a Nexus 7, I don't want to get stuck with another brick. Amazon is pretty ridiculous. Their system is unstable, their device is crap. I have read about problems like this on these things everywhere. Whether its the charging refusal, 0% battery, not starting up, not having Google Play, root headaches and nearly impossible restore scheme, these things are well worth their cheap price.
Shame for you to scrap it, thought I'd throw in my two cents. I've never put mine in fast boot so I don't know if it supposed to show up as Tate in the task manager but I do know if you run fast boot with the get var product it should report something back as Tate so I assume that what you see is good, thing I'd like to ask is did the drivers install for Tate, and if not can u tell me in the tates properties what its hardware id's are? I think you probably need to mod the driver, or you said you did but I don't know if you installed it, usually u have to have a unsigned driver, and I think if it gives u trouble about not letting you install it because its been tampered with you just have to delete or rename the cat file in the directory the drivers are in, then it will just say they are unsigned and prompt you to install them anyways. If you happen to be on windows 8 this probably will get more complicated, because u have to boot up in a special mode to install unsigned drivers
Sent from my Amazon Kindle Fire HD using xda app-developers app
stunts513 said:
Shame for you to scrap it, thought I'd throw in my two cents. I've never put mine in fast boot so I don't know if it supposed to show up as Tate in the task manager but I do know if you run fast boot with the get var product it should report something back as Tate so I assume that what you see is good, thing I'd like to ask is did the drivers install for Tate, and if not can u tell me in the tates properties what its hardware id's are? I think you probably need to mod the driver, or you said you did but I don't know if you installed it, usually u have to have a unsigned driver, and I think if it gives u trouble about not letting you install it because its been tampered with you just have to delete or rename the cat file in the directory the drivers are in, then it will just say they are unsigned and prompt you to install them anyways. If you happen to be on windows 8 this probably will get more complicated, because u have to boot up in a special mode to install unsigned drivers
Sent from my Amazon Kindle Fire HD using xda app-developers app
Click to expand...
Click to collapse
Thanks for trying. But if you'd see what I did to the poor thing out of frustration you'd call me nuts. Its really not coming back now...
I have a Motorola Droid 4. I installed SafeStrap recently on it and installed CM11 to the stock rom (mistake I know). I kept running into issues and I finally sorted all of them out and I decided I wanted to restore back to stock and then install CM11 to a rom slot. I come to find out that I am unable to restore my stock backup as it keeps failing. So I then decide I am going to just go ahead and restore my CM11 backup to rom slot 1 and make it the active boot rom, but that turned out to fail to for whatever reason. I reboot my phone several times and received the Motorola logo followed by the dreaded Android on his back with his chest opened up and the exclamation point/triangle coming out of it.
So I gave in and decided to just go ahead and use the Droid Razr Utility that I have used before to reinstall the stock ROM and start all over. During this process everything seems to be going fine. I am able to boot into Fastboot, the PC recognized the phone and can see it. I then start the recovery by doing option "2" to wipe and install. My phone reboots a couple of times and then comes to the point of another reboot but the phone never turned back on. I've tried many button combinations to get this to boot up but nothing seems to respond. I have attached a screenshot of what the Droid Razr Utility showed when the phone was attempting to restart but never did.
I purchased a Fastboot cable to hopefully get me to the point of my PC recognizing the phone but that does not seem to work. When I plug in my phone Windows never detects anything. I removed all the drivers and nothing. If I plug the phone into a charger the Green light flashes for a split second. If I plug my phone into the computer the Green LED light will stay solid. According to Motorola this indicates that the battery is fully charged. I've tried reseating the battery to no avail.
So based on the information above and the attached screenshot, is my Droid 4 bricked and unusable now?
After doing a bunch of research I think I indeed bricked my phone. Since the ROM I tried flashing to my phone was not for the Droid 4 but rather the Droid RAZR, it looks like my phone is dead. I was hopeful and assumed that this would be able to be reversed by hooking up to a PC but apparently that is not the case. Perhaps I tripped the eFuse or something which is causing the boot loader to not initiate. I guess I need to get a new phone now unless someone has a nifty trick up their sleeve to get the phone accessible via a computer.
You are going to need a Team Black Hat cable, aka fastboot cable. Then plug it in, and run RSD Lite using the DROID 4's fastboot files. You can find the fastboot files at this website below. Download the one that matches the version of Android you have.
LINK: http://sbf.droid-developers.org/phone.php?device=11
Ordered a factory cable on eBay; we shall see; thanks for the information
Even though my computer does not seem to recognize my phone when I plug it in. For example, I plug it in using the Fastboot cable and I never heard a sound from my computer like it knows something was just plugged in?
I did buy a fastboot cable from bluvector on amazon but that didn't seem to do anything for me. My Droid 4 still has a black screen and plays dead:crying:
bean1975 said:
Ordered a factory cable on eBay; we shall see; thanks for the information
Click to expand...
Click to collapse
Are you having the same problem as me? Your Droid 4 will not turn on and just sits at a black screen when you push the power button?
@sd_shadow you out there? I would love to hear your advice on my issue to see if there is any hope for my phone.
I received a FastBoot Cable but when I plug it in nothing happens. I also have a Kindle Fire HD and plugged the fastboot cable into it and powerd it down and back on and it boots normally. I'm wondering if the fastboot cable is faulty? Also I think my droid 4 may be completely shot since pushing the power button does nothing for me so I don't know how I could get back into Fastboot mode, unless a confirmed working fastboot cable will force the phone to boot and enter fastboot mode?
BigPapaGotti said:
@sd_shadow you out there? I would love to hear your advice on my issue to see if there is any hope for my phone.
I received a FastBoot Cable but when I plug it in nothing happens. I also have a Kindle Fire HD and plugged the fastboot cable into it and powerd it down and back on and it boots normally. I'm wondering if the fastboot cable is faulty? Also I think my droid 4 may be completely shot since pushing the power button does nothing for me so I don't know how I could get back into Fastboot mode, unless a confirmed working fastboot cable will force the phone to boot and enter fastboot mode?
Click to expand...
Click to collapse
Motorola Devices will be powered by the Fastboot/Factory cable, when you connect the Droid 4 to pc via a fastboot cable, it should power on but you may need to select fastboot mode in bootmenu options.
Not sure about the kindle HD, but an Original Kindle Fire 1st gen, will boot direct to fastboot mode, when connected to a Fastboot cable
Both require Hardware cable and device to be working correctly.
sd_shadow said:
Motorola Devices will be powered by the Fastboot/Factory cable, when you connect the Droid 4 to pc via a fastboot cable, it should power on but you may need to select fastboot mode in bootmenu options.
Not sure about the kindle HD, but an Original Kindle Fire 1st gen, will boot direct to fastboot mode, when connected to a Fastboot cable
Both require Hardware cable and device to be working correctly.
Click to expand...
Click to collapse
According to the description on the amazon site that I bought this cable from it shows the cable as being able to support Kindle Fire HD, that is why I am thinking that this cable is faulty, since it is not working on my droid nor is it working on my Kindle Fire.
I am thinking on buying a different one and returning my current one but i'm hesitant to do so. I have my doubts that this will allow my Droid 4 to boot up and/or be recognized by my computer. Since I get no response with the Vol-, Vol+, Power button combinations i'm thinking this is hard bricked because of the wrong files I flashed to it.
Before I made this mistake the phone was at least responsive showing the android/exclamation point screen. Then my dumbass ran the wrong flashing utility and that was all she wrote.
Do you think there is hope for my my phone even though the power button yields no response? If the fastboot cable will at least allow my phone to be recognized by my computer then I think i could save it, but that is where i have my doubts, but would love to try.
BigPapaGotti said:
According to the description on the amazon site that I bought this cable from it shows the cable as being able to support Kindle Fire HD, that is why I am thinking that this cable is faulty, since it is not working on my droid nor is it working on my Kindle Fire.
I am thinking on buying a different one and returning my current one but i'm hesitant to do so. I have my doubts that this will allow my Droid 4 to boot up and/or be recognized by my computer. Since I get no response with the Vol-, Vol+, Power button combinations i'm thinking this is hard bricked because of the wrong files I flashed to it.
Before I made this mistake the phone was at least responsive showing the android/exclamation point screen. Then my dumbass ran the wrong flashing utility and that was all she wrote.
Do you think there is hope for my my phone even though the power button yields no response? If the fastboot cable will at least allow my phone to be recognized by my computer then I think i could save it, but that is where i have my doubts, but would love to try.
Click to expand...
Click to collapse
If you flashed Droid Razr firmware, yes it's bricked. or haven't seen anyone recovery from that yet.
@bean1975, did you have any luck with getting the fastboot cable to recover your phone?