Related
Hey Guys,
I am sorry in advance if similar issue has been posted but I really need your help !
I just got my gtab and flashed with TnT Lite 4.4.0. I need to restore the original from factory. Now I am facing a problem, I can't go to the recovery mode because it stayed at viewsonic logo (not gtab). I can see the "recovery key detacted" at upper left corner but nothing else.
Please help me on back to restore the original or how can I go into the recovery mode to install/modify ?
I am just a new born baby and just step in this android world. any suggest is great help for me.
Thank you
Follow my link.
What happens if you hold only the power button for several seconds (10-30). Will your tab reboot? If it does what do you get then?
buchaneer.nl said:
What happens if you hold only the power button for several seconds (10-30). Will your tab reboot? If it does what do you get then?
Click to expand...
Click to collapse
Holding it for 10-30 seconds and then release will yield the same result as if you hold it for 5 seconds and then release. The gtab will turn off. To turn it on again, you need to hold the power button again.
Sorry for not stating the obvious What happens when you restart? Does it start up?
goodintentions said:
Holding it for 10-30 seconds and then release will yield the same result as if you hold it for 5 seconds and then release. The gtab will turn off. To turn it on again, you need to hold the power button again.
Click to expand...
Click to collapse
Hey Goodintentions if you want a monopoly on answering questions go right ahead. My intentions were only to help. Maybe you have more of a vested interest
Haha, I just temporarily have a lot of free time due to almost dying but now suffering from a massive infection. Right now, moving my fingers to type is about the only thing I can do comfortably.
Think of it this way. While I was 40 feet in above ground hand sawing a large branch off, it got loose, caught one of the ropes on its way down, the rope caught my arm, and dragged me down with it. Hanging on for my dear life, I used my other hand to grab the hand saw still dangling and cut the rope freeing my arm. The damn thing took a large chunk of my skin with it. I think it stretched my left arm out several inches.
Anyway, my dumbass decided it wasn't serious enough to go to the doctor. Patched up everything by myself and now I have an massive infection, a very sore arm, and lots of free time.
Edit.
Not to mention that asshole neighbor of mine who called the city to complain that I left the branch out violating city code.
How you get better...
goodintentions said:
Haha, I just temporarily have a lot of free time due to almost dying but now suffering from a massive infection. Right now, moving my fingers to type is about the only thing I can do comfortably.
Think of it this way. While I was 40 feet in above ground hand sawing a large branch off, it got loose, caught one of the ropes on its way down, the rope caught my arm, and dragged me down with it. Hanging on for my dear life, I used my other hand to grab the hand saw still dangling and cut the rope freeing my arm. The damn thing took a large chunk of my skin with it. I think it stretched my left arm out several inches.
Anyway, my dumbass decided it wasn't serious enough to go to the doctor. Patched up everything by myself and now I have an massive infection, a very sore arm, and lots of free time.
Edit.
Not to mention that asshole neighbor of mine who called the city to complain that I left the branch out violating city code.
Click to expand...
Click to collapse
Sorry to hear of your accident.
You have been very helpful to me. Thanks.
Hard-bricked?
Hello everybody,
I had VEGAn-GE-7.0.0-RC1-Harmony-signed flashed into my gtablet and I tried to flash update-smb_a1002-4349-user.
I've got a error (something similar to: bootloader not a command...) and after restart the tablet is bricked.
When I enter into recovery mode, I have the two messages
Detect a recovery key pressed
Booting recovery kernel image
and the tablet stop there. No changes in the screen and no USB recognition.
So I can't fix that with nvflash. It seems that the recovery kernel image (if there is one) is corrupted.
Do you know a solution for this case?
Thanks in advance
fogamz said:
Hello everybody,
I had VEGAn-GE-7.0.0-RC1-Harmony-signed flashed into my gtablet and I tried to flash update-smb_a1002-4349-user.
I've got a error (something similar to: bootloader not a command...) and after restart the tablet is bricked.
When I enter into recovery mode, I have the two messages
Detect a recovery key pressed
Booting recovery kernel image
and the tablet stop there. No changes in the screen and no USB recognition.
So I can't fix that with nvflash. It seems that the recovery kernel image (if there is one) is corrupted.
Do you know a solution for this case?
Thanks in advance
Click to expand...
Click to collapse
You flashed a 1.2 bootloader ROM over a 1.1 bootloader ROM using ClockworkMod. That is a sure recipe for problems. You will have to use nvflash to fix it. Go to Goodintentions "GTablet for Dummies" website. Don't be surprised if you don't see the VS Birds logo (or anything else) when you try to get into APX mode. Many people that have done this don't.
Thanks K J Rad,
Yes, I've tried cod triple red unplugging the batteries
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
http://forum.xda-developers.com/showthread.php?t=1118087
all the night and still no change.
The screen stays with the birds logo and with the two sentences (... booting recovery kernel image), no black screen as described in NVFlash procedure, and my PC doesn't recognise the USB device (not listed with lsusb in Ubuntu and no identification in windows), so I can't nvflash.
I'm going to try to drain the batteries but it seems that the kernel image is corrupted and the sw is not reseted when power off.
Hard case?
Many thanks
fogamz said:
Thanks K J Rad,
Yes, I've tried cod triple red unplugging the batteries
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
http://forum.xda-developers.com/showthread.php?t=1118087
all the night and still no change.
The screen stays with the birds logo and with the two sentences (... booting recovery kernel image), no black screen as described in NVFlash procedure, and my PC doesn't recognise the USB device (not listed with lsusb in Ubuntu and no identification in windows), so I can't nvflash.
I'm going to try to drain the batteries but it seems that the kernel image is corrupted and the sw is not reseted when power off.
Hard case?
Many thanks
Click to expand...
Click to collapse
Did you hold the Volume Down button as you were powering up?
many thanks
That's it.
I was allways pressing up. Sorry by the misundertunding and many thanks.
Regards
fogamz said:
That's it.
I was allways pressing up. Sorry by the misundertunding and many thanks.
Regards
Click to expand...
Click to collapse
Aha! You didn't follow my instructions properly. Goodness...
Added by edit.
Here is a screenshot of that portion of my instruction. Notice where the arrow is pointing at.
Are you restoring to stock to do an RMA?
goodintentions said:
Aha! You didn't follow my instructions properly. Goodness...
Added by edit.
Here is a screenshot of that portion of my instruction. Notice where the arrow is pointing at.
Click to expand...
Click to collapse
Hi, I am looking a zip file
gtab.nvflash.1.2.branch.20110617.zip
the file is 99.41 MB but I ALWAYS stock at 9.9 MB
Is it any available file I can download ??
Please help
What country are you from? I'll host it elsewhere it it makes a difference for you.
Added by edit.
Hang on. I host no such file on my website. Go to my website linked in signature and try to download that nvflash file.
goodintentions said:
What country are you from? I'll host it elsewhere it it makes a difference for you.
Added by edit.
Hang on. I host no such file on my website. Go to my website linked in signature and try to download that nvflash file.
Click to expand...
Click to collapse
I just try to download the nvflash with 1.2 branch with newer update. The nvflash1.2 zip and gtab.nvflash.1.2branch20110508.zip both stopped at 10.0 MB
Please help ! I am at Los Angeles area
Viewsonic G Tablet will not boot. Only APX mode works - 20110707
20110713- FYI. I re-posted the restore step information as a new thread and added some additional content on APX Mode and nvflash.
http://forum.xda-developers.com/showthread.php?t=1167944
Holy cow, man, that's some effort there for your wife. If it were me, I'd say "screw you, wife, here's a paperweight. Try to make it work since I screwed it up."
But seriously, I've said this before and I'm going to say it again. I'm constantly amazed at these rare cases of unrecoverable brickary that only a hand full of people get. And I have 3 gtabs to work with, not to mention thousands of visitors to my site.
So I have a bad feeling here. I was fixing my ad hoc problem and accidentally renamed my /system/bin folder to "bin - Copy" not sure how I did it, a finger swype n boom it was that way. Could not change it back. Rebooted and now I can't get passed the Eee Pad boot screen. Any one know how to fix this?
I've got a similar problem.
There should be a sollution where you start up, holding the powerbutton and volume up. You feel a vibrate and the screen stays black.
with this way you can connect your transformer, and access it. But I don't know how.
Windows reconiges the device as and APX (under linux as an Nvidia device) But I can't connect to it, don't have the drivers and so.
So is anyone knows how to access the prime trough this method, our problem could be solved using adb pulling and pushing these folders.
Greets
If you connect it to your computer can adb access it??
Nope. Going to try a couple more things this evening.
Sent from my PC36100 using XDA App
Well, I tried a bunch of different things: microsd recovery, wipe data, recovery, "up volume/pwr button", broke down n called Asus. So here's what happened in case anyone else comes across this thread: microsd method to flash firmware=nothing, anytime I entered recovery Andy laid down and opened his chest cavity and red triangle !, wipe data done. signature match=freeze up at that screen, no reboot. hard reset with paper clip=nada just reset to frozen eee pad screen. I have linux 11.10 and 10.04BT on another hdd so I booted to both b/c I read a post somewhere about booting the prime by holding up volume/pwr and its supposed to be some kind of nvidia diagnostic mode. Interestingly in windows it changed from an unknown MTP usb to APX device doing this, in Linux it never even came up either way. I don't know enough about this, so I tried searching and reading=nothing fruitful. I'm a Linux and ADB noob so I read and read and read some more, but after trying a few walk throughs, my Prime just seems to be dead. So I called Asus and played dumb, said it froze after trying to update to ICS. He walked me through these other steps I mentioned to no avail. Then he gave me an RMA# so I went ahead and mentioned the excessive light bleed and non-functioning GPS. He noted those issues and now I'm sending it in apparently. I was REALLY hoping to avoid this b/c this was my fault, but my experience with the Prime has prompted me to ad my 2 cents/rant in the general thread.
I wish this had a better outcome, but with the bootloader locked I and many others have been unnecessarily doomed to RMA.
Well that sucks big time... hope you get another soon
hoping to hear about an update to this other than sending it in. unfortunatley i have just done the exact same thing.
There are APX drivers in the dev section. My Prime changed from APX device to Asus Transformer prime APX mode when I installed them. After that I don't know what to do; I think we need an nvflash for the Prime or something.
Mine went into APX mode after the last OTA update failed and won't leave APX mode for anything, so I was looking for a way to connect to it to flash an update or something, but no luck so far. Maybe Asus will release a tool for us to fix a failed OTA update, would be a lot better than sending my tablet away for a month so they can do it.
I searched and searched for this too. Couldn't get anything to work.
As for an update, as of about a couple hours ago, looks like they are sending me a new tablet. Has a different serial number listed as "ready to ship" and states "original serial number: C1O....." which is the s/n of the tab I sent in.
So we'll see if this one comes with no light bleed and working gps. Don't think I'll be screwing this one up! Gonna be extra careful...
I was in the same situation, stuck. I tried everything you did as well and nothing. "Doktaphex" gave me this link http://forum.xda-developers.com/showpost.php?p=22743057&postcount=119 in my post and it worked perfectly. I was sooo damn happy to see Andy actually working instead of laying down when I entered RCK
Oops...shoulda read through. Hehe sorry bout that :/
That would've been just one more thing to try on top of all the other things I tried. If it actually works, then ALL the other ppl that say to use this microsd recovery method need to read your link and actually know what they are talking about. I read method after method and tried them all to no avail.
I did this and that worked for me : http://forum.xda-developers.com/showpost.php?p=22857274&postcount=21
Got my replacement Prime today. Putting it through the paces now. GPS isn't noted on the box, but I don't remember if it was on my first one. Still a C1O serial. Went ahead and updated first, bc I don't care about HC.
GPS: Can see 4 but signal stays under 35, no locks. will try again tom from Dallas
BT/Wifi issue: None, Does not degrade
Wifi range: Not bad, little better than my phone
Light bleed: Better than last, but still 5 spots along bottom and right side
Side Note: put a 64gb microsd in the tab and a 64gb microsd w adapter in dock. Both work fine, now up to 192gb.
I'm very happy Asus replaced this so quick (week and 1 day). I'm not a picky person so I am fine w the lesser light bleed, I will never use gps but it would be nice to have as an option. I bricked my first tab and would gladly have paid for them to reflash it, heck if they called me even now and said, "hey, we found that you bricked your own tab, here's a bill to reflash" I'd gladly pay it. So far I have to agree w everybody's sides to every issue, which is crazy to think, but everyone has legitimate points. Except ppl that expect Asus to still warrant after unlocking n flashing roms, that's ridiculous.
I am rooted but I took all the precautions before the update such as unfreezing. I can't get into boot loader. No matter what kind of reset I'm stuck at the splash screen. Others have this issue and are completely stock. Any guidance is appreciated!
Have same problem coming from stock .28. Actually did a factory reset before update and it looked like update worked fine. Haven't been successfully able to boot into jelly bean. Can't even power off
same problem
me too stuck in to boot screen (asus logo on center nvidia logo in right bottom corner)
after jell bean update !
I'm there too - used Protato's method to the letter (I thought) - it looks like a brick, doesn't it.
OMG asus replied me
Dear Sir/Madam,
Thank you for contacting ASUS Technical Service.
Hi, I'm very glad to help you. For the problem, please try to hold the power button down for 10-15 seconds to reboot the device.
If stills, I suggest you follow the instructions below to perform “Wipe Data” to restore the unit back to the factory default condition.
Warning: Wiping data will erase all user data. The data is irrecoverable after the wipe.
1. Press and hold down “power button” until the system shuts down.
2. Remove the SD card from Eee Pad.
3. Press and hold down “Volume down” button first, and then press and hold down the “Power” button until the below words appear on the screen:
“Checking for RCK..press key in 5 sec to enter RCK”
4. Do not press any button until there is a line “Press to execute, to cancel wiping data.” Press Volume Up button to execute the “Wipe Data”.
5. After the “Wipe Data” process is done, it will reboot automatically. Then Eee Pad should be able to enter the system successfully.
Click to expand...
Click to collapse
problem is device not closing with power button. only restarts itself. volume up + power button closes screen but device still active because apx driver appears in my pc with universal naked drivers.
I have the same problem.
Tried rebooting by holding the power button.
Booting in recovery won't work either.
I can boot in APX, but from there i can' t do anything.
ADB wont recognise my prime...
Contacted Asus about my isue, but knowing asus it will mean waiting for few days, sending in my prime (rooted) and probably having to wait a month to get it back... (3rth RMA in 10 months...)
Selhati said:
I have the same problem.
Tried rebooting by holding the power button.
Booting in recovery won't work either.
I can boot in APX, but from there i can' t do anything.
ADB wont recognise my prime...
Contacted Asus about my isue, but knowing asus it will mean waiting for few days, sending in my prime (rooted) and probably having to wait a month to get it back... (3rth RMA in 10 months...)
Click to expand...
Click to collapse
Do you think they will care if its rooted at this point? I want to RMA mine now this is just the cherry on top. I opened up my prime before but didn't tweak it at all. Hopefully I won't get a 300$ bill after this.
Has anyone figured out how to get pass this issue?
Has anyone figured out how to get pass this issue?
Stuck on splashscreen
I am also experiencing the same issue with my Prime. My tablet had flashed Jelly Bean without a flaw while rooted with a deodexed file I found from one of the developers. It worked great throughout the day and it remained rooted but when I decided to reboot my tablet, it got stuck in the splash screen. Now it will not boot up at all. It is just stuck on the Asus splashscreen. I hope someone figures out how to fix this issue.
Jeez guys, we're all in the same boat, and so far i'm feeling we're F#CKED,
Stuck on asus logo, cant get to the bootloader by pressing volume down and power, can only get to APX mode, and nothing is fixing it, I contacted Asus also, but my bootloader is unlocked, so all im expecting is "Were sorry, your device is out of warranty because it's unlocked" fml.
Brandonxcore said:
Jeez guys, we're all in the same boat, and so far i'm feeling we're F#CKED,
Stuck on asus logo, cant get to the bootloader by pressing volume down and power, can only get to APX mode, and nothing is fixing it, I contacted Asus also, but my bootloader is unlocked, so all im expecting is "Were sorry, your device is out of warranty because it's unlocked" fml.
Click to expand...
Click to collapse
I have tried all the steps listed to fix my prime and nothing seems to work. I feel that were screwed but hopefully someone can prove me wrong. I'm tempted to buy a Nexus 7 now or tf700. If we don't fix our tablets I will have no choice but to get one of them.
Brandonxcore said:
Jeez guys, we're all in the same boat, and so far i'm feeling we're F#CKED,
Stuck on asus logo, cant get to the bootloader by pressing volume down and power, can only get to APX mode, and nothing is fixing it, I contacted Asus also, but my bootloader is unlocked, so all im expecting is "Were sorry, your device is out of warranty because it's unlocked" fml.
Click to expand...
Click to collapse
they'll RMA it for free even if you're rooted/unlocked. they have no way of telling.
EZPIMP69 said:
I have tried all the steps listed to fix my prime and nothing seems to work. I feel that were screwed but hopefully someone can prove me wrong. I'm tempted to buy a Nexus 7 now or tf700. If we don't fix our tablets I will have no choice but to get one of them.
Click to expand...
Click to collapse
I think if everything goes to crap, I'll get a Nexus 7. It's really going to hurt not having a keyboard dock since I use my Prime as a laptop. Reason why I don't really want to get an infinity is because Asus still hasn't ironed out all the issues with the Transformer line. Plus if I hork out another $500 and get burned by a new product come Christmas, I am not going to be happy. Hoping that my Prime will be ok but ya, the worst usually happens to me.
I found this post. I am going to try and see if it works for me. Others are saying that these steps fixed their prime. I'll let you know how it goes for me.
http://forum.xda-developers.com/showthread.php?t=1773280
Any new ideas on how to get this fixed? Stuck on the Asus splash screen alo.
EZPIMP69 said:
I found this post. I am going to try and see if it works for me. Others are saying that these steps fixed their prime. I'll let you know how it goes for me.
http://forum.xda-developers.com/showthread.php?t=1773280
Click to expand...
Click to collapse
Well I tried the steps in the link provided but had no luck since it requires fastboot. My tablet won't turn off or go into fastboot. The only way I think we can repair this is with NVflash but Asus needs to provide the files needed to complete a factory flash. This **** sucks.
EZPIMP69 said:
I found this post. I am going to try and see if it works for me. Others are saying that these steps fixed their prime. I'll let you know how it goes for me.
http://forum.xda-developers.com/showthread.php?t=1773280
Click to expand...
Click to collapse
So what was the result?
Count me in
Just another report of this happening to me. Stuck in the Asus "perfection" logo.
The only thing I have found is that I can turn off the screen following this steps:
Connect it to the power
With a pin press and hold the reset button
Keeping pressed the reset button disconnect the power connector,
Connect the power bak again (always pressing the reset button) and wait about ten seconds before finally release the reset button.
At least now I don't see that dreadful screen reminding me that I have an useless glowing brick in my desk.
Hopefully someone finds a way to unbrick it because I will be costly having to RMA the prime back to the US where I bought it.
T-HO6969 said:
So what was the result?
Click to expand...
Click to collapse
It did not work since I can't boot into fastboot to begin the process.
Let's collect info about the problem.
Let's try to find a common issue of why we got bricked answering some simple questions and hoping someone with better knowledge can use this information to help us. Here are some questions, you can add any information that you consider relevant.
How did you upgrade to JellyBean: I used this method
Unlocked? NO
Rooted"? YES. Because it was necesary in order to update to JB using the procedure linked above
Additional relevant info: My prime have the famous "unknown serial" problem that was never resolved by ASUS. Because of this, it has never received OTA and always have been updated with the firmwares from the ASUS website. This time instead of waiting for ASUS to publish JB in the support website I used the procedure above. Appart from this I have always keep it "stock".
I received a Nook Tablet 8GB from a friend that has it messed up pretty badly.
I have tried option 1 on the thread below and was able to boot into CWR and install the partition zip, then i used MiniTool Partition wizard to setup microsd as described, then place the update zip onto microsd.
http://forum.xda-developers.com/showthread.php?p=36492731
Once i put back into nook and boot up it goes to call customer service.
I also tried the following method here
http://forum.xda-developers.com/show....php?t=1663836
I get the green check mark and after reboot i get call customer service.
Again, im not sure what was done to this device before. Just trying to fix it for a friend. Is there anything else i can do?
Should i be using this method?
http://forum.xda-developers.com/show....php?t=1570022
So im assuming there is no hope since there is no response? I see many threads of bricked NT's so im assuming this sort of this is quite common and thats the reason for the lack of response to this thread.
I have worked with android for 2 years now and never bricked a device. I just find it hard to believe this nook tablet cannot be repaired. But again, i have no idea what was done to it.
"Bricked" is a very loose term: without knowing more what's wrong and/or what was done with a tablet it's hard to suggest how to really fix it. Applying a wrong fix often makes the problem worse rather than better.
But it's not necessarily a total loss: until you can figure how to fix it you might try to run CM10 off an SDcard: see http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/, or http://forum.xda-developers.com/showthread.php?t=2061536.
Not sure how i missed that thread but that worked great!
i was about to throw in the towel and you blessed me with that great info. Thank you so much!
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Try holding the "n" button when you power up. Press power and at that very first flicker after a few seconds, press and hold n.
bignadad said:
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Click to expand...
Click to collapse
Try what Asa suggested above, if it doesn't work then your friend's NT is like mine and many others' -- they only boot into SD with a cold boot and using a powered USB cable. Some people deem this "USB-tethered boot" behavior a manufacturing defect, but it might very well be by design by B&N to discourage people from venturing outside their content wall-garden with easy-to-use 3rd-party ROMs.
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Don Karnage said:
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Click to expand...
Click to collapse
Sorry for your troubles. Fastboot (aka factory) cables are useless on an HDX. If you can't 'see' your device via a standard usb cable or it shows up as "QHSUSB_BULK" then you're done. If the device was purchased within the past 12 months there is a good chance Amazon will exchange it for a refurb. Just say it died during an update (apparently true). No need to mention the prior root attempt which may or may not be related. Call and be nice to the rep; ultimately it's their decision.
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Don Karnage said:
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Click to expand...
Click to collapse
Those are encouraging signs. Do you recall enabling adb? If so there may be a way to revive your device via tether but the the commands/techniques are a little beyond me (others can probably help). Most require root access which you likely don't have. Best guess is the root exploit you tried was partially successful and may have altered some files needed to process ota updates. A factory reset emulates portions of that process likely resulting in the boot loop. If the offending 'update' file(s) can be renamed you might be able to boot successfully.
Don have you ever used ADB? If so this might possibly save you
http://forum.xda-developers.com/kindle-fire-hdx/general/unbrick-solutions-t3059733