Database Develop

[Q] Kindle Fire HD 7 bricked?

I have a conglomeration of issues with my Kindle Fire HD 7. I'm currently in the process of ordering a factory cable from SkOrPn, but wanted to make sure there are no other avenues for me to attempt.
I'm very noob here, so bear with me. I've searched around, and attempted all the fixes that I've found, but for some reason, none are working.
My KFHD7 is currently stuck at the boot logo, non-animated. It came back to my company this way, so I'm not sure exactly what the person that had it before me was attempting to do with it. If I plug it into my PC, with Windows 8 Pro, I do NOT hear anything that tells me that the computer recognizes that the device is connected. I also do NOT see the device in the Device Manager. I attempt to install the drivers from the KFU, but for some reason, those fail every time.
I've installed Ubuntu, to attempt Soupkit, and Firekit. It isn't detected there, either.
Do I have any other options, or is a factory cable the way to go? Also, if/when I order the factory cable, will my computer then be able to detect the KFHD7?
I'm sorry if this question has been answered a hundred times already, but after searching for 3 days, and attempting everything I saw, I've reached the end of my rope.

Boot into the Ubuntu that you have SoupKit installed (will eliminate Windows driver problems), open a terminal and enter the following:
Code:
fastboot -i 0x1949 getvar product
Then reboot (hold power button for 10 seconds) when you see "waiting for device". That will get you into fastboot. From there you can flash a system.img and restore your device. Onemelia has a system.img restore tool in the HD7 dev forum that has a system image included so check it out.
[Edit:] Considering you don't know exactly what was done to the device, you should probably restore the stock recovery and boot partitions too. I've had situations where I've installed Hashcode's stack override, along with the custom boot and recovery images and my device acted the same way. Since the stack is on the system partition, overwriting it with a new system partition and leaving the custom boot and recovery partitions in place would presumably put the device in a hard bricked state, from which there is no recovery.

Will it be a problem that I have Ubuntu 12.10 installed, rather than 12.04 that you reference? Maybe that was half of my issue there.

Ok, scratch my last. Removed 12.10, and put 12.04 on instead. I did as you said, and after initial reboot after the fastboot command, it's still sitting at waiting for device. It's been about 3 minutes. Advice?

honberiz said:
Ok, scratch my last. Removed 12.10, and put 12.04 on instead. I did as you said, and after initial reboot after the fastboot command, it's still sitting at waiting for device. It's been about 3 minutes. Advice?
Click to expand...
Click to collapse
Get the cable. It's worth way more then the price. After you get it, check out the first aide link in my signature. Good Luck!

I was actually JUST reading about your program. To perform a system restore, I'd need a clean backup, wouldn't I? This came to me borked, so I don't have a backup of it. Are there backups that are available for download?

honberiz said:
I was actually JUST reading about your program. To perform a system restore, I'd need a clean backup, wouldn't I? This came to me borked, so I don't have a backup of it. Are there backups that are available for download?
Click to expand...
Click to collapse
Onemelia's system.img restore tool in the development section has a system image...I'm not sure about the boot and recovery images though. If not, PM me and I'll send you copies.
As far as which version of Ubuntu, it shouldn't matter. The key packages are 'dpkg' which comes with all Debian based distros that I know of, and 'apt-get' which comes standard on all Ubuntu based distros I believe, so you should be fine either way. If you're using a 64bit install, I'd suggest you switch to a 32bit install. And make sure you aren't using a USB 3.0 port. As a matter of fact, you should probably switch to a dedicated usb port rather than a hub. A good way to check to see if Linux can even see your device is with the 'lsusb' command...you should see a device called "Lab 126".

Failed Root - Boot Loop

Hello everyone, about five hours ago I was going through the process of rooting my Moto X 2014 Pure (UK). Unfortunately it seems to be stuck in a boot loop. I've crawled through forums but to no avail. Now it's 6:00am and I'm having a slight mental breakdown and would really appreciate some help.
notes:
-The phone stays stuck on the watery 'M' logo that appears after the boot animation.
-Unlocking the bootloader went fine
-had trouble installing the android SDK since I ran out of space on my hard-drive, however the installation log notes that the necessary files were successfully downloaded after I made some space.
-I'm not running TWRP or any equivalent. The only thing I can access is the standard fastboot screen thing.
-I think made two errors with my first attempt at rooting: I forgot to type 'boot' after fastboot and I also hadn't uncompressed the zip folder that the img was contained in (it was CF Root incidentally). The command terminal came back with information alluding to it having done something but the device didn't reboot, so i'm unsure if it did.
-I tried to rectify this by installing different root imgs but the phone still won't boot.
I'm really unsure as to what to do. My guess is that I need to sideload a factory img of some sort. I've sent of for the official img from the Motorola website and am anxiously awaiting a reply but I wondered if anyone knew of any alternatives? All this hassle just so I could run some xposed modules :crying:

SexyEgg said:
Hello everyone, about five hours ago I was going through the process of rooting my Moto X 2014 Pure (UK). Unfortunately it seems to be stuck in a boot loop. I've crawled through forums but to no avail. Now it's 6:00am and I'm having a slight mental breakdown and would really appreciate some help.
notes:
-The phone stays stuck on the watery 'M' logo that appears after the boot animation.
-Unlocking the bootloader went fine
-had trouble installing the android SDK since I ran out of space on my hard-drive, however the installation log notes that the necessary files were successfully downloaded after I made some space.
-I'm not running TWRP or any equivalent. The only thing I can access is the standard fastboot screen thing.
-I think made two errors with my first attempt at rooting: I forgot to type 'boot' after fastboot and I also hadn't uncompressed the zip folder that the img was contained in (it was CF Root incidentally). The command terminal came back with information alluding to it having done something but the device didn't reboot, so i'm unsure if it did.
-I tried to rectify this by installing different root imgs but the phone still won't boot.
I'm really unsure as to what to do. My guess is that I need to sideload a factory img of some sort. I've sent of for the official img from the Motorola website and am anxiously awaiting a reply but I wondered if anyone knew of any alternatives? All this hassle just so I could run some xposed modules :crying:
Click to expand...
Click to collapse
First thing I guess is installing a custom recovery. I recommend TWRP. Try this link to get the zip http://www64.zippyshare.com/v/HPPiFhly/file.html
Unzip the file on your pc.
Take the device to fastboot screen and plug it on pc.
Open the Instalador.bat file and click Enter until it's fully installed.
Then, get back to the fastboot screen and try to open the recovery.
---------- Post added at 01:36 PM ---------- Previous post was at 01:36 PM ----------
Let me know it that works for you.

So I've solved the problem but just figured I'd share the solution; basically don't use the terminal just run the bat file (assuming the img has one). Having rooted all my previous phones I hastily emulated the same process neglecting to notice the extremely convenient bat file included in the folder. Never could get TWRP to flash though. Although I could boot into it using: fastboot boot 'recovery'.img A little tedious but certainly functional. Once I had a working phone again I flashed TWRP using the Flashify App which I was a bit dubious about but it seems to have worked absolutely fine.
So yeah, silly oversight really but at least my phone turns on now; so that's nice. Cheers for the help though fhreire, although I couldn't get that recovery you linked to to work the fact it installed via a bat file is what lead me to find the solution I needed.

[Q] No OS, Stuck in BootLoop/Fastboot, with TWRP, No Download Mode, ADB don't work

I've had my Verizon LG G2 for almost a year and mistakenly upgraded to Lollipop. I researched downgrading to KitKat and it looked safe; I had dual booted my HP Touchpad with a similar process.
I tried rooting with ADB, but it was giving me fits. I used the LG One Click Root Tool. It worked fine. (Running on Windows 7.)
I installed TWRP v2.8.5.1, and downloaded a stock version of KitKat 4.4.4. (I'll admit, at this point, I had looked at multiple guides. Many had missing links or dead ends, but they were all about the same, and always stock.) I followed instructions on clearing and wiping caches, etc. I believe the exact ROM I tried to install was VS98011A_01.zip. It didn't work. It gave the error:
"assert failed: run_program("/tmp/loki.sh") ==0
E: Error executing updater binary in zip"
I looked for more ROMs and tried ParanoidAndroid "pa_g2-4.0-ALPHA-20131203-vs980.zip". At this point, I started to worry and tried installing the Gapps file I downloaded with the stock ROM, and it installed with no problems.
I then tried to install a newer version of TWRP "twrp-2.8.6.0-vs980.zip". (Again, I hadn't really found any great guides at this point, especially to fix my problem, so I was assuming there was something wrong with my ROMs.) It didn't work, and I tried to install Cyanogen Recovery because I ran across it and remembered it from my HP Touchpad. "cm-10.2-vs98012b.zip" did not work, and gave the error above.
I looked for Loki issues and tried downloading a fresh Loki (sorry, I don't have the link) folder and replaced all the files in the original KK .zip I tried. Same loki error. (Sometimes I'll get a "sysMapFile" error, but not often. At this point, I'd dragged a lot of things over to try to install and get anything to work.)
At this point, I tried the following:
http://forum.xda-developers.com/showthread.php?t=2448960
http://forum.xda-developers.com/showthread.php?t=2451696 (as well as a similar one by downloading a laf.img)
http://forum.xda-developers.com/showthread.php?t=2797190
http://forum.xda-developers.com/showthread.php?t=2432476
http://hackerspace.lifehacker.com/how-to-install-a-rom-via-sideload-1505153925
http://forum.xda-developers.com/showthread.php?t=2318497
http://www.androidayos.com/2014/10/06/fix-bricked-lg-g2-stuck-logo-twrp-bootloops-download-mode/
http://forum.xda-developers.com/showthread.php?t=2448960
There were definitely some more links I used but these were the most promising and the ones I still have open.
Several of the LGFlashTools were very close to working, but there were several issues:
1. I can't get it into Download Mode, as it gives a boot certification error.
2. There were some problems with the phone not showing up in Device Manager under "Ports" with COM41, and I thought I had largely resolved that issue. (Depending on the article I was looking at.)
3. Drivers, I'm not sure if they're an issue; I've downloaded several, and installed them, including 2.0 and a 3.1.
ADB does not recognize my device, as I've tried sideloading, although I can still drag and drop files. (I believe I pushed a file into the device early on and it worked though.)
4. Fastboot recognizes there's a device and can boot it via CMD but will not give a number when I use "fastboot devices". I've researched some flashing via Fastboot, and tried flashing the original KK .zip with it, but it said there wasn't enough space. I have about 14GB left on a 32GB device, however.
I hope I've provided enough information, because I've researched and tried so many ways to unbrick it, short of physically opening the phone as suggested here: http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Any advice or suggestions would be greatly appreciated. I would love to know what I did wrong, because I know custom ROMs would be a great alternative to dealing with Lollipop until I can upgrade over a year from now.

[MOTO X1 - BRICKED] I think I got the master level bricked.

Ok, this is only for the Jedi masters.
I have a Moto X (1st gen - XT1058) bricked. However I think I got the master level bricked.
I was using the ROM Retail BR 4.4.4 and I upgraded to version 5.1 via OTA. All went quiet until the unit began to catch on and off yourself. I reinstalled version 5.1 via RSD Lite smoothly. The device worked for a few weeks but after some time the same problems again.
Until the phone died. Do not leave the boot screen.
I thought it was something not too bad, because I could still access the Fastboot (AP Fastboot Flash Mode (S) 30.BE). However I can not get into Recovery mode and something else I do return with errors involving:
Failed to read signature is aboot partition
Boot up failed
The solutions I found on the internet I've tried:
Reinstall the original ROM by RSD Lite (and earlier also suppressing gpt.bin)
- Always fails when the application tries to apply flash partition gpt.bin. If I delete this line in the XML file, the failure persists, but the next line of execution.
Use original gpt.bin files, boot.img, system.img and recovery.img and try to install them through the mfastboot fastboot command and Windows Terminal 7 (32 and 64bit).
Use a file blankflash & the qflash.exe ... command from the Windows terminal. Can install the drives and recognize the specific port of the device, but the process does not continue.
Does anyone have any light around? Something different than I've ever tried?
My daughter is missed to watch Pocoyo in Youtube. It was the only thing that calms my little child.
Help me! :crying:

I bricked my Moto X 2013 VZW Dev Edition - any chance of revival?

I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?

At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.

PiArc said:
At this point I am able to get into fastboot after bricking my XT1060DEV in a similar way. Follow the guide as best as you can in this post. Toward the end of that thread you can see the sequence of events that led me to at least fastboot mode.
Awaiting a response from someone who might know which gpt.bin and bootloader I can flash to have more than a blank phone. I'll try to keep you updated.
EDIT:
You might find it easiest to get QHUSB set up using this guide. This guide has been superseded by the previously posted one, but some people still report success following it.
Click to expand...
Click to collapse
I may not have a chance for a few days, but I will try this. I did try to download the software on the second link you provided and some of the links on that page were broken.

I'm not going to lie, navigating those threads is harsh.
Towards the end of the first linked thread you can see a post with what ended up getting me into fastboot. It might be a decent little roadmap to guide you in the right direction (plus, I think the files I indicate in that particular post are all still up).
Keep us updated!

ohioDroid said:
I'll start out by saying I was careless and had not read various threads before flashing things and causing my issues. I've already bought a replacement phone but I'd like to see if there's any chance to revive the Moto X or not.
What happened:
I had unlocked the bootloader years ago. I was running the (mostly) stock Lollipop 5.1 with XPosed, and got noticed of a security update.
After fully charging the battery, I flashed stock recovery over my custom recovery (TWRP) and then, without thinking, got the latest image from Motorola without realizing it was a 4.4.4 image.
I flashed the system partition using this image thinking it would remove SU and that I could install the update - this soft-bricked the phone when I tried to boot.
Too late, but at this point I re-flashed TWRP and ran a backup. I used adb to extract the backup and my other files from the /sdcard partition.
Factory Reset. The phone boot up at this point.
I tried flashing the logo, gpt.bin (I forgot that Lollipop changed how partitioning worked) and then did another Factory Reset. Phone boots fine.
I then tried restoring the data from my nandroid backup. Rebooted once, and phone seemed to start. And then it went black.
At this point, the phone does not appear to boot at all. I can't use Vol Down + Power to boot into Fastboot, and if I connect to a computer, it does not see the device... USUALLY.
If I connect via USB to my Windows computer, and try to boot into Fastboot, the green LED behind the volume will flash once and my computer will signal the "Hardware connected" sound. I can try to run 'adb reboot bootloader' but adb reports that it doesn't see any devices. My system events note a USB Input Device was added but don't get any further. Within 5 seconds, the "hardware disconnected" sound fires. About 20 seconds later, this will repeat on its own.
I just tried making a fastboot cable from a spare micro usb cable... I may have done it wrong - but it does not seem to have had any effect. The result is the same. It's possible I didn't solder the connection well, though (it was difficult exposing the terminals on my particular cable).
The screen is always black and never lights up in any way.
It kind of makes me think that the device is attempting to boot, fails, and cycles. Is there anything I can do?
Click to expand...
Click to collapse
Try reflashing twrp via fastboot, install custom ROM -OR- download latest XML for your variant flash via rsd lite or manual flash.
Note: When using the XML you will lose everything, including data on internal storage.
Hopefully this helps ?
Also, if your phone stays black it's likely the battery is dead. Leave it hook up for awhile or keep trying to boot into fastboot(while plugged into outlet, not PC) and leave it for a couple of hours, should charge.
I'm speaking from personal experience, just without having Xposed framework, lol.
Sent from my Moto X using Tapatalk