Hello all! Today I have been having a tough day with technology SMH! But anyways I have been looking at every single post on this website and looked on Google about my problem and I can not fix it AT ALL! I'm really new to this hacking rooting stuff. I just bought a kindle fire just last week and I decided to put android 4.0 just last week and I had no problem with doing that what so ever. It was very simple and easy. But for some really I went back to the stock OS and deleted the android 4.0 files off my Fire. But today, I wanted to do it again but this time from a different website. The file was called MIUI.us_blaze_4.0.3-2.2.3-alpha_0xD34D FYI. I thought these files all do the same thing and stuff. Like I said, I am new to this. Never used an android device a day in my life. (Team IOS lol) Back to my problem. So I did the regular on TWRP. I Backed up my data, cleared the Factory Setting,then I went to flash the Zip file I had. After it was done installing or whatever, this is when everything happened. I rebooted my kindle like always, But this time the yellow triangle was on the screen for about 10 min. So I held the power button for 20 and maybe thought it just needed to reboot again. Well, I sat and waited for about 5 min once again and nothing happened at all. I tried to connect my Kindle to my Laptop but it makes the donkdonk noise once like it connected. But then it makes the same noise again but it disconnects. Also, with the KFU (Kindle Fire Utility) it says device is not connected or whatever it says.So, I have been reading online that I need to go into Device manager and do some stuff. But when I go into Device Manager. I see my Kindle for 5 secs when I first plug it into my pc but then it disconnects. I can not believe that I did this. So can anyone please help me out before I do something else stupid to it,it would mean a lot to me! I will take ANY advise right about now! Thank you!
I did the same thing
The file you downloaded was bad i downloaded the same file , I fixed it by running KF utility and reinstalling TWRP , when it tells you to plug in or device not found turn off device plug in usb and push power until turns orange or green forget which one after that it will recognize the device , this worked for me i hope i helped you
Related
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
I have the Lenovo ideapad K1 and have flashed it twice. My third attempt stopped part way through due to a bad image file. Turned the device on and off and haven't been able to access it since. Now I have not animation when powering the device. When I turn on the device the lights come on (2 near the "navigation" button on the front) but that is all. It no longer registers in windows as an APX device either and it says "unknown usb device". The device registered before and I've changed nothing.
So, is it bricked are just playing dead?
UPDATE!! I plugged my pad into the wall charger and then turned it off and on repeatedly. I put it into APX mode while plugged in and saw a flash on the screen instead of the usual soft lighting so I thought, maybe somethings changed. Plugged the pad into the usb port and still now APX. Moved the usb plug to a different location and now I'm in APX . Am able to run NVFlash.bat but getting errors. Will keep trying while looking up info on NVFlash. Still think I'm bricked but will throw everything at it to get it working. Will keep updating this post.
It's working again
I moved the cable to a different usb port, tried installing the stock HC rom first and it partitioned the tab but got stuck sending the recover.img file. So I turned it off again, moved it to a different usb port and tried installing the JB CM9 rom which was the last working rom I had (besides ICS). It worked! When the tablet came back on it had 11% battery left!
I've never appreciated my tablet as much besides the first days I got it. I couldn't really afford a new one right now since I'm recently unemployed so I"m grateful this worked.
My only suggestion with a "bricked" tablet - try try again, try everything, keep you head, walk away and come back, don't give up
Time to go setup my tablet again!
i need help
gendou2 said:
I moved the cable to a different usb port, tried installing the stock HC rom first and it partitioned the tab but got stuck sending the recover.img file. So I turned it off again, moved it to a different usb port and tried installing the JB CM9 rom which was the last working rom I had (besides ICS). It worked! When the tablet came back on it had 11% battery left!
I've never appreciated my tablet as much besides the first days I got it. I couldn't really afford a new one right now since I'm recently unemployed so I"m grateful this worked.
My only suggestion with a "bricked" tablet - try try again, try everything, keep you head, walk away and come back, don't give up
Time to go setup my tablet again!
Click to expand...
Click to collapse
can u send me the HC image, my tablet is showing unrecoverable bootloader error 0x00000000008
any suggestions?
Hope this will work on my K1 issues:fingers-crossed::fingers-crossed:
Hello everybody,
I am new here, but after many searches I found out that this forum can be quite useful. Unfortunately I couldn't find the answer to my problem. Here you go, I start very well for my first thread:
I just got a HTC one M7 international version GSM from a friend, very nice phone and it was already rooted and had Trickdroid installed on it. I started to talk to my friend and he told me I should install KIt Kat on the phone... and from there it went all wrong...
I tried to install a KIT KAT rom I found online, it didn't work and the phone wouldn't start anymore, I would just have access to recovery mode (CWM is installed) and fastboot/bootloader. From there, the phone wasn't recognized anymore by my pc when connected to USB. I then used a mini USB cable to connect a USB key with different .zip file to load them to the phone.
After many attemps, one file finally worked (all the other would abort installation), it was insertcoin M7 kustomizer... I know I should have had reloaded Trickdroid 11.0.0 on it, but it was taking ages to download and went the fast way... which was a really bad decision I guess.
After the installation of insertcoin, the phone rebooted and... rebooted...and keeps rebooting to the HTC white screen (with the red warning: this build is for...)... it goes on and on...
Only thing I can do is hold the volume down key when it reboots and then it takes me to fastboot/bootloader. From there when I try to go to recovery mode it goes to recovery mode for half a second and reboot directly to the white HTC screen over and over again....
Also, USB device is not recognized (but strange, HTC sync manager starts even though it tells me no phone is connected).
Now I have the Trickdroid 11 file ready (1.1GB) but there is no way to install it on the phone... I really don't see how to do it anymore, did I really screw up big time and my phone is more or less a dead weight?
I am going to Kuala Lumpur, Malaysia at the end of the week, maybe someone will be able to find a solution for me...
I shouldn't have touched a phone that was working very well....I know...
Nobody? So my HTC one is dead?
Is the all in one tool going to help? I installed it but since my phone is not recognized by the computer (windows 8.1) when connected via USB, I don't seem to be able to do anything...
sedoriku said:
Is the all in one tool going to help? I installed it but since my phone is not recognized by the computer (windows 8.1) when connected via USB, I don't seem to be able to do anything...
Click to expand...
Click to collapse
This is all if you can find a way to get files to your phone...
I'm not sure which recovery you have but when upgrading from Android 4.2.2, and 4.3 the recovery you are using needs to be updated to the most current version. For example if you are running TWRP recovery you need to be running TWRP 2.6.3.3 for everything to run smoothly. In order to do this though you will need to download your original ROM (No matter how long it takes). Then go google play store and download goo.im and update you recovery with openrecoveryscript and update from there and you should be fine. I would also like to note that it's fully recommended that when you flash 4.4 KK you do a full wipe. This means userdata/cache/dalvik cache wipe, otherwise you will run into problems. Let me know if I missed anything or if you have anymore questions!
Thank you, but unfortunately I still couldn't find a way to access the files on the phone, no matter what I do. The phone starts by itself to the HTC white screen when I connect it to the main to charge it... I can only access fastboot/bootloader... I feel useless...
I feel your pain
sedoriku said:
Thank you, but unfortunately I still couldn't find a way to access the files on the phone, no matter what I do. The phone starts by itself to the HTC white screen when I connect it to the main to charge it... I can only access fastboot/bootloader... I feel useless...
Click to expand...
Click to collapse
After my htc one freezing on the 'quietly trickdroid' loading screen my phone will now not turn on, AT ALL! I think it's screwed : S
I just arrived in Kuala Lumpur and took it to a little shop, they told me they will fix it for me by tomorrow for 50USD... I'll let you know tomorrow if they managed to make the magic happen. I think they would reinstall stock, but that's fine with me, much better than a bricked "rooted" phone. It will take me a while before I start to screw up with a phone again...
ug.I am visiting serbia now. My kindle is about 20 days old. I rooted it, safestrapped etc. Now I like the Kindle so much that I want to upgrade to the 64gb version. So I decided to unroot it without a pc, did a factory wipe which even deleted my stock backup so no OS available to restore. tried to power up and got as far as language choice then keeps going back to same page. So I tried a power down up and it just stays on same screen after I get thru the twrp screen. I dont have a pc available here. I want to at least rid this device of any rooting/twrp/safestrap stuff before I send back to Amazon
Any advice on this?
Fixed! As a last resort, I held the power key for a whole minute while kindle appeared to be resetting
A number of times with my finger stayed on the power button. It then powered up correctly and now runs like
A charm. So for now I am wondering if I really should pursue getting the 64 Gb version.
Hopefully this simple fix will help others.
as i know you´re hdx is bricked
you show grey kindle logo? you are bricked your device and since know we have not solution
Hello everyone.
So I successfully rooted the A10-70L ZA010062ZA using the simple tool: KingoRoot.
It was truly easy; just downloading and installing KingoRoot onto my laptop (I did not trust installing it on the tablet itself) and it turned out to be a big success with just one click of a button ("Root") after plugging the tablet into my laptop using USB (with USB debugging turned on ofcouse).
So here I went and downloaded Linux Deploy onto the tablet and spent a day TRYING to install Kali onto it. Honestly, there were so many issues and errors, I just got frustrated.
I honestly did not figure out how to do this yet; because why? The tablet thought to itself "What madness it this?!" and he shut down instantly, BOOM!
I was confused at first, holding my head with my hands in my hair when i then realised - Wow, okay.. It does NOTHING when i try to turn it on! I freaked when I realised that I have hard-bricked it.
After trying ONE LAST TIME to turn it on, holding the power button for almost a minute before losing hope, IT TURNED ON! But.. It got stuck in a boot loop, showing only the boot screen. I WAS RELIEVED!! I only soft-bricked it.
Now I am currently downloading the stock ROM, which I believe should work. I will post an update on this thread to keep you up to date on what I did and if it was successful.
Question: Is there maybe ANY custom ROM that is compatible with the A10-70L ZA010062ZA?
The stock ROM is cool and everything, but why not make the device a brutally epic device if the possibility exists?!
Xx
EgyptianCobra