Related
All,
I have to say thanks for the help in advance, well I'm in the military and I have never done anything to my G-tablet. All I used it for was to OOVOO and talk with my kids when I am in the DESERT Guys over there are always doing crazy stuff to theirs and crazy stuff always happens to them, some good some bad. :cyclops: Well here it goes my brother-in-law took my tablet without my knowledge and decided he would upgrade me to a better system :crying::crying::crying::crying: well he killed it!!!!!!! and I leave to go back to the desert in a week or so. He says something must of been wrong with it before he touched it, yeah likely story!!! it worked fine when I used it last. I have to say I have little knowledge on how to do things to this tablet IE rooting roms and all of that stuff, not saying I'm not willing to learn just very dumb when it comes to doing it. I'm one of those give it to me step by step by step
So this is what I have done so far
1. I plug it in to my Computer Windows Vista Home premium 64 bit system and it does not recognize it.
2. I opened it up and have disconnected the internal battery cord and plugged it back in still no life
3. I pressed the little white button and no reset happened
4. Held down the power button and down sound button and (3 birds ViewSonic - Detect a recovery key pressed - Booting recovery kernel image) popped up then nothing it just sits like that.
5. I have also let the battery completely drain to zero then charge it back up and still nothing.
Please help me and I'm sorry if I've been rambling on but talking to my kids when I'm deployed is the only thing I look forward to doing when I'm in the desert, Once again I would like to thank the smart guys on this forum for helping us not sooooo smart ones with our problems.
desert G-TABLET said:
All,
I have to say thanks for the help in advance, well I'm in the military and I have never done anything to my G-tablet. All I used it for was to OOVOO and talk with my kids when I am in the DESERT Guys over there are always doing crazy stuff to theirs and crazy stuff always happens to them, some good some bad. :cyclops: Well here it goes my brother-in-law took my tablet without my knowledge and decided he would upgrade me to a better system :crying::crying::crying::crying: well he killed it!!!!!!! and I leave to go back to the desert in a week or so. He says something must of been wrong with it before he touched it, yeah likely story!!! it worked fine when I used it last. I have to say I have little knowledge on how to do things to this tablet IE rooting roms and all of that stuff, not saying I'm not willing to learn just very dumb when it comes to doing it. I'm one of those give it to me step by step by step
So this is what I have done so far
1. I plug it in to my Computer Windows Vista Home premium 64 bit system and it does not recognize it.
2. I opened it up and have disconnected the internal battery cord and plugged it back in still no life
3. I pressed the little white button and no reset happened
4. Held down the power button and down sound button and (3 birds ViewSonic - Detect a recovery key pressed - Booting recovery kernel image) popped up then nothing it just sits like that.
5. I have also let the battery completely drain to zero then charge it back up and still nothing.
Please help me and I'm sorry if I've been rambling on but talking to my kids when I'm deployed is the only thing I look forward to doing when I'm in the desert, Once again I would like to thank the smart guys on this forum for helping us not sooooo smart ones with our problems.
Click to expand...
Click to collapse
1.- Try other windows version, works fine on Windows 7 x32 / x64 - tested my self
3.- wich white reset button? i never saw it !
4.- You tried POWER+VOLUME (+)? - POWER+VOLUME(-)?(this its for nvflash as far i know, im also a begginer)
Your tab is not dead, but it is not properly flashed either. If you hold power and Vol UP and it shows booting recovery but doesnt boot it, then there is a bad recovery flashed, or none at all. To fix this, you will have to NVFLASH a recovery/OS on it. There are better than stock OS's but since you need it for webchating with family I would suggest Frankentab.
Download this file:
http://teamdrh.com/DRH-Downloads/Full_Stock_NVFlash_CWM_5504_Touch.zip
Then extract it somewhere you can find it.
Using a usb Male to usb mini cable, the one that came with your tablet, plug your tab into your computer (tab turned off)
Hold down the VOL DOWN button and press power button and hold it too. The three birds should pop up, then go away, black screen.
After black screen, computer will say found new hardware. You must manually choose the drivers needed, and their location will be in a folder titled "flash usb drivers" and it is inside the folder you downloaded and extracted.
After the drivers are installed, without turning anything off, run the file nvflash_gtablet.bat which is inside the extracted folder you downloaded. This will take a while, but once it is done, you can turn off and turn back on your tablet. After a few minutes, it should completely boot back into a stock ROM.
If you are cool with this, then you are done. If you would like to run something MUCH FASTER then let me know when you get to this point and I will show you how to accomplish this. If you run into any problems report back and I or someone will help.
Just had this problem on a new (well refurbished) gTab I got during black Friday. Works great and is not hard to fix the issue once in APX. hardest part was getting the drivers installed (running win 7 x64).
I had to go to the CWM page to download the correct version of the recovery, the version listed in the guide is outdated, or not listed that it is for 1.1 only and not 1.2.
Seems like a great tablet, can't wait to get using it. Thanks!
camman85 said:
Just had this problem on a new (well refurbished) gTab I got during black Friday. Works great and is not hard to fix the issue once in APX. hardest part was getting the drivers installed (running win 7 x64).
I had to go to the CWM page to download the correct version of the recovery, the version listed in the guide is outdated, or not listed that it is for 1.1 only and not 1.2.
Seems like a great tablet, can't wait to get using it. Thanks!
Click to expand...
Click to collapse
do you remember where you downloaded the right recovery version for windows 7 ?
So, I recently managed to come into possession of a rather tasty little Prestigio PMT3377_Wi tablet and I wanted to root it.
I downloaded TowelRoot as the forum thread for it said "Will this brick my phone? Most probably not. towelroot alone hasn't bricked a phone yet." so I figured I'd give it a bash since I'm new to this and such.
I don't entirely know what happened next since I was letting the app just do it's thing next to me while I was on my desktop and then the app crashed.
Now when I try to boot it it gives me a small flash of a USB symbol, then goes back off, unless i have the USB cable plugged in, in which case the USB symbol would stay present.
So yeah, if anyone can help me, that'd be fantastic!!
Update: I've tried everything I can think off, when I use t he ADB, my device is "unauthorized" and I can't "authorize it" because I can't boot up the OS to get into the settings for that, and I THINK I've tried the TF card update properly, but nothing's worked.
I hope you all don't mind too much if I bump this?
Hi there,
I think my z3tc just died.
I flashed the z3c firmware (only system) via flashtools in order to gain root with giefroot.
The tablet started, but the root process failed, and I had to hard reset the tablet (vol-,vol+,on/off), after that the device would not start again.
I tried the yellow reset-knob (beside the sim slot) for 10 secs ... nothing
vol-,vol+,on/off for 10 secs ... nothing
plugged it to the original wall-charger with the original cable ... nothing, not even the led shows up.
Has anybody an idea, or is my device a case for the wastebin?
Thanks in advance!
Hansifranzi said:
Hi there,
I think my z3tc just died.
I flashed the z3c firmware (only system) via flashtools in order to gain root with giefroot.
The tablet started, but the root process failed, and I had to hard reset the tablet (vol-,vol+,on/off), after that the device would not start again.
I tried the yellow reset-knob (beside the sim slot) for 10 secs ... nothing
vol-,vol+,on/off for 10 secs ... nothing
plugged it to the original wall-charger with the original cable ... nothing, not even the led shows up.
Has anybody an idea, or is my device a case for the wastebin?
Thanks in advance!
Click to expand...
Click to collapse
You flashed the wrong firmware. You could be hard bricked. Basically if you can't get into flash mode and flash the proper firmware then your screwed.
For future reference quadruple check your firmware before you flash the ftf file.
If your rooting SGP621 then you should have flashed the D6603 .93 firmware because that's the one with the exploit.
Sent from my D6603 using XDA Free mobile app
Thanks for the answer.
I have the SPG611, is it the same firmware to exploit as for the SPG621, namly D6603 .93?
Hansifranzi said:
Thanks for the answer.
I have the SPG611, is it the same firmware to exploit as for the SPG621, namly D6603 .93?
Click to expand...
Click to collapse
No the xploit shouldn't work because the system is quite different. SPG621 is the LTE version and I think 611 is the Wi-Fi version. The 621 runs on cellphone hardware very similar to the Xperia Z3 where the 611 has no LTE connectivity. It wouldn't be wise to flash a D6603 firmware on it because the hardware it too different.
Sent from my D6603 using XDA Free mobile app
I just found this:
http://forum.xda-developers.com/z3-...t-rooting-sgp611-giefroot-bootloader-t3017314
So I think it should also work on the WiFi Version (SPG611).
Dead Z3c Tab
Hansifranzi said:
Hi there,
I think my z3tc just died.
I flashed the z3c firmware (only system) via flashtools in order to gain root with giefroot.
The tablet started, but the root process failed, and I had to hard reset the tablet (vol-,vol+,on/off), after that the device would not start again.
I tried the yellow reset-knob (beside the sim slot) for 10 secs ... nothing
vol-,vol+,on/off for 10 secs ... nothing
plugged it to the original wall-charger with the original cable ... nothing, not even the led shows up.
Has anybody an idea, or is my device a case for the wastebin?
Thanks in advance!
Click to expand...
Click to collapse
This is EXACTLY what happened to me. No LEDs going on - nothing. Device 3 weeks old from Amazon Germany. I sent it in for repair, got it back today with a notice that because I had the bootloader unlocked the warranty is void and they didn´t do anything with it. BUT: When I got it back it was alive again, I could get it into fastboot mode. So I called the technician to ask how they had reset the hardware. They said they hadn´t done anything. I remember having read about a guy who had the same problem, when he packed the tablet to send it in after a couple of days he noticed it would turn on again.
So here is what I think: If you flashed the wrong boot.img or whatever and the Z3c Tab goes completely dead (no charging, no LEDs, no nothing) just wait a couple of days. May be some capacitator has to run flat or I don´t know what but just wait.
Pleas let us know if this works for you, might help other people here and I sure wonder if just letting it sit there can help when everything seems to be f*** up
Thanks for sharing your experience. I also read the post from the guy, who wanted to return it and discovered that it turned back to life.
How many days did it take from returning it to amazon to receiving it back?
Did you connect it to the computer with vol-, and the blue led came back?
It has been three days now, but connecting it to the computer or to the wall-charger didn't change a thing.
Took about 3 days to get it back. May be we have to let the battery discharge?
When I got it back (volume down + USB plugin) was working again, when I sent it in didn't do a thing, no LED. Once you have it back to fastboot mode it's really a piece of cake.
Doolittle Duckbill said:
Took about 3 days to get it back. May be we have to let the battery discharge?
When I got it back (volume down + USB plugin) was working again, when I sent it in didn't do a thing, no LED. Once you have it back to fastboot mode it's really a piece of cake.
Click to expand...
Click to collapse
I also thought about the battery, I will wait at least for monday, and then report back.
Hansifranzi said:
I also thought about the battery, I will wait at least for monday, and then report back.
Click to expand...
Click to collapse
Basically the trick here is to let the battery go dead OR disconnect the battery and reconnect it again but I suppose that would be a hastle.
Also, plugging again and again would charge the device especially if you are trying to discharge the battery fully.
If you are certain that all drivers are fully installed and it does not show any sign at all. I would suggest that hold down power + volume up/down depending on which mode you want to boot. The trick here is KEEP HOLDING POWER AND VOLUME KEY while at the same time plugging in the device to your PC. I am sure the LED would blink or something (I do not have the device but all Sony work this way)
I had a similar incident with a Sony Phone, just like your tablet symptoms but this trick worked for me.
Try that and report back to me, I would like to see what happens and if you need any help, do no hesitate to quote me back!
Good Luck and make sure you flash the RIGHT FTF this time
Hnk1 said:
Basically the trick here is to let the battery go dead OR disconnect the battery and reconnect it again but I suppose that would be a hastle.
Also, plugging again and again would charge the device especially if you are trying to discharge the battery fully.
If you are certain that all drivers are fully installed and it does not show any sign at all. I would suggest that hold down power + volume up/down depending on which mode you want to boot. The trick here is KEEP HOLDING POWER AND VOLUME KEY while at the same time plugging in the device to your PC. I am sure the LED would blink or something (I do not have the device but all Sony work this way)
I had a similar incident with a Sony Phone, just like your tablet symptoms but this trick worked for me.
Try that and report back to me, I would like to see what happens and if you need any help, do no hesitate to quote me back!
Good Luck and make sure you flash the RIGHT FTF this time
Click to expand...
Click to collapse
Thanks for the answer!
I just plugged the tablet into the usb-port of my laptop while holding VOL- and POWER, the led showed no signs, same as computer, also no signs. I will try again on Monday, the battery is surely dead until then. Hope dies last.
That guy must have been me Had the exact same story happening with a Galaxy Tab S. Looked like hard bricked, back to Media Markt with it, no, no, we won't lift a finger you evil tinkerer - and then it suddenly worked again. I had realized they must have done something. Because how would the see that my device's software had been tampered with if they didn't turn it on?!
Anyway, I tried that convoluted rooting method on my brand spanking new Z3Tc (is that the official abbrev.?) However, managed to get into flash mode somehow. It's embarassing for somebody like me but I'm on unrooted stock now... after about 20 Android devices, none of which wasn't rooted or an alternative ROM all the way
Good luck on reviving your tablet!
Hansifranzi said:
Thanks for the answer!
I just plugged the tablet into the usb-port of my laptop while holding VOL- and POWER, the led showed no signs, same as computer, also no signs. I will try again on Monday, the battery is surely dead until then. Hope dies last.
Click to expand...
Click to collapse
Led or any othehr signs are useless as long as the device is detected. Had it ?
Try power + volume up as well while flashtool running. It'd give you a better idea of detection. Even try power + both volume up and down.
Also plug in to Sony Official tool and see if that can help you repair it ? It might detect it as well.
Hnk1 said:
Led or any othehr signs are useless as long as the device is detected. Had it ?
Try power + volume up as well while flashtool running. It'd give you a better idea of detection. Even try power + both volume up and down.
Also plug in to Sony Official tool and see if that can help you repair it ? It might detect it as well.
Click to expand...
Click to collapse
When my Tab was dead none of the above worked, also "lsusb" in linux showed that it was not detected.
Concerning the question of what the technicians at MediaMarkt or support.com might have done: I know they used the "emma" software from the sony developer homepage to read out my z3c Tab. That apparently gave them the readout that the bootloader was unlocked. They sent me the screenshot together with the notice that they did not repair anything. So may be download "emma" for Windoze and hook it up to that... I use Linux with FlashTool which is supposed to be the same software (?). However, when my Tab was dead, FlashTool just said no device connected.
BTW: This is also the first (of many) Android devices that I now use UNROOTED. All others were rooted. It was also DEFINITELY the last-ever Sony device I ever bought. The hardware is nice, I need it waterproof because I use it on my motorbike. But this stupid rooting procedure is so screwed up that I will never ever buy Sony Android again!
I was really up and going for Sony, checking the internet on when the new z4 phone comes out, but my z3c tab user "experience" has now taught me better: Never again Sony!!!!!!!!!!!
Thanks for all the responses.
Using Windows 8.1 I tried:
USB-Plugging with all combinations of Power, Vol+, Vol- running
PC Companion
Emma
Flashtool
No Reaction at all.
Maybe the battery is still not empty.
Hope dies last.
Doolittle Duckbill said:
When my Tab was dead none of the above worked, also "lsusb" in linux showed that it was not detected.
Concerning the question of what the technicians at MediaMarkt or support.com might have done: I know they used the "emma" software from the sony developer homepage to read out my z3c Tab. That apparently gave them the readout that the bootloader was unlocked. They sent me the screenshot together with the notice that they did not repair anything. So may be download "emma" for Windoze and hook it up to that... I use Linux with FlashTool which is supposed to be the same software (?). However, when my Tab was dead, FlashTool just said no device connected.
BTW: This is also the first (of many) Android devices that I now use UNROOTED. All others were rooted. It was also DEFINITELY the last-ever Sony device I ever bought. The hardware is nice, I need it waterproof because I use it on my motorbike. But this stupid rooting procedure is so screwed up that I will never ever buy Sony Android again!
I was really up and going for Sony, checking the internet on when the new z4 phone comes out, but my z3c tab user "experience" has now taught me better: Never again Sony!!!!!!!!!!!
Click to expand...
Click to collapse
I will look into rooting Z3 compact without pre-rooted firmware / flashing any zip via recovery. There are few methods and Lollipop is a bit hard to crack but we would find it out soon enough! I will put up a guide in few hours and you can see if it works for you!
I think the support for your tablet is lacking and a need for an actual developer to sort things out.
I am not sure about EMMA much but usually I know about JTAG is used to recover hard brick devices. Giving it to Sony is always better option with an impression that you left it charge over night and it wouldn't turn on again. Always works!
Don't worry. It wouldn't be the first tablet hopefully!
Forgot to mention in my previous posts: when I got my tablet back from service, the battery was almost empty (<2%). That gives some support to the notion that you have to drain the battery to unbrick.
Note to would-be buyers who need root: stay away from this tablet (and probably Sony in general). The rooting procedure described in several threads here will drive you mad. It´s catch-22 all the way. (... after step 28 do step 11 unless your device is not LTE then do step 31 and you´re screwed with bootloop or hardbrick...) What a pile of sh**t!
Just tried again to plug it in,
sadly neither the computer nor the tablet showed any reactions in emma or flashtool.
Will try again in a few days.
Hope still is not dead.
Doolittle Duckbill said:
Forgot to mention in my previous posts: when I got my tablet back from service, the battery was almost empty (<2%). That gives some support to the notion that you have to drain the battery to unbrick.
Note to would-be buyers who need root: stay away from this tablet (and probably Sony in general). The rooting procedure described in several threads here will drive you mad. It´s catch-22 all the way. (... after step 28 do step 11 unless your device is not LTE then do step 31 and you´re screwed with bootloop or hardbrick...) What a pile of sh**t!
Click to expand...
Click to collapse
Nah you just need to read all the threads stick to the one you most understand and be cautious on every step
in my case i thought i needed root but after all the process and setting up my device it didnt feel right so I went back to stock the nice thing is that i have a backup of the TA partition just in case :victory:
I didn't touch the device for a week now.
But nothing has changed, still bricked. I will sell it as broken.
Hope has died. :crying:
Hello,
I own the kindle fire HDX 8.9 3rd generation. Yesterday i rerolled my version back to 3.2.4, everything seemed to be working just fine.
But after i closed my case and reopened it after half an hour my device was shutted down (the battery was 80%). Since i've been trying to turn it on with no succes. I've also contacted amazon support who were willing to give me an "huge" sale on my next purchase (20$) since they don't think it will ever work again.
On my pc in device manager my kindle does show up, but when i try to install adb drivers i get an error 10.
I'm hoping to get some help here.
HybridLion said:
Hello,
I own the kindle fire HDX 8.9 3rd generation. Yesterday i rerolled my version back to 3.2.4, everything seemed to be working just fine.
But after i closed my case and reopened it after half an hour my device was shutted down (the battery was 80%). Since i've been trying to turn it on with no succes. I've also contacted amazon support who were willing to give me an "huge" sale on my next purchase (20$) since they don't think it will ever work again.
On my pc in device manager my kindle does show up, but when i try to install adb drivers i get an error 10.
I'm hoping to get some help here.
Click to expand...
Click to collapse
Did you block OTA and/or disable WiFi after rolling back to 3.2.8? If not you likely received an update from Amazon which often leads to a hard brick (no recovery).
What version were you on before and did you directly edit build prop?
Try holding the power button for up to 60 sec. Any response?
Davey126 said:
Did you block OTA and/or disable WiFi after rolling back to 3.2.8? If not you likely received an update from Amazon which often leads to a hard brick (no recovery).
What version were you on before and did you directly edit build prop?
Try holding the power button for up to 60 sec. Any response?
Click to expand...
Click to collapse
No i didn't block the OTA, i wasn't even planning on rooting and stuff, i downloaded the 3.2.4 from amazons site.
I downgraded from the newest versien 4.?.? (it didn't work with my vpn)
I have absolutely no response when pressing it for 60 seconds
HybridLion said:
No i didn't block the OTA, i wasn't even planning on rooting and stuff, i downloaded the 3.2.4 from amazons site.
I downgraded from the newest versien 4.?.? (it didn't work with my vpn)
I have absolutely no response when pressing it for 60 seconds
Click to expand...
Click to collapse
You can't go from 4.x to anything below 3.2.8. Amazon incorporated anti-rollback protection after 3.2.6. If you try to install an earlier version it will permanently disable the device. Also known as an 'efuse'. Sorry mate, there is no recovery.
Davey126 said:
You can't go from 4.x to anything below 3.2.8. Amazon incorporated anti-rollback protection after 3.2.6. If you try to install an earlier version it will permanently disable the device. Also known as an 'efuse'. Sorry mate, there is no recovery.
Click to expand...
Click to collapse
What the ****...
Why the fuc*k* do they offer a download of 3.2.5 on their website?
So there is seriously no way to recover it? Well good by all my brithday money:good:
**** you amazon
HybridLion said:
What the ****...
Why do they offer a download of 3.2.5 on their website?
So there is seriously no way to recover it? Well good by all my brithday money:good:
**** you amazon
Click to expand...
Click to collapse
Really sorry this happened. For future reference system images are supplied to repair or upgrade a device. Downgrades are always risky and rarely supported regardless of mfg. In this case a little knowledge (likely gained through these forums) met a loaded gun. Unfortunately, there is no known fix to an efuse brick.
Davey126 said:
Really sorry this happened. For future reference system images are supplied to repair or upgrade a device. Downgrades are always risky and rarely supported regardless of mfg. In this case a little knowledge (likely gained through these forums) met a loaded gun. Unfortunately, there is no known fix to an efuse brick.
Click to expand...
Click to collapse
Yeah i feel like a huge turd...
Well thanks anyway... F#king amazon :c
Have you looked at some of the possible techniques around from last year? There were reports of holding the power button down for over a minute to try and get to Fastboot or something... have a look around and you may find something, hope isn't always lost.
You can get into fastboot by holding the minus button while booting, but I am not sure how much it will help with a locked boot loader. Technically, it should flash a factory image, but I am not sure anyone has gotten that to work on the hdx. Note, if you try this, the windows drivers are a pain and there is a special way to run commands for the hdx. Check out the boot unlock op for the commands, the rest of the thread for the drivers, and know you are in uncharted territory.
Good luck,
Leko
From my understanding, blowing an eFuse is physical and thus irreversible unless you replace the actual chip.
I messed mine up, too I believe. I tried flashing the new safestrap ROM with the older safestrap. And now only the gray kindle fire logo stays on. I tried holding down the power button a minute, but just turns the gray logo off and on. I'm assuming there is no way out of this, correct?
manymarius73 said:
I messed mine up, too I believe. I tried flashing the new safestrap ROM with the older safestrap. And now only the gray kindle fire logo stays on. I tried holding down the power button a minute, but just turns the gray logo off and on. I'm assuming there is no way out of this, correct?
Click to expand...
Click to collapse
Correct (sorry).
Yeah.. I gambled. Guess I lost this round.
what kind of douchebag company keeps a version of an os on their website that will brick their device without warning ? if i were you i would never buy one of their products and since the same thing happened to me i will do the same :/
Jasonbrody14 said:
what kind of douchebag company keeps a version of an os on their website that will brick their device without warning ? if i were you i would never buy one of their products and since the same thing happened to me i will do the same :/
Click to expand...
Click to collapse
While I appreciate your frustration this is not Amazon's fault. The actions you and others took are not recommended by Amazon nor most other device manufacturers. The 3.2.8 rollback file that you used was silently captured w/o Amazon's permission and was intended for devices that would never received an OTA update. A few clever individuals figured out how to exploit that file to facilitate 4.5.4 -> 4.5.2 rollbacks (also not supported by Amazon). There are warnings everywhere that wifi must be kept off (or the device placed in 'airplane mode') when using this rollback technique. I am very sorry you lost your device but ultimately the risks and responsibility for bad outcomes are borne by the owner.
Davey126 said:
While I appreciate your frustration this is not Amazon's fault. The actions you and others took are not recommended by Amazon nor most other device manufacturers. The 3.2.8 rollback file that you used was silently captured w/o Amazon's permission and was intended for devices that would never received an OTA update. A few clever individuals figured out how to exploit that file to facilitate 4.5.4 -> 4.5.2 rollbacks (also not supported by Amazon). There are warnings everywhere that wifi must be kept off (or the device placed in 'airplane mode') when using this rollback technique. I am very sorry you lost your device but ultimately the risks and responsibility for bad outcomes are borne by the owner.
Click to expand...
Click to collapse
yeah its my fault for installing an old update i admit that but they host several other versions on their website that arnt 3.2.8 that also brick the device. i just wonder why they would even do that at least instead of permanently killing the device it would just soft brick it :/
Jasonbrody14 said:
yeah its my fault for installing an old update i admit that but they host several other versions on their website that arnt 3.2.8 that also brick the device. i just wonder why they would even do that at least instead of permanently killing the device it would just soft brick it :/
Click to expand...
Click to collapse
Amazon updates don't brick unless: 1) the device is rooted (which means you can get around all protections); or 2) something goes wrong with the update (as occasionally happens to all devices regardless of make). The stock updater will reject attempts to rollback or install an incompatible update. My local auto parts store carries lots of engine elixirs that can work wonders if used correctly. Go off-label and one can 'brick' a $4K engine in minutes.
I'm not ragging on you; what's done is done. Hopefully this post will help someone else contemplating rolling back their device. Tinkers beware: the road to the candy store is laced with land mines.
Was rolling back my kindle fire hdx 7 3rd gen. Using this method, rolled back to 3.2.8. All good, no problems. Then tried to download the firmware to go to 4.5.2, some reason my laptop kept stopping the download partway through, so I tried to download on the tablet, battery was about 40%, download for 4.5.2 was 20% or so. I leave it alone for five minutes and come back and it won't turn on. I tried charging it for bout half an hour, tried resetting it by holding it for 30 seconds, no luck. I plug it into the computer, it shows up as QHSUSB_BULK, tried updating drivers and it can't find anything. I'm at a loss for what to do, I can't find the box for it in case I need to turn it in for another one, I believe it's still under warranty. So my only hope is to somehow unbrick it. Any help would be appreciated.
If its under warranty, get a new one. I'm not sure if you could recover form that with a locked bl.
MinerBoy004 said:
If its under warranty, get a new one. I'm not sure if you could recover form that with a locked bl.
Click to expand...
Click to collapse
I lost the box for it, will try to look for it later. Is it absolutely necessary to find the box? I live on Guam, think of a ****tier version of Hawaii, don't think there are any amazon stores here. What do I need to get another? Pretty sure it's still under warranty.
Rengiil said:
Was rolling back my kindle fire hdx 7 3rd gen. Using this method, rolled back to 3.2.8. All good, no problems. Then tried to download the firmware to go to 4.5.2, some reason my laptop kept stopping the download partway through, so I tried to download on the tablet, battery was about 40%, download for 4.5.2 was 20% or so. I leave it alone for five minutes and come back and it won't turn on. I tried charging it for bout half an hour, tried resetting it by holding it for 30 seconds, no luck. I plug it into the computer, it shows up as QHSUSB_BULK, tried updating drivers and it can't find anything. I'm at a loss for what to do, I can't find the box for it in case I need to turn it in for another one, I believe it's still under warranty. So my only hope is to somehow unbrick it. Any help would be appreciated.
Click to expand...
Click to collapse
Sorry, you did not read through the instructions and numerous cautions that explicitly warn against having a network connection while/after doing a 3.2.8 rollback. Your device received a OTA update which is a death sentence with absolutely no chance of recovery. Hopefully Amazon will allow an exchange.
Davey126 said:
Sorry, you did not read through the instructions and numerous cautions that explicitly warn against having a network connection while/after doing a 3.2.8 rollback. Your device received a OTA update which is a death sentence with absolutely no chance of recovery. Hopefully Amazon will allow an exchange.
Click to expand...
Click to collapse
Ah I see, I did read it, but it honestly slipped my mind when the darn thing wouldn't download on my laptop. Let this be a warning to others then.