Dear developers and enthusiasts
I had installed CM11 on my Fire HDX 7 following these instructions. I wanted to install CM13 and found that I need to unlock the bootloader first. Since the guide says it works only after the bootloader upgrade 3.2.3, I tried to flash the new bootloader as instructed here. TWRP said the flash was successful. I rebooted the device and now it does not boot at all. It is completely dead. Does not respond to any buttons.
Could you please help? Is the device completely dead or can I salvage it somehow?
Thanks
dEvasEnApati said:
Dear developers and enthusiasts
I had installed CM11 on my Fire HDX 7 following these instructions. I wanted to install CM13 and found that I need to unlock the bootloader first. Since the guide says it works only after the bootloader upgrade 3.2.3, I tried to flash the new bootloader as instructed here. TWRP said the flash was successful. I rebooted the device and now it does not boot at all. It is completely dead. Does not respond to any buttons.
Could you please help? Is the device completely dead or can I salvage it somehow?
Thanks
Click to expand...
Click to collapse
If it doesn't respond to anything then it's probably a full brick...
Hold in the power button for a full minute while on the charger if you haven't already...
Just tried it. No response. What do you mean by full brick?
XxD34THxX said:
If it doesn't respond to anything then it's probably a full brick...
Hold in the power button for a full minute while on the charger if you haven't already...
Click to expand...
Click to collapse
dEvasEnApati said:
Just tried it. No response. What do you mean by full brick?
Click to expand...
Click to collapse
completely dead....
Related
My system directory seems to be missing. I've installed teamwin Recovery but am unable to mount the system drive. When I install the latest Cyanogen Mod nightly it appears to install but won't boot. All I've got is Recovery and Fastboot. Help!
So, I had it booting momentarily. Once I had it going I figured I would attempt to load Clockwork Mod Recovery and give it another go. Now I can't even get to the bootloader. Please tell me this isn't bricked!
DustL82 said:
So, I had it booting momentarily. Once I had it going I figured I would attempt to load Clockwork Mod Recovery and give it another go. Now I can't even get to the bootloader. Please tell me this isn't bricked!
Click to expand...
Click to collapse
We don't have enough information. What rom was you on? When you say you had it booting momentarily to where? What Cwm did you flash and how? What happens when you hold down volume down and power together from being off?
flumpster said:
We don't have enough information. What rom was you on? When you say you had it booting momentarily to where? What Cwm did you flash and how? What happens when you hold down volume down and power together from being off?
Click to expand...
Click to collapse
Here is the whole sequence of events...
1) I was on complete stock updated to the latest Asus OTA
2) I used the Asus unlock tool to unlock the bootloader
3) I wanted to gain root access so I tried the freshroot method here http://forum.xda-developers.com/showthread.php?t=1929189. This didn't work and it made my system directory not be found via fastboot.
4) I attempted to load CW Recovery 5.8.3.4 for the TF201 but it wouldn't open so I went with TWRP 2.3.1.0 (both were loaded via fastboot)
5) Once TWRP was working I flashed stock Asus version 10.4.2.17(US) and was able to boot into the welcome screen
6) I still wanted root and I noticed that my recovery image was no longer loading so I attempted to once again push CW Recovery via fastboot.
7) At this point the tablet turns on to the Asus splash screen and in the top left says "The Device is Unlocked". Holding Power + Volume Down lands me in the same spot.
Thank you again for the help!
DustL82 said:
Here is the whole sequence of events...
1) I was on complete stock updated to the latest Asus OTA
2) I used the Asus unlock tool to unlock the bootloader
3) I wanted to gain root access so I tried the freshroot method here http://forum.xda-developers.com/showthread.php?t=1929189. This didn't work and it made my system directory not be found via fastboot.
4) I attempted to load CW Recovery 5.8.3.4 for the TF201 but it wouldn't open so I went with TWRP 2.3.1.0 (both were loaded via fastboot)
5) Once TWRP was working I flashed stock Asus version 10.4.2.17(US) and was able to boot into the welcome screen
6) I still wanted root and I noticed that my recovery image was no longer loading so I attempted to once again push CW Recovery via fastboot.
7) At this point the tablet turns on to the Asus splash screen and in the top left says "The Device is Unlocked". Holding Power + Volume Down lands me in the same spot.
Thank you again for the help!
Click to expand...
Click to collapse
I have a really bad feeling about this. Can you show me where you got that Cwm from please?
flumpster said:
I have a really bad feeling about this. Can you show me where you got that Cwm from please?
Click to expand...
Click to collapse
Yes, I downloaded the Asus Transformer Prime Recovery image from clockworkmod.com/rommanager.
DustL82 said:
Yes, I downloaded the Asus Transformer Prime Recovery image from clockworkmod.com/rommanager.
Click to expand...
Click to collapse
I really have a bad feeling about this mate. The version you mentioned earlier came out at the end of may. Jellybean didn't come out until July. I don't think they released a version since then that supports the Jellybean bootloader and if you flash an ICS recovery onto a Jellybean bootloader you will hard brick your device.
If you cannot access the icons by holding down power and volume down for about 5 seconds while you are powered off then I am afraid it is hard bricked and will have to be returned to asus and have motherboard replaced.
I know it's no conciliation but there are posts everywhere saying not to use CWM on prime
flumpster said:
I really have a bad feeling about this mate. The version you mentioned earlier came out at the end of may. Jellybean didn't come out until July. I don't think they released a version since then that supports the Jellybean bootloader and if you flash an ICS recovery onto a Jellybean bootloader you will hard brick your device.
If you cannot access the icons by holding down power and volume down for about 5 seconds while you are powered off then I am afraid it is hard bricked and will have to be returned to asus and have motherboard replaced.
I know it's no conciliation but there are posts everywhere saying not to use CWM on prime
Click to expand...
Click to collapse
Unfortunately there is at least one post out there saying it will work. On that note, know of anyone who needs some spare parts?
DustL82 said:
Unfortunately there is at least one post out there saying it will work. On that note, know of anyone who needs some spare parts?
Click to expand...
Click to collapse
It can be repaired by asus. Ask them how much to fix. If it's too much these will sell on eBay as people want them for the screen etc.
Hi all,
Please, please, please someone help. I have followed all of the instructions word for word and run the installer app. I am running a Mac and was attempting to install in place of stock Android.
At the end of the installation process the device showed up in recovery mode. The app told me it was over and to wait a moment for the device to boot. I waited 10 minutes or so and the device remained in recovery mode.
So - I then hit reboot from recovery mode and it booted to the Cyanogenmod face with an arrow circling it... Endlessly.
I then followed the instructions on the Cyanogenmod wiki to wipe and reset the phone in recovery mode before attempting the installer again. Same result.
I'm scared that i've destroyed my phone. I really think this should be able to be repaired but i'm just not sure how.
Please someone give me some help!
Which device?
Sorry - it's a Nexus 5.
And i've just tried to flash the stock factory image on Google's instructions, which resulted in the phone getting stuck on the Google logo and not booting. Wow... This is really making me feel sick.
fearofbirds said:
Sorry - it's a Nexus 5.
And i've just tried to flash the stock factory image on Google's instructions, which resulted in the phone getting stuck on the Google logo and not booting. Wow... This is really making me feel sick.
Click to expand...
Click to collapse
Keep cool
We have an awesome community on XDA. Here is a tutorial to return to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Primokorn said:
Keep cool
We have an awesome community on XDA. Here is a tutorial to return to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Thanks for the link. I followed the steps and my phone has gotten stuck on the Google logo, a black screen and a padlock symbol at the bottom. Refusing to boot.
Aaaahhh!!! No idea what is going on here. Any more ideas?
fearofbirds said:
Thanks for the link. I followed the steps and my phone has gotten stuck on the Google logo, a black screen and a padlock symbol at the bottom. Refusing to boot.
Aaaahhh!!! No idea what is going on here. Any more ideas?
Click to expand...
Click to collapse
Did u unlock the bootloader?
EDIT: FYI http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Primokorn said:
Did u unlock the bootloader?
EDIT: FYI http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Click to expand...
Click to collapse
Yes it was already unlocked before I started this stuff.
And thanks for the link.
fearofbirds said:
Yes it was already unlocked before I started this stuff.
And thanks for the link.
Click to expand...
Click to collapse
Try Method no.2
I tried to update my oneplus x to a new version of resurrection remix (the android 7.1 version) by flashing through twrp. Long story short I tried to update the recovery twrp and also update my bootloader but it all went to **** and now my phone is bricked. If I try and boot the phone into either the OS or into recovery I get a boot loop where the oneplus logo appears, the phone vibrates then reboots. I can get into fastboot but when I try and flash either a rom or recovery it tells me I can't because my 'device is not unlocked'. I know my bootloader was unlocked previously but am thinking that by trying to install a new rom it has re-lock or something and I'm not sure if this means my phone is now a paper weight..
Any help would be greatly appreciated!
edit: This problem is fixed. However twrp won't flash/boot correctly now..
Follow this to the letter: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
I did basically the same thing you did and flashed a rom that was compatible with the old bootloader only and it "locked" my bootloader which made the recovery and ROM useless. It took me a few hours to get the device to actually be recognized correctly by the computer and program but it worked. You may also need to google since I remember needing to download basically the same program but from a different site.
Tanner1294 said:
Follow this to the letter: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
I did basically the same thing you did and flashed a rom that was compatible with the old bootloader only and it "locked" my bootloader which made the recovery and ROM useless. It took me a few hours to get the device to actually be recognized correctly by the computer and program but it worked. You may also need to google since I remember needing to download basically the same program but from a different site.
Click to expand...
Click to collapse
Thanks for the reply! I think I may have come across this but wasn't sure if I'd get myself into more trouble since my fastboot is working (it says it's for devices who have nothing). Rekcon it's still my best option?
Edit:
I tried it and worked perfectly. Thanks heaps!
lilfellabob said:
Thanks for the reply! I think I may have come across this but wasn't sure if I'd get myself into more trouble since my fastboot is working (it says it's for devices who have nothing). Rekcon it's still my best option?
Edit:
I tried it and worked perfectly. Thanks heaps!
Click to expand...
Click to collapse
You're welcome! Like I said I was in the same situation. It kept rebooting and when I got into fastboot my heart sank when it said "Device is locked"
So I now have recovery working as well as fastboot (unlocked this time). But I cannot for the life of me get twrp to work correctly. One version out of like 5 I've tried works but won't flash any roms; I read that could be from a bad version.. All others seem to flash from fastboot but when I try to boot I get the dtb not found error. I don't understand why I cant get it to work, this should be the easy part
lilfellabob said:
So I now have recovery working as well as fastboot (unlocked this time). But I cannot for the life of me get twrp to work correctly. One version out of like 5 I've tried works but won't flash any roms; I read that could be from a bad version.. All others seem to flash from fastboot but when I try to boot I get the dtb not found error. I don't understand why I cant get it to work, this should be the easy part
Click to expand...
Click to collapse
dtb not found error means its not compatiable with your bootloader. Did you try official twrp ? And you ever updated to new bootloader?
update your bootloader first, http://forum.xda-developers.com/onep...t3478917/page1
saurabh40629 said:
dtb not found error means its not compatiable with your bootloader. Did you try official twrp ? And you ever updated to new bootloader?
update your bootloader first, http://forum.xda-developers.com/onep...t3478917/page1
Click to expand...
Click to collapse
I'll give it a shot. I am using official twrp yeah - just seems weird because even the old one that used to work fine isn't working. That link doesn't work is this one ok?
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Thanks for the help
lilfellabob said:
I'll give it a shot. I am using official twrp yeah - just seems weird because even the old one that used to work fine isn't working. That link doesn't work is this one ok?
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Thanks for the help
Click to expand...
Click to collapse
Yeah... This is the link.
All working, everyones help is much appreciated! <3 thanks
Hello Folks!
I recently updated the BL of my OPX which was running Ressuerection Remix 5.1.1,and TWRP from blu_spark.Im pretty sure i had unlocked the bootloader but after I updated the BL using this method https://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917.
But now its stuck at One Plus logo and when ever i try to turn it off,it vibrates and turns back on.I cant access the recovery either please help.BTW i can access the fastboot.
Please help
**EDIT**Just followed the Mega-umbrik guide and now its all perfect
Because you didn't update your TWRP I believe. Also the mega unbrick guide was overkill if you have fastboot but at least your up and running again.
Exodusche said:
Because you didn't update your TWRP I believe. Also the mega unbrick guide was overkill if you have fastboot but at least your up and running again.
Click to expand...
Click to collapse
I also had the same problem as OP yesterday.
I had to do the mega unbrick guide, because fastboot can't do anything in that state either. Flashing was not possible (error message: device not unlocked, cannot flash or erase), = bricked
For everyone who can't do anything than entering fastboot (e.g. no recovery, restarting every second) the mega unbrick is necessary. (At least it was in my case.)
Installing the drivers for the unbrick guide was also a pain, because my OS didn't recognized my device in the first place. I had to play with the hardware keys to get it recognized.
Noneatme said:
I also had the same problem as OP yesterday.
I had to do the mega unbrick guide, because fastboot can't do anything in that state either. Flashing was not possible (error message: device not unlocked, cannot flash or erase), = bricked
.
Click to expand...
Click to collapse
My apologies didn't read guess yeah bootloader locked nothing would work except mega unbrick guide. One trick I've read maybe help someone is rolling back the driver think for Windows 10.
Exodusche said:
My apologies didn't read guess yeah bootloader locked nothing would work except mega unbrick guide. One trick I've read maybe help someone is rolling back the driver think for Windows 10.
Click to expand...
Click to collapse
Yeah I learned to be very careful with what to flash and what not. I hope I will never get my devices bricked again, lol.
Hi there,
I have rooted kindle fire hdx 7.
I can't install twrp, so i decide to do it from flashify.
After Reboot, bootloop issue came
Help me till i decide to kill myself for stutipdness.
arshileus said:
Hi there,
I have rooted kindle fire hdx 7.
I can't install twrp, so i decide to do it from flashify.
After Reboot, bootloop issue came
Help me till i decide to kill myself for stutipdness.
Click to expand...
Click to collapse
Attempting to flash a custom recovery (TWRP) on a HDX with with 'standard' bootloader destroys the stock recovery which is required for FireOS to boot. Restoration is not easy and essentially involves rebuilding the device. There are posts throughout this forum that outline what needs to happen but no dedicated threads or step-by-step process. You'll either need to do a ton of reading or simply accept the device is borked and move on.
Davey126 said:
Attempting to flash a custom recovery (TWRP) on a HDX with with 'standard' bootloader destroys the stock recovery which is required for FireOS to boot. Restoration is not easy and essentially involves rebuilding the device. There are posts throughout this forum that outline what needs to happen but no dedicated threads or step-by-step process. You'll either need to do a ton of reading or simply accept the device is borked and move on.
Click to expand...
Click to collapse
or simply can kill myself, cause i spent a lot of money :/ oh, god... jesus...
arshileus said:
or simply can kill myself, cause i spent a lot of money :/ oh, god... jesus...
Click to expand...
Click to collapse
Sorry dude, flashify only works to upgrade/downgrade TWRP on this device, not to make a fresh intall
You forgot unlock bootloader first,neccesary to install TWRP, thats why your device its bricked, if you can get ADB connectivity on the PC using USB Cable, you could have some chance to revive the device.
The easy way : Find a used Kindle with dead display/battery or a new motherboard , to replace the bricked one.
Before do something in your device, always read about the necessary tools/ instructions/ procedures, and make all your questions here.
Tossing out a few clarifications for future readers:
Yousucks2 said:
Sorry dude, flashify only works to upgrade/downgrade TWRP on this device, not to make a fresh intall
Click to expand...
Click to collapse
Flashify can be used for a fresh install if bootloader is unlocked (always) or in special cases (eg: signed image).
Yousucks2 said:
You forgot unlock bootloader first,neccesary to install TWRP, thats why your device its bricked, if you can get ADB connectivity on the PC using USB Cable, you could have some chance to revive the device.
Click to expand...
Click to collapse
Yep - a real boneheaded move. Recovery is also possible by dumping device into 'bulk mode' which is an advanced recovery technique that requires both patience and some technical experience (not to mention attentive reading skills).
Yousucks2 said:
The easy way : Find a used Kindle with dead display/battery or a new motherboard , to replace the bricked one.
Before do something in your device, always read about the necessary tools/ instructions/ procedures, and make all your questions here.
Click to expand...
Click to collapse
HDX disassembly is not for the faint of heart due to copious use of glue; cracked screens are common trying to pry open the clam shell. Probably best to go the 'bulk mode' route first which itself is not easy. My recommendation is to sell the device for parts and pickup up another on an auction site.
Davey126 said:
Tossing out a few clarifications for future readers:
Flashify can be used for a fresh install if bootloader is unlocked (always) or in special cases (eg: signed image).
Yep - a real boneheaded move. Recovery is also possible by dumping device into 'bulk mode' which is an advanced recovery technique that requires both patience and some technical experience (not to mention attentive reading skills).
HDX disassembly is not for the faint of heart due to copious use of glue; cracked screens are common trying to pry open the clam shell. Probably best to go the 'bulk mode' route first which itself is not easy. My recommendation is to sell the device for parts and pickup up another on an auction site.
Click to expand...
Click to collapse
Can you show me any guidelines to understand how hard is it....
arshileus said:
Can you show me any guidelines to understand how hard is it....
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Not sure...
Davey126 said:
https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
Click to expand...
Click to collapse
This will only work if adb or fastboot can still connect,
but in that case I'd suggest to try 1-Click pre-release to
click through a web-UI. No reading required... (-;
BTW, is recovery _really_ checked/needed for FireOS to boot?
I suspect that flashify (or the OP) did more than just overwrite recovery,
which can be _really_bad_ if the bootloader is still locked, since the key
combo to enter fastboot doesn't work...
draxie said:
BTW, is recovery _really_ checked/needed for FireOS to boot? I suspect that flashify (or the OP) did more than just overwrite recovery, which can be _really_bad_ if the bootloader is still locked, since the key combo to enter fastboot doesn't work...
Click to expand...
Click to collapse
In my experience 'yes' to boot although there are obviously exceptions including those running FireOS with a custom recovery on a locked (but still vulnerable) device. Whether the stock recovery contents are actually used or something else happens is unknown...at least to me. Symptom wise a borked recovery is almost always leads to boot issues.
draxie said:
BTW, is recovery _really_ checked/needed for FireOS to boot?
I suspect that flashify (or the OP) did more than just overwrite recovery,
which can be _really_bad_ if the bootloader is still locked, since the key
combo to enter fastboot doesn't work...
Click to expand...
Click to collapse
Seems the issue I'm experiencing
I have got another fire hdx 7.
How i can unlock bootloader? Where is guideline?
arshileus said:
I have got another fire hdx 7.
How i can unlock bootloader? Where is guideline?
Click to expand...
Click to collapse
Same thread as previously linked (here). It is NOT a step-by-step idiot proof guide. You will need to do some advance reading. Suggest digesting the OP then reviewing the last 2-3 months of posts to get a 'feel' for what is required and the questions you may have.
I have done this before on windows 10 . But i am on windows 7 now.
After i clicking on unlock.bat, device goes to fastboot mode. At this time i cant find "android" with warning sign in device manager. I have unrecognised usb device, so i cant set it to usb composite.
What to do? what i miss?
p.s when i am trying use google or amazon drivers set up after fastboot manually selecting from device manager, it says: incompatible.
arshileus said:
I have done this before on windows 10 . But i am on windows 7 now.
After i clicking on unlock.bat, device goes to fastboot mode. At this time i cant find "android" with warning sign in device manager. I have unrecognised usb device, so i cant set it to usb composite.
What to do? what i miss?
p.s when i am trying use google or amazon drivers set up after fastboot manually selecting from device manager, it says: incompatible.
Click to expand...
Click to collapse
Can you help me?
arshileus said:
Can you help me?
Click to expand...
Click to collapse
Could be a borked device, unstable usb interface (either device) or bad cable. Work backwards by trying different cables, different ports on the host (avoid USB3 and hubs) and different hosts. If results are the same you may have a bad device. Good luck.